Warning
This is an in-development test build, not meant for general use. It exists so the people in the linked issue can test a fix and give feedback, and it may have bugs that the regular release doesn't. If you aren't taking part in testing this build on that issue, please use the latest release instead.
This test build is for #462: the GPU crash ("device lost") on Intel Arc when leaving Mysterious Woods. It is test-462-arc-3 (Beta 5.4 plus the fragment shader loop limit) with three new diagnostics that narrow down what in the lit shaders' light loop the GPU hangs on. If it offers to update, skip that while you test.
On Windows, unzip it into a new folder and keep your normal install as it is. Set up your game files from the start screen as before. The first start prepares shaders for longer than usual.
What to try, one run each, in this order (all three, whatever the first ones do). Each run: add the line to larecomp.ini (replace any earlier diagnostic = ... line), play from the Field through Mysterious Woods and out again, and attach lasrecomp.log whether it crashes or not.
diagnostic = lights_off: the lit shaders skip their light loop entirely (small lights like torches and glows won't light the scene).diagnostic = lights_read: the lit shaders still read the light list but then skip the loop (lights look the same as in run 1).diagnostic = stack_regs: normal lighting, but the shaders' loop bookkeeping is built a different way.
The log's first lines say which diagnostic is on ([diag] diagnostic = ...).
Built from 637904d.
| File | sha256 |
|---|---|
LAS.Recomp-test-462-arc-4-linux-aarch64.AppImage
| 4d0e1b016c8758864e34f2bee228db8aadc1d9c861a8bd9721f9d49cd6776eda
|
LAS.Recomp-test-462-arc-4-linux-x86_64.AppImage
| 330835e429c5aee319b0a310c79bfb970ce836b15c856682fdc37724c375accd
|
LAS.Recomp-test-462-arc-4-macOS.dmg
| c6cb2b6e2ed51fe4b5994282ea8749963ed6f55effe5efaaa691f794e08baf99
|
LAS.Recomp-test-462-arc-4-windows.zip
| 90fe0b8e4e4126c5765cc1f1b236eab59377f7a470c4deefffd7f7590aec5478
|