Jump to content
Sign in to follow this  
fael097

script creates new menu on each startup

Recommended Posts

so i configured my 3ds max 2008 to the max9 sdk folder, and everything is working. the only problem is that each time i open 3ds max, it creates a new "Aces Tools" menu on my menu toolbar. i have to remove one each time i start, otherwise they'll reproduce as rabbits and populate my entire menu bar. heres the script: (the acestools.ms file from max9 folder in sdk)--------------------------------------------------------------------------------------------------------------------------------------------------------Get the text for the macro scripts to be created from existing scriptsmacroScript ExportLOD category:"Tools" tooltip:"Export and LOD tool"( try (execute (openFile (acesPluginRoot + acesMax9ScriptsFolder + "\\ExportAndLOD.ms"))) catch (messageBox "This tool is currently not supported."))macroScript UVToolSuite category:"Tools" tooltip:"UV Suite Deluxe"( try (execute (openFile (acesScriptsFolder + "\\UVSuiteDeluxe.ms"))) catch (messageBox "This tool is currently not supported."))macroScript containerCreator category:"Tools" tooltip:"Build Container Tool"( try (execute (openFile (acesScriptsFolder + "\\BuildContainerTool.ms"))) catch (messageBox "This tool is currently not supported."))macroscript wheelTool category:"Tools" tooltip:"Wheel animation tool"( try (execute (openFile (acesScriptsFolder + "\\WheelsSetupTool.ms"))) catch (messageBox "This tool is currently not supported."))macroscript fileRenamer category:"Tools" tooltip:"Rename Flightsim File"( try (execute (openFile (acesScriptsFolder + "\\RenameFile.ms"))) catch (messageBox "This tool is currently not supported."))macroscript AttachPointTool category:"Tools" tooltip:"Attach Point Tool"( try (execute (openFile (acesScriptsFolder + "\\AttachPointTool.ms"))) catch (messageBox "This tool is currently not supported."))macroscript FSCloudTool category:"Tools" tooltip:"Flight Simulator Cloud Tool"( try (execute (openFile (acesScriptsFolder + "\\CloudTool.ms"))) catch (messageBox "This tool is currently not supported."))macroscript FSXShaderTool category:"Tools" tooltip:"Update to and Work with FSX Shaders"( try (execute (openFile (acesPluginRoot + acesMax9ScriptsFolder + "\\FSXShaderTool.ms"))) catch (messageBox "This tool is currently not supported."))macroscript FSXMatEditorTool category:"Tools" tooltip:"Edit materials in the Materials.xml file"( try (execute (openFile (acesScriptsFolder + "\\MaterialEditorTool.ms"))) catch (messageBox "This tool is currently not supported."))macroscript RemoveFSXMaterials category:"Tools" tooltip:"Remove FSX materials from scene"( try (execute (openFile (acesScriptsFolder + "\\RemoveFSXMat.ms"))) catch (messageBox "This tool is currently not supported."))macroscript AnimationManager category:"Tools" tooltip:"Start the FSX Animation Manager"( StartFSXAnimationEditor();) try (fileIn (acesScriptsFolder + "\\Startup\\XMakeFootprint.ms")) catch ()macroscript MakeFootprint category:"Tools" tooltip:"Make footprints per city"( if usingAcesBuild then ( setupFootprintUI () ) else ( messageBox "This tool is currently not supported." )) macroscript FSMobileSceneryTool category:"Tools" tooltip:"Mobile Scenery Offset Tool"( try (execute (openFile (acesScriptsFolder + "\\MobileSceneryTool.ms"))) catch (messageBox "This tool is currently not supported.")) newMenuID = genClassID returnValue:trueif menuMan.registerMenuContext newMenuID[1] then( mainMenuBar = menuMan.getMainMenuBar () subMenu = menuMan.createMenu "Aces Tools" exportItem = menuMan.createActionItem "ExportLOD" "Tools" if usingAcesBuild then UVScaleItem = menuMan.createActionItem "UVToolSuite" "Tools" if usingAcesBuild then containerItem = menuMan.createActionItem "containerCreator" "Tools" wheelToolItem = menuMan.createActionItem "wheelTool" "Tools" if usingAcesBuild then fileRenamerItem = menuMan.createActionItem "fileRenamer" "Tools" attachItem = menuMan.createActionItem "AttachPointTool" "Tools" fsxMatItem = menuMan.createActionItem "FSXShaderTool" "Tools" if usingAcesBuild then fsxMatEditorItem = menuMan.createActionItem "FSXMatEditorTool" "Tools" if usingAcesBuild then removeFSXItem = menuMan.createActionItem "RemoveFSXMaterials" "Tools" fsxAnimItem = menuMan.createActionItem "AnimationManager" "Tools" if usingAcesBuild then makeFPItem = menuMan.createActionItem "MakeFootprint" "Tools" cloudItem = menuMan.createActionItem "FSCloudTool" "Tools" if usingAcesBuild then msoTool = menuMan.createActionItem "FSMobileSceneryTool" "Tools" subMenu.addItem exportItem -1 subMenu.addItem fsxMatItem -1 subMenu.addItem fsxAnimItem -1 subMenu.addItem attachItem -1 if usingAcesBuild then subMenu.addItem UVScaleItem -1 subMenu.addItem wheelToolItem -1 subMenu.addItem cloudItem -1 if usingAcesBuild then subMenu.addItem fsxMatEditorItem -1 if usingAcesBuild then subMenu.addItem containerItem -1 if usingAcesBuild then subMenu.addItem fileRenamerItem -1 if usingAcesBuild then subMenu.addItem removeFSXItem -1 if usingAcesBuild then subMenu.addItem makeFPItem -1 if usingAcesBuild then subMenu.addItem msoTool -1 subMenuItem = menuMan.createSubMenuItem "Aces Tools" subMenu subMenuIndex = mainMenuBar.numItems() + 1 mainMenuBar.addItem subMenuItem subMenuIndex menuMan.updateMenuBar())------------------------------------------------------------------------------------------------------------------------------------------------------i believe the problem lies in the line that starts with:"newMenuID = genClassID returnValue:true"as if i start a comment in there, until the end of the document, every time i start 3ds max, one aces tools entry will disappear. but if i leave it like that, then i wont have the menu after some starts, so how to make it keep the menu, one time?! thanks in advance

Share this post


Link to post
Share on other sites

Already answered at FS-Developer. :(


Fr. Bill    

AOPA Member: 07141481 AARP Member: 3209010556


     Avsim Board of Directors | Avsim Forums Moderator

Share this post


Link to post
Share on other sites
Already answered at FS-Developer. :(
unfortunately nope, manually removing wont fix it, you need to edit the script itself, but im figuring out the answer on max forums :)

Share this post


Link to post
Share on other sites
unfortunately nope, manually removing wont fix it, you need to edit the script itself, but im figuring out the answer on max forums :)
Funny that. I didn't need to "edit" any scripts to have it work properly...

Fr. Bill    

AOPA Member: 07141481 AARP Member: 3209010556


     Avsim Board of Directors | Avsim Forums Moderator

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...