Okay, I am using BlueStreak with gmax to export my halo map, and it says:
Out of Scripter Memory - Use options to increase

How do I fix this? I used to be able to compile my maps easily, and now I get this error..

Check your preferences. Under Maxscript, there is a number (supposed to be 1000).

kk thanks.. for some reason it was at 10..

also when working with very large models its good to increase memory using maxscript listener.

(ex. "heapsize += 100000000" should do the trick if not switch the + and the = in reverse order.) ive ran into this a couple of times when making first person models for my mp40 weapon

I did that but then Gmax crashed after a certain limit.

I have to same problem.
Edited by Head Noob on Dec 13, 2010 at 03:31 AM

am i the only person that barely has errors?

Great. I just did what it says in this form to make it run for big maps and now it opens then crashes.

OMG NEVER DO THIS.
I've had this problem a lot in my gmax days, here's how to fix it:
Go to the gmax folder in program files.
Find gmax.ini, which is your configuration settings. Open it with notepad.
CTRL+F and search for Maxscript.
You SHOULD see a section that looks like this:
Change the Initialheapsize= number down to around 100, so you can open gmax again. Save.
Once inside gmax, set it back to a reasonable number. I suggest 1000, but I use 200 sometimes (if I don't need to run any scripts).
If you can't find that piece of code in the INI, copy and paste my settings (above) into the bottom of the INI file and save it.

EDIT: I also want to add that gmax DOES have the backup system 3DS max uses. File>Open and look for an autoback folder somewhere around the folder where your scenes are saved. Make sure you are looking at "all files" and not only .gmax files.
Edited by SlappyThePirate on Dec 13, 2010 at 05:30 PM

Whoa, you lost me. This is what my heapsize is:

InitialHeapSize=7.500000

So I want to change that number to 100? Or 200? Or the lowest number I can get it?

What was your heapsize before you changed it to a zillion?

Me? I never changed anything yet. I haven't touched the heapsize.

Then what's the problem? You only have to change this value if you cannot run a script or cannot open gmax.

The problem is I'm trying to import a map with a script and it gives me this error:

Out of Scripter Memory - Use options to increase

When I do what you said gmax crashes.

The heap size should be enough to handle what you're importing (BSPs take a lot of heap memory), but not so much that gmax crashes. If your computer crashes regardless, perhaps your computer is bad.

Most likely, This computer is almost out om memory, it runs three operating systems and is a little old.

I no haz configuration settengs :(

i hate to bump this, but now that i searched thru my forums and saw this it shocked me.

oddly though for me my meathod worked absolutely perfectly when i was trying to export the model. (it had a ton of geometry for a first person model. probably cause its got so many curves and stuff.) i was very pleased with the way it turned out for me. im suprised it came back for other people so negitively. i actually searched on internet forums for this very issue"(out of scripter mem use options... etc) and i came up with my meathod. idk lol. its good to have backups. im sorry for causing some of peoples work to get lost. i honestly didnt intend for that to happen. i thought i was helping lol

I would like to apologize as well.
Pepzee said 7.5, and I thought you said 7500000 aka "a zillion". If pepzee is still having this problem, try 0 ans open gmax. Increase by 100 until gmax doesn't crash on startup.

No, I never figured this out. First I changed the heapsize to 0 and got this error:

In file:'..\..\maxsdk\include\maxscript\Colctble.h'
Line: 107

Don't know what that means, then I changed the heap size to 100 and it just crashed while opening it.