Added enough text from the error message so that I know which error it is. Sorted the words in order of importance: 1. Crash, 2. Monitor, 3. during play, 4. error text.

Another good sorting is all causes first in chronological order, then all effects.

Another good sorting is all causes first in order of importance, then all effects. ("Monitor off while Lix plays: Lix crashes with error: Out of VRAM") This is probably even better than what I wrote. The uniqueness of this bug is that the monitor turns off. It makes a lot of sense to put that first.

---

For how long is the monitor off when the bug hits you?

-- Simon

For how long is the monitor off when this bug hits?

If it's for a few seconds, let's say 1-5 seconds, I'll catch the failure and skip the internal savestating. Afterward, the first rewinding will be more expensive, but not overly much so. It would be only a small price to pay.

If it's longer than 10 seconds, I should consider allocating all the VRAM bitmaps for savestating ahead of time.

-- Simon

All right, thanks for confirming that you see a bug like Silken sees.

"Its a windows 10 thing that your screen goes black its really weird": I don't know what exactly happens to you. I only know that Windows 10 turns off laptop screens to save power, but that's not what hits you; you're talking about resolution changes and refresh rate changes.

Workaround: Run Lix windowed, not in fullscreen. Or prefer software fullscreen over hardware fullscreen. But you've probably tried this already.

Will it be easier for you to explain it in German?

I haven't yet asked the Allegro 5 devs about a bug like this in Windows 10, or about Allegro 5's behavior (if it's even allowed to allocate new VRAM bitmaps when the screen is off).

-- Simon

I had given it 70 % to win outright, 20 % to see TOWN or similar sementaic-related white koan (WillLem had prodded in that direction but I had not), and 10 % to see semantically unrelated white koans for an obscure narrow letter-based rule (but it could hardly be anything).

After this many black koans, it's an important guess; others are likely to guess this otherwise.

I'll leave it for somebody else again to master next!

-- Simon

AKHTBN iff it is exactly CITADEL.

-- Simon

CASDLE
MNEMONIC
REST

-- Simon

C
I
ITADEL
CITADELL
CCITADEL
CITADELCITADEL

-- Simon

CITA
CI
CL
LEDATIC

-- Simon

Quote from: WillLemThe previous koan tools (Simon's and namida's) do exactly the same thing

Don't put spaces after the final koan of a row. They're nonbreakable inside tt tags.

Break the lines of the table earlier. You don't know how wide people's browser windows are. zendofmt linebreaks at 80 characters, which I like, and nobody has complained yet.

If we keep getting overly long koans that kill the table layout, we can start putting them outside the table. zendofmt has nothing for this yet.

-- Simon

CTAEL
CATLE
ADEL

-- Simon

Quote from: WillLem on December 06, 2024, 12:47:56 AMAnother idea, perhaps a bit out there: subtitles...?

Where do you want to print subtitles in the browser's list of levels so that they help Silken?

Quote from: Silken Healer on December 07, 2024, 02:12:47 AMlength limit is based on the width of the characters, not the amount of characters

Yes, and even funnier: The editor's length limit depends on the font scaling, which is not perfectly linear with respect to the resolution. At 1280x800, I get 27 X and 4 ., or 27 X and 2 a.

Title max length has always been vague. In the system as it is, you can't expect overly long titles to render abbreviation-free in every resolution. For now, the best is: Make titles shorter than 80 % or 85 % of what the box offers. Even if it fits in the editor, it won't necessarily fit in the level browser. This is a problem, but it's a different problem than what you want here.

For your use case (training variants of existing maps, and you aren't going to release the variants), I'd invent abbreviations and rely on the existing title support. 1P for single-player practice, +L for more lix, +P for more players, +S for more skills.

-- Simon

Yeah, the filename should be unbounded.

No decision for the title. It's good to know that you don't want to release levels with longer titles. Instead, you want to use extra title length as always-visible annotation.

-- Simon

Thanks!

I'll have to ask in the Allegro 5 community if it's even sensible to create video bitmaps while the screen is off. Video bitmaps are attached to Allegro displays, and Allegro displays rely on Windows's screen handling. I create new video bitmaps during play for the internal savestating, to support rewinding in singleplayer and physics recomputation in networked matches.

Blitz, if you get the crash (Lix thinks it's out of VRAM) without turning off the screen, it'll be a separate bug.

-- Simon

Thanks! I haven't merged every map yet into 0.10.27.

Lix multiplayer should be enjoyable without the helper buttons; the helper buttons reveal all trigger areas or highlight your hatches/goals.

Hidden traps and hidden flingers violate this. Hidden exits are even more problematic than hidden traps: Not only will the lix be removed, but your opponent gets a point.

You can bury the exits' trigger areas as long as the colored markers (X in opponent's color, or arrow in your color) remain clearly visible. How much burying is fine will depend on the map. On a busy map, it's better to make more parts of the exit visible than only the colored markers.

In the main Lix download, I don't want to proliferate hidden exits/traps. I should even fix my own map What's Behind the Curtain, which has hidden traps. It may be easy to guess where the hidden frogs are, but I should lead by example.

I've changed two of your maps in the already-released 0.10.27: Sleep Tight (2 players) and Wine Tasting (4 players). The colored exit markers are now clearly visible. I've left all other maps at your discretion:

Unmerged

2p amarcord.txt
2p burningdown.txt
2p catacombs.txt
2p challenger.txt
2p colddudes.txt
2p devilmen.txt
2p donaldducked.txt
2p donkeykong.txt
2p donkeykong2.txt
2p doraemon.txt
2p elgoleador.txt
2p embedded.txt
2p fairytale.txt
2p frankiebots.txt
2p goalonice.txt
2p invertislands.txt
2p itsfreezingtoday.txt
2p jeegrobot.txt
2p kongkingo.txt
2p lemmingsofliberty.txt
2p lemminkhamun.txt
2p manicfriends.txt
2p mayanmaze.txt
2p mechanicalbowels.txt
2p metalemmings.txt
2p mountainmagno.txt
2p myballs.txt
2p northpoletales.txt
2p overthebridge.txt
2p readytowers.txt
2p sakurasan.txt
2p solidarnosh.txt
2p tennisolid.txt
2p thatlongroad.txt
2p tombandtomber.txt
2p totoromadness.txt
2p totorosimplified.txt
2p unholymartyrs.txt
4p utilitybuildings.txt

I can't merge maps that recreate third-party copyrighted sprites (Doraemon, Donkey Kong, Pauline, Mario, and Meta Lemmings). I release Lix under CC0 (public domain), and Lix should remain allowed in Debian, which has strict rules.

There should be no age restriction. This is fickle. I'll err on merging no obscene level titles (please rename "My Balls"), no obscene scenery (North Pole Tales), and no politics. In the end, I can't make objective rules for this, and I'll have to judge everything case-by-case.

-- Simon

If you put longer titles, Lix will abbreviate your titles throughout the UI. You'll see abbreviations in the browser's level list, in the preview, ...

You'd also make it hard to talk about your levels in discussions. You're enticing people to abbreviate instead of typing the entire title, even if it's the first appearance in a post.

It's easy in the code to change the editor's text field for the level title from limited to unlimited. But given the exiting design throughout Lix's UI elsewhere, I prefer to keep that text field limited. It's a clear way to make people choose titles that render properly.

What kinds of titles do you want? Why do you need those? What are alternative titles that would fit, and why are they worse? How do you expect Lix to render your long titles? Do you want two rows of text for the title?

-- Simon