Demul emulator runs extremely slow, really bad performances

Questions about Wine on Linux
Post Reply
User avatar
succodifrutta
Level 1
Level 1
Posts: 7
Joined: Sat Mar 28, 2020 5:26 am

Demul emulator runs extremely slow, really bad performances

Post by succodifrutta » Tue Sep 22, 2020 2:39 pm

Sorry for double post! :oops:
Please, delete the previous one!

Hey guys, title says it all.
For testing purposes I'm using it with same settings (default ones) on both Windows and Wine.
On Windows (Win10 PRO x86_64) the emulator runs really really great!
Demul v0.7 180428
Windows:
  • Demul launches the game instantly and the game then starts immediately
  • CPU usage about ~40%
  • GPU usage about ~36%
  • Framerate >60fps

I created two separate prefixes: with and without DXVK. Both of them are win32 and win7.
The profile without DXVK is a clean default profile, no additions neither winetricks verbs installed.

Code: Select all

WINEARCH=win32 WINEPREFIX=/path/to/wineprefix/demul setup_dxvk install
Into the DXVK one, I also installed:

Code: Select all

WINEARCH=win32 WINEPREFIX=/path/to/wineprefix/demul winetricks list-installed
Using winetricks 20200412 - sha256sum: 40ff4c67804584b73d4d36153e1f64ca426d739f1790bd748f5ded0865e8cc7f with wine-5.17 (Staging) and WINEARCH=win32
remove_mono
remove_mono
remove_mono
winxp
dotnet40
remove_mono
remove_mono
remove_mono
remove_mono
dotnet45
dotnet46
andale
arial
comicsans
courier
georgia
impact
times
trebuchet
verdana
webdings
corefonts
vcrun2013
dotnet_verifier
d3dcompiler_47
Wine (without DXVK):
  • Demul takes about 20 seconds to launch the game and the game then takes about 10 more seconds to start
  • CPU usage is about at ~50%
  • GPU usage ranges from ~19% to ~38%
  • Framerate <29fps
Wine (with DXVK):
  • Demul takes about 20 seconds to launch the game and the game then takes about 10 more seconds to start
  • CPU usage is about at ~24%
  • GPU usage ranges from ~8% to ~38%
  • Framerate <29fps
Without DXVK (output is long >10400 lines):

Code: Select all

