99 replies to this topic

[firepip]

I was originally testing my game on a T-Mobile HTC G2 with Android 2.3.4, it works fine.

I just tested my game on a T-Mobile Samsung Galaxy S2, with Android 4.0.3, and it works fine.

This is a game I just compiled using the latest version of Studio(at the time of this post 1.0.327).

My game is running at 60 for a room speed. Why don't you guys that are having a problem try making a game at 60 room speed, just a small test case, and see if it runs the same speed on windows as on your problem devices. Then, assuming it does, change the room speed to 30, and see if it still runs the same speed. If everything is working correctly, it should run at half the speed since you changed nothing but the room speed, but if it still runs at the same speed, then we know that GM is forcing the room speed to 60, which is what I think is happening.

If my theory is correct, a possible workaround, if you don't have too many objects, could be to simply adjust all of the movement to work with a room speed of 60 instead of 30.

Yea but that would lack on some phones

[wagdog]

I would not recommend coding around this bug. Doing so only opens you up to introduce further bugs in your code.

Hopefully yoyo will fix it soon.

[kburkhart84]

I'm not saying to code around it as a permanent fix, but if it is simple to do, and lets you release your app in working condition, then why not. It isn't any different than other bugs we've had to work around in the past. Also, if the game has more than a few moving objects, than it probably is too much work to do so. Also, until someone with a device that does this bug tries my test, we don't know for sure if it would work anyway. Both of my test devices work fine with my game, so I can't really test this bug.

[WWAZman]

I'm not saying to code around it as a permanent fix, but if it is simple to do, and lets you release your app in working condition, then why not. It isn't any different than other bugs we've had to work around in the past. Also, if the game has more than a few moving objects, than it probably is too much work to do so. Also, until someone with a device that does this bug tries my test, we don't know for sure if it would work anyway. Both of my test devices work fine with my game, so I can't really test this bug.

I'm not going to code my game around a bug that desperately needs to be fixed, just to undo that workaround when it does get fixed. One of my games has 50 objects onscreen. Not doing that.

If anyone needs 305 pm me.

[Robert3DG+]

Mike responded back:

we've figured out what's wrong, and will try to get a fix out once we're back.

Just hang in there a bit longer.

[kburkhart84]

I'm not saying to code around it as a permanent fix, but if it is simple to do, and lets you release your app in working condition, then why not. It isn't any different than other bugs we've had to work around in the past. Also, if the game has more than a few moving objects, than it probably is too much work to do so. Also, until someone with a device that does this bug tries my test, we don't know for sure if it would work anyway. Both of my test devices work fine with my game, so I can't really test this bug.

I'm not going to code my game around a bug that desperately needs to be fixed, just to undo that workaround when it does get fixed. One of my games has 50 objects onscreen. Not doing that.

If anyone needs 305 pm me.

Of course i wouldnt recommend it
for you then.

[Mike.Dailly]

Sorry guys, we've obviously been busy in the run up to GDC Europe, and with being out there for a few days, have been out of the loop a bit.... we were insanely busy out there.

We know what the issue is, and will look to get a fix out in the next day of so. There are a couple of issue needing fixed, so it depends on how quick they ALL get done. I expect 2 days tops - baring disaster.

The issue was that Google changed something on the SDK, and we went with that change, but it turns out not all phones did it. There are so many Android phones/devices that we simply can not test on them all, so this got through our limited testing. The fix for this is quite simple, so it'll be done tomorrow, and will go out next update as soon as the other things are fixed.

[WWAZman]

Thank you Mike.

[cotycrg]

Sorry guys, we've obviously been busy in the run up to GDC Europe, and with being out there for a few days, have been out of the loop a bit.... we were insanely busy out there.

We know what the issue is, and will look to get a fix out in the next day of so. There are a couple of issue needing fixed, so it depends on how quick they ALL get done. I expect 2 days tops - baring disaster.

The issue was that Google changed something on the SDK, and we went with that change, but it turns out not all phones did it. There are so many Android phones/devices that we simply can not test on them all, so this got through our limited testing. The fix for this is quite simple, so it'll be done tomorrow, and will go out next update as soon as the other things are fixed.

Our lord and savior Mike. Thanks, bro

[zinhzeiel]

Thx a lot!!

[Meetle]

Finally! Thank you guys :D

[dasrkrain]

That is some really good news!

[Mike.Dailly]

New version is now out - please go get it and give it a try!!!

[TheMightyAxle]

Cool ! All working here !

[filulilus]

Speed is back to normal!
But 3D rendering is still not working.

[laffertyrh]

Kindle Fire issues...
Creates APK. Installs fine on Kindle. When I go to launch the program it crashes. Sad face. Back to 305 I go.

[_169868]

UPDATED! I'm running it on a Kindle fire and have had no problems...

[laffertyrh]

UPDATED! I'm running it on a Kindle fire and have had no problems...

Hmmm... ok I will go check texture pages. Seems wierd that 305 works but 342 crashes.

[Manuel777]

Why has noone found this to be an excellent opportunity to test out delta time adjusting? Am I a weirdo??

WTF now I'll just make games at 99999 room speed!

[laffertyrh]

UPDATED! I'm running it on a Kindle fire and have had no problems...

Hmmm... ok I will go check texture pages. Seems wierd that 305 works but 342 crashes.

Yup texture size issue. Although the texture size worked in 305 it crashed the Kindle in 342. Lowering the texture size worked. Thanks!