Dr Merlin, my apologies. We do review crash reports but they aren't always comprehensive. Posting here is the fastest way to get help. Please shoot an e-mail to
dan@flyinside-fsx.com . I'm traveling at the moment, but can debug with you November 5th. I realize that's almost two weeks out, so if you'd rather just have a refund, you can e-mail me regarding that too.
DHR - Same goes for you, if you're interested I'll debug with you Nov 5th. To get your simulators working in the mean-time:
1. Remove "d3d11.dll" from your Prepar3D folder.
2. Remove "d3d9.dll" from your FSX folder.
If that doesn't do the trick, it's something odd with corrupted settings. You can clear all simulator settings and caches by clearing:
-C:\Users\YOUR_USER\AppData\Roaming\Lockheed Martin
-C:\Users\YOUR_USER\AppData\Local\Lockheed Martin
-C:\Users\YOUR_USER\AppData\Roaming\Microsoft\FSX
-C:\Users\YOUR_USER\AppData\Roaming\Microsoft\FSX-SE
-C:\Users\YOUR_USER\AppData\Local\Microsoft\FSX
-C:\Users\YOUR_USER\AppData\Local\Microsoft\FSX-SE
I will say, we develop our software in good faith, and test it across a variety of computers (and many beta testers) before releasing - specifically so things like this don't happen. Issues do slip through the cracks with new configurations and setups though. My sincere apologies for the issues you've both run into.
Thanks,
Dan