Quote from: Silken Healer on October 22, 2026, 05:01:49 PM

Quote from: Simon on September 17, 2026, 03:02:56 PMI like it if users can discover the formats and hack Lix at file level.

I also like it if users can discover formats and hack Lix at the file level too.

Quote from: Simon on September 17, 2026, 03:02:56 PMI have a soft spot for the Windows 7 users even though I've never used 7 myself. Those users should install a good text editor: Notepad++, Geany, ...

I also have a soft spot for Windows 7. I also have another soft spot for everything to just work too on the default text editor without having to install a new one, which would incline me to want CRLF to be used. Though this is just my personal soft spot, maybe not a good idea to force on everyone if LF has all these other reasons for being better? Sorry, I don't have the technical background to understand what LF or CRLF means and I haven't had the motivation to understand it lately but I wanted to add my thoughts here before you just decide to go ahead with it as no one else replies. Would there be any way for Windows 7 users still edit Lix levels on Notepad and it would just be trickier or it would just not work entirely or...? Again as I said sorry I don't have the technical background to understand what LF or CRLF means and I haven't had the motivation to read the website explaining but I wanted to put my thoughts here before you just go ahead with it due to no replies.

The problem is that Notepad on systems older than Win10 usually doesn't understand the LF line ending. This means that the text in the file appears to be in one line without line breaks (apart from maybe random line breaks if you have that option on). You can open for example anyway.txt in the Lovely folder with Notepad to see how it looks in Notepad to you (assuming you are on Win7).
The current Lix version creates CRLF endings on Windows when saving a level in the Lix editor. So you can transfrom the line ending to CRLF with "legacy" Lix. Just open Any Way You Want in the Lix editor and save. Then look at the file anyway.txt again, it should show properly then.

You have to rename the part in the replay name 'decompressionmeth1' to 'decompression' for Load Replay to work apparently.

Suggestion:
To create clarity with the timed Outtakes levels there should be the ticks according to D-Lix in the title instead of time.

"Just a quickie": 480
"It's hero time again!": 930

and my suggestion with "Time Out" would be 3180 since the level would give 210s time limit.

15n+45 would be the mere conversion of ticks in seconds, since 15 ticks are a second and Lix starts at 45 ticks. (The first spawn is at 60 ticks.)

But NepsterLix was designed for late C++-Lix, which still had time limits. According to Simon in the NepsterLix thread Lix spawned at 2 seconds in newer C++-Lix. In D-Lix they already spawn after 1 second (45+15=60). That's why in the calculation 1sec=15 ticks are substracted, which leads to 15n+30.

This would lead to

"Just a quickie" has 30s, i.e. 480 phuys in D-Lix
Nepster's own replay says 460 phyus for saving the last required lix.

"It's hero time again!" has 60s, i.e. 930 phyus in D-Lix
Nepster's own replay says 923 phyus for saving the last required lix.

"Time Out" has 180s, i.e. 2730 phyus in D-Lix
Nepster's own replay says  2739 phyus for saving the last required lix.

Nepster's replay is over the limit with 15n+30 for "Time Out" but the Level file says actually 210s ('#SECONDS 210'), which would be 3180 ticks. So this could be a mistake in naming the level since the other levels have the corresponding #SECONDS line. (The level is solvable under 2730 ticks as a side note.)

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).