Problem Weird XR series CTD after installing Velcro Saturns/Dg Launcher

[Mantis]

I am having an extremely weird problem with Orbiter and a couple of addons and I hope someone can shed some light on the issue for me. I am running Orbiter 2010 but I am pretty certain that the same thing happened with 2006. I've found that if I install either the Velcro Saturns or the DG Launcher (also uses velcro), it kills the XR series of addons. If I try to launch a scenario with an XR1, XR2 or XR5 I get an immediate CTD but there are no errors present in the orbiter log. The Velcro addon in question works fine. The standard Velcro rockets release works just fine and so does the Velcro EELV addon. I've even tried installing the Velcro Saturns and disallowed any file over-writes and it still happens. I've duplicated this problem on three different computers now as well. Here's how to duplicate the problem:

1) Install Orbiter 2010
2) Install Orbiter Sound 3.5
3) Install the XR series of addons
4) Install UCGO/UMMU
5) Run Orbiter and launch an XR scenario - it'll load just fine.
6) Install Velcro Rockets
7) Run Orbiter and launch a Velcro scenario - it'll work fine. Launch an XR scenario and it'll work fine.
8) Install Velcro Saturns and/or the DG Launcher.
9) Launch a Velcro Saturn or DG Launcher scenario and it'll work fine. Launch an XR scenario and you'll get a CTD.

I've tried that procedure except that when installing the Saturns/DG Launcher, I refuse to allow file over-writes and the result is exactly the same.

This is driving me nuts! Does anyone have any ideas?

 

[garyw]

Do you have any 0 byte config files in the config directory? ESPECIALLY those related to the XR series?

O-F Staff Note: Changed topic to something a little more meaningful.

 

[Wonderer]

Shouldn't you install ummu before the xr vessels?

 

[Woo482]

Doesn't really matter when you install it as long as it is installed, though it makes more sense to do it before.

 

[dbeachy1]

I've found that if I install either the Velcro Saturns or the DG Launcher (also uses velcro), it kills the XR series of addons.

Based on the results you are seeing it is likely that another add-on is corrupting program memory, causing the CTD. XR vessels use a fair amount of dynamically allocated memory, which makes them more sensitive to other add-ons corrupting memory (i.e., writing to memory they do not "own"). Unfortunately, beyond obtaining a fixed version of the add-on that causes the CTD the only other solution is to run that add-on in its own instance of Orbiter with as few other add-ons as possible in order to minimize the chances of it overwriting another add-on's allocated memory and causing a CTD.

To put it another way, memory overwrite bugs only "hurt" if the memory that was overwritten belongs to another add-on. So the more memory a given add-on allocates, the more likely it is to be the victim of a different add-on's memory bug.

 

[Mantis]

I checked the config files and there are no zero byte config files present. I tried re-installing the UCGO, UMMU, XR Series addons with no effect. It seems like something in Velco Saturns/Deltaglider Launcher is "poisoning" something in the XR Series. I'm going to try copying over the folders from the Velcro Saturns addon one at a time to see if I can narrow down where the problem is.

---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------

Based on the results you are seeing it is likely that another add-on is corrupting program memory, causing the CTD. XR vessels use a fair amount of dynamically allocated memory, which makes them more sensitive to other add-ons corrupting memory (i.e., writing to memory they do not "own"). Unfortunately, beyond obtaining a fixed version of the add-on that causes the CTD the only other solution is to run that add-on in its own instance of Orbiter with as few other add-ons as possible in order to minimize the chance of it overwriting another add-on's allocated memory and causing a CTD.

To put it another way, memory overwrite bugs only "hurt" if the memory that was overwritten belongs to another add-on. So the more memory a given add-on allocates, the more likely it is to be the victim of a different add-on's memory bug.

That makes sense. I see no errors in the Orbiter log but I do see errors in the Windows application log when it happens. The error references Direct Draw.

Faulting application name: orbiter.exe, version: 0.0.0.0, time stamp: 0x4c0bf8a3
Faulting module name: DDRAW.dll, version: 6.1.7600.16385, time stamp: 0x4a5bd9b8
Exception code: 0xc0000005
Fault offset: 0x0004a174
Faulting process id: 0x1718
Faulting application start time: 0x01cb0d6bfc95eb2b
Faulting application path: C:\Program Files (x86)\Orbiter2010\orbiter.exe
Faulting module path: C:\Windows\system32\DDRAW.dll
Report Id: 45b68383-795f-11df-9a2f-40618615b1ac

 

[jinglesassy]

I crash when i am launching anything with the dg-launcher

 

[Voyager]

Just after I installed the DG Launcher XR2 vc stopped working. It has to be dg launcher.

---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------

For me, it is still buggy. Most likely all the addons. How do I upload a zip file up?