Hi all, I am having a bit of a problem I was hoping to get some help with. I am trying to export from 3ds Max 8 on Windows XP and whenever I do, all of the Aces Tools say they're not supported yet. The kicker is that I have Max setup in exactly the same way on my Laptop which is Vista and have no problem with it. In both, I took the Max 7 folder from the SDK, placed it in the Max folder, and directed a path to it, but no joy with the XP. Does anyone know why this would not work?Attached are screenies of the paths for the plugin folder and startup folders and a screenie of the project...Daycab

Boy, for what is supposed to be the 'Premiere' FS site on the web, this sure is a dead board... Have people lost all interest in making planes?

Boy, for what is supposed to be the 'Premiere' FS site on the web, this sure is a dead board... Have people lost all interest in making planes?

Most of us are quite busy with our own work and don't check the forums more than once a day for new questions...Why didn't you simply follow the SDK's instructions for using the tools from the SDK with Max7/8? That you managed to get it working at all on another machince is pure luck, as the scripts are written to read the Registry to obtain much of their path/filename information.You don't need to copy/paste the ..\3DSM7 to Max. In fact you shouldn't, unless you want to edit the Registry manually to update paths stored there (such as the one to modeldef.xml).FWIW, I've found in more than one instance where some of the scripts used have problems where there is any blank space in pathnames......for this reason, I highly recommend (re)installing the FSX SDK to a short path with no spaces in the path, such as C:\FSX_SDK......then follow the simple instructions in the "Using Modeling Tools" document:

3ds MaxIn order for 3ds Max to work correctly with the scripts and tools of this SDK, go through the following steps:Install and run 3ds Max 7+. Select Customize on the main menu. Select Customize Paths from the drop-down menu, then the Plug-ins tab from the Configure Paths. Select Add, and then browse to the Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins folder. Select Use-Path and OK, and this path will appear in the dialog. It is now necessary to shutdown and restart 3ds Max. On restarting, a new main menu item named FS Tools should appear, with drop down options for: AttachPointTool, LODNameTool, AnimationManager and FSCloudTool. You are now ready to use 3ds Max to create Flight Simulator X models.

Is that a Bushby Mustang1 that you are building? Sure looks like it, or, a mid 70s Formula Vee Racer that I've seen before but cannot remember... Looks Nice!

Is that a Bushby Mustang1 that you are building? Sure looks like it, or, a mid 70s Formula Vee Racer that I've seen before but cannot remember... Looks Nice!

Thanks guys, I appreciate the response. The plane is actually Neal Loving's 'Love.' It's currently at the EAA museum at Oshkosh. A neat little racer...n4gix (Bill?) Mine says Aces Tools and Aces Documentation. Do you know what the difference is?Daycab

Thanks guys, I appreciate the response. The plane is actually Neal Loving's 'Love.' It's currently at the EAA museum at Oshkosh. A neat little racer...n4gix (Bill?) Mine says Aces Tools and Aces Documentation. Do you know what the difference is?Daycab

One has the tools (Animation Manager, Attachpoint Tool, etc) and the other has documentation...

My mistake, I meant between FS Tools and Aces Tools... ;)

My mistake, I meant between FS Tools and Aces Tools... ;)

Rule of Thumb - If your menu shows FS Tools, you're running gmax. If it's "Aces Tools" you're running Max.

n4gix (Bill?) Mine says Aces Tools and Aces Documentation. Do you know what the difference is?Daycab

The different names will identify which version of the SDK Tools you have installed and configured:SDK SP2: "FS Tools"from the (FSX SP2) ..\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\FSToolsMenu.mssubMenuItem = menuMan.createSubMenuItem "FS Tools" subMenuSDK Acceleration: "ACES Tools"from the (FSX Acceleration) ..\SDK\Environment Kit\Modeling SDK\3DSM7\Scripts\Startup\FSTools.ms -subMenuItem = menuMan.createSubMenuItem "Aces Tools" subMenuBy editing the fields in either script, you could "customize" the menu name to be anything, such as "I'm A Tool" or some such... :(

By editing the fields in either script, you could "customize" the menu name to be anything, such as "I'm A Tool" or some such... :(

While in FS-X XML coding syntax, spelling and capitalization are important, when (re)naming the "Tools" menu title, make sure that the spelling is correct - considering that in (most) keyboards, the "T" is just above and slightly to the right of the "F", a slipped finger can give your new menu a completely different meaning!

While in FS-X XML coding syntax, spelling and capitalization are important, when (re)naming the "Tools" menu title, make sure that the spelling is correct - considering that in (most) keyboards, the "T" is just above and slightly to the right of the "F", a slipped finger can give your new menu a completely different meaning!

Ok, you guys are officially starting to scare me...So as long as I have the SDK from Acceleration installed in the default path on my C: drive, I should be ok?

Ok, you guys are officially starting to scare me...So as long as I have the SDK from Acceleration installed in the default path on my C: drive, I should be ok?

Yes, although I still highly recommend not installing to the "default" but instead using a shorter path such as C:\FSX_SDK...If nothing else, it a whole lot less typing! :)

Yes, although I still highly recommend not installing to the "default" but instead using a shorter path such as C:\FSX_SDK...If nothing else, it a whole lot less typing! :)

Thanks guys, that worked perfectly!Here's an update. I've actually moved much farther beyond this point. In fact, the exterior model is almost complete...daycab

Cool! I'm delighted you've made such progress... :(