P3D Traffic Toolbox

gray eagle

gray eagle

SOH-CM-2025
I posted a question here http://www.sim-outhouse.com/sohforums/showthread.php/103662-Traffic-Toolbox-for-P3D_V3
but never got any response

Maybe this new thread will be noticed.

I have recently installed the P3d program and am interested as to how to solve my no show Traffic Toolbox issue. I know that there is a dll.xml that is copied over from the SDK folder to the root P3d folder
but I would like to know how to edit the xml file. MY Sdk is installed on my Drive P and so in my P3d but I installed them to their default locations except I changed the C: to P:

I figure once it is set up, where is the tool box located on the upper menu screen in P3d?

Looking for proper notations that go in the dll.xml file located in the Base P3D directory.

Thanks
 
Traffice Toolbox set up issues in P3d

I'm not having any luck trying to install traffictoolbox to my P3d V3.4 program.
Here is situation so far:

Prepar3D is installed here:

"P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\"

SDK is here:

P:\Program Files (x86)\Lockheed Martin\Prepar3D v3 SDK 3.4.22.19868

My DLL.XML file located:

C:\Users\ijdjr\AppData\Roaming\Lockheed Martin\Prepar3D v3\dll.xml


Contents:

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<Path>P:\Prepar3D v3\SDK v3.4.18.19475\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>as_connect</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp.dll</Path>
</Launch.Addon>
</SimBase.Document>


I also have FSX/A installed (On another drive) and SDK for FSX as well.
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK
The FSX version works just fine. In order for it to work, I was told that SDK for FSX had to be installed on another drive,
Is it the same requirement for P3D SDK/traffic Toolbox?
I did run ConfigSDK.exe as administrator ( I guess that was requirement?).

Any way, sure could use some help as to how to get traffic toolbox for my P3d V3.4 to show in my tools menu.
Traffic ToolBox isn't showing in Menu/Tools Dropdown in P3d V3.4
Thanks.
 
It looks like your referencing a different version of the SDK than you have installed and you need to put the full path to it in the DLL.XML
try the following.

<Path>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path>
 
Dangerous Beans said:
It looks like your referencing a different version of the SDK than you have installed and you need to put the full path to it in the DLL.XML
try the following.

<Path>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path>
Click to expand...

I had tried that trick as well and results were negative.
 
Strange thats how I have mine set and it works for me.
Heres my entry

<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>D:\Games\Flight\Programs\Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>

The only other difference I can see is you dont have <ManualLoad>False</ManualLoad> maybe its that.


You do have the same version of P3D and the SDK installed dont you ?
 
Dangerous Beans said:
Strange thats how I have mine set and it works for me.
Heres my entry

<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>D:\Games\Flight\Programs\Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>

The only other difference I can see is you dont have <ManualLoad>False</ManualLoad> maybe its that.


You do have the same version of P3D and the SDK installed dont you ?
Click to expand...

Prepar3D_v3_SDK_Setup_3.4.22.19868
P3D V3.4 3.4.22.19868

(Both Versions match)

I would like to know a little more about your dll.xml file. Where is it located?
My dll.xml is in C:\Users\ijdjr\AppData\Roaming\Lockheed Martin\Prepar3D v3

My dll has entiries for FSUIPC on it as well.

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<Path>P:\Prepar3D v3\SDK v3.4.18.19475\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path> >>>> This looks like what you have ^ I don't know how a different number got in there when I have matching numbers
</Launch.Addon>
<Launch.Addon>
<Name>as_connect</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp.dll</Path>
</Launch.Addon>
</SimBase.Document>


It originally looked like this
<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
</SimBase.Document>
 
Last edited:
Your DLL.XML entry is pointing to P:\SDK v3.4.18.19475 and you say you have Prepar3D v3 SDK 3.4.22.19868 installed so its looking for the wrong version.

your DLL.XML is in the right place so thats OK, I amuse FSUIPC is working fine, if the xml was in the wrong place that wouldnt work.

