The only thing unusual about the flight was that I had had some VAS warnings about 45 minutes before I clicked the middle panel brightness knob to the left of the captain.  Immediate CTD.  My VAS at the time of the CTD was 3.4GB.

 

It's fine...I wanted to go back and try the departure again.  Just thought you'd want to know.

 

 

Just thought you'd want to know.

 

If you're looking to report a bug, or you believe you've found one, it's best to go straight to the queue.

 

If you had been getting the VAS warning, though, sounds more like an OOM. You can check by viewing the crash log. I'm betting you'll either see an OOM, or a dll error like msvcr or ntdll.

 

 

If you're looking to report a bug, or you believe you've found one, it's best to go straight to the queue.

If you had been getting the VAS warning, though, sounds more like an OOM. You can check by viewing the crash log. I'm betting you'll either see an OOM, or a dll error like msvcr or ntdll.

 

It was probably a fluke but if it happens again I'll hunt the queue down.  Wasn't an OOM.

Hi Gregg,

 

Just wondering whether you inadvertently pressed a key a second time before the software had time to process the previous command.

 

I have occasions when I suspect that FSUIPC is creating an autosave file when I press a key, and then, in haste, I re-press it causing a crash.

 

 

I have occasions when I suspect that FSUIPC is creating an autosave file when I press a key, and then, in haste, I re-press it causing a crash.

 

While I don't use FSUIPC autosave, it's possible that it was still rendering a previous click on the switch next to it.  I'll take them a bit more slowly.  No rush to adjusting lights when you're up at cruise.