General Question Missing Functions

[R8-Q88]

Could someone point me to the MFDs/Modules that provide these functions: oapiGetStationCount, and SetBankMomentScale. The lack of these functions causes my installation of Orbiter 2010 to CTD periodicaly. Thanks in advance.

 

[orb]

You mean modules that use those functions, and not provide? Those are legacy and obsolete functions of Orbiter API, i.e. they weren't implemented by any modules, but by the core.

Modules using oapiGetStationCount are very old, as stations were removed very long ago, I don't remember exactly when, but before Orbiter 2005 (maybe in 2003 release :shrug.

Modules using SetBankMomentScale are old too. This function is marked obsolete in Orbiter 2010.

 

[Hielor]

If these are showing up in your Orbiter.log after the CTD they are not the cause of the CTD.

 

[R8-Q88]

They aren't? Then what is causing the CTDs? There aren't any other errors in the Orbiter.log after a crash.

 

[orb]

Can you post a list of all enabled modules and vessels you use?

 

[R8-Q88]

I can do modules right now, it might be a bit for the ships.
Modules:
transx
AttitudeMFD
B3OP
CamShake
EnergyMFDmk2
FlyByMFD
GenesisMFD
GPCMFD
HAL9000
IEATMFD
orbHoverDust
OrbiterSound
orbSonicBoom
orbSpotLight
RaceCheckpointMFD
Rcontrol
ReFuelMFD
ReleaseMFD-Mouse
ReleaseMFD-ShiftD
RPOP
RWarpMFD
ScreenCapture
TetherMFD
ThrustControlMFD
UMMUFA
universalParachute
UnivPTG
WeatherMFD
ScnEditor
Spacecraft3
Spacecraft2
Spacecraft
Multistage2
Stage
And, of course, I am using UCGO and Ummu.

As far as I know, all of these work and are required by one addon or another. I will try to get a list of spaceships created as soon as possible.

 

[Face]

Three addons there trigger my memory: ReleaseMeMFD, RaceCheckpointMFD and TetherMFD.
The first is compiled for O2K6P1, but uses only attachment calls, so it should be fine.
The second is only needed for ORL setups and is self-contained, meaning it will not destroy scenarios when disabled, because it auto-generates objects.
The last is rather old IMHO and could be a cause of CTD on new Orbiter installations.

If you do not use any of them regulary, try disabling them for a while.

In case of unknown CTDs in Orbiter, it is generally a good approach to disable all modules and re-enable them step by step until the CTDs show up again. This way you can narrow it down to only a couple of modules or even a single one.

If no module is causing the CTD, you can proceed to check the scenarios you use the most. Maybe one of the vessel modules is the source of crashes.

regards,
Face

 

[R8-Q88]

Ok, I disabled all of the MFDs/Modules in the "Modules" tab except OrbiterSound. I loaded a DGIV scenario (They have been giving me CTDs forever, I had given up on trying to fix them. They wern't the ones with the missing functions though.) It all went fine until it tried to load the DGIV. It crashed. Here is my Orbiter.log after the crash:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 4e-008 sec
Found 0 joystick(s)
Devices enumerated: 3
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module EnergyConfigurator.dll  [Build ******, API 060425]
Error loading module Modules\Plugin\BombMFD.dll (code 126)
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 1024 x 768 x 16
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 16 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 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 ******, API 061227]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
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 DeltaGliderIV.dll ..... [Build ******, API 060425]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state

 

[Face]

Ok, I disabled all of the MFDs/Modules in the "Modules" tab except OrbiterSound. I loaded a DGIV scenario (They have been giving me CTDs forever, I had given up on trying to fix them. They wern't the ones with the missing functions though.) It all went fine until it tried to load the DGIV. It crashed. Here is my Orbiter.log after the crash:

<snip>
Module EnergyConfigurator.dll  [Build ******, API 060425]
Error loading module Modules\Plugin\BombMFD.dll (code 126)
<snip>

The lines left above let my eyebrows raise. If you disabled all modules, why is EnergyConfigurator and BombMFD still there? Could it be that you have some additional modules installed in /Modules/Startup/ besides AtlantisConfig.dll, AtmConfig.dll and DGConfigurator.dll? If so, try to rename them to e.g. EnergyConfigurator.dll.orig, so Orbiter is not loading them on startup.
For BombMFD I don't know... it looks like it is still activated, but maybe it doesn't show up in the list due to the loading error. Check your Orbiter.cfg file with a text-editor for a line containing BombMFD and delete that line. This should get rid of the entry in the log.

hope that helps,
Face

 

[R8-Q88]

Ok, BombMFD was a MFD that I had installed a long time ago, but I uninstalled it. I removed the line that mentioned it in the Orbiter.cfg. I have no clue what EnergyConfigurator is, but I renamed it anyways. However, any scenario with a DGIV in it, or select other ships, CTD with no apparent cause. Having any scenario with a DGIV in it CTD is pretty annoying, so it would be great if it could be fixed.

 

[IronRain]

Removed Bomb mfd by deleting the line in orbiter.cfg...? You need to delete it from Modules>plugin.

 

[Face]

Ok, BombMFD was a MFD that I had installed a long time ago, but I uninstalled it. I removed the line that mentioned it in the Orbiter.cfg. I have no clue what EnergyConfigurator is, but I renamed it anyways. However, any scenario with a DGIV in it, or select other ships, CTD with no apparent cause. Having any scenario with a DGIV in it CTD is pretty annoying, so it would be great if it could be fixed.

If the log shows no strange module activated anymore, and if the only CTD producers are DGIV scenarios, I'd say your DGIV installation is somehow broken. Try to (re)install the newest DGIV distro from Dan's place. If that fails, I'd report it in Dan's forums.

@IronRain: I had similar effects with unloadable modules. If you have the entry in the Orbiter.cfg, but no loadable module, you don't get the listing entry in the dialog, but the entry in the log.
Try it for yourself: edit the Orbiter.cfg, find the ACTIVE_MODULES lines, add an arbitrary name there (e.g. dummy). If you start Orbiter now, you will not get an entry in the modules tab, but a message in Orbiter.log on starting a scenario. No matter what you do in the GUI, the entry persists. You can only get rid of it by means of text-editing the config file.

I don't think it is important here, though, just a minor cosmetic issue.

regards,
Face

 

[IronRain]

Sorry, I thought he tried uninstalling the mfd in the orbiter.cfg but not really physically Misreading from my side