Ooopsie

[realpilotsimpilot]

Hey all, I was tempted to take a try at VATSIM and installed the voice client and then decided I didn't like so de-installed it and now several add-ons don't work. Notably here, the 747 and the MD11. (The J41 works for some reason.) I tried repair installs of both and that didn't work. The 747 issue appears to be the xml.dll problem, so I'll edit that tonight and see if that works. If not, I'll uninstall and reinstall from scratch, I guess.The MD-11, however, I can't isolate. As soon as I select the MD-11 from the list of planes, I get a CTD. Is this the same issue as the dll.xml, or is it something else? Am I better just unistalling ad re-installing? For what its worth, other add-ons that crashed and had to be fixed include: FSUIPC (registered), FSDT scenery. Not affected were the J41, Captain Sim 727, REX 2.0, GEX/UTX, UT2. Haven't checked the Citation yet. Thanks for any suggestions in advance.

[realpilotsimpilot]

Two other things: Other add-on scenery was not ruined (Fly Tampa)Could I fix this with a FSX.cfg delete/rebuild?

[fozzy]

excuse me but what "vatsim voice client" are you referring to?

[yos233]

FSInn for FSX

[realpilotsimpilot]

Correct. FSInn. Major disaster there.

[Tabs]

Doug, send your dll.xml to me in a support ticket.

[fozzy]

Fsinn isn't a "voice" client. at least not only. Did you install the correct version for your OS and did you follow the VATSIM forums sticky post for problem resolution? Anyway I'd like to have some extra info about the problems which occured during unistall. (Tabs maybe you could provide some insight on what happens? - i'll send you a PM anyway)Thanks, Luca

[BillC]

You need to remove the section regarding FSCopilot from your DLL.XML . That's the only thing that FSInn adds to your dll.xml. It should be the last section in the file, if it isn't (or wasn't) then that can lead to all sorts of problems by itself.

[realpilotsimpilot]

Ryan, thanks. I sumbitted a ticket with my file, but I think I found an old version of the file backed up and mad an attempt to fix it. All you aircraft seem to be working normally now. But, a second set of eyes would be appreciated. For those who wonder what happened: I decided to try online flying, tried SB but it kept telling me it wouldn't install for for FSX for some reason (which apparently it does work, but sometimes is flakey on install), so I tried FSInn. Wasn't happy, so I deleted it (and the copilot program) and then the problems started. As best I can tell it deleted much of the dll.xml file. My troubleshooting seems to indicate that any program that doesn't automatically fire on its own (like REX or UT2), or isn't landclass or scenery (GEX/UTX/FlyTampa) that doesn't make changes to the file was fine, as were add-on aircraft that didn't really use it (CS 727). Anything that relied on the file to operate in the background and use a pull down menu (FSDT/FSUIPC/PMDG) bricked. I reinstalled FSUIPC and FSDT add-on manager and everything was fine there. I was just trying to avoid re-doing all the pmdg products, and liveries, and FS2Crew, etc., etc. I might try Squawk Box again sometime later after I'm sure I've fixed all this.