|
2 registered members (dr_panther, 1 invisible),
620
guests, and 2
spiders. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
Re: crash after level_load
[Re: Iglarion]
#457772
01/29/16 22:03
01/29/16 22:03
|
Joined: Feb 2006
Posts: 1,011
Germany
pegamode
OP
Serious User
|
OP
Serious User
Joined: Feb 2006
Posts: 1,011
Germany
|
After resaving all models and textures in game folder, one of the things i would try is to comment each line of code where you play sounds. I only once had this problem in my game (engine crash without any error message and without any warning) and i found after pain search that i simply put one line for playing sound on wrong place which causes crash. The only luck was that this was happening always and only in the same level, and it helped me a lot. Also with this you will check did you maybe have damaged sound file. In your case i don't think that problem is in damaged file, it should probably show engine error message but with this kind of crash you simply must eliminate this possibility.
Whether there is any previous indication that crash will happen, such as a sudden jump in consumption of memory in debug panel or something? We use FMOD to play all sounds and music ... at least the fmod debugger showed no problem. If there was a way to debug the level and code it would be much easier. I didn't really get it why the SED debugger uses an XML data structure internally :-(
|
|
|
Re: crash after level_load
[Re: Superku]
#457775
01/29/16 23:05
01/29/16 23:05
|
Joined: Feb 2006
Posts: 1,011
Germany
pegamode
OP
Serious User
|
OP
Serious User
Joined: Feb 2006
Posts: 1,011
Germany
|
Almost every function in the project writes log information when starting, exiting and several information while running. In case of this crash the engine just crashes once the first wait(1) after the level_load is reached. I'm already logging out all currently running functions between level_load and wait, something like:
level_load("xyz");
print_all_running_fct();
wait(1);
But that didn't help. I removed all of those functiona, but the crash still occured. The only way to get rid of this crash was to add or remove a model in the level, but I'm sure that the crash will appear at another point of the game, because I did quite the same some months ago. I had exactly the same crash, just the starting level was another one, but the level that crashes was the same. Then I changed the order of the models in WED and the crash didn't occur anymore ... until now.
|
|
|
|
