Crash when Monitor off While Lix Plays Level, Error Box: "Out of VRAM"

[Silken Healer]

Yeah I turn the monitor on manually with a button on the back I dont time it but I wanna get back to Lix ASAP so I assume its only 2 secs or so

[Silken Healer]

Download: Lix executable that can skip automatic savestates

Does this help?

This executable is based on the current 0.10.27. It's a Windows 64-bit executable in release mode. This helps to judge framestepping performance after the monitor is back on.

The idea here is: We skip automatic savestates if you'd get the out-of-VRAM exception. The code is in branch vram-savestates in my unstable repo.

-- Simon

When I open that I get a bunch of red X errors

"The code execution cannot proceed because allegro something.dll was not found. Reinstalling the program may solve the problem"

btw 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?

[Forestidia86]

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

[Silken Healer]

Can I have both in the folder at the same time?

[Simon]

Yes.

-- Simon

[Silken Healer]

This fixes it! Thank you Simon!

[Simon]

Thanks for testing!

All right, I'll earmark this for the next release 0.10.28.

-- Simon

[Blitz]

The Monitor Turns back on instanly but Lix Just Crashes it also immediately Crashes Lix seams to hate every program itsept it self and the hz change with the ticks so Lix crashes randomly when it hits an other hz programm

[Simon]

Sorry, I have no idea what you're saying.

Please terminate your sentences with a period.

Too many things are "it". Please replace the many "it"/"IT" with "Lix", or with the name of your other program.

Did you run the experimental version of Lix (that I attached in reply #14), or did you run the stable version of Lix?

What exactly changes refresh rates ("Hz")? Monitors? Lix? Other applications?

-- Simon

[Blitz]

Sorry

What exactly changes refresh rates ("Hz")? Monitors? Lix? Other applications? I mean everything as long as the fps or ticks drops Lix crashes

-- Simon

[Blitz]

and the version... yeah no...



this is the full message:Lix version:  0.10.27
Session date: 2024-12-19 17:51:00
    49.73 Skipping automatic savestate at 40 ticks.
    49.74     -> Out of video memory. Can't create bitmap of size 672x400 with flags 5120.
    50.41 Skipping automatic savestate at 50 ticks.
    50.41     -> Out of video memory. Can't create bitmap of size 672x400 with flags 5120.
    51.12 src\graphic\internal\getters.d:49:
    51.12 Can't find unrecolored spritesheet at: data/images/lixsprites.png. The spritesheet is required for physics because the number of sprites per row affect worker cycles. Is your Lix installation broken?
    51.16 0x00007FF71772D264
0x00007FF71772CFA4
0x00007FF71772886D
0x00007FF71771D5F1
0x00007FF7176EE804
0x00007FF71762C37C
0x00007FF7175E9F43
0x00007FF71758C234
0x00007FF71758237A
0x00007FF717582744
0x00007FF7175828EC
0x00007FF7175FB379
0x00007FF7175FC396
0x00007FF7176025B3
0x00007FF717603A04
0x00007FF7175C331A
0x00007FF7175C2B39
0x00007FF7175C1CEB
0x00007FF7175C4674
0x00007FF7175C3E49
0x00007FF7176F3C45
0x00007FF7176F38D1
0x00007FF7176F3BA3
0x00007FF71773B07A
0x00007FFA9BED7374 in BaseThreadInitThunk
0x00007FFA9DAFCC91 in RtlUserThreadStart

[Forestidia86]

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

[Simon]

Blitz, thanks for the logs and the screenshot! I know exactly what's going on now. Forestidia, thanks for the straightforward reproduction.

Lix recolors the spritesheets only on demand (lazy loading). And it looks like Lix crashes consistently when the monitor is off while Lix wants an image file from disk for the first time. Both a savestate and a loaded image allocate a new VRAM bitmap.

The obvious situation for new VRAM bitmaps during play was the automatic savestate. The expiremental version skips this savestating when the VRAM allocation fails, and this looks good, and I'll release this in 0.10.28.

I can also look into changing the times when Lix loads new files from disk. E.g., I can anticipate what will be needed (spritesheets mostly), and move this loading to the start of the level, or even earlier. But I'll release 0.10.28 today without this.

-- Simon

[Blitz]

In the middle of this year I sent you Simon a crash report could it be that this problem caused this on because before I had the blue screen there was a crash report in Lix and then it closed and I guess that the mouse cursor clicked which crashed Lix but it couldn't create a report because I didn't have another program open and Windows hates something like that when it has its head is not enforced, so there was a critical error that caused the Blue screen and no crash report Silken would it Make sense if it did that?