• 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.

Reinstall now no Tools

just reran Gmax...tried the MAXScript and now I got this message

-- Bootstrap script file that will load all other applicable scripts
global FSXGamePackName="FSX_GMaxGamePack"
global FSXSDKLocation = maxUtils.getPluginPath() as stringStream
SDKMarker = findString (FSXSDKLocation as string) FSXGamePackName
FSXSDKLocation = subString (FSXSDKLocation as string) 1 ((SDKMarker - 1) + FSXGamePackName.count)
global FSXScriptRoot=FSXSDKLocation + "\\scripts"

--Setup the usingAcesBuild variable to be false
global usingAcesBuild = false

execute ( openFile ( FSXScriptRoot + "\\FSXMaterial.ms" ) )
execute ( openFile ( FSXScriptRoot + "\\FSXAnimation.ms" ) )
execute ( openFile ( FSXScriptRoot + "\\FSToolsMenu.ms" ) )

there must be something Im missing........just what I dont know!!!!!!
 
didnt think having Aicarrier would matter since it comes up ina different Tab then the Tools
and yes I am running the Gmax from a desk top short cut
and Hey at this point I will try anything and any help is welcome
E-mail is murrayluck@live.ca
 
Just sent this with a zip attachment via email:

Here is a zip of what may be esssential files -- all ini's that I could find, plus the desktop link plus more or less all of the folders in the FSX_GmaxGamePack folder.

It seems that for some reason your startup script that you are quoting in your latest fails to locate or access the SDK files. So you may want to point the script explicitly to where they are located. And since you are running Win 7 you might try going offline and to temporarily deactivate User Account Control.

Best of luck ...

Edit: Wait those three files that gmax wants to exceute are all in here, not in SDK: c:\Gmax\gamepacks\FSX_GmaxGamePack\scripts
 
Last edited by a moderator:
Well thanks for the E-mail, I wish I could say that it helped, but still no tools tab
I reinstalled again, ran the Bootstrap files, the config files.. checked all the Paths, disabled the UAC so I can write to file that I coulded before, but still no Tab, ADE report says everythings fine , right verison,All my other Tools like FS Design and Gmax work fine but still no Tool Tab appearing. checked the dll files and the config file Trusted=1 everything checks out...I am now officialy lost boss...I got nothing...
Whats the next step?
Lucky
 
You sure know the dll file that must be edited is in C:/users/xxxname/Appdata/t/roaming/microsoft/FSx.
And I would see the updates services packs, how they were installed and his order it's something one must observe strictily.
 
Hi Folks

<RANT>
The entire point
of requesting the user post their ADE-report and dll.XML
is that doing so, will enable issue identification in 99% of cases.

Please address the fundamentals
before suggesting outlandish options. :D
</RANT>



LuckyMurray -
Go back to your original post
and look at your ADE-report and dll.XML.

Specifically compare the folder paths where -
- You'd installed the SDK into.
- You're telling FSX where the in-game tools are located.

The paths must be valid, otherwise the tools wil not load.

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\
C:\Program Files (x86)\Microsoft Flight Simulator X SDK\SDK\blah blah blah

Fix your dll.XML accordingly.



HTH
ATB
Paul
 
Ok lets start again..here is the ADE report and the dll fileThe verison check out and the Paths check out...what am I missing here???

*************************************************************************************************
[Date of Report: 03/10/2011 5:25:48 PM
Operating System: Microsoft Windows 7 Home Premium
OS Service Pack: Service Pack 1 (1.0)
OS Version: 6.1.7601 (64 Bit)
OS Language: English (Canada) => separator: '.'
Nodename: SIGNS_WONDERS
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: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\
FSX Version: 10.0.61472.0 (fsx-sp2.20071210-2023)
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.61472.0 (fsx-sp2.20071210-2023)
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.728b
Connected to FS9 ok: no
Connected to FSX ok: no]

The only thing is see here is that it is stating that my OS serivce is 1, but I have service pack 2 installed.

<?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>"C:\Program Files (x86)\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 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>"C:\Program Files (x86)\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll"</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
</SimBase.Document>
And the Paths are all right for where the folders are...... So any guess on where I went wrong??

My FSUIPC is working but simconnect says it cant find the Path for the Tools.
All my other programs work.. Ive tried putting the Path in quotes,, tried a relative Path. and I have used the Absolute Path, nothing seems to matter it still cant find the Tools,,,come on and embarass me by show me where I made the stupid mistake.. got to be one here somewhere
Lucky
 
Boy do I feel stupid now.

your right again BASys, your line think about the fundamentals got me thinking and there it was.
Path way was C: Program Files (x86)\Micosoft Flight Simulator X SDK\SDK
But it should have read

C: Program Files (x86)\Microsoft Games\Microsoft Flight............

I was missing the \Microsoft Games\ silly me.
Really feel like an idiot now...but hey everythings working fine so feeling stupid is a small price to pay.
Thanks everyone who tried to help me out
and once again my hats off to you BASys

Where would we be outwith you............lost..lol
thanks again everyone
Lucky
 
I'm delighted that you found (and reported) the solution. Might I strongly recommend that in the future, if you have reason to reinstall from scratch...

...do not accept the "default installation path(s)" but instead specify unique and SHORT paths instead...

...thus avoiding the problems associated with having programs who's files change frequently in the silly "Program Files..." folder?

I use:

D:\FSX
D:\FSX_SDK
 
n4gix said:
I'm delighted that you found (and reported) the solution. Might I strongly recommend that in the future, if you have reason to reinstall from scratch...

...do not accept the "default installation path(s)" but instead specify unique and SHORT paths instead...

...thus avoiding the problems associated with having programs who's files change frequently in the silly "Program Files..." folder?

I use:

D:\FSX
D:\FSX_SDK
Click to expand...

+1
This is fantastically good advice from Bill! I have done just that when I first read about it here at FSDeveloper and it makes using FSX and the SDK so much more simplistic and less prone to errors. A belated thanks for your very helpful recommendation Bill.
 
Good advice.
Next time Ill set it up that way... right now Im not going to fix what isnt broken..lol
Thanks again Guys and the Beers on me...lol
Lucky
 
You must log in or register to reply here.
Back
Top