Problem AMSO Lunar Rover Crash

Pyromaniac605

Toast! :D
Joined
Aug 15, 2010
Messages
1,774
Reaction score
0
Points
0
Location
Melbourne
I've been having tons of fun with AMSO because I couldn't get NASSP to work. Anyway I was having a go at Apollo 17 (my personal favourite) then my eyes lit up when I saw the LRV attached to the side so I hopped over pressed 'K' and it started to unfold, then it turned around, then Orbiter crashes. Any idea what might be causing this? I've had no problems with other AMSO vehicles.

Darren
 
This happens to me and to Aeadar as well. I've been trying to nail down a cause but so far have failed. I've even tried disabling all MFDs which was ACSoft's suggestion but it didn't help. Aeadar tried it with a clean install of Orbiter and it still happened to him so I'm almost conviced that it's some kind of C+ runtime issue or something else along those lines. I've had it happen on all three of my current computers as well as my former desktop PC that was recently retired.
 
Last edited:
So by the sounds of it nobody has ever drove the rover. :(

Darren

Edit: YAY! I got it working try the Apollo 16 LRV mission.
 
Last edited:
See "How to ask for help with an Orbiter issue", items 9 & 10. You certainly haven't done item 9, and judging by your post here, I'm guessing that you haven't done item 10 either.

EDIT: BTW, just because you waited all of two hours while the majority of the Orbiter community is either asleep or busy with other things (who knows, maybe even busy trying to find a solution to your problem...) doesn't mean "nobody has ever driven the rover."
 
See "How to ask for help with an Orbiter issue", items 9 & 10. You certainly haven't done item 9, and judging by your post here, I'm guessing that you haven't done item 10 either.

Actually in this case number 9 wouldn't help - nothing gets written to the log when orbiter CTD in this case.

---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------

So by the sounds of it nobody has ever drove the rover. :(

Darren

Edit: YAY! I got it working try the Apollo 16 LRV mission.

From what I understand it works great for most people. I guess we're just unlucky!:lol: The Apollo 16 one crashes for me at the same point as the 15 and 17 missions. I'd love to solve this one - AMSO is my favorite addon for sure.
 
Actually in this case number 9 wouldn't help - nothing gets written to the log when orbiter CTD in this case.
Of course, but what you are looking for is what went on before the crash. If nothing else, the log would answer the clean install question.
 
Does it really matter tblaxland? I've solved the issue. Mantis did you run the one in miscellaneous? That's the one I used.

Darren
 
Unfortunately, I am not able to reproduce the case here.

Anyway, let's do some investigations, to see if we can isolate the problem. Here included is a "post-deployment scenario", I would like you try.

Situation was saved just after the whole LRV deployement of AMSO scenario: "Miscellaneous\Apollo 16 LRV deployment".

Code:
BEGIN_DESC
Post LRV deployement test.
END_DESC
BEGIN_ENVIRONMENT
  System AMSO\Sol
  Date MJD 41428.1160899466
END_ENVIRONMENT
BEGIN_FOCUS
  Ship AS-511_LM_vessel_crew1_EVA
END_FOCUS
BEGIN_CAMERA
  TARGET AS-511_LM_vessel_crew1_EVA
  MODE Extern
  POS 3.04 -126.90 -4.03
  TRACKMODE Ground Moon
  GROUNDLOCATION 15.49806 -8.97405 3.28
  FOV 40.00
END_CAMERA
BEGIN_SHIPS
AS-511:AMSO\Apollo
  STATUS Orbiting Moon
  RPOS -988715.33 -2431.39 -1547677.56
  RVEL -1367.218 235.162 874.509
  AROT -7.84 55.96 47.74
  AFCMODE 7
  PRPLEVEL 0:0.361000
  NAVFREQ 0 1 2 3
  XPDR 0
  STATE 10
  LANDINGSITE 1
  ABORTSTATUS 0
  MISSIONTIME 349537.358395
  PWR 0.000000
  DLMS 0
  SPCEVA 0
  GOTK1 0
  GOTK2 0
  SPCDTH 0
  LMPDTH 0
  OPENSM 0
  SUBSAT 0
  MAGANT 0
  PASBRK 0
  LMCRBK 0
  BEACON 0
END
AS-511_LM_vessel:AMSO\LM_vessel
  STATUS Landed Moon
  POS 15.4976884 -8.9738102
  HEADING 181.79
  AFCMODE 7
  PRPLEVEL 0:0.094000
  NAVFREQ 0 1 2 3
  XPDR 0
  STATE 2
  LANDED 1
  ABORTED 0
  EVA 1
  EVIX 0
  LOIX 0
  BEACON 0
  C1DEAD 0
  C2DEAD 0
  CRWGON 0
END
AS-511_Landing-site:AMSO\LandingSite
  STATUS Landed Moon
  POS 15.4985931 -8.9734100
  HEADING 0.00
  AFCMODE 7
  NAVFREQ 0 0
END
Moon_rock1:AMSO\Moon_lab
  STATUS Landed Moon
  POS 15.4784536 -8.9739784
  HEADING 181.79
  AFCMODE 7
  NAVFREQ 0 0
END
Moon_rock2:AMSO\Moon_lab
  STATUS Landed Moon
  POS 15.4798443 -8.9741363
  HEADING 181.79
  AFCMODE 7
  NAVFREQ 0 0
END
Moon_rock3:AMSO\Moon_lab
  STATUS Landed Moon
  POS 15.4782880 -8.9736755
  HEADING 181.79
  AFCMODE 7
  NAVFREQ 0 0
END
Moon_rock4:AMSO\Moon_lab
  STATUS Landed Moon
  POS 15.4784039 -8.9737088
  HEADING 181.79
  AFCMODE 7
  NAVFREQ 0 0
END
Moon_rock5:AMSO\Moon_lab
  STATUS Landed Moon
  POS 15.4795662 -8.9756325
  HEADING 181.79
  AFCMODE 7
  NAVFREQ 0 0
END
Moon_rock6:AMSO\Moon_lab
  STATUS Landed Moon
  POS 15.4782463 -8.9752947
  HEADING 181.79
  AFCMODE 7
  NAVFREQ 0 0
END
AS-511_LM_vessel_crew1_EVA:AMSO\crew_EVA
  STATUS Landed Moon
  POS 15.4977082 -8.9739417
  HEADING 13.03
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  STATE 1
  OBJ 0
  EVA_TIME 11.000000
  EXHAU 0.000000
  ATCST 2
  DEAD 0
  VISCMD 4
  PT1CMD 4
  PT2CMD 0
  VISANG 1.000000
  PT1ANG 1.000000
  PT2ANG 0.000000
  PT3ANG 0.000000
END
AS-511_LM_vessel_crew2_EVA:AMSO\crew_EVA
  STATUS Landed Moon
  POS 15.4979060 -8.9740455
  HEADING 309.69
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  STATE 0
  OBJ 0
  EVA_TIME 11.000000
  EXHAU 0.000000
  ATCST 2
  DEAD 0
  VISCMD 4
  PT1CMD 0
  PT2CMD 0
  VISANG 1.000000
  PT1ANG 0.000000
  PT2ANG 0.000000
  PT3ANG 0.000000
END
AS-511_Lunar_Rover:AMSO\Lunar_Rover
  STATUS Landed Moon
  POS 15.4978432 -8.9739411
  HEADING 181.79
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  BUILDED 1
  EVATC1 0.000000
  EVATC2 0.000000
  CREW1 0
  CREW2 0
  CDTDTH 0
  EXHC1 0
  EXHC2 0
  DRILL1 0
  DRILL2 0
  VISPR1 0.000000
  VISPR2 0.000000
  SUN1PR1 0.000000
  SUN1PR2 0.000000
  SUN2PR1 0.000000
  SUN2PR2 0.000000
  SUN3PR1 0.000000
  SUN3PR2 0.000000
  RADCOPR 0.000000
  BATTEMP 0.000000
  OVERHEAT 0
  VISCMD1 0
  VISCMD2 0
  SUN1CMD1 0
  SUN1CMD2 0
  SUN2CMD1 0
  SUN2CMD2 0
  RADCOCMD 0
END
END_SHIPS

Are-you able to load this scenario ?

If yes, does the LRV perform normally (please try to embark/disembark astronauts, to drive the LRV from outside and also in first person mode, etc...) ?

This should learn us if this crash has something to do with the deployement animation or not.

ACS
 
Thanks ACSoft. This is my favorite addon bar none and it would be fantastic to get the LRV working. That scenario does indeed CTD for me. My Orbiter log is below. In the other scenarios, everything works flawlessly until the very instant that deployment and movement of the LRV is completed. At that exact point it crashes.

Code:
a**** Orbiter.log
Build Jun  6 2010 [v.100606]
Timer precision: 4.65436e-007 sec
Found 0 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (ATI Mobility Radeon HD 4300 Series)
==> Direct3D T&L HAL (ATI Mobility Radeon HD 4300 Series)
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 ProjectApolloConfigurator.dll  [Build ******, API 060425]
Module uap.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 transx.dll ............ [Build 100528, API 100527]
Module ScnEditor.dll ......... [Build 100606, API 100606]
Module RWarpMFD.dll .......... [Build 100314, API 091124]
Module RendezvousMFD.dll ..... [Build ******, API 050206]
Module Rcontrol.dll .......... [Build 100606, API 100606]
Module OrbiterSound.dll ...... [Build ******, API 060425]
Module Meshdebug.dll ......... [Build 100606, API 100606]
Module Map3DMFD.dll .......... [Build 100620, API 100606]
Module LunarTransferMFD.dll .. [Build 100621, API 100603]
Module LuaMFD.dll ............ [Build 100606, API 100606]
Module LuaConsole.dll ........ [Build 100606, API 100606]
Module LTV-MFD.dll ........... [Build ******, API 060425]
Module LaunchMFD.dll ......... [Build 100816, API 100606]
Module JUPITER_MFD.dll ....... [Build ******, API 060425]
Module InterMFD53.dll ........ [Build 090521, API 060425]
Module HerschelPlanckMFD.dll . [Build ******, API 060425]
Module Glideslope.dll ........ [Build ******, API 060425]
Module Framerate.dll ......... [Build 100606, API 100606]
Module FlightData.dll ........ [Build 100606, API 100606]
Module ExtMFD.dll ............ [Build 100606, API 100606]
Module CustomMFD.dll ......... [Build 100606, API 100606]
Module CRT.dll ............... [Build ******, API 060425]
Module BTC2.0.dll ............ [Build ******, API 060425]
Module BaseSyncMFD.dll ....... [Build ******, API 060425]
Module BaseLand.dll .......... [Build ******, API 060425]
Module AutoFCS.dll ........... [Build ******, API 050206]
Module AttitudeMFD.dll ....... [Build ******, API 060425]
Module ProjectApolloMFD.dll .. [Build ******, API 060425]
Module UnivPTG.dll ........... [Build 100629, API 100606]
Module RPOP.dll .............. [Build 100620, API 100606]
Module GPCMFD.dll ............ [Build 100621, API 100606]
Module Collision-core.dll .... [Build ******, API 060425]
Module NAVSET.dll ............ [Build ******, API 060425]
Module ReFuelMFD.dll ......... [Build ******, API 060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1366 x 768 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Loading 8816 records from star database
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
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]
Module Satsat.dll ............ [Build ******, API 061227]
Module Saturn.dll ............ [Build 100215, API 100212]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
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
Finished initialising world
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetNavRecv
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.
---------------------------------------------------------------
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
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.
---------------------------------------------------------------
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
 
Last edited:
Can you replicate the crash in a clean install (ie, Orbiter + OrbiterSound + AMSO only). With all those plugins running, there is a good chance that one of them is conflicting with AMSO when the rover is deployed (eg, referencing an object that has been deleted or referencing some memory they deallocated that AMSO happens to overwrite when the rover is deployed).
 
Thanks ACSoft. This is my favorite addon bar none and it would be fantastic to get the LRV working. That scenario does indeed CTD for me. My Orbiter log is below. In the other scenarios, everything works flawlessly until the very instant that deployment and movement of the LRV is completed. At that exact point it crashes.
Hi Mantis,

Please follow the judicious advise of tblaxland and deactivate all the plugin modules, except OrbiterSound. This will eliminate a lot of potential reasons for the crash.

I would like you also try the "post-deployment" scenario published in my previous message (copy the contain of the window into your notepad and save it into "Orbiter\scenario" as "LRV-test.scn" file and run this scenario). The precise point you described, where you get the CTD, correspond to the creation of the LRV vessel itself (just after the LRV turn on itself). This is why I suspect the problem belong to LRV vessel and probably not to the LRV deployment itself (which is are multiple and complex animations of a folded LRV mesh which belong to the LM vessel).

If the included scenario crash, it will confirm that the problem belong only to the LRV vessel module and as nothing to do with LM vessel module. But if you can run this scenario and use the LRV, I will know that the CTD is linked with this very particular situation: The LRV vessel creation just after deployment.

To know this information will allow me to prepare some furhter "debug materials" I will publish here, so you can test.

ACS
 
That log actually was from your test scenario. I ran it again with all modules except for Orbiter Sound disabled and the result was the same:

Code:
**** Orbiter.log
Build Jun  6 2010 [v.100606]
Timer precision: 4.65436e-007 sec
Found 0 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (ATI Mobility Radeon HD 4300 Series)
==> Direct3D T&L HAL (ATI Mobility Radeon HD 4300 Series)
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 ProjectApolloConfigurator.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 WarpDriveMFD-Mk2.dll .. [Build 100808, API 100606]
Module UnivPTG.dll ........... [Build 100629, API 100606]
Module uap.dll ............... [Build ******, API 060425]
Module transx.dll ............ [Build 100528, API 100527]
Module TrackIR.dll ........... [Build 091120, API 091120]
TrackIR module not found.
Module ScriptMFD.dll ......... [Build 100606, API 100606]
Module ScnEditor.dll ......... [Build 100606, API 100606]
Module RWarpMFD.dll .......... [Build 100314, API 091124]
Module RPOP.dll .............. [Build 100620, API 100606]
Module RendezvousMFD.dll ..... [Build ******, API 050206]
Module ReFuelMFD.dll ......... [Build ******, API 060425]
Module Rcontrol.dll .......... [Build 100606, API 100606]
Module ProjectApolloMFD.dll .. [Build ******, API 060425]
Module NAVSET.dll ............ [Build ******, API 060425]
Module Meshdebug.dll ......... [Build 100606, API 100606]
Module Map3DMFD.dll .......... [Build 100620, API 100606]
Module LunarTransferMFD.dll .. [Build 100621, API 100603]
Module LuaMFD.dll ............ [Build 100606, API 100606]
Module LuaConsole.dll ........ [Build 100606, API 100606]
Module LTV-MFD.dll ........... [Build ******, API 060425]
Module LolaMFD.dll ........... [Build 100823, API 100606]
Module LaunchMFD.dll ......... [Build 100816, API 100606]
Module JUPITER_MFD.dll ....... [Build ******, API 060425]
Module InterMFD53.dll ........ [Build 090521, API 060425]
Module HerschelPlanckMFD.dll . [Build ******, API 060425]
Module GPCMFD.dll ............ [Build 100621, API 100606]
Module Glideslope.dll ........ [Build ******, API 060425]
Module Framerate.dll ......... [Build 100606, API 100606]
Module FlightData.dll ........ [Build 100606, API 100606]
Module ExtMFD.dll ............ [Build 100606, API 100606]
Module CustomMFD.dll ......... [Build 100606, API 100606]
Module CRT.dll ............... [Build ******, API 060425]
Module Collision-core.dll .... [Build ******, API 060425]
Module BTC2.0.dll ............ [Build ******, API 060425]
Module BaseSyncMFD.dll ....... [Build ******, API 060425]
Module BaseLand.dll .......... [Build ******, API 060425]
Module AutoFCS.dll ........... [Build ******, API 050206]
Module AttitudeMFD.dll ....... [Build ******, API 060425]
Module OrbiterSound.dll ...... [Build ******, API 060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1366 x 768 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Loading 8816 records from star database
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
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]
Module Satsat.dll ............ [Build ******, API 061227]
Module Saturn.dll ............ [Build 100215, API 100212]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
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
Finished initialising world
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetNavRecv
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.
---------------------------------------------------------------
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
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.
---------------------------------------------------------------
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
 
Last edited:
According to that log you have a lot of modules still active, things like WarpDriveMFD-Mk2.dll and collision-core.
 
Ok I ran the scenario again with a clean Orbiter install (just AMSO and Orbiter sound installed) and it still CTD. Here's the log:

Code:
**** Orbiter.log
Build Jun  6 2010 [v.100606]
Timer precision: 4.65436e-007 sec
Found 0 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (ATI Mobility Radeon HD 4300 Series)
==> Direct3D T&L HAL (ATI Mobility Radeon HD 4300 Series)
Module AtlantisConfig.dll .... [Build 100606, API 100606]
Module AtmConfig.dll ......... [Build 100606, API 100606]
Module DGConfigurator.dll .... [Build 100606, API 100606]
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.
---------------------------------------------------------------

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1366 x 768 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Loading 8816 records from star database
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
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]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100215, API 100212]
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 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
Finished initialising world
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetNavRecv
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.
---------------------------------------------------------------
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
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.
---------------------------------------------------------------
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state

