Problem CTD when arriving Brighton Beach in DGIV

[sequoia]

Hey folks,

Every time i approach Brighton Beach with the DGIV the program crashes at a distance between 5 - 25 kilometres from the base. Other Vessels work fine here. Since i am not the smartest guy in computer things and i did not found anything about this issue, i try it now here.

Program: Orbiter 2010
System: Windows 7 64-Bit, 4 GB RAM, Processor AMD Athlon 7550 Dual Core 2.50 GHz, ATI Radeon HD 3200 Graphics

The Logfile:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 4.08535e-007 sec
Found 1 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (ATI Radeon HD 3200 Graphics)
==> Direct3D T&L HAL (ATI Radeon HD 3200 Graphics)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module OrbiterSound.dll ...... [Build 121120, API 100830]
Module HideCursor.dll ........ [Build ******, API 060425]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module AeroBrakeMFD.dll ...... [Build ******, API 100830]
---------------------------------------------------------------
>>> 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 LaunchMFD.dll ......... [Build 140111, API 100830]
Error loading module Modules\Plugin\XRVesselCtrlDemo.dll (code 126)
Module transx.dll ............ [Build 140205, API 100830]
Module BaseSyncMFD.dll ....... [Build 100616, API 100603]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module HUDDrawer.dll ......... [Build 130423, API 100830]
Module Map3DMFD.dll .......... [Build 101102, API 100830]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1920 x 1080 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
Joystick throttle: Z-AXIS
Joystick throttle control detected
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 ShuttlePB.dll ......... [Build 100830, API 100830]
Module DeltaGlider.dll ....... [Build 100830, API 100830]
Module LuaInline.dll ......... [Build 100830, API 100830]
Module ShuttleA.dll .......... [Build 100830, API 100830]
Module DeltaGliderIV.dll ..... [Build 140107, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state

The Config. File:

; === ORBITER Master Configuration File ===
EchoAllParams = FALSE
LPadRect = 672 155 1214 717

; === Logical parameters ===
StartPaused = TRUE
DamageModel = 1
RefuelOnPad = FALSE
GenericMFDSize = 4
InstrumentUpdateInterval = 0.01

; === Visual parameters ===
EnableCloudShadows = TRUE
EnableSpecularRipples = TRUE
EnableLocalLights = TRUE
CSphereBgImage = Visible (DSS2/Wikisky)
CSphereBgPath = csphere\dds2
CSphereBgIntensity = 0.05

; === Visual helper parameters ===
Planetarium = 7146

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

; === Camera parameters ===
CameraPanspeed = 0.1

; === Device settings ===
DeviceIndex = 4
ModeIndex = 29
Fullscreen = TRUE
FullscreenPageflip = FALSE

; === Joystick parameters ===
JoystickIndex = 1
JoystickThrottleSaturation = 10000
JoystickDeadzone = 5000

; === Active plugin list ===
ACTIVE_MODULES
  OrbiterSound
  HideCursor
  ScnEditor
  AeroBrakeMFD
  LaunchMFD
  XRVesselCtrlDemo
  transx
  BaseSyncMFD
  ExtMFD
  HUDDrawer
  Map3DMFD
END_MODULES

Am i doing this right? Any suggestions are very welcome!

 

[ADSWNJ]

Can you hit Ctrl-S to save a .SCN file into your Quicksave folder, and then post that?

What are you running when it crashes (i.e. what MFD's, what autopilots, etc)? Is there a specific thing you do to crash it, or is it just distance to Brighton Beach.

Maybe you have some corruption in the surface tiles if it's location-specific?

 

[PhantomCruiser]

I thought the same thing regarding the tiles. But if it doens't happen with other craft I'm kind of stumped.

 

[Lisias]

UCGO ?

It's just wild guessing, but...

Do you have UCGO installed? If yes, what version?

I was experiencing some CTDs here, and then reinstalled the UCGO 3.0 and then run the 1.5 patch.

It can be something with Orbiter Sound - since the crash happens always in the same situation, can be a problem triggered by a specific sound effect.

 

[sequoia]

Thank you / Obrigado for the replies and hints! I checked and tried a few things and get closer to the problem.

I guess it's just that simple: Other Vessels in the scenario causes the CTD. I deleted all other ships via scenario editor and could finally land :thumbup:

Does anyone know if this is a general problem? I do understand that too many vessels in one scenario means a bigger workload for the computer. But the default orbiter scenarios come with a large variety of ships too (and work fine here). Are there specific ships that shouldn't be combined in one scenario? Or is it just my slightly outdated computer system that can't handle this?

Last test run was with one parked XR2 at BB (and the DGIV, of course). The program tolerated this and it worked well So now i'm gonna check some vessel combinations here

For example a scenario that always crashes:

BEGIN_DESC
Orbiter saved state at T = 6781
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 52006.8325487688
END_ENVIRONMENT

BEGIN_FOCUS
  Ship DGIV
END_FOCUS

BEGIN_CAMERA
  TARGET DGIV
  MODE Cockpit
  FOV 50.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE Orbit
  PROJ Ship
  FRAME Ecliptic
  ALT
  REF Moon
END_MFD

BEGIN_MFD Right
  TYPE Map
  REF Moon
  BTARGET Brighton Beach
  ZOOM 4
  POS -0.84 0.58
END_MFD

BEGIN_PANEL
END_PANEL

BEGIN_SHIPS
ISS:ProjectAlpha_ISS
  STATUS Orbiting Earth
  RPOS -5449284.38 -3415380.48 2019819.29
  RVEL -4300.535 6300.194 -944.836
  AROT 26.19 67.61 59.41
  AFCMODE 7
  IDS 0:588 100 1:586 100 2:584 100 3:582 100 4:580 100
  NAVFREQ 0 0
  XPDR 466
END
Mir:Mir
  STATUS Orbiting Earth
  RPOS -3464547.66 -348173.64 -5692596.82
  RVEL 6606.450 -244.718 -4001.117
  AROT 173.62 -33.28 -87.94
  AFCMODE 7
  IDS 0:540 100 1:542 100 2:544 100
  XPDR 482
END
Luna-OB1:Wheel
  STATUS Orbiting Moon
  RPOS 814046.72 2084663.61 73.17
  RVEL -1378.688 538.431 0.017
  AROT 0.00 0.00 177.40
  VROT -0.00 -0.00 10.00
  AFCMODE 7
  IDS 0:560 100 1:564 100
  XPDR 494
END
PB-01:ShuttlePB
  STATUS Landed Moon
  BASE Brighton Beach:2
  POS -33.4450804 41.1217033
  HEADING 220.00
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 484 124
END
GL-NT:DeltaGlider
  STATUS Landed Moon
  BASE Brighton Beach:4
  POS -33.4375001 41.1315931
  HEADING 70.00
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000
  NAVFREQ 0 0 0 0
  XPDR 0
  GEAR 1 1.0000
  AAP 0:0 0:0 0:0
END
SH-02:ShuttleA
  STATUS Landed Moon
  BASE Brighton Beach:5
  POS -33.4299198 41.1282963
  HEADING 43.18
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000
  NAVFREQ 0 0
  XPDR 0
  PODANGLE 0.0000 0.0000
  DOCKSTATE 0 0.0000
  AIRLOCK 0 0.0000
  GEAR 0 0.0000
  PAYLOAD MASS 0.0 0
END
DGIV:DeltagliderIV
  STATUS Orbiting Moon
  RPOS 520661.01 956953.99 -1442842.16
  RVEL 1125.711 639.964 843.205
  AROT 37.75 -46.85 24.89
  PRPLEVEL 0:0.883380 1:0.993945
  THLEVEL 4:0.014192
  IDS 0:45 100
  NAVFREQ 166 488
  XPDR 0
  ;-------------------------- Skin parameters must contain directory name of skin (without space) 
  MeshSkin mining
  ;-------------------------- Cargo payload must contain name of config file or "none".(see doc) 
  CargoPayload none
  NOSECONE 0 0.00
  GEAR 0 0.00
  AllDoorsState 0 0.00 0 0.00 0 0.00 0 0.00 0 0.00 0 0.00 0 0 0.00
  But1Cockpit 0 0 0 2 2 2 0 2 2 2 2 2 2 2 2 1 1 2 1 1 1 4
  But2Cockpit 0 0 0 0 0 0 0 0 2 2 2 2 2 0 50 0 0 0 1 1 0 0
  TransEffect 0
  LifeBut1State 0 2 1 2 1 2 2 2 2 2 2 2 2 0 0
  LevelBatt 100.0000
  Emergency_power 10000.0000
  VoltageStartBus 0.0000
  VoltageGen1 96.2800
  VoltageGen2 96.2800
  VoltageGenBus 96.0000
  O2tankALevel 99.5579
  N2tankALevel 100.0000
  O2tankBLevel 100.0000
  N2tankBLevel 100.0000
  CabinO2Level 21.3954
  CabinCO2Level 600.0000
  CabinTempLevel 21.2000
  CabinPressure 14.7000
  CabinMoistLevel 36.0000
  CabinDustLevel 0.0002
  CabinO2Setting 21.4000
  CabinTempSetting 21.2000
  CabinPressSetting 14.7000
  AntennaTarget no_target
  O2ConsumptionSetting 1
  FuelConsumptionSetting 1
  MainenginePower 1
  ;------------------Crew parameters  UMMUCREW Function-Name-Age-CardiacPulse-WeightKg (fonction of Pilot must be: Capt) 
  NoOneOnBoard 0
  NoPilotOnBoard 0
  UMMUCREW Capt-Francois_Bowman-41-65-94
  UMMUCREW -Peter_Dawson-35-69-84
  FailGearFailure 0
  FailGearCollapse 0
  FailLeftMainEngine 0
  FailRightMainEngine 0
  FailHoverEngine 0
  FailRcs 0
  FailSurfaceControl 0
  FailComputer 0
  FailComputerBlueScreen 0
  FailAutopilot 0
  FailExtRadiator 0
  FailAirbrake 0
  FailNoseCone 0
  FailCanopy 0
  FailAntenna 0
  FailLeftTurbo 0
  FailRightTurbo 0
  FailCargoDoor 0
  SpacesuitTimer 0
  UCGO @@0,1,0,0,@@1,1,0,0,@@2,1,0,0,@@3,1,0,0,
END
END_SHIPS

BEGIN_ExtMFD
END

Do you have UCGO installed?

Yes, latest Version. Checked that.

Maybe you have some corruption in the surface tiles if it's location-specific?

No, i removed the surface tiles data from the Brighton.cfg folder for a test. Still crashing.

 

[ADSWNJ]

Thanks Sequoia. The offending line is:

DGIV:DeltagliderIV

Orbiter tries to find Orbiter\Config\Vessels\DeltagliderIV.cfg (which doesn't exist on your install), and then Orbiter\Config\DeltagliderIV.cfg (which should never exist), and then it gives up and dies. I suspect you have copied this .scn file from somewhere else, and/or you are trying to run it on an installation of Orbiter that does not yet know about the DeltagliderIV, or you have accidentally deleted the DeltagliderIV.cfg file.

No problem though: to fix this, go to Dan Steph's download page here and download DeltaGliderIV-3 + UMmu 3.0 - 2014 édition.
Run the downloaded .exe, tell it where your Orbiter directory is, and then press the Install button. Say YES to the 'Patch outdated UMmu.dll", OK, and Patah all addons and follow the instructions. Then exit the installer and go check that your orbiter\Config\Vessels directory now has a DeltagliderIV.cfg file.

If it does, then your scenario will now run properly.

 

[sequoia]

Thank you for the efforts, ADSWNJ, but.... i have the latest Dan Stephs stuff you linked above. There is also the Orbiter\Config\Vessels\DeltagliderIV.cfg file in my installation.

I guess it is really this specific scenario (shown above) wich causes the problem. Can't remember where i got it from, but i think i built it myself from another scenario (is there, by the way, a better method to create a scenario?). Then i built other scenarios based on this particular scenario and so the CTD's appeared to me as a generic bug, i think. Took me 2 weeks to figure that out :facepalm: Hope you can follow me and my english here :lol:
I tested some new scenarios with different amount / type of vessels lately and everything works properly. Wich is GOOD!

Conclusion: I don't know what causes the CTD's but i know now how to prevent that. Regardless, your advices helped me. It's good to get some hints.

 

[ADSWNJ]

Your English is excellent! So long as everything is working now, we are good. :thumbup:

Generally - you need to be very careful with any editing of a .scn file, as every add-on will work differently with the data, and some are less forgiving if something is wrong. (E.g. some insist on tabs, some want spaces, some will tolerate comments on the end of the line, others will die if you do this). If you cut and paste a whole vessel section or MFD section from one .scn to another, it will usually be OK, but editing data for a specific section ... take a backup first and be sure you know what you are doing!