• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning

SDK Install Issue

F

FSX68

Banned
I've installed SDK and I do not see the tools menu/bar on the main screen.

I used the default path for the SDK install (Drive C).
I used the rules from http://www.fsdeveloper.com/wiki/index.php?title=SDK_Installation_(FSX)

I use win 7 64 bit OS. I have FSX Acceleration installed.
FSX is on Drive E:

here is the ddl.xml contents (Toolbox):

ADE Check report:
*************************************************************************************************
Date of Report: 5/28/2013 7:59:12 AM
Operating System: Microsoft Windows 7 Home Premium
OS Service Pack: n/a
OS Version: 6.1.7600 (64 Bit)
OS Language: English (United States) => separator: '.'
Nodename: IJDJR-PC
ADE installed: yes
ADE Path: C:\MSFS\FS Design Tools\Airport Design Editor 9x
ADE Install Version: 1.55.4805.28665
ADE File Version: 1.55.4805.28665
ADE Info: Airport Design Editor 9x Version 1.55.4805.28665
FXS installed: yes
FSX Path: E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\
FSX Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)
FSX Trailing '\' Error: False
FX9 installed: no
FS9 Path: n/a
FS9 Version: n/a
FS9 Trailing '\' Error: False
RTM Simconnect: yes
SP1 Simconnect: yes
SP2 Simconnect: yes
FSX SDK installed: yes
FSX SDK Path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\
FSX SDK Trailing '\' Error: False
BGLComp Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)
BGLComp >= SP1: yes
Shp2Vec found: yes
.NET 1.1 installed: no
.NET 2.0 installed: yes
.NET 3.0 installed: yes
.NET 3.5 installed: yes
XML3 installed: yes
XML4 installed: yes
XML5 installed: yes
XML6 installed: yes
FSUIPC/FS9 installed: n/a
FSUIPC/FSX installed: 4.90
Connected to FS9 ok: no
Connected to FSX ok: yes


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

..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll
</launch.addon>
</simbase.document>

I have a hunch that there is a short in the system where SDK is not pointing to FSX but I did a config sdk check and
I also did FSX and SDK ADE Check; that checks OK.

Usually, if one adds things to FSX i.e. FSUUIPC or other items (I think SDK also) I would get the OK to run/accept signature. I did not get it so it
doesn't show up in the top menu bar of FSX while in flight.

Looking for some troubleshooting suggestions......:icon35:
 
Hi Folks

FSX68 said:
Looking for some troubleshooting suggestions......
icon35.gif
Click to expand...
FSX68 -
Please, if you've problems with the instructions,
then post your issue over at FSDeveloper.



FSX68 said:
I have a hunch that there is a short in the system where SDK is not pointing to FSX
but I did a config sdk check
and I also did FSX and SDK ADE Check;
that checks OK.
Click to expand...

Correct on your hunch.

Incorrect on -
- Assuming configsdk is some kind of check.
- Assessing your check results.



dll.xml is read in the context of FSX.

It tells FSX where to find bits,
and then what to do with them.



In your case,
from the snippet you've posted, (forum mangled),
dll.xml is telling FSX,
that the SDK is on the same drive as FSX.



As per the associated SDK Installation (FSX) - Troubleshooting article-
3 Configuration

If you had installed both FSX & SDK to their default locations,
a quick indicator that the SDK is correctly installed,
the OPT should now be available from the FSX in-game Tools menu.

If you had installed either FSX, or the SDK, to a non-default location,
you must run configsdk.exe from the SDK's root folder.
N.B.
Running configsdk.exe will only correct the registry paths.
It will not update/correct the user's dll.xml file, (see FSX in-game Tools menu below).
Click to expand...

snipped to below

4.2.3.2.2 SDK Non-Default Installation Location
If either FSX or the SDK is installed to a non-standard location
then use a full path (aka absolute path). e.g.
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\Object_Placement.dll


If you'd installed the SDK to your F: drive,
then the full path would be:
F:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\Object_Placement.dll
Click to expand...



HTH
ATB
Paul
 
BASys said:
Hi Folks


FSX68 -
Please, if you've problems with the instructions,
then post your issue over at FSDeveloper.





Correct on your hunch.

Incorrect on -
- Assuming configsdk is some kind of check. <<< I was not inferring that is was a check. I know its purpose!!!!!
- Assessing your check results.



dll.xml is read in the context of FSX.

It tells FSX where to find bits,
and then what to do with them.



In your case,
from the snippet you've posted, (forum mangled),
dll.xml is telling FSX,
that the SDK is on the same drive as FSX.



As per the associated SDK Installation (FSX) - Troubleshooting article-


snipped to below





HTH
ATB
Paul
Click to expand...

From your original reply
3 Configuration

