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

3DS Max 2008 FSX SDK Setup

Messages
10,163
Country
us-arizona
Hey all,

Is there anything I should know about setting up Max 2008 for the FSX SDK? Its Max 2008 instead of Max 7 thru 9, and I have my FSX SDK on H drive (external).

I have set aside today to see if I can get this finally running. I pray it only takes an hour instead of a week.

So far, my Clouds and Scenery FSX SDK's popup 'usually' when I open up Max. But no FSX Tools selection on the toolbar (should there be with Max?).


A thousand thanks for any help and input on this.



Bill
 
Bill, I've just emailed you a zipped folder with my revised scripts for ..\3DSM9...
 
Hey Bill,

Many thanks Sir. Off to check it out.

I also noticed we have here a SDK forum room. I didnt notice it until now. My oops..



Bill
 
Hey Bill,

Ok, got it, installed it, have been modifying it all afternoon. You have your SDK in a diff drive and with a diff folder name, so I have been going through all the MS scripts (max scripts) and all other files in your folder, renaming all over to H: drive and related folder.

I still get a few error messages when starting up Max though. I have gone through all files now 3 times, did find still some more on the final pass using Find and E: for drive names. I must have missed a folder designation though.

Here are my present Errors....

(When I get this working, I am going to burn it to several backups so that there is no way I have to do this again, lolol... I saw all your personal notes in the code, 'I must fix this' 'I must find a better way to do that' etc... So much work into getting this done that it literally almost brought a tear to my eye. This is alot of work....)


Bill
 
Last edited:
Hi Bill,

so you finally decided to get your hands dirty on that. Fine. Here's my :twocents:

Error 1 : MaxXML, MaxUtils and modeldef.xml

Did you do as you're told? Configure System path, etc...

Errors 2, 3 :

should disappear after resolving the above issue.

Cheers
 
Hey Capt-X,

Yep. Finally going to face the beast. No running away this time.

I hand wrote all the paths. Oh... I think maybe you mean via the Max end...

Off to check that.



Bill
 
Ok, I have reset the link(s) to the Max folder. This time it linked 4 different sets instead of one. Nice...

Still have warning messages, and now I have either 2 or 3 sets of tools and I have FSX Documentation Tabs accross the top, off the page of the toolbar, where FSX Tools should be. (Not complaining that the tools are up, lol.. so long as they can function).

When I click on the FSX Tools, I get a XML sheet and a error. Something in the XML must be not properly linked. I went through all the code. I must have missed something.

So, I boot up Max, and about 8 warning popups, all the same as before, and lots of tools.

Why on Earth would it be reopening tools? I do not have any other tools or Max folders in there. Only the one.
 
Is your SDK with SP2? For 2008, you definitely need the Max9 versions of the plugins. Check PM.
 
Last edited:
Is your SDK with SP2? For 2008, you definitely need the Max9 versions of the plugins. Check PM.

I sent Bill my entire ..\3DSM9 folder with the scripts edited to remove some path errors as well as set some paths ACES forgot.

Bill, be certain that you change this entry at the very top of the
FSToolsMenu.ms file:

global acesScriptsFolder="E:\\FSX_SDK\\SDK\\Environment Kit\\Modeling SDK\\3DSM9\\Scripts"

The above entry I added to hard-code the path to the "acesScriptsFolder" variable, since their stupid Registry hack doesn't work reliably...

Bill, I spent an entire week sorting out all these silly issues, so take a deep breath and go slowly. ;)
 
Hey guys,

Roger that Bill. Proceeding carefully and steadily.

Just took a nap, got up, booted up Max and not one single Error came up.

Well.... I couldnt believe that. So I rebooted. Waited. Got fully running again. Double clicked on the icon and Max booted up again (again) with NO errors. :D


Bad news, tools are not yet working. They are now no longer popping up when I boot up Max, and not able to be accessed when in the FS Tools flyout at top of the toolbar.


I do have about 12 or so 'fsx documentation' tabs accross the top, and one FS Tools tap.

For me, this is progress. Great to see it starting to function.

Note, I am getting errors when I open the tools, and I get a broken XML sheet (I dont think its actually XML, diff symbols). Perhaps my link to the Docs are not wired right.

Also, if I may ask, how does the operation go when say selecting Animation Manager? Does one click on it on a second window that is like HTML? or does the tool window appear? Or would it be 'in' that window that comes up with the code?


Bill
 
Last edited:
Man, I found an error and now the tools windows are popping up. They still do not function but they are popping up.

The XML window still pops up as well.

The Animation Manager pops up normally but the animation listings are not there.

I did copy out my Gmax FSX parts XML sheet into Max 2008. They appear to be the same.

Export also does not work.

Off to dig around some more.

Sweeeeet progress...
 
I think I found something that might be an issue.

This is calling for something that concerns the Animation Manager; located in the Animation Manager MS script.


xmlParser = MaxXML();

