For some reason, I get an access violation when pressing the reset hotkey while playing a level. I wonder if it has to do with hovering the cursor over the trapdoor, then pressing the reset hotkey (I could be wrong, though).

Flopsy apparently caught a case of this on video. I'm waiting for his video to upload to see if I can pick up on any more-specific details that might help track down why this happens, or at least how to consistenly reproduce it.

I tried to replicate such an error, but for me everything runs fine. In fact I never got such an error since the new version.

This sounds like a very slippery problem    Maybe it's bound to happen on certain level types

I'm running on v1.47-C. This is the first time that this issue has happened to me in this version.

By doing this, I get weird effects, not nessecerially always the exception. Some other effects I've seen:

- A red-colored lemming appears in the top-left corner
- A "list index out of bounds" error; clicking OK on this one does not cause any kind of crash (the game will resume normally afterwards)
- A "ghost shadow"; ie: a shadow remains but there is no lemming projecting it

I haven't been able to actually reproduce the access violation with these steps, nor does Flopsy's video show exactly those steps. Pressing restart /while/ moving the cursor over a lemming, after at least 10 seconds have passed (suggesting it may relate somewhat to the saved states in memory) often triggers an unescapeable error; sometimes it's List Index Out Of Bounds rather than access violation. Holding the escape key will sometimes get out of this one, presumably because it triggers exiting the level before the next error message can pop up.


The common thread in all cases, nonetheless, seems to be that the cursor must at least be on a lemming when the restart key is hit, and possibly even moving. So the suggested workaround until I can figure out and fix this is to always make sure the cursor is not on a lemming before hitting restart.

In addition to the V1.47n-C2 release that should log any problems, here's an experimental release (1.47n-D:FC73BC8) that should fix the problem altogether. Some minor graphical glitches may still occur under the conditions that would trigger this, but crashes should not.

Unlike V1.47n-C2, this also includes other pending changes so far for V1.47n-D / V1.48n (such as the desync-proofing and extra object helper icons).

https://www.dropbox.com/s/o1r8mdzkyml7y5l/NeoLemmix.exe?dl=1

I'm going to assume this is fixed and close this topic now, since no one's reporting this issue on V1.47n-D or the V1.48n experimentals.

If it does arise again, feel free to start a new topic (or unlock this one, if the person encountering it has that ability).