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

Vista 64-3ds max 9-Aces Toolset trouble

G

Gerard

Messages
19
Hi all,

up till recently I've been using the Aces toolset plugins for 3ds max 9 with Windows XP and all worked well. Now I've upgraded (new hardware, fresh install) to Vista Ultimate 64 bit and I keep getting this error:

sdkerror.jpg


I checked and re-checked Customize > Configure System Paths > 3rd Party Plug-Ins tab > Add > E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM9 in 3ds max but to no avail.

Further info:

Vista Ultimate SP1 64bit
3ds max 9 SP2 32bit
FSX SP2 + SDK SP2 on E:\Program Files (x86)\Microsoft Games

I hope someone has a solution because I'm stumped...

Thanks

Gerard
 
Last edited:
REALLY wild guess.....

could it be that the tools script is not recognizing the path with the (x86) in it?
 
As I replied at FFDS, I would first try installing the SDK to a shorter path outside of the ..\Program Files folder, which Vista seems to "protect" much too agressively... :banghead:
 
FelixFFDS said:
REALLY wild guess.....

could it be that the tools script is not recognizing the path with the (x86) in it?
Click to expand...

Well, some people got it to work, as you can read here: http://www.fsdeveloper.com/forum/showthread.php?t=9007

I was hoping they could shed some light on the issue... Maybe Vista's User Account Control screwed things up during 3ds max installation... I reinstalled with UAC off but that didn't help.

Neither did installing the SDK to a different location BTW

gh
 
I posted an answer to this in yor thread at FFDS. Try putting a slash at the end of your path name on Max config i.e. '\'

This works for me..... nothing else to do to make it work.

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM9\Plugins\

I find I have to make sure I do this for texture paths also.
 
robby88 said:
I posted an answer to this in yor thread at FFDS. Try putting a slash at the end of your path name on Max config i.e. '\'

This works for me..... nothing else to do to make it work.

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM9\Plugins\

I find I have to make sure I do this for texture paths also.
Click to expand...

Bingo! Thanks muchly!

gh
 
Now who would have imagined that Autodesk would make such a silly change in the way paths have to be specified... :tapedshut
 
I ran into the same issue, but not with 3DS 9, 3DS 2009 (same version?). Adrian Woods just stated that the 2009 version (on sale since February 08) does not work. 2008 does work but is unsupported.

What I also found interesting was the reference to the effect that any new published SDK would support the currently released version - this is not true for ESP, arguably a newer release - that doesn't work either in 3DS 2009.

I modified the scripts to load (had to hard code the paths in the acetools.ms script, and I now have a problem with the menu getting new entries every time the script runs (haven't researched yet). Also, I get the DLL warning that the plugins where compiled with an earlier version, so that doesn't look good even if you get past the error above.


Etienne
 
Last edited:
You must log in or register to reply here.
Back
Top