-- Determine where the document is located (need plugin directory)
-- TODO : Need easy way to do this!!!
if (MaxUtils == undefined) then
(
filePath = "H:\fsx\public\core\bin\art\Max6_Plugins"; <<< here
--print "Failed finding plugin path!!";
 
Latest in the Max 2008 Setup Saga....

In finding two or more strings that had Max7 depiced instead of Max9, and in changing those, I now am back to 2 sets of popup windows of all FSX tools popping up, 9 error messages, and my Max seems to be collecting tons of FSX Documentation tabs on the top toolbar, lol..

:D

It must be collecting them for some reason. Perhaps for sentimental reason? Time for rest...


Bill
 
Last edited:
I had prayed this would only take an hour. But I invisioned it possibly taking 1 to 2 weeks. 1 At least. But.......... I was faithful! I hoped for 1 hour... :D
 
It must be collecting them for some reason. Perhaps for sentimental reason? Time for rest...


Bill

Bill, when the scripts "run" they are supposed to remove all of the toobar entries and then "rebuild them."

However, you need to open up the Customize/Customize User Interface menu, then click on the "Menus" tab.

Select every instance of "FS Tools" and "FS Documentation" and then click on "Remove" button to clean up the User Interface.

Once you have the FS Tools running properly, this will no longer be necessary, as the scripts will keep everything tidy from that point on. ;)
 
I think I found something that might be an issue.

This is calling for something that concerns the Animation Manager; located in the Animation Manager MS script.


xmlParser = MaxXML();

-- Determine where the document is located (need plugin directory)
-- TODO : Need easy way to do this!!!
if (MaxUtils == undefined) then
(
filePath = "H:\fsx\public\core\bin\art\Max6_Plugins"; <<< here
--print "Failed finding plugin path!!";

Your system should never even call this part of the maxscript, once it's running properly. A large part of the problem is that Mike Singer had to script these tools so that they would work for them using the shared machine's folder structure...

...and user's folder setups. Unfortunately, there are far too many errors in the scripts to allow them to be as "universal" as they were intended to be.

IF I ever find the time, I do intend to create an entirely new set of scripts that remove all references to ACES' development paths entirely, and make the Max9/2008 "FS Tools" work properly for everyone without requiring so much pain and suffering! :banghead:
 
Hey Bill,

Roger that.

So long as I can get it working, I will be fine. I can always unlink the tools, reboot, then relink the tools again. I was wondering though if I do that, will the FSX materials disappear or clear out?

I tried Animation Manager and Model Export this morning. No go on both. Model export 'almost' worked, but near the end, said it had a unrecognized 'something' and ended the compile, (Export failure), and the Animation Manager doesnt show the Animations master list, but... the Attach point does, so I know the list is working, but its not working in finding its way to the Animation Manager.

Off to continue checking things.

I guess I should have had the FSX SDK in the C drive instead of H drive. That would have helped on most of this.

The fear I have from several crashes is that having my important stuff on an alternate drive keeps them from being erased in a windows castrophe. You reload Windows (heavy repair) and it would sometimes erase my files, though it says it isnt going to do that... Your documents folder gets erased, so now my photos and business are on alternate locations now... I am prepared... But dang, this happens, lol...
 
Ok.... Out of my 'instantaneous' state of depression, shirt sleeves rolled back up, coffee cup filled with hot, potent tea, mind is alert, heart is receptive...

I have downloaded a 'pure' package from Felix (number 2) and tried an experiment.

I noted that in the 3DSM9 pack, that it has folders that Max has; Scripts, Startup, and Plugins. When we add Scripts to Gmax, we put them in the appropriate folders. Same with manual installations of planes in FS. So I thought, what if I place these files into Max in their proper folders (if they were being treated 'normally' as Max addon scripts and things). So I did...

No warning messages popped up, Tools showed up at the top, but all tools didnt work stating 'Not Presently Supported'. So, I back stepped and removed the various components from Max of the 3DSM9 pack.

I then linked to the new 'pure' 3DSM9_Pure pack and tried it again. This is a non-touched pure set of scripts for the package.

Warning signs, and blank tool popups. Animation manager was a mess.

So now, I am about to embark on the same thing I was doing for the last 2 days (or 3 days) prior, resetting links and locations in all the scripts and files, going through all the code, section by section, page by page...


eeks...

If only I could say to my computer; 'Jarvis... ' (Iron Man, home computer network AI system, I guess British).. 'Relink all 3DSM9 inner file links to Max with code networked back to the appropriate locations they are stored at... ' and the computer would go through each and every file and change 'location links' in the pages of code to the corrected locations.


I guess if I wanted to, I could also just reinstall the FSX SDK into C: drive and that might just cause it to work without changing things around...

hmmm.. . (thinks about that)... laughs... no chance... lol... silly me. (My thoughts are that it still wouldnt work, and then my Gmax installation would then be offline and unable to work and I would really be in deep... deep deep... um.. water.. yeah.. )



Bill
 
Last edited:
Honestly Bill, you'll spend forever trying to faff out the really convoluted MaxScripts ACES wrote...

...above and beyond which is that there seems to be an error in the Max9_FSModelExp.dle module!

It's stripping out a "backslash" from the path to modeldef.xml file, which generates an "cannot find modeldef.xml" error message when exporting...

For example, here is the absolute path to my modeldef.xml file:

E:\FSX_SDK\SDK\Environment_Kit\Modeling_SDK\bin

Max9_FSModelExp.dle is returning this path when run:

E:\FSX_SDKSDK\Environment_Kit\Modeling_SDK\bin
 
Back
Top