Simviation Forums

hello,

after some considerable reading, i managed to find and download the latest version of the SDK, which comes with support for Max 9 (or so i figure)

the trouble is that upon loading the scripts, i get a number of error messages reporting the failure of their loading, and i am yet to see a FS tools menu in 3dMax

what could i be missing here? here's what i did so far:

i installed the SDK that came with the FSX disk, only to find that the scripts provided didn't support Max9

then i downloaded both updates and went to install the SDK SP1, which prompted me to remove the old installation and replace it for the new one... i said 'ok' and proceeded to install

then i installed the SDK SP2, which again prompted me to remove the old for the new, to which i replied 'ok' again and installed...

then i did as the setup instructions bade, setting the 3dmax system paths to load the scripts (the file path was a little different this time, but i pointed it to the scripts)

and i got a number of error messages

then i tried copying the scripts to 3dmax's own script folder, respecting the paths of the scripts stored in the startup folder within...

still i got a number of error messages...

so i ask here for some enlightenment... since i'm at my wit's end right now...

thanks in advance

HarvesteR

oh, and here's the MaxScript listener window output, with some error messages... it seems that every SDK script has failed to load

Code: Select all

Welcome to MAXScript.

-- Error occurred in anonymous codeblock
--  Frame:
--   fsxMatItem: undefined
--   makeFPItem: undefined
--   subMenuItem: undefined
--   submenu: <MixinInterface:menu>
--   attachItem: undefined
--   fsxAnimItem: undefined
--   fileRenamerItem: undefined
--   msoTool: undefined
--   mainMenuBar: <MixinInterface:menu>
--   usingAcesBuild: undefined
--   UVScaleItem: undefined
--   exportItem: <MixinInterface:menuItem>
--   subMenuIndex: undefined
--   fsxMatEditorItem: undefined
--   containerItem: undefined
--   removeFSXItem: undefined
--   wheelToolItem: undefined
--   cloudItem: undefined
-- Error occurred during fileIn in <File:C:\3ds Max 9\scripts\startup\AcesTools.ms>
>> MAXScript Auto-load Script Error - C:\3ds Max 9\scripts\startup\AcesTools.ms Exception: -- Type error: if-test requires BooleanClass, got: undefined <<

i'm sorry... i must be sleepwalkingposting then... i can't remember ever even being at fsdeveloper.com, much less having an account or posting  :o  :-?  ;D

anyways, copy over the 3DMax 8 scripts you say, hmm now that i think of it, i don't think my SDK came with a Max8 script folder... only Max7 and Max9

is this even possible? maybe the SDK installation 'forgot' to install something  ::)  i think it's more likely that i'm missing something

Cheers

EDIT: ahh now i saw the thread that had continued on without me... i didn't think the subjects were that close to each other, so i posted again here...  :P  it's on FFDS, not fsdeveloper

EDIT 2: just checked... i don't have any folder related to 3Ds Max 8 in the SDK... only Max 7 and 9

Ok, here's a follow up on what's happened:

i decided that it was too much trouble keeping the SDK in a non-standard path... so i uninstalled it and installed it again in it's default folder, then applied both SP1a and SP2 packages (no trouble there)

ok, but the Max scripts still won't work... and i have no 3DMax8 script folder... only 7 and 9... so i did what in my head sounded like the next best thing, and copied the Max7 scripts and plugins to the Max9 folder and pointed to it in 3D Max's system paths dialog...

well, still no luck... the error messages are different, but 3DMax still rejects the scripts although now there is an ACES Tools menu in the menu bar... actually.. now there's quite a lot of 'em  :P



and couldn't figure out how to remove them... deleting the script path didn't work... and neither did any of the tools... all report several error messages and none are doing their job... in fact, after i closed the ones that popped up when i fired up 3DMax, they refused to appear again, saying 'this module is no longer supported'

i think it goes without saying... but... i'm stumped  :P

help please?  :-/

Cheers

and here goes yet another follow up:

i restored the Max9 folder in the SDK to it's original state (i kept a backup) and pointed a 3DMax system path to the Plugins folder intead of scripts... and huh! it worked... to an extent...  :o

most dialogs open now... (i haven't tested them all as of this post)
except that closing them brings 3DsMax to a crash  :P

but there are no error messages this time!! that's gotta be a good thing  :D now, to figure out how to close them dialogs without crashing the program... (or maybe i'll just keep 'em all open  ;D good thing i have 3 screens)

ok, here's where i'm at now..

max7 plugins = error messages and don't work

max9 plugins = no error messages and SOME work without crashing Max...

to be more specific only LOD Tool and FS Shader Tool are crashing... all others work fine

the ones that do crash, however, are doing so randomly, not necessarily just upon closing them, but inevitably when doing so...

i'll try now copying just those plugins from the max7 folder and see what happens... but now at least this seems on par with what i've been reading about bugs in the max9 version... and not the insane situation i was but a few minutes ago  :-?

any thoughts, please post  :)

Cheers

well, i haven't tested everything thoroughly, but from what i'm seeing i think it's safe to say:

SUCCESS!!!  :D

all tools now work without crashing Max!!!
now, onwards to development!! i think i'll try making a dummy aircraft just to see if everything is working ok...

Thanks Fr. Bill for all the help!!

Cheers

HarvesteR

oh and BTW, i still have 3 more Aces Tools menus than a normal person would require.... if anyone know how to get rid of them, i'd be even more thankful  ;)

Cheers Again

I think you'd have saved some frustration had you contacted Chuck for help...

I'm sorry, but I did mean the ..\3DSM7 scripts.

By the way, I remember now that the copy of XToMdl.exe in the ..\3DSM9 folder is not digitally signed, so you will need to copy/paste the signed version from the ..\3dSM7 folder if you are running Vista (which doesn't like unsigned .exe or .dll files!)...

it's ok... the good thing about this is that now i got to know the SDK a lot better even before i started working