[ck3D]

Context: rotating sector 0 somewhere inside of sector 1024 (IIRC, maybe the other way around). Wall 0 is one of the boundary walls between the two.

Upon user action I am still trying to pin down (but seems to have to do with save/quit game/reload?), wall 0 might load way outside of map/corrupt, and from then on loading the room containing it will result in EDuke crash (tested with latest).

OG thread/post with log file and debug.map, can also share saves if needed: https://forums.duke4...161#entry387161

Still studying the map in case it's a map thing but the values and behavior make it seem like it's not.

[stillTodd]

I am no mapper, but I do QA and understand basic to medium C (including dabbling in Build). I can see if I can establish a pattern of recreatable behavior.

I'm used to the eduke32 version that comes with Dukeplus. Is that acceptable or should I use a newer/specific version?

Edit: I read more carefully, and if I'm reading with enough coffee present, it looks like things get funky with older versions of eduke32. As an aside, I feel like - on my slow system - for whatever reason the controls are not as responsive on newer versions than the one included with DP. I may be hallucinating that.

To explain: I'm keyboard only unless mouse required, and have a weird-ass method of play that involves a lot of jumping, autoaim and running backward while shooting, so I'm maybe a corner case in play style. As a result, keyboard control reaction time is paramount here.

[ck3D]

Thanks for offering to look into it; I just tried and confirmed my theory, it is saving, quitting game, then reloading the save that kills the map, including in newer EDukes.

Doesn't seem to break when reloading without quitting.

Can be achieved as soon as map start (in the non debug version) seeing as the problematic wall can be loaded from there.