Thanks. It took a while to track down.
You’re right that this is part of a larger, systemic problem. To debug this I used a monitoring tool (procmon) that shows what is going on within a running process (file access, library calls, etc.). Well, it’s not pretty (and, to be fair, for Windows programs (I include Xbox in that, same codebase after all), it never is).
I would never have expended the effort if it were not for the fact than, when it runs error-free, this sim is glorious. The in-flight experience, and the install/menu environment are different beasts.
It’s like Mr Hyde is bringing you the good medicine from Dr Jekyll, after ****ing in it.
It took me a week to install on release because of installer bugs (needed to throttle internet speed).
And numerous subsequent CTD issues. And hard crashes causing a reboot. The latter due, it turns out, to a failing power supply.
I see you’ve had a similar problem. I know nothing of Xbox - is there no way to access the filesystem directly?
1 Like