oldman65 wrote:nks71 wrote:I tried the X2 in gauntlet, just to verify that not only it skids (with nitro or not), but also drives in a weird new manner that created more handling issues than what it solved.
Another piece of excellence from GL...
MP-31 is also semi-autonomous and decides on its own!
Yep, basic physics are bonked and they are trying to paper over it by fiddling with the cars one by one. It's not working. For some reason, they don't want to or can't address the real issue.
My hypothesis is that they are using common code with A9 and it isn't compatible with all the A8 cars. Esp, not the F1 cars.
I've no proof of that, but my gut says that's the most likely reason. And it is definitely a strategy software companies use to save time and development costs.
Regardless of the cause, handling is effectively still broken. I'm hoping they continue to work on it. Maybe, someday, they will get the right.
I did a gauntlet experiment with the X2 in the second position on Classified.
I ran one race, and the X2 glitched in the curve after the wooden track and jump-off - straight into the side walls.
I rebooted the app, ran another challenge that I won, and then ran again, against the same Classified challenge. Exact same line - no X2 glitch, whatsoever. I won.
So, other than frustrating the guy who I challenged again, it shows that there is some variability to the glitching. It appears to get worse after the app has run for a while or right after first start-up. I also have seen the same in TLEs and MPs. Sometimes, after first starting, your cars glitch all over. Then, after a reboot, everything is smooth (well, within the normal "glitchiness")
Yes, it is anecdotal, but there seems to be something to this... it maybe just a dynamic memory management issue, particularly related to the state of server synch and related device performance issues.
Lesson learned.. start app, run a race, restart app, run gauntlet after you confirmed everything is fine. Don't run ads and other memory and GPU hogs, prior.