12/31/2023 0 Comments Elite dangerous stuck screen commander![]() This package does not work on a 64-bit installation If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug. WINEPREFIX=/home/den/.steam/steam/steamapps/compatdata/359320/pfx winetricks corefonts dotnet40 vcrun2012 quartz Final result after first command (I also tried to launch downloaded dotNetFx40_Full_x86_圆4.exe manually - it said that my installed version is higher then current one) Sorted out issue with x32 wine - looks like I didn't clean system well.ġ. OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20ĭeviceName = Intel(R) HD Graphics 520 (Skylake GT2) OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.0.0-devel (git-19af208c7d) OpenGL shading language version string: 1.30 OpenGL core profile profile mask: core profile OpenGL core profile context flags: (none) OpenGL core profile shading language version string: 4.50 OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.0-devel (git-19af208c7d) OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) OpenGL vendor string: Intel Open Source Technology Center Vendor: Intel Open Source Technology Center (0x8086)ĭevice: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) (0x1916) Maybe your installation has only the 32-bit programs?Įxtended renderer info (GLX_MESA_query_renderer): If not setting the WINEPREFIX made it work, check if the prefix in the default prefix (the one used without setting it) is 32 or 64-bit. Notice WINEARCH, it shows if the prefix arch is 32 or 64-bit. One approach to check the prefix is by opening winetricks using a terminal. I am using Proton 3.16-4 and have Wine Staging installed. ![]() Your problem seems to be that the 64-bit wine executable is not available, which is a bit strange, as it should properly use the 64-bit version when the WINEPREFIX is 64-bit. There is no GPU hang happening in this case. ![]() I am not 100% sure this is a Intel Mesa issue, the crash is happening both with and without DXVK and the addresses shown in the error messages are very close, tried with the Transform Feedback patches applied and no success. If using DXVK, in the moment it crashes the following can be read from Steam logs:Ģ169.251:00aa:00d3:err:seh:setup_exception stack overflow 3760 bytes in thread 00d7f85128ef5000058ed0760 stack 0x58ed0000-0x58ed2000-0x58fd0000Ģ851.011:00ab:00c8:err:seh:call_stack_handlers invalid frame 58a3c478 (0x58b02000-0x58c00000)Ģ851.011:00ab:00c8:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception.īe aware Elite Dangerous requires some steps until it is possible to open it using Steam Play. On Windows 10 the shader loading takes 1 or 2 seconds so maybe it's too fast to notice if it goes further than 10. Normally it crashes when still showing 0, but it can reach up to 10. Elite Dangerous using Steam Play crashes when the shaders are loading.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |