Speak about anything related to Asphalt 8!
no avatar

nks71

Veteran

Windows Phone
Posts

2874

Location

Greece

You're probably right @oldman65
no avatar

simplyjens

Senior Member

Windows PC
Posts

475

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.
User avatar

loriel_s

Senior Member

Apple TV (iOS)
Posts

176

Location

South Australia

I got the Centenario a couple of weeks ago. Everything going great and getting used to it...til This. Watch the end. Lucky I was recording at the time!

https://youtu.be/TA_1vJk_huU
User avatar

oldman65

Veteran

Apple (iOS)
Posts

4891

loriel_s wrote:
I got the Centenario a couple of weeks ago. Everything going great and getting used to it...til This. Watch the end. Lucky I was recording at the time!

https://youtu.be/TA_1vJk_huU

I feel your pain. At least you didn't die into a wall. That's what happens to me most times. Thx for posting.
Car I most want added to A8:
       1991 MAZDA 787B
Moving to new forum: https://asphalt8.freeforums.net/
User avatar

oldman65

Veteran

Apple (iOS)
Posts

4891

@simplyjens I can’t tell either, but restarting the app seems to help the game in general; so, you could be on to something. Next time I’m having a rash of the skids, I’ll give it a try...
Car I most want added to A8:
       1991 MAZDA 787B
Moving to new forum: https://asphalt8.freeforums.net/
User avatar

Harry K

Veteran

Windows Phone
Posts

4307

oldman65 wrote:
@simplyjens I can’t tell either, but restarting the app seems to help the game in general; so, you could be on to something. Next time I’m having a rash of the skids, I’ll give it a try...


The game defiantly has a memory dump/RAM flush issue, most obvious when they first (unsuccessfully) introduced quick reruns. When the random AI behaviour became an "intentional feature" because they couldn't get it back to normal.

Rebooting should not be necessary. Skidding is a core code error in the global physics. It should not be fixed one car at a time.
So long, and thanks for all the fish. New, independent A8 forum - https://asphalt8.freeforums.net/
User avatar

oldman65

Veteran

Apple (iOS)
Posts

4891

@Harry K, I agree on the core code error point. I hope that my latest hypothesis is wrong, but I fear that they have merged some of the A8 and A9 code and it has caused these issues. This would limit their ability to modify the base code. And would explain why they seem to be trying to patch the cars one-by-one. I fear there will never be a fix for this issue and that we will be left with a mixed batch of poorly handling cars subject to random glitches. 😞
Car I most want added to A8:
       1991 MAZDA 787B
Moving to new forum: https://asphalt8.freeforums.net/
no avatar

woopsynutts

Senior Member

Windows PC
Posts

499

while searching for something else in older posts I found this 3 years old thread :

viewtopic.php?f=1505&t=596780

nothing new here boys... 🤣
@bruhsonbro : "GLitchloft programmers are F,n mooks.  I literally mean f them mooks"
User avatar

oldman65

Veteran

Apple (iOS)
Posts

4891

woopsynutts wrote:
while searching for something else in older posts I found this 3 years old thread :

viewtopic.php?f=1505&t=596780

nothing new here boys... 🤣

 We remember that. It was fixed when they modified the physics in the Halloween/Transylvania update later that year.

 For whatever reason, they modified the physics again and this time they refuse to fix the base physics. Now they are trying, and mostly failing, to patch individual cars one-by-one.

 We can only guess why this continues to be an issue, but we are having to live with it again.

 If we could go back to that late 2018 code base, the cars would be rock solid. But that's not gonna happen...
Car I most want added to A8:
       1991 MAZDA 787B
Moving to new forum: https://asphalt8.freeforums.net/
no avatar

woopsynutts

Senior Member

Windows PC
Posts

499

early 2018 is when they activated their hard troll mode ON for many cars and global physics, yes
the MP4-25 and 31 where never that good with hadling before, just go search for their original dedicated Champ threads and see...
it just got very worse from there, and the X2 which appeared a few months later was a handling nighmare from it's original release
as you mention, the official "handling fix" which happened at the end of this year got things a lot better, too bad it was not to last !
and the reason why it's not fixed, a deliberate choice ? or incompetency from **** mookteam ? or both ?
I have my idea about this and don't expect anything to be changed soon....
@bruhsonbro : "GLitchloft programmers are F,n mooks.  I literally mean f them mooks"