Problem XR-2 and XR-5 quit working. HELP!!!

stevcast

Addon Developer
Addon Developer
Joined
Jun 14, 2008
Messages
160
Reaction score
0
Points
0
I have been working on Orbiter 2010 for the past three weeks, installing, testing and retesting addons and everything seemed to be going well untill yesterday when I decided to retest the XR-2 and XR-5. Now every scenario with these two ships gives me a CTD. I have tried reinstalling the ships, and also removing the most recent addons but nothing seems to work.
If anyone else has had this problem and can direct towards a solution I would greatly appreciate it!!!
My post CTD Orbiter log reads as follows:

Code:
**** Orbiter.log
Build Jun  6 2010 [v.100606]
Timer precision: 4e-008 sec
Found 1 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (NVIDIA GeForce 9100  )
==> Direct3D T&L HAL (NVIDIA GeForce 9100  )
Module AtlantisConfig.dll .... [Build 100606, API 100606]
Module AtmConfig.dll ......... [Build 100606, API 100606]
Module DGConfigurator.dll .... [Build 100606, API 100606]
Module EnergyConfigurator.dll  [Build ******, API 060425]
Module OrbiterSound.dll ...... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module ScnEditor.dll ......... [Build 100606, API 100606]
Module CustomMFD.dll ......... [Build 100606, API 100606]
Module ScreenCapture.dll ..... [Build ******, API 060425]
Module MeshLand.dll .......... [Build ******, API 060425]
**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1024 x 768 x 32
Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
Loading 8816 records from star database
Joystick throttle: Z-AXIS
Joystick throttle control detected
Module Sun.dll ............... [Build 100215, API 100212]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100215, API 100212]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100215, API 100212]
Module VenusAtm2006.dll ...... [Build 100606, API 100606]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100215, API 100212]
Module EarthAtmJ71G.dll ...... [Build 100606, API 100606]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
---------------------------------------------------------------
>>> ERROR: Missing texture: AWIDE.dds
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 750]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Missing texture: AWIDE.dds
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 750]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Missing texture: 08.dds
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 750]
---------------------------------------------------------------
Module Moon.dll .............. [Build 100217, API 100215]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100215, API 100212]
Module MarsAtm2006.dll ....... [Build 100606, API 100606]
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 100215, API 100212]
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]
ERROR in configuration file for Amalthea: Syntax error in SURFBASE list
ERROR in configuration file for Metis: Syntax error in SURFBASE list
ERROR in configuration file for Himalia: Syntax error in SURFBASE list
ERROR in configuration file for Pasiphae: Syntax error in SURFBASE list
ERROR in configuration file for Sinope: Syntax error in SURFBASE list
ERROR in configuration file for Lysithea: Syntax error in SURFBASE list
ERROR in configuration file for Ananke: Syntax error in SURFBASE list
ERROR in configuration file for Leda: Syntax error in SURFBASE list
ERROR in configuration file for Callirrhoe: Syntax error in SURFBASE list
ERROR in configuration file for Themisto: Syntax error in SURFBASE list
ERROR in configuration file for Megaclite: Syntax error in SURFBASE list
ERROR in configuration file for Taygete: Syntax error in SURFBASE list
ERROR in configuration file for Harpalyke: Syntax error in SURFBASE list
ERROR in configuration file for Kalyke: Syntax error in SURFBASE list
ERROR in configuration file for Iocaste: Syntax error in SURFBASE list
ERROR in configuration file for Isonoe: Syntax error in SURFBASE list
ERROR in configuration file for Praxidike: Syntax error in SURFBASE list
ERROR in configuration file for S2002-J1: Syntax error in SURFBASE list
ERROR in configuration file for S2000J11: Syntax error in SURFBASE list
ERROR in configuration file for S2001-J2: Syntax error in SURFBASE list
ERROR in configuration file for S2001-J3: Syntax error in SURFBASE list
ERROR in configuration file for S2001-J4: Syntax error in SURFBASE list
ERROR in configuration file for S2001-J5: Syntax error in SURFBASE list
ERROR in configuration file for S2001-J6: Syntax error in SURFBASE list
ERROR in configuration file for S2001-J7: Syntax error in SURFBASE list
ERROR in configuration file for S2001-J8: Syntax error in SURFBASE list
ERROR in configuration file for S2001-J9: Syntax error in SURFBASE list
ERROR in configuration file for S2001-J10: Syntax error in SURFBASE list
ERROR in configuration file for S2001-J11: Syntax error in SURFBASE list
Module Satsat.dll ............ [Build ******, API 061227]
Module Saturn.dll ............ [Build 100215, API 100212]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Enceladus.dll ......... [Build ******, API 050206]
SATSAT Enceladus: Terms 33
Module Iapetus.dll ........... [Build ******, API 050206]
SATSAT Iapetus: Terms 605
Module Janus.dll ............. [Build ******, API 060425]
Module Epimetheus.dll ........ [Build ******, API 060425]
Module Helene.dll ............ [Build ******, API 060425]
Module Telesto.dll ........... [Build ******, API 060425]
Module Calypso.dll ........... [Build ******, API 060425]
Module Polydeuces.dll ........ [Build ******, API 060425]
Module Uranus.dll ............ [Build 100215, API 100212]
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 100215, API 100212]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
ERROR in configuration file for Naiad: Syntax error in SURFBASE list
ERROR in configuration file for Thalassa: Syntax error in SURFBASE list
ERROR in configuration file for Larissa: Syntax error in SURFBASE list
ERROR in configuration file for N2011_N15: Syntax error in SURFBASE list
Finished initialising world
Module DeltaGliderXR1.dll .... [Build 100607, API 100606]
Module ShuttleA.dll .......... [Build 100606, API 100606]
Module ShuttlePB.dll ......... [Build 100606, API 100606]
Module DeltaGlider.dll ....... [Build 100606, API 100606]
Module LuaInline.dll ......... [Build 100606, API 100606]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiGetStationCount
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
ERROR: DDraw object is still referenced: 4
---------------------------------------------------------------
>>> ERROR: Destroy framework objects failed
>>> [OrbiterGraphics::Exit3DEnvironment | .\OGraphics.cpp | 1029]
---------------------------------------------------------------
**** Closing simulation session
**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1024 x 768 x 32
Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
Loading 8816 records from star database
Joystick throttle: Z-AXIS
Joystick throttle control detected
Module Sun.dll ............... [Build 100215, API 100212]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100215, API 100212]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100215, API 100212]
Module VenusAtm2006.dll ...... [Build 100606, API 100606]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100215, API 100212]
Module EarthAtmJ71G.dll ...... [Build 100606, API 100606]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
---------------------------------------------------------------
>>> ERROR: Missing texture: AWIDE.dds
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 750]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Missing texture: AWIDE.dds
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 750]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Missing texture: 08.dds
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 750]
---------------------------------------------------------------


