• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

SDK Installation Issues

K

kblythe

Messages
4
Country
us-virginia
This thread is a little old, but I hope it is still monitored. I recently upgraded from FS9 to FSX. Better late than never I guess. Anyway, It is FSX Gold Edition (includes FSX Deluxe and Acceleration pack). I have tried to install the SDK (several times) and still don't have the tools menu! I have edited the dll file. I even thought maybe there was an issue with FSX itself, so I reinstalled it too. I think I am just missing something small, but can't figure it out. The dll is located at:

C:\Documents and Settings\CHUCK'S GAME SETUP\Application Data\Microsoft\FSX

And reads:

<?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>.E:\Chuck\Microsoft Games\FSX\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>.E:\Chuck\Microsoft Games\FSX\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>.E:\Chuck\Microsoft Games\FSX\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
</Launch.Addon>
</SimBase.Document>

You will notice that there is a "." before the drive designation for each of the paths, when I didn't have them placed there, FSX wouldn't load.

I would like to start developing some missions and the like, but this is driving me nuts! Any help is more than welcome, even if it's to point out something that should be a no-brainer.
 
Hi Folks

kblythe -
What do you think typing the following would actually do ?
<Path>.E:\Chuck\Microsoft Games\FSX\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>

You might as well have typed -
<Path>DONTBOTHERTRYINGTOLOADTHISFAULTYPATH.E:\Chuck\Microsoft Games\FSX\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>



Remove the .

Delete or rename your fsx.CFG.

Launching FSX will rebuild a corrected fsx.CFG.



Any further issues
please ensure you've fully read and applied - FSDeveloper - Wiki - SDK Installation (FSX).



HTH
ATB
Paul
 
BASys, Let me start by saying I have not programmed anything more difficult than my alarm clock in a very long time (Last programming language used was BASIC). Having said that, I would like to start programming again as a hobby. So, I have no idea what the "." in front of the path would or would not do.

I followed your advice with removing the periods, renamed the cfg file, started FSX, and again, it would not load.

The main reason I posted my question is because I followed the instructions and still have had no luck. Please keep in mind that I am not a computer programmer but would like to create a few addons for my game and maybe learn a little something along the way.
 
Hi Folks

kblythe -
No worries.
I probably should have added some smilies there. :D



If FSX is failing to launch
after applying the correct paths in the dll.xml
then there's probably something wrong with your underlying FSX/OS installation.



To check that all prerequisite components are installed,
please download Martin Grossman's ADE Checker

Run ADE Checker.
Save the report, and post it here.




Arno -
Could you please split this thread
and move these recent posts to an appropriate section, (non-wiki).



HTH
ATB
Paul
 
Last edited:
Not sure what happened?!

BASys; No problem, I was just a little frustrated with FSX SDK. I had followed your instructions and nothing seed to work right. Sorry if I seemed a little short.

Now for the good news, I got the darn thing working.

:confused:

Last night, while all of the normal people were fast asleep, I searched for more instructions (specific to Gold Edition). I found a post (http://www.simforums.com/forums/forum_posts.asp?TID=31522) that looked a lot like the process I had been following all along (hence the confusion).

I figured I had nothing to lose, except a few hairs :D, so I removed the SDK and Acceleration and started over with the basic FSX. I reinstalled everything, yet again, and it actually works this time!!!

I did do one thing different, I let the SDK install to it's default location. As I was following the check list for installing this crazy software, I noticed that I did not have the dll.xml file in the C:\Documents and Settings\<user name>\Application Data\Microsoft\FSX folder. At that point I decided I would copy it from one of the other locations and make the appropriate edits. Having said all of that, I am still confused on the following points:

1. Why did it take this many installs for it to work, one of which I removed everything FSX?

2. Why did I have to use the default location for the software?

3. Why did the installation not place the dll.xml file in the correct folder?

Anyway, none of these questions need to be answered, unless you really want to figure it out :scratchch, since it is now working. Maybe if I get bored I will uninstall everything and try to reinstall in a location of my choosing, but for now I think I will just be satisfied that this challenge is finally over. :banghead:
 
Last edited:
Hi Folks

kblythe -
No worries.

Excellent on getting the tools running.



Before answering your questions,
as previously requested -
To check that all prerequisite components are installed,
please download Martin Grossman's ADE Checker

Run ADE Checker.
Save the report, and post it here.
Click to expand...
That should give some clues,
and may assist others in the future.



PS
Several of the steps in the other doc are irrelevant.
Particularly the last section
which is for running simconnect on a 2nd PC which has no FSX installed.



HTH
ATB
Paul
 
Last edited:
Ade

Here's the file. I'm not sure what this ADE program does or checks, but I do have FS9 installed. Anyway, here it is:

*************************************************************************************************
Date of Report: 10/3/2009 11:22:21 AM
Operating System: Microsoft Windows XP Professional
OS Service Pack: Service Pack 3 (3.0)
OS Version: 5.1.2600 (32 Bit)
OS Language: English (United States) => separator: '.'
Nodename: CASA-OVMFFUG1VN
ADE installed: no
ADE Path: ADE not found
ADE Install Version: n/a
ADE File Version: n/a
ADE Info: n/a
FXS installed: yes
FSX Path: E:\Chuck\Microsoft Games\FSX\
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\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: not installed
Connected to FS9 ok: no
Connected to FSX ok: no

It would be nice to help some other unlucky soul with this headache. Although a few of the steps seemed they would be pointless, I figured I didn't have anything to lose by following step by step instructions.

Good luck sorting out the data in the report. I would like to know what it all means, I get the main points but not all of the details.
 
After following all instructions and still not getting the word 'tools' in my menu, I found and installed the latest fsuipc. I did this and also had to manually change about 3 'trues' to 'falses' in the dll.xml.

Viola! Tools showed up. I clicked on it and a window appeared.... and locked up FSX and the window itself. Only ctl-alt-del got me out.

I noticed some other fsuipc stuff with many zip files within the dl. These seem to pertain to sdk. Do I install these as well? Bob
 
Hi Folks

jyarddog -
It may possibly be the "Run permissions" dialog box,
displayed on first running a tool.

If your slider settings are too high,
and you don't pause the sim
before clicking the menu,
a dialog box may initially display
but instantly be over-drawn by the FSX window.

Pressing ESC, might bring it back to the foreground.

HTH
ATB
Paul
 
I did not see any run permissions window. The tools window when I clicked the word 'tools' stayed on top. My sliders are at dense and autogen at normal. Sometimes I run them at very dense with ono problems except for autogen I try to keep it at normal.

Tried again just now. on pause and on slew, hit tools, window opens, fx tools menu bar at top. everything is still frozen. esc did not get me out. just ctl-alt-del Bob
 
Last edited:
FSX SDK in Windows 7 64 bit

I would (humbly) suggest that a note be added recommending users of Windows 7 64 bit systems that all FSX and related programmes be installed outside of the dreaded C:\programs(86x) directory, and NOT in the default installation location (I used a different drive but this is probably exceeding requirements).

I spent a week or more during the holidays carefully uninstalling and reinstalling following the installation directions found here (which are otherwise excellent!) without success until I stumbled on a suggestion to install away from the overly security controlled default location.
 
Program Files(86) comment

First, thanks to Basys for helping with a difficult subject...explaining Microsoft's patches,fixes,etc. and how they go together.

I have the hated "Exporter Host not valid" message which appears in my FSX half of my dual (FS2002)/FSX gamepack.

I got infected with this on my 32 bit Win XP system, and never got it solved.
I just kept plodding ahead with the other half of my gamepack.

I have Win7 Home Premium 64 bits installed on my new home built hyper fast i7-2600K system. I also have FSX Acceleration.

I have everything working except the final step exporting with the FSX plugins.

I export fine with the FS2002 gamepack. My system will not export even a simple FSX export edittable mesh box with a GUID and a friendly name. It takes me right to the final click and then......Exporter Host Not Valid

The SDK Wiki does not include a warning about Program Files (x86) and I hope you can tell me what the difference is between Program Files, and Program Files(x86).
I thought I allowed the system to install FSX/SDK in the default path, and I got it installed in Program Files(86).....?????????
I hope someone else can confirm that's normal for FSXA. I think it is simpler to use default settings, myself.

Also, it seems to me that there would be different downloads for 64 bit and 32 bit Windows O/S's.

Does the SDK WIKI point only to downloads that covers both 32-bit and 64 bit OS's?


This is what I have now....



MicroSoft .NET Framework 4 Client profile......38.8MB 4.0.30319
MicroSoft .NET Framework 4 Extended..........51.9MB 4.0.30319

MicroSoft Visual C++ 2005 Redistributable 428KB 8.0.56336
MicroSoft Visual C++ 2005 Redistributable 2.38MB 8.0.50727.42
MicroSoft Visual C++ 2005 Redistributable(x64)610KB 8.0.59192
MicroSoft Visual C++ 2005 Redistributable -86 596KB 9.0.30729.4148

MSXML 4.0 SP2 (KB954430) 1.27MB 4.20.9870.0
MSXML 4.0 SP2 (KB973688) 1.33MB 4.20.9876.0
MSXML 4.0 SP2 Parser/SDK 1.33MB 4.20.9818.0
MSXML 4.0 SP3 Parser 1.47 MB 4.30.2100.0


My first pass at installing .NET 2.0 failed because I think it was a 32 bit download.


 
John, everything about FS9 and FSX is 32bit. The Program Files (x86) folder is where all 32bit programs are placed by default.

What you are experiencing however is precisely WHY so much emphasis has been give to

DO NOT USE DEFAULT PATHS...​

Beginning with Vista, and continuing into Win7, MS has been tightening up the darn security to the point that it strangles the user's ability to manage his/her own damn system! While the new protection systems may work seamlessly with the newest software written specifically to work with it, they don't play at all nicely with our "legacy software" that actually expects us to read/write files in the actual program's own folder structure (think scenery, aircraft, etc.).

As one recent example, just the other day a fellow modeler was trying to write a command line to compile his .x file using xtomdl.exe. Because the complete default paths are so ludicriously long, he actually ran into the maximum number of characters in the command line before he could finish! :eek:

So no, I do not agree at all that using the "default paths" is easiest. To the contrary, it ultimately leads to frustration and angst, not to mention heart burn!

My suggestion would be to uninstall the SDK and then reinstall it using a rational and sensible short path, such as C:\FSX_SDK, then run the config.exe program to update the FSX tools to recognize the new, shorter custom path.
 
Default paths

Thanks so much for your input. I will start over. (again).
This hobby has a Darwinian survival aspect to it. I understand the popularity of Linux more and more. The pitiful, rush out the product, we'll patch it later, aspect of US culture is killing us. My guys had a common complaint: we never have time to do it right,,,we always have time to do it over. I never had a good answer for that one.

I am still wary about the SDX aspect of it.

ADE-Checker would not run because of an error.

Component COMDLG32.OCX or one of its dependencies not correctly registered: a file is missing or invalid


The old Dot net framework 2.0 doesn't show in my control panel....when I run the Dot Net 2.0 64 version it tells me it's folded into my OS. I have to assume I have the Framework 2 issue flattened. Or do I?

I have Framework 4 installed...does that mean I have Framework 2 installed??? I understand I am supposed to.....

Jeez.......

Basys, can you post your appropriate Control Panel downloads in a jpg file and I will try to copy...I assume you are using Win 7...I hope so....
 
I got Microsoft.Net Framework 4 client profile Microsoft visual C++ 2008 redistributable, MSXML 4.0 SP2. Thats all
Dont know what al this is for but people talking much about :o
Windows 7 FSx accel. ahh, and the important thing all running ok.
 
Download the COMDLG32.OCX

and then Register it.

Serach by Google how you can Register The COMDLG32.OCX

it is very easy and not Dangerous.

I have this done in the past serveral Times.
 
Installing SDK in WIN7 x64 from DVD GOLD

I had to jump some hoops to get it installed because I was getting a DVD read error when trying to open the DVD to access the SDK installation folder.

1. Try to open DVD with browser.
2. Stop infinite access/no reading by ejecting disk
3. Use Microsoft Fix It, Trouble installing software/hardware DVD access problem
4. Once fix is started, it will ask to try a DVD. Insert FSX DVD
5. It will now fix it.
6. Open DVD from browser

Installation Order for GOLD DVD (which is FSX with Accel)

1. Install SDK from Disk 1
2. Install SDK from Accel Disk
3. Execute SDK MSI from Accel Disk

I had to do the FIX IT thing for each DVD disk.
 
You must log in or register to reply here.
Back
Top