002c:fixme:winediag:LdrInitializeThunk wine-staging 5.17 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
00f0:fixme:sync:NtSetTimerResolution (5000,0,0x31fec0), stub!
00f0:fixme:shell:BrsFolder_OnCreate flags BIF_NEWDIALOGSTYLE partially implemented
00f0:fixme:shell:BrsFolder_OnCreate flags 10 not implemented
00f0:fixme:shell:BrsFolder_OnCreate flags BIF_NEWDIALOGSTYLE partially implemented
00f0:fixme:shell:BrsFolder_OnCreate flags 10 not implemented
00f0:fixme:shell:BrsFolder_OnCreate flags BIF_NEWDIALOGSTYLE partially implemented
00f0:fixme:shell:BrsFolder_OnCreate flags 10 not implemented
00f0:fixme:shell:BrsFolder_OnCreate flags BIF_NEWDIALOGSTYLE partially implemented
00f0:fixme:shell:BrsFolder_OnCreate flags 10 not implemented
00f0:fixme:shell:BrsFolder_OnCreate flags BIF_NEWDIALOGSTYLE partially implemented
00f0:fixme:shell:BrsFolder_OnCreate flags 10 not implemented
00f0:fixme:shell:BrsFolder_OnCreate flags BIF_NEWDIALOGSTYLE partially implemented
00f0:fixme:shell:BrsFolder_OnCreate flags 10 not implemented
0100:fixme:sync:NtSetTimerResolution (5000,0,0x31fec0), stub!
010c:fixme:ver:GetCurrentPackageId (0D5BFEF0 00000000): stub
0108:fixme:sync:NtSetTimerResolution (5000,0,0x31fec0), stub!
010c:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B66CB90, 10, 0, (null), 3, 3, 00000000, 0x00000000
010c:fixme:wbemprox:client_security_Release 6795F768
010c:fixme:wbemprox:enum_class_object_Next timeout not supported
010c:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B66CB90, 10, 0, (null), 3, 3, 00000000, 0x00000000
010c:fixme:wbemprox:client_security_Release 6795F768
0114:fixme:ver:GetCurrentPackageId (0D7DFEF0 00000000): stub
012c:fixme:ver:GetCurrentPackageId (0DE3FEF0 00000000): stub
010c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 17 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 18 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 19 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 20 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 21 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 22 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 23 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 24 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 25 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 26 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 27 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 28 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 29 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 30 not handled yet.
010c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 31 not handled yet.
013c:fixme:ver:GetCurrentPackageId (0D5BFEF0 00000000): stub
0138:fixme:sync:NtSetTimerResolution (5000,0,0x31fec0), stub!
013c:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B673830, 10, 0, (null), 3, 3, 00000000, 0x00000000
013c:fixme:wbemprox:client_security_Release 6795F768
013c:fixme:wbemprox:enum_class_object_Next timeout not supported
013c:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B671D88, 10, 0, (null), 3, 3, 00000000, 0x00000000
013c:fixme:wbemprox:client_security_Release 6795F768
0144:fixme:ver:GetCurrentPackageId (0D7DFEF0 00000000): stub
015c:fixme:ver:GetCurrentPackageId (0DE3FEF0 00000000): stub
013c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 17 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 18 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 19 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 20 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 21 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 22 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 23 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 24 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 25 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 26 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 27 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 28 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 29 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 30 not handled yet.
013c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 31 not handled yet.
0164:fixme:ver:GetCurrentPackageId (1948FEF0 00000000): stub
016c:fixme:ver:GetCurrentPackageId (0D5BFEF0 00000000): stub
0164:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B759A80, 10, 0, (null), 3, 3, 00000000, 0x00000000
0164:fixme:wbemprox:client_security_Release 6795F768
0164:fixme:wbemprox:enum_class_object_Next timeout not supported
016c:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B6745C8, 10, 0, (null), 3, 3, 00000000, 0x00000000
016c:fixme:wbemprox:client_security_Release 6795F768
016c:fixme:wbemprox:enum_class_object_Next timeout not supported
0164:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B75C028, 10, 0, (null), 3, 3, 00000000, 0x00000000
0164:fixme:wbemprox:client_security_Release 6795F768
0174:fixme:ver:GetCurrentPackageId (196AFEF0 00000000): stub
018c:fixme:ver:GetCurrentPackageId (19D0FEF0 00000000): stub
016c:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B674998, 10, 0, (null), 3, 3, 00000000, 0x00000000
016c:fixme:wbemprox:client_security_Release 6795F768
0190:fixme:ver:GetCurrentPackageId (0D7DFEF0 00000000): stub
01a8:fixme:ver:GetCurrentPackageId (0DE3FEF0 00000000): stub
0164:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
016c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 17 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 18 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 19 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 20 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 21 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 22 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 23 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 24 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 25 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 26 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 27 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 28 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 29 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 30 not handled yet.
0164:fixme:d3d:wined3d_check_device_multisample_type multisample_type 31 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 17 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 18 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 19 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 20 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 21 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 22 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 23 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 24 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 25 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 26 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 27 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 28 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 29 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 30 not handled yet.
016c:fixme:d3d:wined3d_check_device_multisample_type multisample_type 31 not handled yet.
01b0:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts.
0130:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts.
0160:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts.
01b0:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #3:
01b0:fixme:d3d_shader:print_glsl_info_log     Vertex info
01b0:fixme:d3d_shader:print_glsl_info_log     -----------
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[3].w" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[4]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[5]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[6]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[7]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[8]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[9]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[10]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[11]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[12]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[13]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[14]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[15]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[16]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[17]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[18]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[19]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[20]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[21]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[22]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[23]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[24]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[25]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[26]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[27]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[28]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[29]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[30]" might be used before being initialized
01b0:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[31]" might be used before being initialized

