Car Control Issues Listing

I am experiencing random skids with the Valhalla. Here's a couple of them I recorded:
https://www.youtube.com/watch?v=geifs6cEHYU

Added to the list, I'll send it to CC too

.
At this point, it would be easier to make a list of cars that don't skid. 😳

.
At this point, it would be easier to make a list of cars that don't skid. 😳

lol - nice one!

As you probably know by now, the guys at GL are doing their best to get rid of us old riders that do not spend money. The best way, of course, is to make us mad skidding around with our best cars.
Sad but true. These problems are NOT a bug. Thanks a lot.

As you probably know by now, the guys at GL are doing their best to get rid of us old riders that do not spend money. The best way, of course, is to make us mad skidding around with our best cars.
Sad but true. These problems are NOT a bug. Thanks a lot.

A possible, even plausible explanation. But if this is intentional why inflict new cars like the Valhalla?

This is an endemic problem with game physics. More noticeable in the faster cars.

If you run a fresh, test account with a speed h@ck the Dart miss/behaves the same way at >400Km/h.

Harry, I did believe that this was a problem for us non-paying oldies. If not, it's even worse. I've been in the computer business since the early nineties, so rest assured that I can spot a bug over an intentional f-ckup any day. It's not physics, it's programming. If you do not want cars to skid, then you do not add that to the code. Simple, isn't it?

Here is the McLaren 650S GT3 showing the issue in Mount Teide...

https://youtu.be/moKf3P0TXJU

✌️😷

Harry, I did believe that this was a problem for us non-paying oldies. If not, it's even worse. I've been in the computer business since the early nineties, so rest assured that I can spot a bug over an intentional f-ckup any day. It's not physics, it's programming. If you do not want cars to skid, then you do not add that to the code. Simple, isn't it?

Well I've been a programmer since the late 70's (amongst many other things). The University where I worked has a full version of A8's code via a third party. Messy code.

Every handling issue is down to someone p...ing around with the programming that drives the basic game physics engine. Most likely accidentally.

I'd go for ineptitude rather than malicious intent.

I’m with @Harry on this one. Somebody, made a change somewhere to the physics and failed to account for all the dependencies.

What scares me is that @Andreea said they were trying to debug and fix this one car at a time. I think this approach will fail. The issue is not car specific. It is something more basic.

I’m also an old time programmer. Started late 70’s. Worked on many complex enterprise coding projects. Stuff that makes A8 look trivial. Stuff that had multiple companies involved. Both proprietary and open source code. And code that was developed and supported for decades. What happens is that the code becomes more and more difficult to modify because the complexity grows and the knowledge by the current developers of the dependencies within the code shrinks as the employees invariably move on and are replaced by newer employees. Often these transitions are accompanied by inadequate knowledge transfer and nothing can replace experience. So, somebody comes in and needs to make what may seem like a simple fix or to implement a new feature, and they simply don’t understand all the dependencies and they break something.

It is also clear that A8 does not have sufficient regression testing. This problem is easily recreated and would have been caught by proper test cases immediately.

✌️😷

Wow, nice to hear you guys with actual experience! I haven't written code (basic )since 1984, so I am way behind you. But, how come only one car skids at only some spots? If it was unintentional, then any car would skid at any (random) spot? Or?