If you had installed both FSX & SDK to their default locations,
a quick indicator that the SDK is correctly installed,
the OPT should now be available from the FSX in-game Tools menu.

If you had installed either FSX, or the SDK, to a non-default location,
you must run configsdk.exe from the SDK's root folder. <<<< Dude, I did this before!!!!!
:ipepsi2:
Running configsdk.exe will only correct the registry paths. >>>> I also know this.
It will not update/correct the user's dll.xml file, (see FSX in-game Tools menu below). <<<< I kind of figured that out.
 
If I remember correctly there are two SDK's one on the FSX disk and one for acceleration on the accel disk if you install the wrong one it won't show up(had the same issue myself) that's about all I can think of sorry. If you are using the accel SDK then you can check below and compare your dll and see if all the <launch>junk is in the right place.

<Launch.Addon><name><Name>Object Placement ToolName></name><disabled><Disabled>FalseDisabled></disabled><manualload><ManualLoad>FalseManualLoad></manualload>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dllPath>Launch.Addon><launch.addon><Launch.Addon><name><Name>Traffic ToolboxName></name><disabled><Disabled>FalseDisabled></disabled><manualload><ManualLoad>FalseManualLoad></manualload>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dllPath>Launch.Addon></launch.addon><launch.addon><Launch.Addon><name><Name>Visual Effects ToolName></name><disabled><Disabled>FalseDisabled></disabled><manualload><ManualLoad>FalseManualLoad></manualload>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dllPath>Launch.Addon></launch.addon><launch.addon>

Sorry copy/paste came out kind of goofy</launch.addon></launch>
 
Because FSX is not in the default C: drive the paths in the dll.xml must be complete such as:

<Path>E:\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dllPath>

with path being the actual path you have FSX set to on the E: drive.
 
Hi Folks

Sorry for the delay,
the forum was offline for maintenance
when I tried to submit this reply originally.



gradyhappyg -
FSX68 has already installed the appropriate SDK SP version,
which matches his FSX game SP version.



FSX68 -
FSX68 said:
I did a config sdk check and
I also did FSX and SDK ADE Check; that checks OK.
Click to expand...
From your followup reply,
I'm guessing you might have mean't check, as in ticked the box.

Two nations divided by a common language.
Click to expand...
:icon_lol:



You'd said -
FSX68 said:
I used the rules from http://www.fsdeveloper.com/wiki/index.php?title=SDK_Installation_(FSX)
Click to expand...
but were still having problems,
thus inferring that the instructions at FSDev were inadequate.



Unfortunately you'd missed the key aspects
contained in the linked to, related SDK Installation (FSX) - Troubleshooting article.

In my reply -
rather than me just saying go read the troubleshooting article, :icon_lol:
I'd quoted those relevant aspects directly from the SDK Installation (FSX) - Troubleshooting article
specifically so that any future visitor with the same issue,
whose search had pulled up your thread
could read the answer here, without them having to visit FSDev.



re: troubleshooting suggestions -
My reasoning for asking you to post at FSDev,
was that if you believed there were problems with the content of the SDK Installation instructions,
your feedback to that forum, would aid improve those article's instructions.



Back to your FSX problem -
SDK Installation (FSX) - Troubleshooting article said:
4.2.3.2.2 SDK Non-Default Installation Location
If either FSX or the SDK is installed to a non-standard location
then use a full path (aka absolute path). e.g.
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\Object_Placement.dll


If you'd installed the SDK to your F: drive,
then the full path would be:
F:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\Object_Placement.dll
Click to expand...

You'd chosen to install FSX to a non-standard location.

You therefore need to edit your dll.xml
to change all occurences for your SDK's current relative path,
to incorporate the full path to your SDK.

e.g.
from - ..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll
to - C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll



HTH
ATB
Paul
 
mmann said:
Because FSX is not in the default C: drive the paths in the dll.xml must be complete such as:

<Path>E:\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dllPath>

with path being the actual path you have FSX set to on the E: drive.
Click to expand...

Tried that and no Joy!!

<?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>E:\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>
</SimBase.Document>

Now I assume that you mean to edit the dll.xml in the traffic toolbox folder yes? I used notepad to make the edits.
 
Hi Folks

FSX68 -
Your SDK is on your C drive.
FSX SDK Path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\


BASys said:
dll.xml is read in the context of FSX.

It tells FSX where to find bits,
and then what to do with them.
Click to expand...

BASys said:
You'd chosen to install FSX to a non-standard location.

You therefore need to edit your dll.xml
to change all occurences for your SDK's current relative path,
to incorporate the full path to your SDK.

e.g.
from - ..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll
to - C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll
Click to expand...

HTH
ATB
Paul
 
BASys said:
Hi Folks

Sorry for the delay,
the forum was offline for maintenance
when I tried to submit this reply originally.



gradyhappyg -
FSX68 has already installed the appropriate SDK SP version,
which matches his FSX game SP version.



FSX68 -

From your followup reply,
I'm guessing you might have mean't check, as in ticked the box.

:icon_lol:



You'd said -

but were still having problems,
thus inferring that the instructions at FSDev were inadequate.



Unfortunately you'd missed the key aspects
contained in the linked to, related SDK Installation (FSX) - Troubleshooting article.

In my reply -
rather than me just saying go read the troubleshooting article, :icon_lol:
I'd quoted those relevant aspects directly from the SDK Installation (FSX) - Troubleshooting article
specifically so that any future visitor with the same issue,
whose search had pulled up your thread
could read the answer here, without them having to visit FSDev.



re: troubleshooting suggestions -
My reasoning for asking you to post at FSDev,
was that if you believed there were problems with the content of the SDK Installation instructions,
your feedback to that forum, would aid improve those article's instructions.



Back to your FSX problem -


You'd chosen to install FSX to a non-standard location.

You therefore need to edit your dll.xml
to change all occurences for your SDK's current relative path,
to incorporate the full path to your SDK.

e.g.
from - ..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll
to - C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll



HTH
ATB
Paul
Click to expand...

I did edit to the traffic toolbox dll.xml and it still does not show in FSX

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

<simbase.document type="Launch" version="1,0">
<launch.addon>
<!--?xml version="1.0" encoding="Windows-1252"?-->

<!--?xml version="1.0" encoding="WINDOWS-1252"?--><!--?xml version="1.0" encoding="WINDOWS-1252"?-->
<simbase.document version="1,0" type="Launch"><launch.addon>
</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>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>
</SimBase.Document>

</launch.addon></simbase.document>

I had tried to install the two sdk files from my Accel DVD but that are so slow that I just copied them from the DVD to my hard drive and installed them from the HD. Hope that didn't
make a difference.
 
gradyhappyg said:
If I remember correctly there are two SDK's one on the FSX disk and one for acceleration on the accel disk if you install the wrong one it won't show up(had the same issue myself) that's about all I can think of sorry. If you are using the accel SDK then you can check below and compare your dll and see if all the <launch>junk is in the right place.

<Launch.Addon><name><Name>Object Placement ToolName></name><disabled><Disabled>FalseDisabled></disabled><manualload><ManualLoad>FalseManualLoad></manualload>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dllPath>Launch.Addon><launch.addon><Launch.Addon><name><Name>Traffic ToolboxName></name><disabled><Disabled>FalseDisabled></disabled><manualload><ManualLoad>FalseManualLoad></manualload>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dllPath>Launch.Addon></launch.addon><launch.addon><Launch.Addon><name><Name>Visual Effects ToolName></name><disabled><Disabled>FalseDisabled></disabled><manualload><ManualLoad>FalseManualLoad></manualload>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dllPath>Launch.Addon></launch.addon><launch.addon>

Sorry copy/paste came out kind of goofy</launch.addon></launch>
Click to expand...

There is one SDK on Disk one of FSX and two SDK files to install on the Accel DVD. The 2nd SDK on the Accel DVD will cancel out the 1st one.
How did you manage to do a cut and paste that looks like the xml file i.e the format and colors look like that in the xml editor.
I did my edits using notepad.
 
FSX68 said:
There is one SDK on Disk one of FSX and two SDK files to install on the Accel DVD. The 2nd SDK on the Accel DVD will cancel out the 1st one.
How did you manage to do a cut and paste that looks like the xml file i.e the format and colors look like that in the xml editor.
I did my edits using notepad.
Click to expand...

Just opened it with IE explorer and copied it, still didn't come out the way I wanted but better than the copy from notepad.
 
FSX68 said:
There is one SDK on Disk one of FSX and two SDK files to install on the Accel DVD. The 2nd SDK on the Accel DVD will cancel out the 1st one.
Click to expand...
You already have the correct versions installed.

FSX68 said:
How did you manage to do a cut and paste that looks like the xml file i.e the format and colors look like that in the xml editor.
Click to expand...
The forum's display rendering strips out your xml,
but it is present in the "new Post" email notifications.

As the CODE button functionality is also currently being affected -

Try either -
- Wrapping your text in HTML tags, (middle row, second-rightmost button above).

HTML: 
<?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>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
  </Launch.Addon>
</SimBase.Document>

- Wrapping your text in PHP tags, (middle row, rightmost button above).
PHP: 
<?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>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
  </Launch.Addon>
</SimBase.Document>



As the above code looks correct,
are you editing the correct dll.xml file ?

i.e.
The active dll.xml file located in Win7 at - C:\Users\USERNAME\AppData\Roaming\Microsoft\FSX\dll.xml



HTH
ATB
Paul
 
Hi Folks

FSX68 -
Just found attempting to edit my above post,
strips out both the HTML and PHP version content. :icon_lol:

Was going to add -
EDIT - Deleted potentially misleading additional info.

HTH
ATB
Paul
 
BASys said:
Hi Folks

FSX68 -
Just found attempting to edit my above post,
strips out both the HTML and PHP version content. :icon_lol:

Was going to add -
If you had already been editing the correct dll.xml,
and only if that has already failed.

As a last resort,
some persons found they'd had to enclose their path in double-quotes "fullpath"
e.g.
HTML: 
"C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll"

HTH
ATB
Paul
Click to expand...

IT WORKS!!!!! Woot!!!!!!! :applause:
I was editing the wrong xml file
here is what I have 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>Object Placement Tool</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Visual Effects Tool</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\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>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4_Loader.dll</Path>
</Launch.Addon>
</SimBase.Document>

I also change all the true to false. Glad you said something about editing the right xml file.

Thanks again. All is well.........
 
Hi Folks

FSX68 -
Excellent.

However, from your posted dll.xml,
I'm expecting only one tool currently shows up in-game, (rather than 3).
i.e. the traffictoolbox

You'll need to edit dll.xml
adding the full path for the visualfxtool and object_placement dlls.




PS - Important
In your last post,
you've quoted my "last resort" double-quotes "fullpath" suggestion.

For the sake of anyone seeking similar solutions -
Please could you edit your last post,
and delete that quote,
as its inclusion potentially could be misread as adding double-quotes "fullpath" having solved your issue.

Many thanks.



Have fun developing.
ATB
Paul
 
Please explain

BASys said:
Hi Folks

FSX68 -
Excellent.

However, from your posted dll.xml,
I'm expecting only one tool currently shows up in-game, (rather than 3).
i.e. the traffictoolbox

You'll need to edit dll.xml
adding the full path for the visualfxtool and object_placement dlls. >>>> I did edits for all three with proper paths.




PS - Important
In your last post,
you've quoted my "last resort" double-quotes "fullpath" suggestion.

For the sake of anyone seeking similar solutions -
Please could you edit your last post,
and delete that quote, >>>>>> Not sure what you mean, please explain
as its inclusion potentially could be misread as adding double-quotes "fullpath" having solved your issue.

Many thanks.



Have fun developing.
ATB
Paul
Click to expand...

I highlight in red comments next to yours......
 
Hi Folks

FSX68 -
I was referring to your "it works" post of May 28th, 2013, 21:56



You've quoted the following irrelevant misleading text -
BASys said:
Hi Folks

FSX68 -
Just found attempting to edit my above post,
strips out both the HTML and PHP version content. :icon_lol:

Was going to add -
If you had already been editing the correct dll.xml,
and only if that has already failed.

As a last resort,
some persons found they'd had to enclose their path in double-quotes "fullpath"
e.g.
HTML Code:
"C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll"
HTH
ATB
Paul
Click to expand...
Please delete the above text.



BASys said:
You'll need to edit dll.xml
adding the full path for the visualfxtool and object_placement dlls.
Click to expand...
FSX68 said:
>>>> I did edits for all three with proper paths.
Click to expand...



Your "it works" post of May 28th, 2013, 21:56,
indicates you'd only edited one of the three paths -
FSX68 said:
<simbase.document type="Launch" version="1,0"><launch.addon>
<name>Object Placement Tool</name>
<disabled>False</disabled>
<manualload>False</manualload>
..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll
</launch.addon>
<launch.addon>
<name>Traffic Toolbox</name>
<disabled>False</disabled>
<manualload>False</manualload>
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll
</launch.addon>
<launch.addon>
<name>Visual Effects Tool</name>
<disabled>False</disabled>
<manualload>False</manualload>
..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll
</launch.addon></simbase.document>
Click to expand...
Do you now have 3 working tools ?



HTH
ATB
Paul
 
Made edits

BASys said:
Hi Folks

FSX68 -
I was referring to your "it works" post of May 28th, 2013, 21:56



You've quoted the following irrelevant misleading text -

Please delete the above text.








Your "it works" post of May 28th, 2013, 21:56,
indicates you'd only edited one of the three paths -

Do you now have 3 working tools ?


HTH
ATB
Paul
Click to expand...

I guess I do, I made the edits (read entered correct path) like I did the first one.
 
I have never got the SDK thing to work myself.

Windows XP, FSX/Accel and OS all on the same C drive. Think I looked at some suggested fixes at e.g. FSDevelopers etc and tried some things but it looked like too much bother to continue further. Something simple like this - essentially a utility - and from MS should not be so fiddly.

Shame because it has some useful things like the AI viewer.
 
You must log in or register to reply here.
Back
Top