Heres my XML for comparison

<?xml version="1.0" encoding="Windows-1252"?>


<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>D:\Games\Flight\Programs\Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Visual Effects Tool</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>D:\Games\Flight\Programs\Prepar3D v3 SDK 3.4.22.19868\Modeling SDK\Special Effects SDK\visualfxtool.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>A2A Feel</Name>
<Disabled>False</Disabled>
<Path>Modules\A2A_Feel.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
<Launch.Addon>
<Name>AccuFeelMenu</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\AccuFeelMenu.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>A2A Service</Name>
<Disabled>False</Disabled>
<Path>A2A\Shared\A2A_Service.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
<Launch.Addon>
<Name>b21 vario sound control</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\b21_vario\b21_vario.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
<Launch.Addon>
<Name>Flight Recorder</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>ObjectFlow_P3D</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>D:\Games\Flight\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>XMLTools3D</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>XMLTools3D.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
<Launch.Addon>
<Name>Captain Sim Menu</Name>
<Disabled>False</Disabled>
<Path>Captain_Sim\Captain_Sim.b767.menu.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Captain Sim Menu</Name>
<Disabled>False</Disabled>
<Path>Captain_Sim\Captain_Sim.b757.menu.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Captain Sim Sound</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Captain_Sim\bin\cs.sound.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Captain Sim 707 Sound</Name>
<Disabled>False</Disabled>
<Path>Captain_Sim\707\cs.sound.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Captain Sim 520 Menu</Name>
<Disabled>False</Disabled>
<Path>Captain_Sim\520\cs.sound.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Carenavigraph</Name>
<Disabled>False</Disabled>
<Path>.\Carenavigraph.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>as_connect</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp.dll</Path>
</Launch.Addon>
</SimBase.Document>
 
My SDK is Prepar3D v3 SDK 3.4.22.19868

Prepar3D_v3_Academic_3.4.22.19868

They both have matching numbers.

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<Path>P:\Prepar3D v3\SDK vPrepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path>
</Launch.Addon>
<Launch.Addon>


Still no workie.....
 
According to your DLL.xml, your path says the SDK is inside your main P3D folder, which it shouldn't be. My main P3D folder is in D:\Lockheed Martin\Prepar3dv3 My SDK is in D:\Lockheed Martin\ Prepar3D v3 SDK 3.4.22.19868. If you have them both on P: try deleting Prepar3D v3 out of the path./Russell|
 
smoky942 said:
According to your DLL.xml, your path says the SDK is inside your main P3D folder, which it shouldn't be. My main P3D folder is in D:\Lockheed Martin\Prepar3dv3 My SDK is in D:\Lockheed Martin\ Prepar3D v3 SDK 3.4.22.19868. If you have them both on P: try deleting Prepar3D v3 out of the path./Russell|
Click to expand...

Both P3d and SDK are located under Program Files (X86) Lockheed Martin under their own separate folders. SDK is not within the P3d Folder.


So, to summarize, they both go to Lockheed Martin folder then branch out to their separate folders.

P:\Program Files (x86)\Lockheed Martin\Prepar3D v3

P:\Program Files (x86)\Lockheed Martin\Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK
 
OK, but the path you have is not telling the computer to look in the correct place, it's telling it to look on P: for Prepar3Dv3, then look inside that for the SDK. It needs to say, folder by folder exactly where the SDK is located.


<Path>P:\Prepar3D v3\SDK vPrepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path>

Alter that line to...<Path>P:\Program files(x86)\Lockheed Martin\ Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path>

That should work if the SDK is where you just said.

/Russell.
 
smoky942 said:
OK, but the path you have is not telling the computer to look in the correct place, it's telling it to look on P: for Prepar3Dv3, then look inside that for the SDK. It needs to say, folder by folder exactly where the SDK is located.


<Path>P:\Prepar3D v3\SDK vPrepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path>

Alter that line to...<Path>P:\Program files(x86)\Lockheed Martin\ Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path>

