Cris Tales crashes on 3rd gen Intel Celeron 1007u

[iWisp360]

When you reach specific places of the game, such as the ruins at the final of the game, it crashes instead of loading the scene successfully, and then, when seeing the entire game logs, a d3d11 error happens.

Software information

• Game: Cris Tales
• Resolution: 1280x720
• Vsync: enabled

System information

• GPU: Intel HD Graphics (Ivy Bridge GT1)
• Driver: Mesa 26.0.8
• Wine version: cachyos-proton-10.0-20260425
• DXVK version: idk, it's what my cachyos proton provides
• Distribution: Fedora KDE 44, tested on wayland with lutris as the game launcher

vulkaninfo output
game logs when the crash happened

[iWisp360]

the issue isn't reproducible on my PC with a Radeon RX 6550m, the same proton version, and PROTON_DXVK_SAREK=1 %command% as the Launch options on steam, because the offending part of the game referred in this issue loads successfully on my pc

[pythonlover02]

I think I know what the issue is, if I am correct it's our own soft budget cap.

On UMA, the constructor sets heap->budget to 80% of heap size (~1.2 GiB on your 1.5 GiB IVB iGPU). Then tryAllocDeviceMemory early-outs. Every fallback in alloc() hits the same check, so it throws DxvkError > d3d11 returns E_INVALIDARG > Unity crashes.

It shouldn't be hard to fix if it's that, but it will need testing on your machine @iWisp360.

For now I will be reading upstream source code and sarek to avoid any regressions. Will add another comment once I have a fix for you to test.

[pythonlover02]

@iWisp360 could you check if this build fixes your issues; you can use wine + this dxvk version for testing it

[iWisp360]

@iWisp360 could you check if this build fixes your issues; you can use wine + this dxvk version for testing it

Gotta try, but it will take some time due to power outages here. Thanks for the support

[iWisp360]

I was able to reproduce this error on a Pentium N3710, with GPU "Mesa Intel HD Graphics 405 (BSW)", the pc has 4gb of ram.

Gotta send logs.

[iWisp360]

I was able to reproduce this error on a Pentium N3710, with GPU "Mesa Intel HD Graphics 405 (BSW)", the pc has 4gb of ram.

Gotta send logs.

Same d3d11 error from the initial post on the game logs with the dxvk build u sent. I used this wine build and heroic games launcher to run it on the Braswell gpu. Do u want an apitrace with this wine build and the prefix with the dxvk build u sent installed on it?

[iWisp360]

I was able to reproduce this error on a Pentium N3710, with GPU "Mesa Intel HD Graphics 405 (BSW)", the pc has 4gb of ram.
Gotta send logs.

Same d3d11 error and crash from the initial post on the game logs with the dxvk build u sent. I used this wine build and heroic games launcher to run it on the Braswell gpu. Do u want an apitrace with this wine build and the prefix with the dxvk build u sent installed on it?

Also, do u want a video to see how it crashes?

[pythonlover02]

thx for testing on both machines.

I want to go through the plausible issues one by one on a branch and then give a final build, you test it and we see if it works. I got some ideas of stuff that has been flagged as wrong and fixed/mitigated on upstream like suballocator fragmentation, chunk sizes being too large for the leftover headroom, GTT exhaustion from Unity staging copies, etc.

If none of those work, its probably Mesa/i915 genuinely not being able to satisfy the allocation on these iGPUs and we are out of DXVK side options.

While I work on the branch, can you try DXVK_CONFIG="dxvk.maxDeviceMemory=1024" It caps sarek at 1024 MiB which sounds counterintuitive but may force earlier eviction and dodge the fragmentation buildup.

Apitrace and a video its welcome :).

First build in a day or so.

Thanks for the support

np, im glad i can help.

[iWisp360]

Will try tomorrow, thx

[pythonlover02]

@iWisp360 could you test this build?

It lowers VRAM/GTT usage a bit on startup, using smaller memory chunks growing as needed instead of grabbing big ones from the start, which won't fix the crash by itself but should reduce pressure and give a bit more headroom before the ruins scene.

The main thing I added is better logging at the failure point, it now prints a table with heap size, what DXVK has allocated, what's actually used, and what the driver reports as allocated/budget (if your driver supports VK_EXT_memory_budget, which yours should).

Basically it helps me giving me more info about it :). So i will need the updated logs with this build.