[...]

0160:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #195:
0160:fixme:d3d_shader:print_glsl_info_log     Vertex info
0160:fixme:d3d_shader:print_glsl_info_log     -----------
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[3].w" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[4]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[5]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[6]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[7]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[8]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[9]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[10]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[11]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[12]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[13]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[14]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[15]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[16]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[17]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[18]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[19]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[20]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[21]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[22]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[23]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[24]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[25]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[26]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[27]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[28]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[29]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[30]" might be used before being initialized
0160:fixme:d3d_shader:print_glsl_info_log     0(24) : warning C7050: "vs_out[31]" might be used before being initialized

[...]

wine: Unhandled page fault on read access to 00000002 at address 65802583 (thread 01cc), starting debugger...
wine: Unhandled page fault on read access to 00000002 at address 65802583 (thread 010c), starting debugger...
With DXVK (output is normal):

Code: Select all

002c:fixme:winediag:LdrInitializeThunk wine-staging 5.17 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
00f0:fixme:sync:NtSetTimerResolution (5000,0,0x31fec0), stub!
0100:fixme:sync:NtSetTimerResolution (5000,0,0x31fec0), stub!
010c:fixme:ver:GetCurrentPackageId (0D6FFEF0 00000000): stub
0108:fixme:sync:NtSetTimerResolution (5000,0,0x31fec0), stub!
010c:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B675540, 10, 0, (null), 3, 3, 00000000, 0x00000000
010c:fixme:wbemprox:client_security_Release 6795F768
010c:fixme:wbemprox:enum_class_object_Next timeout not supported
010c:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B673AA0, 10, 0, (null), 3, 3, 00000000, 0x00000000
010c:fixme:wbemprox:client_security_Release 6795F768
0114:fixme:ver:GetCurrentPackageId (0D91FEF0 00000000): stub
012c:fixme:ver:GetCurrentPackageId (0DF7FEF0 00000000): stub
0170:fixme:ver:GetCurrentPackageId (0D6FFEF0 00000000): stub
016c:fixme:sync:NtSetTimerResolution (5000,0,0x31fec0), stub!
0170:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B6753B0, 10, 0, (null), 3, 3, 00000000, 0x00000000
0170:fixme:wbemprox:client_security_Release 6795F768
0170:fixme:wbemprox:enum_class_object_Next timeout not supported
0170:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B6757C8, 10, 0, (null), 3, 3, 00000000, 0x00000000
0170:fixme:wbemprox:client_security_Release 6795F768
0178:fixme:ver:GetCurrentPackageId (0D91FEF0 00000000): stub
0190:fixme:ver:GetCurrentPackageId (0DF7FEF0 00000000): stub
01d0:fixme:ver:GetCurrentPackageId (1899FEF0 00000000): stub
01cc:fixme:ver:GetCurrentPackageId (0D6FFEF0 00000000): stub
01d0:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B67DB48, 10, 0, (null), 3, 3, 00000000, 0x00000000
01d0:fixme:wbemprox:client_security_Release 6795F768
01d0:fixme:wbemprox:enum_class_object_Next timeout not supported
01cc:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B675450, 10, 0, (null), 3, 3, 00000000, 0x00000000
01cc:fixme:wbemprox:client_security_Release 6795F768
01cc:fixme:wbemprox:enum_class_object_Next timeout not supported
01d0:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B67BAC8, 10, 0, (null), 3, 3, 00000000, 0x00000000
01d0:fixme:wbemprox:client_security_Release 6795F768
01dc:fixme:ver:GetCurrentPackageId (18BBFEF0 00000000): stub
01f4:fixme:ver:GetCurrentPackageId (1921FEF0 00000000): stub
01cc:fixme:wbemprox:client_security_SetBlanket 6795F768, 0B6734D0, 10, 0, (null), 3, 3, 00000000, 0x00000000
01cc:fixme:wbemprox:client_security_Release 6795F768
01f8:fixme:ver:GetCurrentPackageId (0D91FEF0 00000000): stub
0210:fixme:ver:GetCurrentPackageId (0DF7FEF0 00000000): stub
0288:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0288:fixme:seh:WerSetFlags (2) stub
0288:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub
wine: Unhandled page fault on read access to 00000002 at address 65802583 (thread 01cc), starting debugger...
wine: Unhandled page fault on read access to 00000002 at address 65802583 (thread 010c), starting debugger...
Also, Demul crashes on exit (File-->Exit) only when a game is running: here's the backtrace.

