What’s up all! I’m having issues with my brand-new game (: I’m going to try to keep this short and sweet.
Here are the facts/things I have done:
everything is on the lowest settings possible, capped at 60 fps.
my computer is more than capable of running darktide.
i went to the launch options in steam and typed “–lua-heap-mb-size 2048”
and i went to launcher.exe.config and did it there too.
the error code thingimabob is: GUID: b8e50840-e48e-4200-9865-2e8f4c12654b
Log File:
Info Type:
[Engine Error]: Page allocator ‘render_page_allocator’ failed allocating 65536 bytes, total 363724800, last error: The paging file is too small for this operation to complete. , error code: 1455
Assertion failed ptr at D:\a\d\rel_engine_darktide\release\2024_10_23_Patch1.6.0x\runtime\foundation\memory\page_allocator_win.cpp:237 in function stingray::PageAllocator::allocate_vmemory
[PC] Do You Use Mods? (Optional):
No, I don’t use mods
Reproduction Rate (Required):
Constant (100%)
Platform (Required):
PC - Steam
[PC] Crash Report (Optional):
GUID: b8e50840-e48e-4200-9865-2e8f4c12654b
Log File:
Info Type:
[Engine Error]: Page allocator ‘render_page_allocator’ failed allocating 65536 bytes, total 363724800, last error: The paging file is too small for this operation to complete. , error code: 1455
Assertion failed ptr at D:\a\d\rel_engine_darktide\release\2024_10_23_Patch1.6.0x\runtime\foundation\memory\page_allocator_win.cpp:237 in function stingray::PageAllocator::allocate_vmemory
From the error messages it’s unrelated to Lua heap so that 2gb switch won’t do anything and is a virtual mem/page file issue.
That error 1455 is indeed:
ERROR_COMMITMENT_LIMIT
1455 (0x5AF)
The paging file is too small for this operation to complete.
The obvious stuff (forgive me if stupid and too obvious, worth a check):
OTOH do you have a system managed page file? Enough actual free space for the swap file?
Probably unrelated, oddly, in another slightly similar Virtual Memory error 1455 turned out outdated drivers were causing issues for the other user. Though here it’s “render_page_allocator”, going to assume not a VRAM issue if everything was set to lowest etc ?
FS staff will probably be in the offices soon with hopefully more help, they can look at the logs and see if there’s more there.
If you’re asking, odds are you didn’t mess with it.
It’s just the first troubleshooting step to check based on the error number.
Check to see if virtual mem is set to auto, then maybe try manually setting it from the amount of RAM you have for min to double that for max. Make sure you have the free space to cover the size. The old rule of thumb for manual 1.5 is outdated AFAIK, and better to leave it system managed (auto).
The default should be “Automatically manage paging file size for all drives” checkbox checked, so it’s likely something else unless you or someone else messed with it, and the error message said “render_page_allocator” *GPU?). How To Manage Virtual Memory (Pagefile) In Windows 10 | Tom’s Hardware
Besides the usual follow-up troubleshooting steps, FS might have more insight. I just hoped it was the obvious first steps just in case, based on the error number, to solve your issue.
Good luck, keep us posted.
There were two issues I had to fix:
1, lua kept crashing. I had to manually give lua more mbs, something that should have been done by default
2, and this is an issue on my part most likely, but still, I had to set up virtual memory.
any way please work on fixing the game, i should not have had to fix the first issue on a brand-new game!
i would expect more out of fatshark as I have played vermintide for a long time without any issues, but here we are.