Trainguy
Trumpeter
Hi everyone!
I've been around for a while but only recently got back into Orbiter properly again.
Anyway, I've slowly been building up an Orbiter installation including various addons, texture replacements etc. I installed the DG-IV-3 to play around with it and came accross a problem.
When I attempt to decompress the airlock, the pressure drops to exactly 10% before the sim freezes and displays a dialogue box. This is what I mean:
Pressing 'ignore' immediately terminates the programme and any other option displays the windows 'Orbiter.exe is not responding' dialogue box before self-terminating a few seconds later.
I was able to replicate the problem exactly on a clean install of orbiter with only D3D9 Client R15 (to my knowledge the latest stable version) OrbiterSound 4.0 and the DG-IV-3 (both the latest versions from DanSteph's website) installed in that order over Orbiter 2010-P1. I created the symbolic links D3D9 asks for and enabled D3D9 client and OrbiterSound in the menu but otherwise made no changes from the default installation (or in the config programmes of the DG-IV or OrbiterSound).
I tested the decompression in various situations, including but not limited to Earth Orbit (both launching from Earth and undocking from the ISS) Mars Orbit and the Martian Surface, with the above result every time. The setup of the rest of the DG-IV (skin choice, power settings, door status etc) doesn't have any affect on the outcome. So far as I can tell, Orbiter and the DG-IV otherwise work perfectly fine.
However, the problem occurs only when I use the D3D9 client - performing exactly the same steps I did in the scenario the above image is from with the built in D3D7 client (load, undock the ISS, close the nosecone then decompress the airlock chamber) leads to the airlock decompressing fine and I can EVA normally.
Does anyone have any idea what's going on?
Any help/thoughts/suggestions would be much appreciated.
Many thanks for your help in advance
Trainguy
PS I will attempt to respond to any replies promptly but as I'm on a summer placement at the Rutherford Appleton Laboratory at the moment (hence the signature) I may not be able to.
PPS Some technical information (all from testring clean install):
The dialogue box which pops up is exactly the same every time, so I've only included one example.
Orbiter log from the above run (the last few lines seem unusual?):
Computer (actually 3 year old laptop which still runs perfectly well) specs: Windows 7 64bit, Intel i5 2450-M (2.5GHz), 8GB RAM, Intel HD Graphics built in chip. Included in case they're relevant.
I'm fairly sure I have the latest versions of DirectX, C++ redistributable files etc but I haven't explicitly checked for a couple of months.
I've no idea if Orbiter.cfg is relevant (as I said - I didn't make any changes other than those detailed above) but here it is anyway in case it helps:
I hope I've provided enough information - I'm aware it makes for a long post so if you've read this far - thank you very much!
I've been around for a while but only recently got back into Orbiter properly again.
Anyway, I've slowly been building up an Orbiter installation including various addons, texture replacements etc. I installed the DG-IV-3 to play around with it and came accross a problem.
When I attempt to decompress the airlock, the pressure drops to exactly 10% before the sim freezes and displays a dialogue box. This is what I mean:
Pressing 'ignore' immediately terminates the programme and any other option displays the windows 'Orbiter.exe is not responding' dialogue box before self-terminating a few seconds later.
I was able to replicate the problem exactly on a clean install of orbiter with only D3D9 Client R15 (to my knowledge the latest stable version) OrbiterSound 4.0 and the DG-IV-3 (both the latest versions from DanSteph's website) installed in that order over Orbiter 2010-P1. I created the symbolic links D3D9 asks for and enabled D3D9 client and OrbiterSound in the menu but otherwise made no changes from the default installation (or in the config programmes of the DG-IV or OrbiterSound).
I tested the decompression in various situations, including but not limited to Earth Orbit (both launching from Earth and undocking from the ISS) Mars Orbit and the Martian Surface, with the above result every time. The setup of the rest of the DG-IV (skin choice, power settings, door status etc) doesn't have any affect on the outcome. So far as I can tell, Orbiter and the DG-IV otherwise work perfectly fine.
However, the problem occurs only when I use the D3D9 client - performing exactly the same steps I did in the scenario the above image is from with the built in D3D7 client (load, undock the ISS, close the nosecone then decompress the airlock chamber) leads to the airlock decompressing fine and I can EVA normally.
Does anyone have any idea what's going on?
Any help/thoughts/suggestions would be much appreciated.
Many thanks for your help in advance
Trainguy
PS I will attempt to respond to any replies promptly but as I'm on a summer placement at the Rutherford Appleton Laboratory at the moment (hence the signature) I may not be able to.
PPS Some technical information (all from testring clean install):
The dialogue box which pops up is exactly the same every time, so I've only included one example.
Orbiter log from the above run (the last few lines seem unusual?):
Code:
**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 4.10516e-007 sec
Found 0 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9Client.dll ........ [Build 150111, API 100830]
Module OrbiterSound.dll ...... [Build 121120, API 100830]
**** Creating simulation session
D3D9Client: [DirectX 9 Initialized]
D3D9Client: Sytem has XNA math support
D3D9Client: [3DDevice Initialized]
D3D9Client: [Loading Stars]
D3D9Client: [Loading Constellations]
D3D9Client: [D3D9Client Initialized]
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module DeltaGliderIV.dll ..... [Build 140107, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
D3D9Client: [Scene Initialized]
UpdateSurface Blitting Failed 0x3B50998 (clbkCreateSurface) -> 0x3B53BE8 (clbkCreateSurface)
D3D9ClientSurface::CopyRect() Failed
I'm fairly sure I have the latest versions of DirectX, C++ redistributable files etc but I haven't explicitly checked for a couple of months.
I've no idea if Orbiter.cfg is relevant (as I said - I didn't make any changes other than those detailed above) but here it is anyway in case it helps:
Code:
; === ORBITER Master Configuration File ===
EchoAllParams = FALSE
LPadRect = 335 55 885 628
; === Device settings ===
DeviceIndex = 2
ModeIndex = 6
; === Active plugin list ===
ACTIVE_MODULES
OrbiterSound
END_MODULES