Results on one of the better laptops I currently have access to. When I have time I can try it on older, slower computers too. I believe the computer is relatively new model that came out within the last 2-3 years.
(yes, the logs show that I aborted one of the first benchmark runs, because it was clicked on by accident, partly due to the mouse issue noted immediately below. The log does end with a completed benchmark run.)
But bad news: with D lix, mouse actually has bugs for me on this computer in both windowed and fullscreen mode, that do not happen with the current C++ lix. I suspect this may be due to the DPI settings I'm using. I'll try to explain more on that in another post. In fullscreen, lixd is not correctly handling mouse cursor movement, such that for example when I moved the mouse as far to the lower-right as I can, the cursor displayed in the program is nowhere close to the lower-right corner, as seen in the attached zipped screenshot. Note that it's not just merely the game's cursor being displayed in the wrong position--where the game's cursor is displayed does actually correctly reflect the UI element in the game you will be able to click on--so this bug means there are areas of the game's display that I cannot reach to click on at all.
In windowed mode, the mouse is okay, but it fails to retain mouse capture once I switched out to another window via Alt+Tab. And I kind of have to always do that at the start because for some reason, when launched lixd insists on positioning the window off to the lower-right corner of the screen instead of centering it like one would expect. And since it starts off with working mouse capture, I can't move the window without using Alt+Tab first to switch out first (which turns off the mouse capture, allowing mouse to reach the title bar of the window to drag). In C++ Lix when I do this sort of thing, as soon as I switch focus back to the Lix window, mouse capture will work correctly again. In D Lix, it seems to permanently lose mouse capture, so the system mouse cursor (ie. the arrow) remains visible at all times after the switch out, and mouse is no longer confined to the window when the window has focus. The system-mouse-cursor remains visible actually also happens if I Alt+Tab in fullscreen mode.
One other fun side effect of the mouse problem in fullscreen is that, I discover the level selection UI currently does not seem to respond to ESC to go back to the main menu. So in fullscreen mode I end up stuck if I go there, because due to the aforementioned bug, I can't position the mouse to reach either button.