Please help with random game crash with no error in the Vintage Story Logs

[Pawels]

Hi everyone!

I have searched this forum and others for similar trouble-shooting. I thing I know what is happening but I do not know how to proceed further. I tried to play with low/medium/custom graphic options and smaller world 256kx256k - always with the same random exit to desktop without Vintage Story Crash report.

I try to play on Dell Latitude 7455:
Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) CPU   3.42 GHz
Qualcomm(R) Adreno(TM) X1-85 GPU
PC SN740 NVMe WD 1TB
32,0 GB RAM
System type: 64-bit, procesor ARM
Windows 11 Business

Since in the Vintage Story crash logs was nothing I found Windows events overview with Appplication Errors and there I found:

1. Application: Vintagestory.exe
CoreCLR Version: 7.0.2024.26716
.NET Version: 7.0.20
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF9967ADCB4

2. Nazwa aplikacji powodującej błąd: Vintagestory.exe, wersja: 1.20.12.0, sygnatura czasowa: 0x66470000
Nazwa modułu powodującego błąd: OpenGLOn12.dll, wersja: 0.0.0.0, sygnatura czasowa: 0x68544bd1
Kod wyjątku: 0xc0000005
Przesunięcie błędu: 0x000000000050dcb4
Identyfikator procesu błędu:  0x486C
Czas uruchomienia aplikacji powodującej błąd: 0x1DBE3BEFEEC3E02
Faulting ścieżka aplikacji: C:\Users\(I hide the user name)\AppData\Roaming\Vintagestory\Vintagestory.exe
Faulting ścieżka modułu: C:\Program Files\WindowsApps\Microsoft.D3DMappingLayers_1.2506.2.0_arm64__8wekyb3d8bbwe\x64\OpenGLOn12.dll
Report Id: 65fd30c1-32d2-4938-8d86-9436a97155eb
Faulting pełna nazwa pakietu: 
Faulting identyfikator aplikacji względnej dla pakietu:  

 

I reinstalled the game and thought that getting rid of the .NET 7 would help since it always crashes first but I could not start the game with other (never/older) versions. The game seemed more stable though after I reinstalled the .NET... until it crashed in the next hour.

[FlareUKCS]

Considering the information given, I would guess its the GPU,  research how compatible your Qualcomm(R) Adreno(TM) X1-85 GPU is with OpenGL (which is what Vintage Story uses).

 

[wildforester]

The issue may more so be that the translation from opengl to directx12 is faulty. That'd appear to be what's happening, the opengl being implemented on directx12

[Pawels]

5 hours ago, FlareUKCS said:

Considering the information given, I would guess its the GPU,  research how compatible your Qualcomm(R) Adreno(TM) X1-85 GPU is with OpenGL (which is what Vintage Story uses).

 

 

5 hours ago, wildforester said:

The issue may more so be that the translation from opengl to directx12 is faulty. That'd appear to be what's happening, the opengl being implemented on directx12

Thank you Flare and Wildforester. I think you are right. I will check if I have the "OpenCL™, OpenGL®, and Vulkan® Compatibility Pack" installed and test if that helps.

[Pawels]

I have installed "OpenCL™, OpenGL®, and Vulkan® Compatibility Pack" but it did not change a thing. I start to believe there is no solution apart from allowing is the settings to change between DirectX and OpenGL. Do you have any other suggestions to make Vintage Story work on this laptop? Or, perhaps there is a different place where I can seek help directly from the dewelopers?

[Pawels]

Dear @radfast I have seen you posted information regarding performance update. I installed v1.20.12 (stable) and experience the error described in this thread. Is there a possibility you know the solution?

[FlareUKCS]

I am hesitant to add to this as I am not competent regarding none x86 architecture CPU's, but cursory research suggests the issue is with compatibility with the CPU as well, a ARM chip lacks a lot that the x86 chips have as standard, and typically is bypassed by translating the relevant calls, this leads to issues where niche calls can be overlooked or simply not included.

In short I think your CPU may not have the compatibility required to run the game. The game is designed on a more open to the public system of libraries as in OpenGL and OpenAL, probably a library like SDL2 or SFML... open libraries that are not mainstream, so may get skipped by compatibility coders for more mainstream application. 

I would either refund, or look for none official patches for compatibility, check your compatibility softwares community pages to see if there is some open sourced patches, or put up a reddit thread in a relevant compatibility software section for unofficial patches for your compatibility software.

Sorry I couldn't help much.

[Pawels]

5 hours ago, FlareUKCS said:

I am hesitant to add to this as I am not competent regarding none x86 architecture CPU's, but cursory research suggests the issue is with compatibility with the CPU as well, a ARM chip lacks a lot that the x86 chips have as standard, and typically is bypassed by translating the relevant calls, this leads to issues where niche calls can be overlooked or simply not included.

In short I think your CPU may not have the compatibility required to run the game. The game is designed on a more open to the public system of libraries as in OpenGL and OpenAL, probably a library like SDL2 or SFML... open libraries that are not mainstream, so may get skipped by compatibility coders for more mainstream application. 

I would either refund, or look for none official patches for compatibility, check your compatibility softwares community pages to see if there is some open sourced patches, or put up a reddit thread in a relevant compatibility software section for unofficial patches for your compatibility software.

Sorry I couldn't help much.

Dear Flare, you were very helpful, since nowhere else I could find information that could direct me closer to identify the reason for crashes. It is a pity that no one from VS Team replied with their take on the issue. I will leave the topic open for now. I will try in the coming week to find a way to play the game and share the outcome. Of course, I am quite positive that your reasoning is correct, which means there is little chace I will succeed. Hopefully someone from the VS Team will also give some input.

[radfast]

@Pawels nobody from the dev team has the hardware you are using, I would not like to say whether the game should work on such hardware or not.

In principle:

• the game is well-tested on common PC and Mac hardware (Intel, AMD, and Apple Silicon)
• we do not currently make an ARM64 native code version of the game, we hope to do that in future, it will be dependent on availability of some of the libraries we use
• we use many components of .NET 7 runtime  (game versions up to 1.20) or now .NET 8 runtime (game version 1.21+).  As a sophisticated multiplayer game written in C#, could be said we test .NET runtime to its very limits.  .NET runtime is supposed to be cross-platform of course, but it may be that the .NET runtime is bugged on your hardware, especially if having to use a compatibility mode
• I do recommend try game version 1.21, and try updating .NET 8 runtime for your specific hardware, maybe Microsoft found and fixed some bugs

Having made those general points, the reported crash looks specific to the OpenGL -> D3D 12 mapping, that is the module reported as crashing in the report you posted.

That is not the game's fault, it's what we call a "3rd party issue".  Meaning it's a bug in your GPU driver or OpenGL->D3D mapping.  The GPU driver or OpenGL->D3D mapping is unique to your hardware, it's made by your hardware manufacturer I guess.  You need to report the issue to them, not to us.

The game definitely will not work unless it's on a system which has full OpenGL support.  Specifically, your GPU needs to be able to support at least OpenGL version 3.3 without issues.  Almost every other GPU manufactured in the last 10 years can do this, including integrated graphics on low-mid range CPUs.