![]() But you ought to be able to complete all four of the above steps in half an hour or so, assuming you don't get lost. Of the four above steps, the most difficult and painful, by far, is the first step, because you need to install lots of development stuff on your computer in order for wine to compile. Step 4: Rebuild wine (both configure and make). Note that you have to be in the wine-staging "patches" directory when executing patchinstall.sh. Replacing "././wine-source" with the path to your wine-2.21 source. patchinstall.sh DESTDIR=././wine-source kernel32-SetFileCompletionNotificationModes Step 3: Apply the patch "kernel32-SetFileCompletionNotificationModes" from wine-staging using patchinstall.sh: You can get it with git, or you can get it here: /wine-compholio/wine-staging/archive/v2.21.tar.gz Step 2: Download wine-staging 2.21 source. You can get wine 2.21 source with git, or you can get it here: /pub/wine/source/2.x/wine-2.21.tar.xz Make sure you build wine 2.21 and not some development version. I'll attempt to explain how to do this here. I get a bunch of this which seems like it could be related.Ġ13b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0x11.Ġ13b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0x12.Ġ13b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0xe.Ġ13b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0xd.Ġ13b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0圆.Ġ13b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0xf.Ġ13b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0x5.Ġ13b:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!Ġ13b:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table.Ġ13b:fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!Ġ13b:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table.Ġ13b:fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!Ġ13b:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table.įor me, in order to stop the mouse-downs-register-as-mouse-clicks problem in Diablo 3 2.6.1 with wine-staging 2.21, I had to recompile wine with the right patch. Tried disabling dx11 but that prevents Battle.Net from loading so I can't do that. ![]() Launches, transparent screen followed by crash. Used dxvk-setup (dxvk package, Debian 10). Running in terminal directly in Wine the following error message is generated at crashing:Ġ76c:fixme:d3d_shader:shader_glsl_input_pack Unhandled sysval semantic 0x2.Ġ6d4:err:seh:dispatch_exception unknown exception (code=c0000420) raisedĪmdgpu: amdgpu_cs_query_fence_status failed.Īmdgpu: The CS has been cancelled because the context is lost.ĭoes not work on Wine 5.0 stable. I’m experiencing freez at Diablo 3 when using latest Wine, the game just freezes. Tested on Alllen and Heath Zed 10FX USB sound card. so just clicking on the sound Icon, tools icon and going to Applications tab allowed me to adjust the volume of the game. To resolve this problem you need to run the game in particular way to tell Linux to use a Windows-like memory address space: setarch i386 -3 wine ''Įdit /etc/pulse/nf and add default-fragment-size-msec = 5Īfter that the volume was really low and it appears that pulse volumes bars per application. As a result of this, many aspects of the application will fail to function properly (including chatting, authenticating, and closing the game). ![]() On systems with more than 4 GB of memory Diablo III sees an unusual amount of memory (from its perspective) due to differences in the memory layout on Windows and Linux. (To use the 32-bit client, go to App -> Settings -> Game Settings -> Diablo III -> "Launch 32-bit client (instead of 64-bit)".) In order to get around this and have a usable fps, either 1) use the 32-bit client, or 2) use DXVK (not directly supported on AppDB). For some reason the 64-bit client has abysmal performance (around 1-2 fps). This should be fixed as of Wine 6.19 ( commit link).ģ2-bit game client uses DirectX 9, while 64-bit client uses DirectX 11. Extremely low performance with 64-bit game client If you find that they are still required, please post it in the comments.ġ. Below workarounds should not be needed anymore to run the game. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |