FSX:SE Can I use the SDK Tools/Addons with FSX:SE?

Okey, I removed the entries in FSX.cfg, then I reinstalled the SDK, and this time it asked me for permission to use the modules. However, there is still nothing in-game. I'm afraid to touch the dll.xml files right now but I'll take a peek at them. I'm pretty sure they have the correct file paths.
 
This FSX is not cooperative. Several times already, I've done exactly what those posts and multiple other posts are instructing me to do, but it never works. Twice already I've been asked if I want to run the .dll files upon boot which leads me to believe they work, however upon loading FSX nothing appears.
 
I think they show up under the ADDONS heading on the toolbar. The one at the top of the screen when you're flying. Or that appears if press alt while flying. They aren't separate entries on the toolbar.

I don't mean any insult, just making sure...
Pat☺
 
My Impression is that the OP is scared to Change any definitions for FSX. My Suggestion is to download "SIMconfigBackup" from here:

https://aviation.pero-online.de/wordpress/?page_id=551

Create a backup of all the FSX configuration files everytime before he is going to Change something! This will give him, from the perspective of psychology, a more secure Feeling always being capable to revert to the previous state!

Thats what Im doing for years now and it has helped me many times! I also do this before I install a new addon or scenery!

Edit:

I found meanwhile also a Video desribing the functionality of "SIMconfigBackup":


End-Edit:

Kind regards from Switzerland

Conrad
 
Last edited:
Hello...

Can you show what the fsx.cfg shows now?
I was actually looking at it right now, specifically the 'TRUSTED" addons. Scrolling down, I see that all my panels/gauges for my add-on aircraft end with =2. The SDK tools do appear on the list as well, but they end in =1. Might this be the problem? (Once or twice the dialog box popped up and I enabled them)
 
Possible, but unlikely, IMO. Why? All my .DLL and .GAU entries end in a 1, with some of the .gau files ending in =0. All the "normal" FSX XML gauges and devices end in =2.
All that in MY FSX.CFG file.

That's why I say unlikely. If they're that way in mine, and work fine for me in my system, I don't believe that it has anything to do with your situation, see? Si... :rotfl:

Still trying to think, which isn't easy for me o_O, of a possible solution to your situation. Haven't gotten any brainstorms lately. Not even a light idea-rain, or thought-fog...:laughing:

Still hoping someone can come up with an idea I haven't been able to work out yet.
Pat☺
 
My suggestions is to post your FSX.cfg, DLL.xml and EXE.xml here on this Forum, so someone can have a look at the definitions, otherwise it will be difficult just by guessing to determine the Problem!
I have been an IT-professional for 48 years and experience showed most of the times, that the real Problem sit's in front of the Computer. It happened sometimes also to me!

Edit:
I have included my excerpt from DLL.xml although I run Prepar3D V1.4, I have my SDK not installed into the Flightsimulator-path. Everything runs fine on my System!
Code:
   <Launch.Addon>
        <Name>Traffic Toolbox</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D SDK 1.4.4747.0\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Object Placement Tool</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D SDK 1.4.4747.0\Mission Creation Kit\Object_Placement.dll</Path>
    </Launch.Addon>
It has been mentioned several times on this thread that you should download the Prepar3D SDK 1.4.4747.0 from this site and install that one. It is not obvious to us if you have followed those suggestions!
End-Edit:
 
Last edited:
My suggestions is to post your FSX.cfg, DLL.xml and EXE.xml here on this Forum, so someone can have a look at the definitions, otherwise it will be difficult just by guessing to determine the Problem!
Alright....... link to .cfg, dll.xml and exe.xml

(I made a few graphic modificiations onto the cfg but I haven't even touched the exe)

It has been mentioned several times on this thread that you should download the Prepar3D SDK 1.4.4747.0 from this site and install that one. It is not obvious to us if you have followed those suggestions!
I did install that SDK, however nothing has changed.
 
Looking at you configuration files, I could not find any Errors, strange so far. Everything looks okay from the distance, although I dont know FSX-SE. I would suggest you the following proceeding:
  1. Install SimConfigBackup from the link I described somewhere above, if not done already so.
  2. Backup all your configuration files with SimConfigBackup, carefully checking that you catch all the files as desribed on the Website of SimConfigBackup (by Peter Rosendahl).
  3. Create a copy of "FSX.cfg" just to be 100% certain and save this copy.
  4. Delete "FSX.cfg".
  5. Start FSX-SE, this will create a new "FSX.cfg". You will have to confirm again all Gauges and Modules, but this is worth the Trial.
  6. See now what happens, you should see and have in the Menu-bar of FSX-SE an Menu-Option "Addons" click on that and see if you see the Modules from the SDK.
If not, then it will be impossible to determine your Problem from the distance, something is strange in that case and has to do something with your Setup somewhere!
 
Looking at you configuration files, I could not find any Errors, strange so far. Everything looks okay from the distance, although I dont know FSX-SE. I would suggest you the following proceeding:
  1. Install SimConfigBackup from the link I described somewhere above, if not done already so.
  2. Backup all your configuration files with SimConfigBackup, carefully checking that you catch all the files as desribed on the Website of SimConfigBackup (by Peter Rosendahl).
  3. Create a copy of "FSX.cfg" just to be 100% certain and save this copy.
  4. Delete "FSX.cfg".
  5. Start FSX-SE, this will create a new "FSX.cfg". You will have to confirm again all Gauges and Modules, but this is worth the Trial.
  6. See now what happens, you should see and have in the Menu-bar of FSX-SE an Menu-Option "Addons" click on that and see if you see the Modules from the SDK.
If not, then it will be impossible to determine your Problem from the distance, something is strange in that case and has to do something with your Setup somewhere!
Alright.... this is getting really wonky. I (backed-up and) deleted my .cfg and FSX made a new one for me. Upon bootup I had to allow the modules to run. That was a hopeful sign. Also, when the menu opened the MUSIC also started (it never does nowadays), plus an informational sign showing off a few cool things about the SDK. That was a VERY hopeful sign. However, booting up into the actual flight mode, there was still NOTHING THERE. I rebooted several times (losing the informational sign in the process) but they still didn't show up.
 
Ok, here goes nothing...

Remember to always make a back-up copy before you edit, or change, any of these files!
Also, ONLY ever use NotePad, which comes with Windoze, or NotePad++, a freeware which works very nicely for this sort of thing. ANY other program could add symbols you can't see that would mess the file up badly.

Only make ONE change at a time, then save the .cfg file off, and start FSX to check out the effect of the change.
Ensure FSX is completely and totally closed before you open the FSX.CFG file for editing.

Just a little side note: I went in and separated each heading's entries from the next heading by putting a CR (carriage return, or enter key stroke) between. Like this:
[Heading_one]
line=one
line=two
line=etc

[Heading_two]
line=one
line=two
line=etc

That makes it easier, for me, to locate each heading as I look for them. They're not all crowded one atop the next this way, which, for me, makes it harder to separate them out.

Here we go! :yikes:
In your FSX.cfg file try these:
First, try changing the following line under the heading
[Main]
HideMenuFullscreen=1

to
HideMenuFullscreen=0

It's the last entry under that heading, just before the heading [PANELS}.

Save it off, and try it. Change nothing else whatsoever. Go into a flight, and see what's shown under Addons up on the menu bar, while flying.


Another little detail that may be causing troubles:
You have 3 headings labeled
[DISPLAY.Device.NVidea etc etc etc]
Comment out the SECOND and THIRD entries. Leave the first one alone. You can either put the comment indicator in front of the two or three lines concerned, like this
//[DISPLAY.Device.

OR you can delete them entirely. That means the heading and the two or three lines under each one, before the next heading shows up.
Having more than one of those headings per file can cause some interesting effects, none of which are desirable.

Another little detail that may, or may not, have anything to do with your main trouble, but which you'll probably want to correct eventually:
Under the heading
[Display]
change the line
WideViewAspect=False
to
WideViewAspect=True

Last, but certainly not least:
Under the heading
[GRAPHICS]
ADD the line
HIGHMEMFIX=1

This is very important. Don't skip this!

I honestly don't know that any of these changes will have any effect on your original difficulty, but they need to be made, eventually. This is as good a time as any ;)
Let us know how "things" turn out!
Pat☺
 
Ok, here goes nothing...

Remember to always make a back-up copy before you edit, or change, any of these files!
Also, ONLY ever use NotePad, which comes with Windoze, or NotePad++, a freeware which works very nicely for this sort of thing. ANY other program could add symbols you can't see that would mess the file up badly.

Only make ONE change at a time, then save the .cfg file off, and start FSX to check out the effect of the change.
Ensure FSX is completely and totally closed before you open the FSX.CFG file for editing.

Just a little side note: I went in and separated each heading's entries from the next heading by putting a CR (carriage return, or enter key stroke) between. Like this:
[Heading_one]
line=one
line=two
line=etc

[Heading_two]
line=one
line=two
line=etc

That makes it easier, for me, to locate each heading as I look for them. They're not all crowded one atop the next this way, which, for me, makes it harder to separate them out.

Here we go! :yikes:
In your FSX.cfg file try these:
First, try changing the following line under the heading
[Main]
HideMenuFullscreen=1

to
HideMenuFullscreen=0

It's the last entry under that heading, just before the heading [PANELS}.

Save it off, and try it. Change nothing else whatsoever. Go into a flight, and see what's shown under Addons up on the menu bar, while flying.


Another little detail that may be causing troubles:
You have 3 headings labeled
[DISPLAY.Device.NVidea etc etc etc]
Comment out the SECOND and THIRD entries. Leave the first one alone. You can either put the comment indicator in front of the two or three lines concerned, like this
//[DISPLAY.Device.

OR you can delete them entirely. That means the heading and the two or three lines under each one, before the next heading shows up.
Having more than one of those headings per file can cause some interesting effects, none of which are desirable.

Another little detail that may, or may not, have anything to do with your main trouble, but which you'll probably want to correct eventually:
Under the heading
[Display]
change the line
WideViewAspect=False
to
WideViewAspect=True

Last, but certainly not least:
Under the heading
[GRAPHICS]
ADD the line
HIGHMEMFIX=1

This is very important. Don't skip this!

I honestly don't know that any of these changes will have any effect on your original difficulty, but they need to be made, eventually. This is as good a time as any ;)
Let us know how "things" turn out!
Pat☺
(sorry for the late reply, I've been really busy lately)

I thank you very much for your help. Unfortunately, none of that worked. :(

At this point, I don't know what else to do. I think I'll just stick with MCX now.
 
Top