Here's some infos:

Code: Select all

wine-staging 5.17.2-1
winetricks 20200412-1
dxvk-bin 1.7.1-1
nvidia 450.66-22
nvidia-settings 450.66-1
nvidia-utils 450.66-1
lib32-nvidia-utils

Code: Select all

$ uname -srmo
Linux 5.8.10-arch1-1 x86_64 GNU/Linux

Code: Select all

$ file demul/*
d3dcompiler_47.dll:        PE32 executable (DLL) (console) Intel 80386, for MS Windows
demul.exe:                 PE32 executable (console) Intel 80386, for MS Windows

[...]

$ file demul/plugins/*
gdrCHD.dll:     PE32 executable (DLL) (GUI) Intel 80386, for MS Windows
gdrDemul.dll:   PE32 executable (DLL) (GUI) Intel 80386, for MS Windows
gdrImage.dll:   PE32 executable (DLL) (GUI) Intel 80386, for MS Windows
gpuDX11.dll:    PE32 executable (DLL) (GUI) Intel 80386, for MS Windows
gpuDX11old.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows
netDemul.dll:   PE32 executable (DLL) (GUI) Intel 80386, for MS Windows
padDemul.dll:   PE32 executable (DLL) (GUI) Intel 80386, for MS Windows
spuDemul.dll:   PE32 executable (DLL) (GUI) Intel 80386, for MS Windows

Please, let me kone if you need some other infos.

Thanks, bye! :wink:

User avatar
succodifrutta
Level 1
Level 1
Posts: 7
Joined: Sat Mar 28, 2020 5:26 am

Re: Demul emulator runs extremely slow, really bad performances

Post by succodifrutta » Thu Sep 24, 2020 5:49 am

So... About this:
succodifrutta wrote:
Tue Sep 22, 2020 2:39 pm
Without DXVK (output is long >10400 lines):

Code: Select all

[...]

00f0:fixme:sync:NtSetTimerResolution (5000,0,0x31fec0), stub!

[...]

Was wondering if the issue could be related to NtSetTimerResolution, so I tried older version of Demul: DEmul v0.7A 180816.
Why that specific version? Because on the next one (101017), they made this change in particular, see NEWS):
- MISC: set windows timer resolution to min possible value
And I thought that could be somewhat related...
But no, still same performances problems! :(

Does someone know if there's some relationship between my issues and the WINE's fixme message: 00f0:fixme:sync:NtSetTimerResolution (5000,0,0x31fec0), stub!?

Anyone ever faced issues with NtSetTimerResolution in WINE?

User avatar
succodifrutta
Level 1
Level 1
Posts: 7
Joined: Sat Mar 28, 2020 5:26 am

Re: Demul emulator runs extremely slow, really bad performances

Post by succodifrutta » Mon Oct 05, 2020 4:37 pm

Hey guys! Tried with last wine-staging (5.18), but still same problems...

No one has any ideas at all about this issue? :(

Thanks, bye! :wink:

Post Reply