Hi all

Not sure if this is a sim connect problem or not

so appologies if it should have gone there

 

I had a perfectly working UT2 until this morning
I was playing around with simconnect,trying to get something else to work and as part of that I had to adjust the exe file found in the users, app data, roaming, Microsoft, fsx directory
it currently looks like this
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
    <Name>Couatl</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>fsdreamteam\couatl\couatl.exe</Path>
</Launch.Addon>
<Launch.Addon></Launch.Addon>
<Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>UT2</Name>
    <Path>C:\Flight simulator X\\Flight One Software\Ultimate Traffic 2\UT2Services.exe</Path>
<NewConsole>True</NewConsole>
<Launch.Addon>
</SimBase.Document>

Unfortunatly I forgot about making a backup of this file,and now I have no UT2.
I have also been playing around with the simconnect.xml file but as I had changed this and then run fsx I still had UT2 at that point so I don't think that has caused the problem
I'm now totally lost I've put it all back to how I think it was but I can't get UT2 to work
Can anyone help get it working again or am I going to have to do a complete uninstall and reinstall (please don't say I do

Thanks

update when I run ut2 control panel I get this pop up box first
The launch Addon start tag on line 20 does not match the end tag of sim base document .line21 post 3
it then starts

 

 

<Path>C:\Flight simulator X\\Flight One Software\Ultimate Traffic 2\UT2Services.exe</Path>

 

It looks to me light you have an extra \ in there preventing the program from starting up.
 

Yea I thought so too but tried that and still had no joy

thanks anyway

<Launch.Addon></Launch.Addon>

Just above the UT2 entry in your exe.xml, you have <Launch.Addon></Launch.Addon>>>>>delete this double entry

 

Also may I suggest you download Notepad +. Good for editing xml files etc, and will keep formatting in place http://notepad-plus-plus.org/

Thanks Julian

unfortunately no joy still won't work

Thanks Julian

unfortunately no joy still won't work

Is the UT2 entry still in your FSX.cfg Pete ? simobjects.... ? DLL.XML ok? Am wondering if UT2 is not liking the port in simconnect, hard to say though.

When UT2 does not launch, I go into the UT options and change the traffic density from 100% to 95% .  Then I relaunch and for some reason the traffic comes back.

You've said what the answer is, but the trees are stopping you from seeing the forest? Line 20 does not match, in XML-speak! You have sets of <Launch.Addon></Launch.Addon> that contain instructions between them that are read. How many of each of those two do you have?

 

When you get that # for each, the light will come on and you will think line 20 might want to read "</Launch.Addon>"???

Thanks all guys

bit more info on this now,seems all very strange but I eventually found an old backup of the exe.xml file.Now the strange thing is the only difference between this and the current failing exe is that the current failing has entries for couatl,as I have some fsdt airports installed .

At no point when I was playing around with the exe file did I touch any of the entries to do with couatl but when I ran this old backup file by renaming it UT2 started to work!!!!

I thought  great put the couatl entries back in and its back to normal,but nope failed again

I've tried moving the couatl entry above and below the ut2 entry it fails on both occasions,take it out and it works.

fsx runs normally as far as I can tell,but don't know yet what the implication of not having the couatl lines will have,but I'll keep looking

Well I eventually got it working again

thanks meshman I eventually saw the forest!! however it still didn't work

but reinstalling the couatl addon manager to the exe.xml sorted it out,the only thing I can think that was causing it was another file somewere that was linked  to the exe file???

 

any way thanks all for your help everyone ( a current working backup has now been made)

 

rgds