|
|
Post by Brutus Aurelius on Oct 20, 2015 10:56:05 GMT -5
The walking SFX just continues to loop after a Templar stops moving. So far, muting both Music and SFX fails to stop it, as it keeps playing. Same for exiting the app. Force close seems to fix it tho, but it will just keep looping.
Kindle Fire/Android bug
|
|
|
|
Post by ntsheep on Oct 20, 2015 13:41:58 GMT -5
I have been having this problem too. Thought is was something with my tablet so didn't mention it. Was trying to figure it out more before I said something. It happened a lot with the previous 1.1.7 version. Has happened about two times today while testing the new version but hasn't repeated since.
Toshiba ATC-7 tablet
Android 4.4.2
|
|
|
|
Post by Cory Trese on Oct 20, 2015 13:52:51 GMT -5
Sorry folks. We'll contact Amazon and Toshiba to see if they have any work around.
|
|
|
|
Post by ntsheep on Oct 20, 2015 15:12:26 GMT -5
I'm sorry I can't give you more good info. Not sure what's causing it. Especially when it only happens some of the time. For me it usually stops it seems after I attack a xeno with any ranged weapons. After that, I can play and there's no more looping sound.
|
|
|
|
Post by Cory Trese on Oct 20, 2015 15:35:14 GMT -5
I'm sorry I can't give you more good info. Not sure what's causing it. Especially when it only happens some of the time. For me it usually stops it seems after I attack a xeno with any ranged weapons. After that, I can play and there's no more looping sound. Thanks for the update. If playing the attack sound really stops the loop, then it is definitely a hardware issue with the sound system on that Android. Amazon already closed my ticket -- no workarounds / no support for that device. Unfortunate. Hopefully not too many people have that issue during the mobile launch. |
|
|
|
Post by Cory Trese on Oct 21, 2015 0:03:51 GMT -5
Isolated the hardware bug, wrote a work around for it.
Another secret technology of the Trese Brothers ... labeled "Android OS SFX Bug Work Around #7"
Sorry for the annoying noises, next update will fix it.
|
|
|
|
Post by ntsheep on Oct 21, 2015 0:10:05 GMT -5
Damn your good. I figured we never would have found out what was causing it if it was a specific device bug. Not unless I took apart my tablet and attack it with a logic probe.
|
|
|
|
Post by Cory Trese on Oct 21, 2015 0:18:09 GMT -5
Suffer no bugs to live. The report got us looking.
I also have a lot of devices to test with.
Without the report, I doubt I would have found it.
|
|
