Trace:shader_parse_descriptor_ranges: Type 0x3, descriptor count 16, base shader register 0, register space 0, offset 0. Trace:shader_parse_descriptor_ranges: Type 0, descriptor count 128, base shader register 0, register space 0, offset 0. Trace:shader_parse_descriptor_table: Descriptor range count 1. Trace:shader_parse_root_parameters: Type 0, shader visibility 0. Trace:shader_parse_root_signature: Parameter count 4, offset 24. Trace:shader_parse_root_signature: Version 0x1. Warn:skip_dword_unknown: Skipping 4 unknown DWORDs: Trace:vkd3d_shader_parse_root_signature: dxbc, root_signature 0x21ea60. Trace:vkd3d_shader_serialize_root_signature: root_signature 0x21ef50, dxbc 0x21ef40. I'm not sure what's going on with the others yet, they just error immediately, and I haven't gotten a good log file to dig into yet. * these values come from Windows 7 SP1 */ -#define WINE_FILEVERSION 6,1,7601,17514 -#define WINE_FILEVERSION_STR ".17514" -#define WINE_PRODUCTVERSION 6,1,7601,17514 -#define WINE_PRODUCTVERSION_STR ".17514" +/* these values come from Wind*/ +#define WINE_FILEVERSION 10,0,19041,1000 +#define WINE_FILEVERSION_STR "1.1000" +#define WINE_PRODUCTVERSION 10,0,19041,1000 +#define WINE_PRODUCTVERSION_STR "1.1000"īut the only DirectX 12 test I've been able to run so far is the API overhead test. #define WINE_FILEDESCRIPTION_STR "Wine kernel DLL" a/dlls/kernel32/version.rc +++ b/dlls/kernel32/version.rc -25,10 +25,10 LANGUAGE LANG_ENGLISH, SUBLANG_DEFAULT Unlike the PROTON_USE_WINED3D=1 case, the loading screen appears for both the demo and graphics tests, but it quits before rendering anything.ĭiff -git a/dlls/kernel32/version.rc b/dlls/kernel32/version.rc The tests are broken on the Intel iGPU in the Xeon E3-1276v3 running Mesa 19.0.8 on Linux 5.1.18. Those are wined3d in either case, so the bug is not in wined3d. Even the direct3d 9 tests break with it, but work without it. PROTON_USE_WINED3D=1 breaks all tests (they seem to crash), causing scores of 0.Test results complain about Time Measurement data being not available, which in conjunction with the system info issues, causes test results to be deemed invalid.The SystemInfo component is completely broken, causing it to report unknown GPU, among other things. 3DMark Advanced thinks it is 3DMark Basic, so plenty of tests (including the Vulkan one) that are exclusive to 3DMark Advanced cannot be run.The default launch option does not work, so force 32-bit or force 64-bit must be selected to launch it. 3DMark has multiple issues in proton 4.11-1 on top of direct 3D 12 not working:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |