Software Debug...again and again.

[AnakinSkyobiliviator]

Some of the Add On I use for orbiter make my computer to prompt a debug window, which I click debug which shuts Orbiter down. One of them was notably the new OrcusPatera I downloaded today. I use Windows XP (yes, old but I find it reliable) for orbiter, and as I previously mentioned, uses a netbook. During the loading screen, a debug message comes up saying "orbiter.exe has encountered a problem and needs to close. We are sorry for the inconvenience." and when I check the orbiter.log it shows everything is fine (this is for loading up OrcusPatera) :

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 2.79365e-007 sec
Found 0 joystick(s)
Devices enumerated: 4
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D HAL (Intel(R) Graphics Media Accelerator 3150)
Module AtlantisConfig.dll .... [Build ******, API 060425]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module OrbiterSound.dll ...... [Build 121120, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module CSSC_Spawner.dll ...... [Build 120331, API 100830]
Module HCLV_MFD.dll .......... [Build 130722, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module CamShake.dll .......... [Build 100811, API 100606]
Module RWarpMFD.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.
---------------------------------------------------------------

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1018 x 568 x 32
Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
Graphics: Stencil buffer depth: 8 bit
Graphics: Active lights supported: -1
Loading 8816 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-008, Terms 6400/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 UCGOShuttleA.dll ...... [Build 121229, API 100830]
Module Ummu.dll .............. [Build 121224, API 100830]

What is going on? As I said, some other add ons have similar debug problem...

 

[Izack]

Sometimes, no error is written during a failure. It could be, for example, an internal error in one of the loaded modules. The Orbiter log generally reports missing files (textures, meshes, configurations, etc.), but not on functions using invalid handles or whatever. To debug this, the best way is to find by trial and error which addon/module is causing the bug. Is this only happening with Orcus Patera, or with the UCGO Shuttle A, or any other module reported in the log? The solution could take a while to find, but there really isn't a magical alternative to the bug hunt.

 

[AnakinSkyobiliviator]

Well, it occurs to some other add-on too, sadly. How do I pinpoint them?

 

[JMW]

Start with a "clean" (new) Orbiter installation, and add Add-ons one at a time till it happens. Eliminate that one and continue loading untill it happens again:thumbup:

 

[AnakinSkyobiliviator]

Oh....This is going to be a big problem. Because, even though I am new, I got tons (and I mean tons) of add ons...And some add on tend need to be installed before others, so when it don't work, I have to download the one required and I will lose track...Could the problem be caused by an outdated API?

 

[SolarLiner]

JSGME is really underestimated and should be at best raised as a standard for addon installation.
With it you can easily add and remove add-ons, and makes investigations in case of a bug.

 

[AnakinSkyobiliviator]

JSGME? What's that? And I notice that a part of the problem may be my msvcr80 or something like that. I tried updating it but my computer does not allow.

 

[SolarLiner]

JSGME is a piece of software that handles MOD installing/uninstalling for you. You simply install your add-ons in a subfolder of the MODS folder, and let JSGME copy the files on demand. I believe there is some tutorials out there, but I just use it everywhere, because of its great abilities.

 

[AnakinSkyobiliviator]

Well, I just extract the files directly into Orbiter, and it works. Now, I think I need a way to find the faulty file without ruining everything...

 

[Zatnikitelman]

Or you could just extract a new orbiter install and extract the addons into the clean installation one at a time. You can have as many copies of Orbiter as you want on your machine!

 

[AnakinSkyobiliviator]

Well, what we are talking about here is opening a file in an order that may or may not work due to file requirements, and, in testing every single one of them sounds...very time consuming.

Update: I found the problem! (hopefully it is the last one) I knew something is glitchy about my Mars, so I check one by one and the debug message disappeared! (For now) Thanks for the suggestions!