memory problem

[`teh1]

Press shift-command-3 and it will take a screenshot and put it on your desktop as Picture 1.png. Upload the screenshot to http://imageshack.us/ and paste the link here. Make sure that the screenshot has the error message in it. In other words, take the screenshot while the error message is popped up.

[⑨]

There actually IS an "Out of memory" message, as far as I know and that is the exact message.
It usually appears when a malloc() returns NULL, which happens when no memory can be allocated because it's either full or something else is preventing it.
That means that you don't have enough RAM, or that there is too much going on in your game.
A large map with a lot of polygons or groups could cause this, for example.

[gamecat]

Here is the screen . When after telling the editor to run dim3 try to open but dose not instead the screen shot shows up.

[`teh1]

Looks as though the Engine is already open in the background. Try quitting it first.

[gamecat]

I saw in the screenshot the Engine was open. The Engine I didn't know had to force quit. But click on OK  on the error message it quits the Engine so you don't need to force quit.

[Gungnir]

The Engine I didn't know had to force quit.

Huh?  Do you mean that you had to force quit it after you took the screenshot?

[`teh1]

That could have been the problem. Did you still get the error after force quitting the engine? If not then this is a bug – As Oddity mentioned, it works fine on his system which is far inferior to yours.

[gamecat]

No I didn't

[`teh1]

Well then, since you didn't get the error after quitting the engine the problem is solved! Have to make sure the engine isn't running in the background next time.

[Nightblaze]

Quitting the engine wouldn't solve the problem if he was testing in the engine...

So basically the only thing you can do is save what you do in the editor, quit the editor, and run the engine and test your game.

[⑨]

Actually I really doubt that this has anything to do with it.
Starting the engine from the editor when it's already running in the background does nothing but bringing it to the front.
I don't see how this would display the "Out of memory" error.
You can't even tell if the engine was running before, just by looking at the screenshot.
This is something completely different and I just figured out what it was.

If you create an entirely empty map and the engine tries to load it, it will throw that error.
That's what it is, nothing else.
Probably because of some weird malloc(-1) or something like that. I'm not actually sure. Maybe it's something different that Brian is not handling correctly.

[`teh1]

Fair enough. Put some good stuff in your map, gamecat. And bink, remember that it wasn't responding. He had to force quit it. Theoretically, yes it should simply bring it to front, but perhaps it started to hog a lot of RAM.

[gamecat]

You are right about it being empty.