dll.xml changes by itself?

[dolph98]

Hi,

I am using FSUIPC 4.853 and am flying using the VRS TacPack open beta. These are the only two entries I have in my dll.xml file:

<Launch.Addon>

<Name>VRS_TacPack</Name>

<Disabled>False</Disabled>

<Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FSUIPC 4</Name>

<Disabled>False</Disabled>

<Path>Modules\FSUIPC4.dll</Path>

</Launch.Addon>

Upon closing FSX I get a stack_hash error if FSUIPC is loaded first. This does not interfere with my flight sim enjoyment but I just don't want the error. So I found that by putting the TacPack entry first, the error goes away. But after flight, FSUIPC is again first in the list and I get the stack_hash again.

Question: Is there some reason FSUIPC needs to be first to load and is it changing the file automatically? If not, any idea what is changing it? Is FSX doing it? (okay, that's three questions...)

BTW, VRS has it on their list of things to fix eventually, it appears that Tac_Pack does not quite clean up after itself and causes this stack-hash on some PCs. It's not a bug per se, but it bugs me.

Thanks in advance.

[Gypsy Baron]

Hummm....my dll.xml has FSUIPC4 as the last entry and it has been that way forever. I suspect that perhaps the TacPac app

might be manipulating the dll.xml to place itself last. FSUIPC4 certainly would not be doing that.

Paul

[Pete Dowson]

Upon closing FSX I get a stack_hash error if FSUIPC is loaded first. This does not interfere with my flight sim enjoyment but I just don't want the error. So I found that by putting the TacPack entry first, the error goes away. But after flight, FSUIPC is again first in the list and I get the stack_hash again.

Question: Is there some reason FSUIPC needs to be first to load and is it changing the file automatically? If not, any idea what is changing it? Is FSX doing it?

As Paul says, it must be TacPack doing it. FSUIPC itself doesn't touchit at all -- only its Installer amends the DLL.XML file, and that always puts FSUIPC4 last.

Try making the DLL.XML read-only. That may work, or it may just make the failure change its reported cause. If you do this and it works, remember to temporarily change it back when installing other add-ons which may want to update it.

Regards

Pete

[dolph98]

Ok, thanks guys. Pete, I will do as you suggest and try making it RO for now. Maybe the culprit will fail and propogate an error to some level I can see what is doing it.