I'm beginning to wonder if maybe it needs some C+ runtime or something that I don't have on my computer.

---------- Post added at 10:04 AM ---------- Previous post was at 10:03 AM ----------

According to that log you have a lot of modules still active, things like WarpDriveMFD-Mk2.dll and collision-core.

They were still there but disabled. I ran it again with a clean install though and got the same result.
 
OK, now we know that you get the CTD just with the LRV vessel.

Try the following:

Edit my scenario and remove just the LRV vessel in the "SHIPS" section

it is the following part, located at the end of the list:

AS-511_Lunar_Rover:AMSO\Lunar_Rover
STATUS Landed Moon
...
RADCOCMD 0
END

And tell me if still have the CTD while loading the scenario.

Normally, it should load without any problem and you should see a folded LRV inside the LM. If it is the case, I will prepare for you a special debug LRV module dll, where I will deactivate some part(s) of the code. Maybe this could help to localize the part of the code which trigger the CTD.

It is perfectly possible that it is your C++ runtime library which cause the problem. What is the version of the Windows OS you are using ? Can-you try to do the test on a PC with Windows XP SP3 ? This the OS I use.

ACS
 
Thanks for the help ACS. I removed the LRV section from the scenario as directed and it no longer crashes. I am running Orbiter on three computers: 2 running Windows 7 Ultimate 64Bit and 1 running Windows 7 Ultimate 32 bit and I have the same problem on all of them. I tried running Orbiter in Windowx XP Mode on my 64 bit systems and it still crashes. Running in XP mode is the same as running a XP Professional 32Bit.

