I've tested the example program. It created the hardware fullscreen on non-primary monitor No. 1. The console window was created on primary monitor No. 2.
Attached is an allegro.log debug level.

I tested a bit (Lix 0.10.29 - release build - win64 - Allegro 5.2.10):

• Monitor no. 2 is set as primary monitor.
  
• Before play, go to Windows's monitor/display settings, and choose: Extend the display to all screens.
  
• Start Lix.
  
• Observe how Lix starts on monitor no. 2 in software fullscreen.
  
• Start a level and play.
  
• During play, go to Windows's monitor/display settings, and choose: Display to only monitor no. 2.
  

Either:

Out of VRAM error:
193.41 src\basics\alleg5.d:26:
193.41 Out of video memory. Can't create bitmap of size 913x946 with flags 5120.

Or:

Graphics stutter for 0.5 seconds or 1 second. After that, Lix continues to run smoothly without further stutter. But if there was terrain modification in that 1 second of stutter, e.g., a builder was building, then the newly built bridge slap is not drawn, and will continue to be invisible throughout the future:

Can reproduce this. Monitor with no. 2 set to primary monitor. Software fullscreen starts on monitor no. 2 but hardware fullscreen on monitor no. 1. I assume hardware fullscreen is determined by the assigned number of the monitor.

In your linked thread there is an answer that says "make sure its not full screened in the settings. it has to be windowed mode for this to work", though I don't know if it's accurate.
Does the Win+Shift+left/right arrow work with software fullsceen?
Is your primary monitor called 1 in the monitor settings or a different number?

Second option - allegro5.cfg

You can also create an allegro.log by modifying the allegro5.cfg and putting it in the same folder as the Lix executable. (This works even with release DLLs, i.e., with the DLLs that Simon offers in the main download. You don't need debug DLLs.)

allegro5.cfg can be found in the allegro5 github repo. Below [trace], which is in line 193 as of January 2025, set the trace level (level=) to one of the following lines:

level=debug	... to get all the information, but this will produce a huge logfile,
level=info	... to get lots of info, but not everything; this is a good level,
level=warn	... to get errors and some extra information,
level=error	... to get errors only.

Save this allegro5.cfg in the folder where lix.exe is. Then run Lix as normal. After playing, you'll find allegro.log in the same folder. Read it with any text editor.

(Simon restructured/edited this post for better readability/information.)

Quote from: Silken Healer on December 21, 2024, 12:16:27 PMAll my replays except the first have the fixed version, even though I reselected bunker buster from my ../network

Can you post the first replay that has the old version and another one of this session that has the fixed version?

Can you explain exactly what you did, esp. the timeline?

The levels are not (permanently) stored in the server. Simon might give a more elaborated explanation of how the server works.

This happens for me if I Win+L (equivalent to monitor turn off) immediately after starting the first level after opening Lix (with exp. version).

You should be able to open options.sdl (found in the folder user (which is itself in the Lix directory)) with most text editors, like e.g. Notepad (Editor in German). You can drag and drop it or right-click, click Open with (Öffnen mit in German) and select notepad or another editor.

(options.sdl is not a dll file.)

Quote from: Silken Healer on December 15, 2024, 09:09:00 PMI'm not sure [...] if you can change it from the options.dll,

It looks like it can be changed in options.sdl to odd numbers (decimal notation, name: guiColorRed; guiColorGreen; guiColorBlue).

Attached an example of the messed up colors.

Can you give the numbers which it happened with?

Quote from: Silken Healer on December 11, 2024, 03:59:19 PMbtw do I need to put that in a folder? I know Lix is self-contained. It's not gonna create a bunch of folders in a directory that already has stuff in it on the first time I run it right?

You have to put it in your Lix folder where the other lix.exe is. Lix is dependant on Allegro5 dlls which are part of the Lix distribution (and needs other files of the distro as well).

Quote from: Blitz on December 04, 2024, 07:14:10 AMThat Bug happens to me to somtimes my Problem is mostly when my RAM or Arbeitsspeicher reaches its max but it schould fix after you reopen lix

Which version of Lix do you use 32bit or 64bit?