Any help would be greatly appreciated!!!!


Stevcast
 
Last edited by a moderator:

dbeachy1

O-F Administrator
Administrator
Orbiter Contributor
Addon Developer
Donator
Beta Tester
Joined
Jan 14, 2008
Messages
9,214
Reaction score
1,560
Points
203
Location
VA
Website
alteaaerospace.com
Preferred Pronouns
he/him
Hmm, that looks pretty messy. I recommend a standard troubleshooting approach:

1. Install a clean instance of Orbiter 2010 to a new directory and configure your video options for "Direct3D T&L HAL", 32 bpp color.
2. Install OrbiterSound.
3. Install UMMu.
4. Install the XR2 and XR5.
5. Try loading some of the default XR scenarios. They should work.
6. Now install one of your other add-ons and test again.
7. Repeat step 6 until the CTD occurs.

That will pin down the buggy add-on. Once you determine which add-on is causing the crash you can remove that add-on from your main Orbiter installation.
 

N_Molson

Addon Developer
Addon Developer
Donator
Joined
Mar 5, 2010
Messages
9,271
Reaction score
3,244
Points
203
Location
Toulouse
Think to check Orbiter.log after you try a new addon, even if it seems to work well. Errors are never a good thing and can cause CTDs, especially when you have a lot of them, because it's impossible to know how errors interact with other errors !
 

stevcast

Addon Developer
Addon Developer
Joined
Jun 14, 2008
Messages
160
Reaction score
0
Points
0
Thanks Guys!! I thought I was doing an adequate job testing and retesting the addons, I guess I was wrong!! I'll have to try it all over again. Just out of curiosity, is there any program available that will do just that, point out conflicting, or "buggy" addons so they can be removed without having to redo hour upon hour of work?!!
 

Mantis

Member
Joined
Oct 23, 2009
Messages
547
Reaction score
0
Points
16
Location
Mississauga, Ontario
Thanks Guys!! I thought I was doing an adequate job testing and retesting the addons, I guess I was wrong!! I'll have to try it all over again. Just out of curiosity, is there any program available that will do just that, point out conflicting, or "buggy" addons so they can be removed without having to redo hour upon hour of work?!!

I don't know of any such utlities but in my own testing, I did notice a couple of addons that do in fact cause problems with the XR series. One of them is the Velcro Saturns and I can't recall what the other one was. I remember with the Velcro Saturns, there were no errors in the event log but there was an event in the Windows System log that referred to DirectDraw.

What I do is make a backup copy of my orbiter folder before installing any new addons and then make sure that everything works before removing the backup. If I come across something that conflicts with something that I really like (such as the XR series, AMSO, Shuttle Fleet, etc.) I simply restore my backup and skip that addon or run it in a separate instance of Orbiter.
 

