Hi All,
Please forgive me for not addressing this sooner. If this was actually one specific bug this would've been fixed a long time ago. Issue is that the -2005270523 bug is very meaningless. It basically means "somewhere in the program, in the last few seconds, something made DirectX give up." We've seen it happen (and fixed it), in bugs with our stereo-rendering system. We've seen it happen with buggy NVIDIA drivers (and seen those cases fixed with updates). It can happen because a different add-on does something wrong (and FlyInside catches the error), and it can happen because we do something wrong which messes up an add-on's behavior. We've had some users run into this due to a damaged Oculus HDMI cable (multiple users over time). That's a long-winded way of saying, that despite all of you seeing the same error message, everyone is quite possibly experiencing a different bug or underlying cause.
If you're interested:
0. Make sure you're up-to-date on drivers, that your PC is stable in general, try turning down any overclocks you aren't 100% confident in.
1. Try disabling add-ons. If the error goes away, shoot me an e-mail (
dan@flyinside-fsx.com) letting me know which add-on is related. We can dig in and see if it's fixable.
2. Make a backup of your settings. Try turning down settings, deleting the settings file to get defaults, or simply changing them. If that makes a difference please send me your original Prepar3D.cfg so I can take a look and see if there's some settings combination we aren't compatible with.
3. If you are experiencing these crashes with default settings and no add-ons, please contact me. That's strange but we'll do some deep/detailed debugging with you to try to hunt it down.
Thanks,
Dan