When the option to lock the mouse while panning / rotating the camera is enabled, the performance can be a bit awkward in 0.0.25.0 due to the new code for this functionality. Next update will have some significant improvements for this.

I've also found a bug where the camera can't be rotated while in virtual lemming mode using the mouse. I haven't figured out the cause (or even narrowed down if this is related to the new code) yet.

Uploaded V0.0.25.0.

Changes:
> Added a menu to configure hotkeys.
> Added default hotkeys for instant min/max RR (Ctrl + Minus / Ctrl + Plus).
> Adjusted climber-bomber behavior to match that of DOS L3D.
> Fixed a bug that allowed skills to continue after ascending / descending.
> Fixed a bug that caused Clone Camera hotkeys to not work.
> Fixed a bug that resulted in the level select screen sometimes opening on a subfolder instead of the main folder when coming from the title screen.
> Improvements to how freezing the mouse cursor while panning/rotating the camera, and confining the camera inside the game window, is implemented.
> Removed the placeholder lemmings on the lemmings lost side of the postview screen.
> Rendering has been overhauled; there should be a lot less graphical oddities now.
> Unofficial levels are no longer included in the download.

Game: https://www.neolemmix.com/download.php?id=576
Music: https://www.neolemmix.com/download.php?id=530

I have removed all fanmade / test levels from the download now. Winterland is still included. The adjusted-for-Loap verison of Lemmings Plus 3D can be obtained from the pack's topic. There are no changes from the version included with Loap 0.0.24.0 so you can just keep using that if you have it.

Not yet as of f5a497b. 1 and 4 are consistent (continues), as are 2 and 3 (stops). Encountering a turner / blocker also stops.

As of adf2529 these are all consistent and result in the skill stopping. The only exception is if the skill is newly assigned (ie: the basher / miner has been given the skill, but not yet arrived at a position where he starts actually bashing or mining).

I finally finished putting together a collection of replays for the L3D levels in Loap.

Note that two of these - "Five Towers" and "Castle Peralus" - at least, won't work on the current test build. They'll work on the next one, or if you build from the current source. This is due to a physics fix regarding climber-bombers.

If your level relies on exploiting bugs in order to solve, then of course it is going to break when the bug gets fixed. The way to avoid this is to not make levels that rely on bugs to solve.

There can be cases where a bugfix ends up breaking a level that does not rely on the bug, simply due to exactly how the fix works. Such cases tend to be very rare, and more often than not the level itself doesn't break, just the replay, and it's usually just a matter of a few small tweaks to make a new replay that does work.

You are majorly overreacting here. Taking as an example the level you sent me - the replay fails with the bugfix implemented, but only by one lemming. That lemming can be saved simply by slightly changing the timing of one skill assignment, so the level as a whole is fine. If you've followed good practice and kept replay files for all your levels, you can run a mass replay check with the new version, and see exactly what levels fail. Unless you are deliberately relying on bugs as part of your levels' solutions (which is something you should not be doing in the first place), chances are very few if any replays will break, and most of those will be just the replay breaking.

Proxima's post is mostly spot-on about this. The one correction:

Much later, someone noticed that stoner oh-noers could still exit because they hadn't been specifically prevented; this was also immediately fixed.

While the fix has been implemented in the source code, it isn't yet included in a released stable build. It is included in the new-objects experimentals and will be included in 12.13.0 stable build.

I did a bit of Googling and was pointed towards MonoDevelop. Downloaded this in a Debian VM and attempted to build.

Upon opening Loap.sln (solution file containing Loap, the main project; LoapCore, which is a library containing physics and data functions seperate from the UI / visuals; and DeRNC, which as the name suggests decompresses RNC-compressed files as many L3D data files are), was prompted to install .NET. The website I was taken to suggested .NET 6.0 or 7.0; however the Windows builds have been built with .NET Core 3.1. Quick attempts to install this version failed, so went with 6.0.

wget https://packages.microsoft.com/config/debian/12/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb
rm packages-microsoft-prod.deb
sudo apt-get update
sudo apt-get install dotnet-sdk-6.0

I get MSB4236 error when trying to build all projects now. Some quick Googling suggests this is an issue with .NET 6.0 in some cases; rather than trying to fix it, let's try 7.0 first.

sudo apt-get remove dotnet-sdk-6.0
sudo apt-get install dotnet-sdk-7.0

I still get the same. >_>

Okay, let's see if a command line build works any better.

dotnet publish -c Release -r linux-x64

No errors. It seems to have worked. Let's go to the output folder and try to run it...

I try to run it. Nothing happens. I try in terminal; we're getting an error message about "can't find a valid ICU package". Some searching suggests intalling libicu63 should do the trick. It's not supported on Debian 12; I try the version that is (libicu72) but it seems to be already installed and not helping.

I also found a question regarding this issue on Stack Overflow. Didn't quite get what it was referring to, but came across a post on GitHub and it clicked. Tried this, ran the app again...



Performance is awful any time 3D graphics are in use, but that's very likely due to running it in a VM. It seems to work though!