Thanks for everyone who has reported the death bug/loss of career bug. This is where the game suddenly announces that you are dead/lost your career/have a death timeout when you have just landed nicely or even just spawned in & out without doing anything.
If this happens to you, please type ZZZ into the chat window--this really helps me to track down the cause of the bug.
This has been a very, very hard bug to track down and fix because I can't replicate it at all and it seems to happen pretty infrequently and with no pattern I've been able to figure out. So typing in those XXXs into chat really will help.
It's happened to be twice recently and those have allowed me to make the most progress on fixing the problem, because I knew exactly when it happened and what I was doing, and was therefore able to narrow things down quite a bit by looking at the server logs.
I've put in a lot more debug messages into the log to narrow down exactly where it's happening in the code (one of the difficulties in bug fixing with CloD is you can't run it in a dev environment or do real debugging, because it's running within the game, which is proprietary etc. So we're back to 1980s-era debugging practices--luckily the ones I'm most familiar with anyway!)
FYI the possible causes I previous identified either were not the cause or at least, not the full cause. They may have caused some incidences of the bug, but certainly not all.
What I have it narrowed down to now is, somehow the server thinks you are either going a fast speed, like over 130mph and/or at a high AGL or 20 feet off the ground, and/or a high vertical speed, like over 2000 fpm/12mps. Even though in fact you are sitting on the ground at full stop.
So I'm not sure if this is a game bug or something new in a recent CloD version or maybe a transient reading that happens for a millisecond when you jump out of an aircraft and ai takes over, or just what.
But regardless it's bizarre and I haven't really "caught it in the act" yet to fully understand what is going on at that moment. I do have it narrowed down to a couple dozen lines of code where the problem is definitely happening, so that is helpful.
Also I have debug info being recorded through those lines of code now, so I can pretty much tell what's going on line by line (though, not within the CLoD code that is probably the ultimate cause of the problem. We'll have to work around, not fix, whatever is going on there.)
FYI!
Bookmarks