Bug XR dialogue error

[Brycesv1]

for some reason lately if i add any of the XR ships with the scenario editor it keeps spamming "nose cone closed" warnings at me. if im flying it stops but as soon as i cut the engines it starts yelling at me again. anyone know why?

 

[dbeachy1]

That callout occurs when the XR vessel is within 100 meters of another vessel and the distance between the two vessels has decreased since the previous frame. If you're getting that all the time then something weird is going on. I recommend a standard troubleshooting approach:

1. Install a clean instance of Orbiter to a new directory.
2. Install OrbiterSound.
3. Install UMMu.
4. Install the XR1.
5. Load up a default scenario and see if the problem occurs (which it shouldn't).
6. Install one of your other add-ons and test again. If it fails, you've found the problem add-on.
7. Repeat step 6 until the problem occurs.

 

[Brycesv1]

it doesnt happen on default scenarios. only ones where iv edited the XR vessel into the scenario. in this particular instance i had copied the location from a DGIV before i moved the XR over a few hundred feet to the runway. Orbiter was also paused while i edited it in. do u think this may have effected how the scripts are run? maybe because they are initialized within 100 feet of the other craft it sets that as a default? i have no idea

 

[dbeachy1]

Orbiter was also paused while i edited it in. do u think this may have effected how the scripts are run? maybe because they are initialized within 100 feet of the other craft it sets that as a default?

No, all that matters is the state of the vessels after Orbiter is unpaused and running. One more condition I forgot to mention: In addition to the previous two conditions, you must have one of your XR vessel's NAV radios tuned into a target vessel's IDS or XPDR. To clarify, here is how the XRs decide which vessel to use for docking callouts:

1. Check the first of the XR vessel's NAV radio frequencies and check if any docking ports on any vessels exist in the sim with that IDS frequency (for example, 137.4 MHz on the ISS). If found, compute its distance from the XR's docking port and save it.
2. Repeat step 1 for all four NAV radios. If one or more target vessels found, use the closest vessel as the target docking vessel.
4. Otherwise, since no target docking ports were found with those IDS frequencies, repeat step 1 but this time check for other vessels using those XPDR frequencies.
5. If one or more target vessels found, use the closest vessel.
6. If there are still no vessels found, don't perform docking callouts (i.e., none of the XR's NAV radios are tuned to any other vessel's IDS or XPDR frequencies).
7. Otherwise, since we found the closest docking candidate vessel, check the docking distance to the target vessel and perform the callouts (and "docking port is closed" warnings) if 1) the vessel is within 100 meters of the XR's docking port, and 2) the vessel has moved closer to the XR vessel's docking port since the last frame.

So to summarize, your NAV radios determine which vessel will be targeted for docking distance callouts, and even then only if the vessel is within 100 meters of your ship and you are approaching it. If you are getting constant callouts it sounds like one of your NAV radios is tuned to a nearby vessel and that vessel with within 100 meters and your vessel is approaching that vessel.

In any case, if you can post your problem scenario (please remember to use [ CODE ] tags), I can take a look here.