SDK Tool Box on the frits

gray eagle

gray eagle

SOH-CM-2024
I was installed a new program to P3d (GSX by FSDT) and it installed fine but since then, my FSUIPC/AI Carriers/and SDK disappeared.

I have managed to gain FSUIPC back using the DLL.XML file it created and it shows in P3d, the problem is trying to build on that DLL that FSUIPC made by addng the SDK tool box entries.
When I do, it will cause the FSUIPC to vanish from the menu screen, until I remove the SDK addon, and then revert to the ddl.xml that FSUIPC made, then FSUIPC will at least show in P3D.

Here is what the DLL.XML looks like thus far:
<?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:\Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path>
</Launch.Addon>
<Launch.Addon>

http://www.sim-outhouse.com/sohforums/showthread.php/104768-P3D-Traffic-Toolbox

If I used the one that worked before FSUIPC will disappear and Tool box won't show in P3D either.

<?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>
</Launch.Addon>


If I use the plain ol FSUIPC dll.xml that is created, FSUIPC will show in P3d:

<?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>


Fortunately, AI carriers uses a exe.xml so that one is isolated from this mess and still works.

Trying different tricks with the dll.xml with no luck

Here is path to SDK:

P:\Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll


Back to square one with getting the Traffic ToolBox to show in P3d. What is wierd, the script that worked before will nether show FSUPIC nor TT BOX. :dizzy:


EDIT: If I use this script then SDK Tool Box will work:

<?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>P:\Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK

\TrafficToolbox.dll</Path>
</Launch.Addon>
</SimBase.Document>


Edit:

It works now,


<?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>P:\Prepar3D v3 SDK 3.4.22.19868\Environment SDK\Traffic Toolbox SDK\TrafficToolbox.dll</Path>
</Launch.Addon>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
</SimBase.Document>

I figure it was the way the two programs (Launches) were joined together in one dll.xml and they were not combined properly.
I could use a separate DDL for FSUIPC (and it worked) and same for SDK toolbox then I must of combined them in a way were none of those
two programs would not launch. When combining multi launches in DLL.XML, Where one ends and one begins is confusing to me.
 
In the dll.xml, exactly as in the exe.xml, each individual thing being launched has to have a "self-containted" section. For every <Launch.Addon>, there must a </Launch.Addon>.

For example, for the Traffic toolbox entry, you will have
<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>
</Launch.Addon>

Now, if you want to have FSUIPC, you have have the entire entry, thus:
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>

You can't "combine" them. So for each and every <Launch.Addon>, there must be one </Launch.Addon>.
You can NOT have one <Launch.Addon>, then several
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
Sections, and THEN one </Launch.Addon>

Picture it as each thing you add to the file as a separate and unique entry to the file, not as something that can be combined into all one entry.
Does that help any?
Pat☺
 
PhantomTweak said:
In the dll.xml, exactly as in the exe.xml, each individual thing being launched has to have a "self-containted" section. For every <Launch.Addon>, there must a </Launch.Addon>.

You can't "combine" them.
Pat☺
Click to expand...


I think you may of misunderstood my question, Let's just rephrase the question, I wanted to MERGE them into one thus I just wanted to know where one ends and one begins.
Some of the header on the second entry (below) I would think needs trimming (Not necessary) but how much? How about the first entry? Anything need trimming on that one?

<?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>SDK\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>
</SimBase.Document>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

<?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>



Two separate DLL entries that are for two different program, you can figures out which prog they are for just by reading the names
Now, to get to the brass tacks, I simply wanted to know if I wanted to combing these two dlls into one dll, where would the first end and the second one begin.
I know that you just can't jam them together as they are,(they don't work that way) they need a bit of editing in order to COMBINE them into one - this is in essence my question.
How to as I say COMBINE them or MERGE them into one. It can be done as I have seen examples of others posted here that contain numerous programs.
I got lucky the other day and managed to get my FSUIPC AND Toolbox to work when I was combining the two, I remember trimming the header on the second one when I merged the two dlls
just wanted to know what is the cardinal rule for this process.

Hope that helps - clarify the initial question........
 
Last edited:
If I'm reading you correctly, you want to change these:

<?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>SDK\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>
</SimBase.Document>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

<?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>


into 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>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>SDK\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
</SimBase.Document>

This should do the job.

Dave
 
dhazelgrove said:
If I'm reading you correctly, you want to change these:

<?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>SDK\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>
</SimBase.Document>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

<?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>


into 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>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>SDK\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>
<Launch.Addon> <<<<<<<< is this were you attached to the first one and stripped every thing above it's entry?
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
</SimBase.Document>

This should do the job.

Dave
Click to expand...

I think I found a good explanation of how to combine two separate DLL into one over here:

http://www.prepar3d.com/forum/viewtopic.php?f=6322&t=123950

Very informative.
 
Last edited:
Dave hit the nail on the head with his example.
If you want to combine the two examples you gave into one dll.xml, Dave's example is exactly correct. It's what I've done on the occaisions I've added entries to the dll.xml, at least, and mine have always worked properly. Same methodology is also used for the exe.xml file.

Does this answer your questions, Mr. Grey_Eagle?
Pat☺
 
PhantomTweak said:
Dave hit the nail on the head with his example.
If you want to combine the two examples you gave into one dll.xml, Dave's example is exactly correct. It's what I've done on the occaisions I've added entries to the dll.xml, at least, and mine have always worked properly. Same methodology is also used for the exe.xml file.

Does this answer your questions, Mr. Grey_Eagle?
Pat☺
Click to expand...

Dave's answer didn't go into the level of detail that I was searching, sure two dll's were combined but I wanted a bit more in depth explanation.
I appreciate your and others explanations from here; To quote your question, What really answers my questions, came from a lady named "poppet" here:

http://www.prepar3d.com/forum/viewtopic.php?f=6322&t=123950


**Amen**
 
You must log in or register to reply here.
Back
Top