Good catch, thanks. Link is fixed. I had put 3 'a' in a row by mistake.

WillLem: Written summary of the feature testing will follow here tonight. Then you need not watch it all.

-- Simon

Recording done. Editing usually takes a few weeks for them. I'll link it here when it's published.

Mostly Lemmings 1 with its history and oddities. Some tenets of custom level design. Short glimpse into L2, L3, other licensed games.

-- Simon

Splitters are particularly problematic code-side

What issues do you see code-wise?

At best, I see how splitters can be boring when you send too few lems through: 50 % of the time, a splitter does nothing but prepare itself for the next time. namida grabbed it from L3D, where it rotates by ±τ/4 all of the time instead of 50 % of the time, in hope that it works well enough in 2D. Reminds me of how I hopefully took the walker from L3, where it either turns or cancels, but oddly never both.

-- Simon

WillLem, yep, happy to have you join. Haven't yet heard back from you yet. How is it?

Would somebody else be up to join if WillLem can't make it? It's well possible that you're deeper into custom levels than I've been, that you've been around Lemmings Forums longer, ...

In a pinch, it's fine if I'm the only one from the forums here to join.

-- Simon

Right, we fix bugs in the physics nowadays. Indeed, the cultural difference is surprising in hindsight. Thanks!

MazuLems, I haven't played it properly. >_>;; I'll try to remember it for the podcast, but I'm not sure if I'm the most qualified to bring that one up. Which brings me to:

Who would like to join?

Since yesterday night, we have an open seat. Patrick, the player from their community who built a CustLemm pack, has dropped out of the planning. Nobody else but the two main organizers and I are on it, and they would be happy to have a 4th person on the podcast. The recording will be this Sunday, March 24th, some time during the European afternoon. Podcast participant guide, they use a Jitsi conference call that runs in the browser, and you're supposed to record yourself locally and submit the ~2-hour recording to them afterwards.

Hop on IRC: #dosgameclob on AfterNET.

-- Simon

So - for whatever reason, UserSetNuking seems to be needed wherever it currently appears in the latest commit.

I agree! From digging the source: UserSetNuking is indeed part of the physics, not the UI. It's good that it's part of the physics, then it makes it the prime candidate to check in StateIsUnplayable, ShouldWeExitBecauseOfOptions, ..., which all care only about a reached physics state (and maybe options), never about UI.

UserSetNuking tells you if a nuke has been applied from the replay to the physics state, either now or during any earlier physics update. This is exactly what you want to know: Is the nuke active. (And it's not: Has the user double-clicked the nuke button on this main loop iteration.)

There is also ExploderAssignInProgress, which becomes true when UserSetNuking becomes true, but eventually becomes false when physics have run out of lemmings that can receive countdowns. Thus, this ExploderAssignInProgress isn't useful for us.

Let's still have a session tomorrow as planned.

-- Simon

Quote from: Simon on March 14, 2024, 12:49:10 AM

What happens to this option when we start NL with empty options file/new installation/...?

Same thing as with every other option: a default is set (in this case, Always Exit To Postview).

Consider to change the default to: Exit only if won, freeze if lost. namida agreed that this can be a sensible default.

That will then happen to match what I saw in the settings menu after supplying the exp 3 config. If we want to debug this properly: My hunch is that you hardcoded the defaults in two different places (e.g., once in the options menu, and once in code that loads config files) and the two defaults don't agree.

@Simon - Let me know if you'd like another session on this.

I'll be available tomorrow (Tuesday) evening from 18:00 UTC through 23:00 UTC. I'll also be available Wednesday from 18:00 UTC through 23:00 UTC. I'll sit in Mumble at those times.

Alternatively, at these same times, I can stream playtesting. If you're really fast with the bugfixes, a stream may be more useful than code review in Mumble. But I'll plan for looking at code via Mumble.

-- Simon