Segmentation Violation, Trying to find solution.
I haven't been playing Doomsday for too long, but i too have had this problem as many of you have and from what i'm reading on the various forums, nobody really knows what's causing it, everybody has their own idea's of what might be causing it but let's face it, it's a real head scratcher.
I myself have been doing a little research into this because i absolutely adore this wonderful game and so badly want it to work perfect and the only thing stopping this now is this randomly occuring error. I have made some progress in discovering the problem i think. For a start, the SEGMENTATION VIOLATION i beleive is not and error from the Doomsday Engine itself, but from windows. A SEGMENTATION VIOLATION refer's to illegal memory access which would suggest that the problem lies within Doomsday's attempt to access a memory location that is not permitted by Windows. I think the reason this only occurs when using 3D models, is because Doomsday needs to allocate a lot more memory in order to load the 3D models, it's possible that it's running out of legal memory to work with.
I'm not absolutely sure how the original Doom worked i terms of loading into Ram, i always assumed, what with using sprites, that it just loaded everything into memory as sprites take up such tiny amounts, let's just say for the moment that it does, that would mean that when you load a Doom level using 3D models, the Engine is trying to load the entire monster set + decorations for that level all at the same time, which would explain the mass slow down on larger levels. It is possible to use "-maxzone" command in the shortcut to allocate more ram for Doomsday to work with, but even this is not enough as i have found even with a whole gig alocated for Doomsday, i still gets this error on larger levels.
I'm not sure how correct i am in this idea, but it's closer than anyone else seems to have gotten so far, i'm 99.9 percent sure on the error being a Windows error due to illegal memory access, but not sure on the rest, ive never mapped the original, only Doom 3. Any input on this idea would be much appreciated, i beleive between all of us we can find the solution to this problem.
Mark Page
=========
I myself have been doing a little research into this because i absolutely adore this wonderful game and so badly want it to work perfect and the only thing stopping this now is this randomly occuring error. I have made some progress in discovering the problem i think. For a start, the SEGMENTATION VIOLATION i beleive is not and error from the Doomsday Engine itself, but from windows. A SEGMENTATION VIOLATION refer's to illegal memory access which would suggest that the problem lies within Doomsday's attempt to access a memory location that is not permitted by Windows. I think the reason this only occurs when using 3D models, is because Doomsday needs to allocate a lot more memory in order to load the 3D models, it's possible that it's running out of legal memory to work with.
I'm not absolutely sure how the original Doom worked i terms of loading into Ram, i always assumed, what with using sprites, that it just loaded everything into memory as sprites take up such tiny amounts, let's just say for the moment that it does, that would mean that when you load a Doom level using 3D models, the Engine is trying to load the entire monster set + decorations for that level all at the same time, which would explain the mass slow down on larger levels. It is possible to use "-maxzone" command in the shortcut to allocate more ram for Doomsday to work with, but even this is not enough as i have found even with a whole gig alocated for Doomsday, i still gets this error on larger levels.
I'm not sure how correct i am in this idea, but it's closer than anyone else seems to have gotten so far, i'm 99.9 percent sure on the error being a Windows error due to illegal memory access, but not sure on the rest, ive never mapped the original, only Doom 3. Any input on this idea would be much appreciated, i beleive between all of us we can find the solution to this problem.
Mark Page
=========
Comments
This is the same level it was crashing on before, but i can get a lot further now, before it crashed always around the same place at the start of the level, so i must have done something to make this change.
Edit (DaniJ): Added [/code] tags.
Make sure it is a clean install, by removing the old deng instalation and then installing the new version.
see if that fixes the crash