The funny thing is that ever other part of AMSO works perfectly with my setup. It's just the LRV that gives me grief.
 
AMSO:Lunar Rover Crash

O/S: Vista Home Premium (x86)
6.0.6001 service pack 1 Build 6001
AMD Dual Core 4450e
Graphics:ATI Radeon HD 3450

Having just installed the 2010 orbiter, AMSO 1.19 ,module's and enhanced texture's, I also had the same CTD with the Lunar rover. However, when it failed the Problem Signatures showed the following information:
Problem Event Name: APPCRASH
Application Name: Orbiter.exe
Application Version: 0.0.0.0
Application Timestamp: 4c0bf8a3
Fault module Name: msvcr80.dll
Fault module Version 8.0.50727.4053
Fault module Timestamp: 4a594c79
Exceptio Code: c0000005
Exception Offset: 000173bd

Is the msvcr80.dll part of C+ runtime which as been mentioned in other posts?

I Downloaded and installed (in the orbiter base file) the latest version of msvcr80.dll, and the rover deployed and ran. When I switched orbiter off/on the rover CTD came back. I then did a clean install with just AMSO and sound, the rover CTD happened again, and orbiter log showed the same information as mantis. Installed msvcr80.dll and rover ran, but when orbiter switched off/on rover failed.
In a clean install I have tried both of your scenarios, and orbiter immediately does a CTD.
As to Orbiter 2010 itself, I must say I am well impressed with graphics and the overall challenge it sets.
 
