Game crashing every 3-4 races
Every 3 or 4 races the game is crashing and throwing me at the home screen displaying the following message"Unfortunately,No Limits Has stopped."Below that message i have 2 options:REPORT and OK.I ha...
Forum Discussion
@batstroke13 and @Druffi551 Does your phones meet the minimum system requirements?
Link: [READ FIRST]Basic Troubleshooting and Support Information
Yes, they should. The galaxy s6 is samsungs newest smartphone or so called "flag ship".
Well. I checked the minimum requirements in detail, since galaxy s6 users all seem to have problems with crashes. The s6 matches everything with ease. The only thing that might cause a problem is the GPU.
The minimum requirement statement for the GPU is not a 100% clear to me. They mention 3 GPU's and state that as minimum requirement. Does that mean, that only those 3 GPU series are supposed to be supported? If so, please add the mali series to your supported GPU's since samsung uses it in countless smartphones.
I have Adreno and it crashes and runs very slow. So no. Your GPU is not a problem
- I would die from laughing if my s6 wasn't a supported device.The devs must look into that matter ASAP.It's so annoying.
The game is just buggy as hell.
Firemonkeys' claims that the problem has something to do with minimum requirements. Nope. People with iPhone 6s, iPad Pro, Galaxy 6 Edge+, and other such devices crash every 3-4 races. Maybe low-end devices that barely meet the requirements crash even more often, but upgrading to a new device isn't going to make the crashes every 3-4 races go away.
Firemonkeys also claims that the problem is other apps using up your memory. Looking at the crash reports, yeah, sometimes they are out-of-memory crashes--but it has nothing to do with other apps using up your memory. I tried everything I could when the game started crashing regularly after the 1.1 update. Reboot your phone, don't launch anything else, kill the apps that the OS auto-launches, start the game, and it'll still usually crash around 4 races in.
Clearly, the problem is a new bug they added in the 1.1 update, not anything every single one of their users are all doing wrong.
Featured Places