stevcast

Addon Developer
Addon Developer
Joined
Jun 14, 2008
Messages
160
Reaction score
0
Points
0
Come to think of it, I did have some problems with Velcro Saturns in different scenarios, maybe that is part of the problem. I did get a couple of the XR-2 scenarios to work, and at least that gives me a foundation to start from. I just wish that there was a program that would illuminate any conflicts in addons before it snowballs out of control. As you install more to your Orbiter addon list, it gets more and more difficult to test every one of them, and eventually, you'll miss something, and the problem starts all over again.
 

garyw

O-F Administrator
Administrator
Moderator
Addon Developer
Tutorial Publisher
Joined
May 14, 2008
Messages
10,485
Reaction score
209
Points
138
Location
Kent
Website
blog.gdwnet.com
Thanks Guys!! I thought I was doing an adequate job testing and retesting the addons, I guess I was wrong!! I'll have to try it all over again. Just out of curiosity, is there any program available that will do just that, point out conflicting, or "buggy" addons so they can be removed without having to redo hour upon hour of work?!!

Backup before you install something new. This way you have the ability to restore.

Another option is to use some sort of source code control tool for managing differences in the installation caused by installing addons
 

stevcast

Addon Developer
Addon Developer
Joined
Jun 14, 2008
Messages
160
Reaction score
0
Points
0
And my XR confusion continues!!!!!!

I have totally redone my Orbiter 2010 to the point that I have a fair number of addons working , however, one thing I have noticed is that when I do install an addon that is "buggy" (as far as the 2010 version is concerned), it shuts down the XR-2 and XR-5 ships and causes all of these scenarios to CTD. If I take the addon out, XR-2 and XR-5 work flawlessly again. I guess my question is, why are these two ships so susceptible to interference from other addons? When I recheck other ships, they all continue to work fine.
I just tested ISS 4.25, and it caused the XR's to crash again. There are so many addons available, and I would like to have a fair sampling of all of the great work that everybody has done, but not at the expense of losing two of my favorite ships.
If anyone can enlighten me on just what the heck is going on, I would really appreciate it!

Stevcast
 

dbeachy1

O-F Administrator
Administrator
Orbiter Contributor
Addon Developer
Donator
Beta Tester
Joined
Jan 14, 2008
Messages
9,214
Reaction score
1,560
Points
203
Location
VA
Website
alteaaerospace.com
Preferred Pronouns
he/him
EDIT:
First, please be sure you are testing with the latest XR version of your ship (click here for more information).

If you're getting CTDs even with the latest XR version, read on: In a nutshell, XR vessels allocate a fair amount of memory and use a large number of C++ objects. The vast majority of Orbiter add-ons, OTOH, take a simpler "use large switch statements in several large methods" approach that most of Orbiter SDK samples use (which makes perfect sense for sample SDK code, BTW).

So, when an add-on overwrites memory that it did not allocate, the bug is harmless unless some other add-on has already allocated and is using that memory. So if you have five add-ons that only allocate a handful of C++ objects, they are using much less of the [ame="http://en.wikipedia.org/wiki/Dynamic_memory_allocation"]memory heap[/ame] than an XR vessel that allocates several hundred C++ objects, and so they are much less sensitive to memory corruption bugs. It's frustrating, I know, but all you can do is narrow down the add-on(s) that cause your CTDs and not install them.

EDIT:
One more thing I should add: one of the XR tests I do here is load up Orbiter under the Visual Studio debugger with the debugger's memory heap checks enabled and then run a scenario with 6-8 XR vessels (XR1/XR5/XR2 mix) in Earth orbit. Then I bounce around between the vessels and switch between 2D panels, VC, etc. in order to test for any XR memory bugs. It's a pretty brutal test. :)
 
Last edited:

Tommy

Well-known member
Joined
Aug 14, 2008
Messages
2,019
Reaction score
86
Points
48
Location
Here and now
I believe the missing textures and surfbase errors indicate that an add-on surface base is incorrectly installed - you have to update Earth.cfg to include the textures. "AWIDE" may indicate that Wideawake International (Ascension Island) may be part of that problem. However, I don't see why that would cause a CTD only with XR vessels unless the scenario files show the vessel LANDED at the base (ie, on a LPAD - and Wideawake doesn't have any)
 

stevcast

Addon Developer
Addon Developer
Joined
Jun 14, 2008
Messages
160
Reaction score
0
Points
0
Thanks to everyone that helped explain my XR-2, XR-5 problem. My solution; I installed another copy of Orbiter 2010, and am only installing a select few addons that play well with the two ships. At the time of this writing, both versions of Orbiter are working great, and I seem to have the best of both worlds!! Again, thanks to everyone.

Stevcast
 
Top