msvcr80.dll is I believe part of the VC++ 2008 runtime - hence the name, MS VC R 80.
 
Lunar Rover CTD

ACSoft
Just like to echo mantis, and thanks for help. Ran both your scenario's and first one immediatly crashed and second one loaded with rover in LM. If I press K rover deploys and turns and then CTD. Unlike mantis I am running on Vista home premium.
 
Hello everybody,

My idea was to remove the animation code of the LRV vessel module, to see if the crash come from this complex part. But, after I started doing this for a while, I finally decided to renounce, because of the complexity and the interweaving of this code inside the rest of the code. It would have been too much work to do this just for such a test. This would even have had consequences on another vessel module (crew), because of the sun visors (communication between both modules about sun visors animations status) and required to modify also this module.

Now, msvcr80.dll track seem to be an interesting one. On my own system, I founded this dll only in some very few and particular directories and NOT inside "System32" directory. This mean, most certainly, that in my configuration, I DO NOT RUN THIS DLL CODE FOR ORBITER AT ALL AND THEREFORE, FOR THE LRV MODULE CODE EITHER.

Unfortunately, I am not a specialist AT ALL, of this kind of problems. In fact, this is typically the kind of problems which make me sometimes totally mad about the Windows operating system !!!

Is there any way to know which runtime libraries are used on a specific system, with a specific application ? Does anybody have some clues & help about this ?

For example, Orbiter 2010 install msvcp71.dll & msvcr71.dll. Does not this mean that Orbiter (and consequently Orbiter's addons) run with these runtime libraries ?

EDIT:

Folk's, guess what !!! After my several tries and manipulations around this problem, I have also updated my Orbiter to the last version with the official Patch #1 and ... suddenly... I got the CTD !!! So I avoided to reboot my PC and immediately restarted to work on the problem.

It is not the first time I had such kind of mysterious problem in AMSO, so my first try was right on the target: this CTD is linked with the big LRV mesh preloading.

Without preloading this mesh, the code work. Don't ask me why !!!

Please download here:
http://www.acsoft.ch/tmp/Test-Modules.zip

A new set of modules for you to test. In this version, I have moved all the LRV meshes preloading, inside the LM vessel module, instead of the main Apollo vessel module. On my system, this overturn the CTD problem. I hope it will also do it for you. Please confirm.

If it does, I will publish a new official AMSO patch, with this new set of modules, along with a new version of the AMSO "Earth.cfg", compatible with Orbiter 2010-P1.

ACS
 
Last edited:
Back
Top