Software Clean Install of Orbiter, first CTD after adding Textures

[LTrotsky]

Wondering if there is any solution or if CTDs are just part of the deal.

Clean install of orbiter.

Added texture packs from Orbit Hangar as follows :

csphere100830
Earth091124_11_14
Mars091218_11
Moon090730_L11
Planets_and_moons

Here is the cfg file

; === ORBITER Master Configuration File ===
EchoAllParams = FALSE
LPadRect = 146 35 1423 702

; === Logical parameters ===
DamageModel = 1
InstrumentUpdateInterval = 0.1

; === Visual parameters ===
EnableCloudShadows = TRUE
EnableSpecularRipples = TRUE
EnableLocalLights = TRUE
NightlightBrightness = 0.2
CSphereBgImage = Hydrogen alpha (WHAM)
CSphereBgPath = csphere\h_alpha
CSphereBgIntensity = 0.2

; === Physics engine ===
DistributedVesselMass = TRUE
NonsphericalGravitySources = TRUE
RadiationPressure = TRUE

; === Camera parameters ===
HUDColIdx = 1

; === Device settings ===
DeviceIndex = 4
ModeIndex = 17
Fullscreen = TRUE

; === Active plugin list ===
ACTIVE_MODULES
  ScnEditor
  ScriptMFD
  LuaConsole
  LuaMFD
END_MODULES

Here is the install check log file

Orbiter installation verification.

w tests to verify a valid
Orbiter installation. Normally, this test needs to be executed
only once after installation. To run it again, execute the
'testinstall' utility in the Install subdirectory.
-----------------------------------------------------
Test 1: Directory structure
	Orbiter root directory:	C:\ProgramsT\Orbiter2010
	Folder Config	 found.
	Folder Meshes	 found.
	Folder Textures	 found.
	Folder Scenarios	 found.
	Folder Doc	 found.
	Folder Script	 found.
	Folder Modules	 found.
	Folder Flights	 found.
	Folder Html	 found.
	Folder Install	 found.
-----------------------------------------------------
Test 2: C++ runtime libraries
	Runtime libraries ok.
-----------------------------------------------------
Test 3: Checking DirectX
	Scanning dxdiag output:


Processor: AMD A8-4500M APU with Radeon(tm) HD Graphics    (4 CPUs), ~1.9GHz
Memory: 6144MB RAM
DirectX Version: DirectX 11
Card name: AMD Radeon HD 7640G
For full DirectX diagnostics, see file dxdiag.log.
-----------------------------------------------------
Moving Orbiter executable into place.
-----------------------------------------------------
Orbiter installation verification complete.
No problems found.

Here is the log file

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 5.39914e-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]

The test was a DG Earth -Eject-Lunar Transit-BB Landing- Eject- Earth Return- Deorbit- Landing cycle. I find I can do this, takes a while, and puts everything through the paces (including me).

CTD occurred during de-orbit. Attempted to use the LUA Console. Then Selected a different MFD, Attitude RCS. When I clicked on a button in the AttitudeMFD = CTD.

Operating system = Windows7 Home Premium
AMD A8-4500m APU with Radeon 7640g HD Graphics 1900Mhz, 4 Cores

6.0GB Physical Memory

Video : AMD Radeon 7640G 512mb DDR3 655MHz, memory bandwidth 25.6gb
Sound : AMD HD Audio (7.12.0.7705) Realtek HD Audio (6.0.1.6577) 4.54mb

Any ideas welcome.

 

[dgatsoulis]

Here is the log file

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 5.39914e-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]

Those are all the contents of the log file? Seems a bit small.

When I clicked on a button in the AttitudeMFD = CTD.

How can it be a "clean" install when you have AttitudeMFD? That's not included in the default Orbiter installation.

If you do have AttitudeMFD, it seems that it is not compatible with Orbiter 2010.

**** Orbiter.log
Build Aug 30 2010 [v.100830]

From the [ame="http://orbithangar.com/searchid.php?ID=3165"]AttitudeMFD link[/ame]
Orbiter Version: 060929

It should work ok with Orbiter 2006P1

 

[LTrotsky]

That is the log file. Nothing was left out.

The "Attitude RCS" is part of the default Orbiter install. There are no add-on MFDs in this install. What I find a bit strange is the default Orbiter install also has an MFD called "test1".

 

[dgatsoulis]

What I find a bit strange is the default Orbiter install also has an MFD called "test1".

IIRC the test1 MFD is a showcase for an MFD created by a lua script instead of a .dll file

When I clicked on a button in the AttitudeMFD

When I read that you clicked on AttitudeMFD I thought that you had the MFD of the link in my previous post, not the Attitude RCS-MFD.
It would also be a resonable explanation for the CTD, while now I can't think of any.

 

[LTrotsky]

right sorry about the mis-label.

---------- Post added at 02:29 AM ---------- Previous post was at 12:35 AM ----------

