Thanks !
I tried the 0.2.2 on my Orbiter-2010 setup, but got nearly the same...CTD when loading the provided "ready-for-take-off or Cold+Dark" scenario.
I tried:
-disabled all other third-party modules, except Orbiter-Sound and SCN-edit
-used D3D9 R15 in full-screen
=Orbiter hangs and the onyl way to solve this was a complete reboot of my system.
The last message seen on the screen: loading "Sr71rBody.dds"
After reboot:
-tried the DX7 inline-client in window-mode
=CTD like in V0.2.3
-tried the D3D9 client in window-mode, too
=same, CTD (so no hang).
There are no related messages in orbiter.log.
Question was the previous 0.2.2 not the build for Orbiter-2015-beta ?
Maybe it's better to test with 0.2.1 in Orbiter-2010.
I waill answer myself
>Question was the previous 0.2.2 not the build for Orbiter-2015-beta ?
Nope, because the Orbiter-2015-Beta-Build was called "0.3.1".
---------- Post added at 06:28 PM ---------- Previous post was at 05:24 PM ----------
Did some more testing:
On my notebook (Windows7) I have an exact copy of my existing Orbter-2010-setup, from my Desktop (WinXP).
However, I tested the 0.2.2 vesrion on my notebook:
-loading went fine (Cold+Dark), no crashes or hangs.
Even the fact, that I have not disabaled all other third-party modules.
It just works.
The main difference between both systems is the graphics-card.
On my crashing-Dekstop I use NVIDIA, the notebook uses an ATI-card.
However, somehow this vessel does not like my Desktop.
On my notebook, I am currently flying around KSC to test the AP.
I like the pre-start-up-cockpit procedures.
Also the AP is working nice.
I.e. when switching-off heading, the rudder is set to neutral, so you can still fly the plane manually (i.e. UAP or the DG-AP set the rudder at a random-state when switching AP off).
Maybe you should create an universal-atmospheric-autopilot-MFD using your nice working AP-code from the SR71. (?)
Last test:
I used the latest version on my notbook, too.
Here all went fine, too.
But no-go on my desktop, where I don't have any problems with other Orbiter addons.
Maybe a missing non-Win7-dll ?