XR5 Addon incompatability?

[Zatnikitelman]

Does anyone know of any addon specifically that is incompatible with the XR5? I was trying to get myself re-interested in Orbiter (kick in the pants so to speak) and installed XR5 onto my CSA Orbiter which has numerous addons mostly station modules from Mustard's site, the CEV/CaLV addon by Francisdrake, Simcosmos and others and Sputnik's CVEL Titans 1.34.
I've tried running the default XR5 scenarios and they run fine on a cleaner installation with only my CLB development stuff, but any scenario with XR5 in my CSA installation CTDs when loading with no clues in the Orbiter log file.
Thanks for any help!
Zat

 

[RangerPL]

XR-class vessels require UMMU. Is it installed?

If not, then: http://orbiter.dansteph.com

 

[Zatnikitelman]

Yea, it's installed. I forgot to install it on another Orbiter setup and it promptly informed me that I didn't have it.

 

[dbeachy1]

I recommend a standard troubleshooting approach:

1. Install a new Orbiter instance.
2. Install OrbiterSound and UMMu.
3. Install the Vanguard.
4. Install one of your add-ons and test your installation.
5. Repeat step 4 until the problem occurs. Then remove the last add-on installed and continue until all your add-ons have been tested.

That will pin down the problem add-on(s).

 

[Zatnikitelman]

I'll try and report back unfortunately I have probably 20-40 addons on there. Could SC3 vessels be eliminated? If it can then that instantly eliminates 90% of those. I'll get to work however.

[EDIT]
I just realized that there was an error recorded in the orbiter.log file that isn't in the place I was looking.

Joystick throttle: Z-AXIS
No joystick throttle control detected
ERROR: DInput error DIERR_OBJECTNOTFOUND
       [C:SourceOrbiterOrbiter.cpp / 1624]
Module Sun.dll [API v.050206]

The error is there when I run other scenarios, but they don't CTD. I'll keep looking.

 

[Piet Barber]

i would like to add that a very useful tool for troubleshooting is to install all modules with the Generic Mod Enabler. I have found several times that it is not the incompatibility of modules that is the problem, but the order in which they are installed which can do it.

For instance, I was once flying the Ananake Tether ship, and after my DG was released, I never could turn on the thursters. I spent an afternoon tracking it down and found that it was the UMMUFA was unhappy about there being nobody on board. With the GME I was able to remove and reinstall without having to use Windows and its terrible file management.

 

[Zatnikitelman]

Thanks for all the assistance. I decided just to a fresh install using the same addons and such and it works well so I have no idea what the problem was.
Thanks everyone!

 

[Drenake]

Hi everybody, I'm new to this forum and first I want to say thanks to all programmers for all the beautiful addons you've created.

Unfortunatly, I have a probleme.

When I create a scenarios with the XR-5 Vanguard and the ESS Station from Siriusfett, it works only the first time. i.e. when I load the scenario for the first time, everything is fine, then I shut down Orbiter and I reload the same scenario (or any other scenario with ESS) and... no more ESS. When I press F3, I can still focus on it, but I don't see the station and when I go in cockpit view, I found a normal cockpit, no more UMmu interface.

I have been able to reproduce the bug on a clean installation of Orbiter 060929, UMmu 1.5, orbitersound 3.5, the XR-5 Vanguard 1.0c and Ess Station v1. I also recreated this bug with Ceres v2 also by Siriusfett.

I did a little search and what I found is that when I load a scenario with both XR5 and ESS (or Ceres), a file named "ESS.cfg" is being created in Config/Vessels, but there is nothing written in it, and when I delete this file, everything returns to normal, until I reload the scenario.

Since both station were made by siriusfett, I suspect there is an incompatibility between his addons and the XR5, but I can't be sure, I am not a programmer.

I hope I described the problem correctly and if anybody has a solution, i'd like to know plz.

 

[dbeachy1]

I did a little search and what I found is that when I load a scenario with both XR5 and ESS (or Ceres), a file named "ESS.cfg" is being created in Config/Vessels, but there is nothing written in it, and when I delete this file, everything returns to normal, until I reload the scenario.
Since both station were made by siriusfett, I suspect there is an incompatibility between his addons and the XR5, but I can't be sure, I am not a programmer.
I hope I described the problem correctly and if anybody has a solution, i'd like to know plz.

The root of the problem is that Ess Station installs its config file incorrectly: it is installed to Config\Ess.cfg instead of Config\Vessels\Ess.cfg. What happens, then, is that the Vanguard tries to open Config\Vessels\Ess.cfg in read-only mode to check for XR Payload data. The API call is:

oapiOpenFile(filename, FILE_IN, CONFIG);

...where 'filename' is Vessels\Ess.cfg. The bug (or 'feature?') in the Orbiter core is that oapiOpenFile will create an empty file if it does not exist, even if the file was opened in read-only mode. This is why an empty Config\Vessels\Ess.cfg file appears after the simulation runs once. On restart, then, the Orbiter core (correctly) checks for Config\Vessels\Ess.cfg first, and it finds an empty file so it assumes that the vessel has no DLL or mesh defined. That is why there is no Ess cockpit or mesh when Orbiter restarts.

Fortunately the fix is very simple: move Config\Ess.cfg to its correct location: Config\Vessels\Ess.cfg. You may want to drop Siriusfett a friendly note asking him to update the installation zip files to install Ess.cfg to Config\Vessels.

BTW, those stations are sweet!

 

[Drenake]

Thanks for the answer, I should now be able to put the XR5 back in my scenarios without any problem... I'll notify Siriusfett about his zip files and again, thanks a lot.

 

[cry_wolf]

i also have this problem with the xr5 vanguard. when i create a scenario with the xr5 and other modules, for example the SSBB or spacecraft 3 modules this work only the first time

 

[dbeachy1]

It sounds like the exact same problem: if an add-on vessel installs its configuration file to the wrong directory (Config\foo.cfg), the problem will occur as detailed above. The solution is two-fold:

1. Move the vessel's configuration file from the incorrect directory (Config\foo.cfg) to the correct directory: Config\Vessels\foo.cfg
2. Contact the vessel's author asking him to update his installation zip file to install the configuration file to the correct directory (Config\Vessels).