Installed UT2 into P3Dv3 using the EMT and following instructions online.  I get my AI traffic in P3Dv3 with no issues, but when I launch UT2 I get the following errors:

 

 

When I try to edit the repaints i get the following error code:

 

See the end of this message for details on invoking 

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.ArgumentOutOfRangeException: InvalidArgument=Value of '0' is not valid for 'SelectedIndex'.

Parameter name: SelectedIndex

   at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)

   at (Object , Int32 )

   at ..()

   at ..(String )

   at ..(Object , MouseEventArgs )

   at System.Windows.Forms.Control.OnMouseClick(MouseEventArgs e)

   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8669 (QFE.050727-8600)

----------------------------------------

UltimateTraffic2

    Assembly Version: 2.9.0.0

    Win32 Version: 2.9.0.0

----------------------------------------

System.Windows.Forms

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------

System

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------

System.Drawing

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8663 (QFE.050727-8600)

----------------------------------------

Microsoft.VisualBasic

    Assembly Version: 8.0.0.0

    Win32 Version: 8.0.50727.8662 (QFE.050727-8600)

----------------------------------------

System.Xml

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------

System.Runtime.Remoting

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------

System.Configuration

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------

System.Data.SQLite

    Assembly Version: 1.0.65.0

    Win32 Version: 1.0.65.0

----------------------------------------

System.Data

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------

System.Transactions

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------

{92b4f56c-8992-46b6-9774-f0799fa6ca8c}

    Assembly Version: 0.0.0.0

    Win32 Version: 2.9.0.0

----------------------------------------

System.ServiceModel

    Assembly Version: 3.0.0.0

    Win32 Version: 3.0.4506.8674 (QFE.030729-8600)

----------------------------------------

System.EnterpriseServices

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------

System.Core

    Assembly Version: 3.5.0.0

    Win32 Version: 3.5.30729.8674 built by: QFE

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

 

I have seen that error can be caused by a .cfg file with a missing "ui_variation" line.  I have removed all of the defult aircraft, AI Aircraft and UT2 aircraft folders one by one, removing them from the SimObjects .cfg files and it doesn't fix the issue.

 

At this point I don't know what to do.  Should I just attempt a clean P3Dv3 install and immediately install UT2 after that?

 

Any help would be appreciated.

After a clean re-install I can now edit my aircrafts in UT2, except it is not seeing ANY other folders in the SimObjects folder, including my AI Aircraft folder that was added to the simobjects.cfg file.

 

After my re-install the exe.xml and simobjects.cfg files are not in the appdata/roaming/p3d folder.  I was able to make a new simobjects.cfg, but am missing the exe.xml file.

 

Any ideas and could that be the reason why the other simobjects aren't appearing in UT2?

 

AI is showing in P3Dv3 now with no issues.

 

EDIT:

After adding a new FP using Power Pack, UT2 now CTD when I launch it.  I seriously don't know what to do here.  No one else using it with P3Dv3 seems to be having these problems.

Rob,

 

Are you saying that you only see the UT2 aircraft when you access the Repaints section of the UT2 utility software? If so, then you need to add another SimObjects statement to your Prepar3D.cfg file. There should be one in there with respect to the UT2 aircraft folder, and you need to add another one that points to your AI Planes folder. The UT2 one should be ".0", and your AI planes one needs to be ".1". Sorry that I can't be more specific, but I am at work at the moment!

 

I have no idea if this will solve your CTD problem, but it's just possible that this is happening because UT2 can't find your AI planes folder until you have done the above.

Rob,

 

Are you saying that you only see the UT2 aircraft when you access the Repaints section of the UT2 utility software? If so, then you need to add another SimObjects statement to your Prepar3D.cfg file. There should be one in there with respect to the UT2 aircraft folder, and you need to add another one that points to your AI Planes folder. The UT2 one should be ".0", and your AI planes one needs to be ".1". Sorry that I can't be more specific, but I am at work at the moment!

 

I have no idea if this will solve your CTD problem, but it's just possible that this is happening because UT2 can't find your AI planes folder until you have done the above.

Yes, I'm only seeing the UT2 aircraft.  In FSX, I would see all of the aircraft that was in the SimObjects folder.  I did add a new line to the simobjects.cfg for the AI Folder, didn't know I needed to as well for the P3D.cfg, I will check it out when I get home today.  Thanks!

I didn't know that I had to add another line either! I just guessed, and it worked!

How did you install UT2?  Did you use the EMT?  Every time I launch UT2 after being installed it asks for the FSX.CFG and FSX.EXE file.  

I installed it manually using (I think) some instructions that I found on YouTube. I do remember having a bit of a problem when first trying to run the UT2 utility, but I managed to sort it out. The problem is that I am not exactly sure how I did it. I really wish that I had recorded it step by step