Topic: SOLVED: Auto-map crashes level.

[-<WillyP>-]

So, test flying a level and I hit tab for the auto-map, but it 'dings' and crashes the level. I tested on other levels and the auto-map works fine, it's only in this level I am building. Any clues?



Call stack:
------------------------------------------------------------------
    main.exe 0056fa7c()
    kernel32.dll 7c817077()
------------------------------------------------------------------

[TechPro]

Never had the automap trigger a game crash.   Can't be of much help with this one.  Sorry.

[(LL)Atan]

Maybe your level hits a limit. Too big, or such a thing.
Did you see any warnings? (Message Bar)

[-<WillyP>-]

No warnings. I can fly to all parts of the mine and everything looks okay. No lagginess, either.

Ok, I've looked at your list of limits for D3Edit... I took that as a list of limits only to display the mine correctly in the editor, since I had already exceeded those limits and it seemed ok. But, I can't say for sure that I have tested the automap recently... 

Are those limits applicable to the mine in game also?

Specifically, your limits list 30 doors, I have 40. Do I need to remove 10 doors? Or does this mean doors won't display properly in D3 Edit?

[Scyphi]

Well, I'm no expert, but the most logical explanation to me is that you've got too much of something that's causing problems.

[(LL)Atan]

from Limits located at Fischlein:

MAX_ACTIVE_DOORWAYS   100   // specific doors inside mine
MAX_DOORS    60    // predefined Doors useable by Editor

These are the Door(way) limits.
As you can see it seems that 100 Doorways (this are Rooms with contain doors inside a mine) are allowed.
But you can have max 60 different doors.

Other idea, did you try DirectX and OpenGl inside D3 setup?
If you can't figure it out send me the mission and I'll give it a try to localize the problem.

[-<WillyP>-]

Ok, tried Direct3D, this time when it crashed I got the message about not finding a free polymodel. IIRC that means I must have deleted a polymodel from the mn3 but it is still placed in the mine. I'll look closer at that and get back to this.

I did not have the option of DirectX, I think you meant Direct3D... right? I had a choice of OpenGL or Direct3D. The DirectX tab says I have 9.x


Slightly off topic... but the tut you sent me list the doors in mine as 30 and different doors in the editor as 60.

MAX_ACTIVE_DOORWAYS            30   // specific doors inside mine
MAX_DOORS               60   // predefined Doors useable by Editor

30 does seem a rather small number, though!

[(LL)Atan]

Yes, Direct3D

Seems you didn't got the updated values. Just look on Fischleins, these are the last values.

60 Doors and 100 active doorways.
The last value isn't a real fixed one, you may be able to build a level out of 400 'Door-rooms'.

No free polymodel tells you, that you have too much polymodels inside your level.
There is given a max value of 1000 inside the editor. Even if you just own 100-200 you must see all that polymodels count during your game, means including ships, marker, weapons, spews etc. To make this clear give it a try with the check mod and fire a flare. Look how much 'objects' now inside your room, wait until the flare is near at it's end of life. The objects will increase for a short time to a bigger number..
I don't believe that D3 fills all objects into the memory at start, so it could be an idea to try starting the automap inside different rooms far away from the place you did it now. Maybe it runs then. This way you could possible focus to the 'bad' room.

[-<WillyP>-]

Ok. I only got that message about polymodels with Direct3D... Not with OpenGL. But, look at the screenshot I posted above, stats lists only 123 poly objects.

Automap crashes wherever I try it. The level starts at terrain. It crashes there. I've tried a number of different rooms, they all crash. I will try check.



I'll get the correct values from Fisch's site and update DescentiaPedia.

[-<WillyP>-]

Ok, automap fixed!

I removed unused polymodels from the MN3... but forgot to remove them from the gam file! Doh! Seems strange though that this would crash the automap but not the level.


Thanks so much for your help!

[SaladBadger]

I removed unused polymodels from the MN3... but forgot to remove them from the gam file! Doh! Seems strange though that this would crash the automap but not the level.

When it's the fusion engine we are talking about... Anything could happen at any wrong situation

[(LL)Atan]

@ WillyP
First of all it's a good message, good news!
Reading this.., maybe it would be an idea to let D3Edit check if all things inside the gam are really inside the mn3. Don't know if that is possible and I could insert it, but I place this idea on my todo list just now.

@InsanityBringer

When it's the fusion engine we are talking about... Anything could happen at any wrong situation

What would you like to tell us with your comment? I can't see the usable idea behind.
 

[SaladBadger]

That's mostly a joke at how buggy the fusion engine feels.

Granted, I haven't really done much modding, but for what I have played the Fusion engine does not always like working properly.

[-<WillyP>-]

That's a great idea, Atan... maybe could also check and see if there are items in the MN3 that aren't in the level.