That should work if the SDK is where you just said.

/Russell.
Click to expand...


I've changed this to read:


<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<Path>P:\Program files(x86)\Lockheed Martin\ Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>as_connect</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp.dll</Path>
</Launch.Addon>
</SimBase.Document>



Still no joy.
 
Mmm, tricky devils these DLL.XML. The only difference between yours and mine, I note, is the absence of this line <ManualLoad>False</ManualLoad> Try putting that line straight after <Disabled>False</Disabled> and see if that does the trick. If that doesn't work, then maybe it's because you have P3D in Program files (X86). I was told to never put the flight sim in Program files (X86) because of possible permissions problems. I have no idea whether that is true or not.


/Russell
 
smoky942 said:
Mmm, tricky devils these DLL.XML. The only difference between yours and mine, I note, is the absence of this line <ManualLoad>False</ManualLoad> Try putting that line straight after <Disabled>False</Disabled> and see if that does the trick. If that doesn't work, then maybe it's because you have P3D in Program files (X86). I was told to never put the flight sim in Program files (X86) because of possible permissions problems. I have no idea whether that is true or not.


/Russell
Click to expand...

I changed per your suggestion
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>False</Disabled><ManualLoad>False</ManualLoad>
<Path>P:\Program files(x86)\Lockheed Martin\ Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>as_connect</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp.dll</Path>
</Launch.Addon>
</SimBase.Document>

It still don't work. It wants to install to a Program files (86) location so all I did was change the C to a P drive and left the rest intact.
I think I did try a Program Files (With out the 86) and had no luck with that either.

Here is what P3d says about installing SDK

http://www.prepar3d.com/SDK/Environ...+Kit/Traffic+Toolbox+SDK/Traffic+Toolbox.html
 
I'm sorry grey eagle, but I'm out of ideas. I was told way back in the early FSX days to keep away from installing into Program files (X86) so always have. I make a folder direct onto my D drive, name it Lockheed Martin, then install P3D and the SDK into that. It's always worked flawlessly. One last long shot. I assume to edit the DLL.XML you right click, then choose edit from the drop down menu. When you've done that, do you left click it to see if it opens correctly ?. I ask because I had a problem a long time ago where, after editing, the bloody thing wouldn't work. Just one dot or dash missing or out of place stops the DLL.XML from opening (and working) in it's normal black and red print. Probably not the case, but worth checking.

/Russell.
 
@ grey eagle

Since already my FSX times, and having read on various sites recommendations about that, I do not install my flight simulator and related programs inside Windows stock folders - Programs (x86) or Programs - due to the security controls on these particular folders by the OS.
Any way, if you have everything already installed in those folders, please make sure you have set the .exe files to be run as administrator, might ease the security control matter.
I have not made a backup of a P3D clean install since version 3.9, but in this version, there is already a traffictoolbox.dll file in my backup of this clean install.
Inside my latest P3D, I also have a traffictoolbox.dll reporting version number 3.4.22.19868, and this is the version my dll.xml file is calling.
Quote
<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>F:\Lockheed Martin\Prepar3D v3\traffictoolbox.dll</Path>
</Launch.Addon>
Unquote

Possibly you can give a try to calling the dll file located directly inside P3D?

Hope this helps
Philippe
 
It works

I reinstalled SDK to the root dir and named it Lockheed Martin and below is my xml file that shows path I used. :encouragement::untroubled:
Don't think it liked the Program Files(86) location....



<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>False</Disabled><ManualLoad>False</ManualLoad>
<Path>P:\Lockheed Martin\Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path> <<<<<< Notice the new path?
</Launch.Addon>
<Launch.Addon>
 
Last edited:
Good to know you have left the "dark side" and other computer gremlins area.
What I was meaning is that both named windows folders are more controlled about read/write rights than other folders, which might prevent some applications to work without troubles.
Blue skies and nice flights!
 
You must log in or register to reply here.
Back
Top