1.9beta Plutonia map 30 weird crash

SearinoxSearinox
edited 2010 Sep 14 in Technical Support
I'm experiencing an extremly odd crash with plutonia map 30. Charging at full speed and hitting this corner will freeze the game. Staying precisely in the corner and pushing against it is fine but charging at about a 45 degree angle into it will freeze up Doomsday. This happens regardless of addons, you can run the game clean and it will sdill do it. I've clipped my way to the back of the gatekeeper, where there is a narrow area between wall and its structure, then took the code off. Hitting the corners there has the same effect. This oddity does not, to the best of my knowledge, occur anywhere else in other games or levels. The logs do not reveal anything. Also note, because it requires HITTING the corner, have clipping off.

EDIT: I've added a screenshot of the place and angle to be attacked, for referrence. http://i54.tinypic.com/qrc0t0.jpg

Comments

  • SearinoxSearinox
    I've come up with some extra info by examining the bug. Remember I said that the backend of the gatekeeper also crashes me? I checked the map and these spots have identical geometry, pointing to the engine not liking something about these type of occurences. I tried hugging the outer walls and sliding in slowly and that resulted in me being "catapulted"(presumably the wallrun glitch) right through the wall, outside map bounds.

    Here is a picture of the areas, and now I will proceed to lookup other levels of Doom and look for similar geometry in order to see if I can reproduce it in other areas. http://i52.tinypic.com/24w6l54.jpg So far it's looking to be a collision detection bug.
  • DaniJDaniJ
    We already have enough info about this particular issue, thanks.
  • SearinoxSearinox
    Okay please drop the entire report. It seems that the most recent build does not have it.

    As the result of a beta 6.9 crash I have documented in another thread, I went down to 6.8. This is the version I am using now and the version which has the bug in question. As a simple test I went back up to 6.9 and was unable to reproduce the bug. It was most likely fixed. I will however continue using 6.8 until the other bug is fixed aswell.
Sign In or Register to comment.

© Vanilla Keystone Theme 2024