OK Just ran the test again. Same result. Beginning the re-entry interface I click the Attitude RCS button, and a CTD results. (that is, in the MFD selection panel, I attempt to open the Attitude RCS mfd, an hourglass comes up, and a CTD is reported in about 3 seconds).

Here is the log file from that session. I did not re-start the Orbiter Launchpad, and the datetime on the file is correct.

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 5.39914e-007 sec
Found 0 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (AMD Radeon HD 7640G)
==> Direct3D T&L HAL (AMD Radeon HD 7640G)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module ScriptMFD.dll ......... [Build 100830, API 100830]
Module LuaConsole.dll ........ [Build 100830, API 100830]
Module LuaMFD.dll ............ [Build 100830, API 100830]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1600 x 900 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: 8
Loading 15382 records from star database
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 DeltaGlider.dll ....... [Build 100830, API 100830]
Module LuaInline.dll ......... [Build 100830, API 100830]
Module HST.dll ............... [Build 100830, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state

Hmmm. Would an off-version texture file cause something like this?

 

[Quick_Nick]

Can you post a scenario file from just before you would hit the button and crash? Then someone can try to reproduce this.

 

[LTrotsky]

Yes in fact I managed to remember to do a quicksave. This is close enough to the re-entry interface (a few minutes).

 

[LTrotsky]

I ran the save and the problem did not repeat itself.

To recap :

Three tests were performed.

Test 1. Started at BB, performed Lunar Eject, Earth Return, and attempted de-orbit and re-entry. Selecting Attitude RCS, after the simulation had run without interruption during the described sequence, resulted in a CTD.

Test 2. Same as above.

Test 3. The scn file in the above post was captured during the beginning of the de-orbit and re-entry sequence. The scn file above therefore does not include a lunar eject or earth return sequence. Launched the scn file (altitude approx 128km, location approx 200km se of Cape Canaveral, orbit trajectory will intersect KSC on this orbit. This is the beginning of the de-orbit sequence, with re-entry scheduled to begin in about 1 hour. At the beginning of the scenario (which, to repeat, is a save from the flight in Test 2), select Attitude RCS (exactly as it was selected during Test 2) does NOT result in a CTD.

This suggests that the CTD may occur only after a number of memory operations / swaps, after the simulation has run for a while. Is it possible that with the additional textures there have been a great many video memory operations or swaps, which creates the potential of a CTD because there is some tiny thing that is not quite kosher in an operation that has been done thousands of times during the running of the simulation? Dunno.

Incidentally, I cant seem to use Attitude RCS the right way or something. All I want to do is have the craft pitch up at 20 to 40 degrees during the re-entry. It goes all over the place, and I end up having to do the re-entry on full manual - which without a joystick is a great challenge. Not that it matters for de-bugging, but I got this process down to the point where I usually arrive over the target with sufficient remaining velocity and altitude to land safely. Sometimes I have to turn around though.

 

[LTrotsky]

Additional Testing on System Settings

Perhaps not many people run Orbiter 2010 on a laptop.

I've noticed that when I task out from a full-screen session (perhaps to capture a screenshot) when I task back into Orbiter, some visual elements are missing or corrupted. These usually redraw, but the vessel name information on the vessel (like, DG-1 or whatever) after this, is always a black box and never redraws in the session.

This suggests that some laptops may have some difficulty running Orbiter in full screen - that is, corrupted video information may create a CTD at some point during the session.

What I am trying now is running in a windowed session. When I do this, the described corruption never occurs. I will report if the CTD issue happens with less frequency as a result.

 

[BruceJohnJennerLawso]

How fast are you trying to run the simulation? Orbiter should usually be almost crash free at 1000x time acceleration or less, but trying to do long periods of maximum time warp is usually not a good idea, especially when near planets, moons, and that sort of thing. Its probably caused by huge loading spikes when doing a close flyby of a planet that would normally take several hours, but in this case the computer is being asked to retrieve all of the texture files for it in milliseconds.

Just a note, I also have noticed the full screen minimization issues, which also wreak havoc with Orulex amongst other things. I'm pretty sure that its a general Orbiter quirk, not a laptop only thing.

 

[LTrotsky]

Generally I think this is it.

The crashes of note (the ones that happen after doing a mission involving some planning and work) happened during time accel and recordation of a mission (creating a playback file). The playback files of these crashes involve sim sessions that had been running for at least several hours, and at least 1 million or possibly several million sim seconds.

Furthermore, playing with the video card settings revealed that on some settings in combination with the video options in Orbiter resulted in some instability.

At present I am running the sim in a windowed session, which does not generate any image corruption on a task out, and have tweaked the video settings on the graphics card. Orbiter, ironically, seems more stable if you actually jack up the settings (set anti-aliasing to max for example). Also, the screenshots look much more realistic if not beautiful (added the max resolution textures for most bodies). Yesterday and today ran a tran-mars mission and had only 1 CTD for the whole trip. And yes, I made it. Nice 75km orbit too. :woohoo: