Announcement

Collapse
No announcement yet.

Wine-Staging 8.9 Ships With The Very Latest VKD3D Code

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wine-Staging 8.9 Ships With The Very Latest VKD3D Code

    Phoronix: Wine-Staging 8.9 Ships With The Very Latest VKD3D Code

    Following the release of Wine 8.9 on Friday for enabling Windows games and applications to run on Linux, Wine-Staging 8.9 is now available for this more testing/development-focused flavor of Wine that more liberally picks up in-development patches...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    I'm glad they'e working on it, because it needs work, because it doesn't work.
    Latest Mint with all udates, long term app, an development wine just dies. Real wine just works. Unfortunately no time here to debug Windows, Windows software or Windows [not an] Emulator.
    E


    gavron@EG7540:~/.wine/drive_c/APPNAME$ wine APPNaME.exe
    0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
    0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
    0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
    0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
    00c8:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
    0098:fixme:wineusb:query_id Unhandled ID query type 0x5.
    0098:fixme:wineusb:query_id Unhandled ID query type 0x5.
    0098:fixme:wineusb:query_id Unhandled ID query type 0x5.
    0098:fixme:wineusb:query_id Unhandled ID query type 0x5.
    0098:fixme:wineusb:query_id Unhandled ID query type 0x5.
    00d4:fixme:service:QueryServiceConfig2W Level 6 not implemented
    00f8:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
    00f8:errle:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002
    00f8:errle:CoMarshalInterface Failed to marshal the interface {5c6fb596-4828-4ed5-b9dd-293dad736fb5}, hr 0x80004002
    0134:err:rpc:I_RpcReceive we got fault packet with status 0x80004002
    00d4:fixmele:NdrClearOutParameters (01FAE710,007434A0,01FAE8DC): stub
    00f8:errle:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d
    00d4:errle:ifproxy_release_public_refs IRemUnknown_RemRelease failed with error 0x800706be
    00d4:fixmele:CoCreateInstanceEx no instance created for interface {5c6fb596-4828-4ed5-b9dd-293dad736fb5} of class {c2cc40cb-43e3-4cb4-9be6-47540a0a30b0}, hr 0x80004002.
    00d4:fixme:advapi:RegisterEventSourceW ((null),L".NET Runtime Optimization Service"): stub
    00d4:fixme:advapi:ReportEventW (CAFE4242,0x0001,0x0000,0x00000456,00000000,0x0001 ,0x00000000,01FAF72C,00000000): stub
    00d4:err:eventlog:ReportEventW L".NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Service Manager returned a fatal error (0x80004002). Will stop service\n"
    00d4:fixme:advapieregisterEventSource (CAFE4242) stub
    00d4:fixme:advapi:RegisterEventSourceW ((null),L".NET Runtime Optimization Service"): stub
    00d4:fixme:advapieregisterEventSource (CAFE4242) stub
    0024:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
    0024:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
    0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
    0024:fixme:ntdll:EtwRegisterTraceGuidsW register trace class {044973cd-251f-4dff-a3e9-9d6307286b05}
    0024:fixme:ntdll:EtwRegisterTraceGuidsW register trace class {3044f61a-99b0-4c21-b203-d39423c73b00}
    0024:fixme:ntdll:EtwRegisterTraceGuidsW register trace class {d00792da-07b7-40f5-97eb-5d974e054740}
    0024:fixme:ntdll:EtwRegisterTraceGuidsW register trace class {cfc4ba53-fb42-4757-8b70-5f5d51fee2f4}
    0024:fixme:ntdll:EtwRegisterTraceGuidsW register trace class {efdf1eac-1d5d-4e84-893a-19b80f692176}
    0024:fixme:ntdll:EtwRegisterTraceGuidsW register trace class {c71408de-42cc-4f81-9c93-b8912abf2a0f}
    0024:fixme:ntdll:EtwRegisterTraceGuidsW register trace class {840c8456-6457-4eb7-9cd0-d28f01c64f5e}
    0024:fixme:ntdll:EtwRegisterTraceGuidsW register trace class {c424b3e3-2ae0-416e-a039-410c5d8e5f14}
    0024:fixme:ntdll:EtwRegisterTraceGuidsW register trace class {300ce105-86d1-41f8-b9d2-83fcbff32d99}
    0024:fixme:ntdll:EtwRegisterTraceGuidsW register trace class {561410f5-a138-4ab3-945e-516483cddfbc}
    0024:fixme:ntdll:EtwRegisterTraceGuidsW register trace class {02d08a4f-fd01-4538-989b-03e437b950f4}
    0024:fixme:ntdll:EtwRegisterTraceGuidsW register trace class {ea40c74d-4f65-4561-bb26-656231c8967f}
    0150:errle:CoGetContextToken apartment not initialised
    0024:fixme:msvcrt:__clean_type_info_names_internal (790B22CC) stub
    0024:fixme:msvcrt:__clean_type_info_names_internal (7A3BEC7C) stub
    0024:fixme:msvcrt:__clean_type_info_names_internal (03B8914C) stub
    0024:fixme:msvcrt:__clean_type_info_names_internal (7842E65C) stub
    gavron@EG7540:~/.wine/drive_c/APPNAME$‚Äč

    Comment


    • #3
      Why does it mention testing vkd3d with DOOM eternal, that game is native vulkan and doesn't use DX12 at all.

      Comment


      • #4
        So this is about the VKD3D that is not the Proton one right? Is it on the same level as that one?

        Comment


        • #5
          Originally posted by peterdk View Post
          So this is about the VKD3D that is not the Proton one right? Is it on the same level as that one?
          No, vkd3d-proton is years ahead when it comes to running DX12 games compared to upstream vkd3d. Upstream vkd3d still doesn't even support feature level 12_0 or shader model 6, and as a result can run almost no games.

          Comment


          • #6
            Originally posted by mbriar View Post

            No, vkd3d-proton is years ahead when it comes to running DX12 games compared to upstream vkd3d. Upstream vkd3d still doesn't even support feature level 12_0 or shader model 6, and as a result can run almost no games.
            Then why doesnt wine(-staging) switch to Proton's VKD3D then?

            Comment


            • #7
              Originally posted by MastaG View Post

              Then why doesnt wine(-staging) switch to Proton's VKD3D then?
              There is no reason to, you can install it to the prefix like with DXVK. Wine also depends on upstream vkd3d for wined3d's vulkan backend and the HLSL compiler, even Proton ships upsteam vkd3d in addition to vkd3d-proton for it's HLSL compiler part, it's just not useful for running d3d12 games.

              Comment


              • #8
                Originally posted by mbriar View Post
                Why does it mention testing vkd3d with DOOM eternal, that game is native vulkan and doesn't use DX12 at all.
                Just goes to show how far detached from reality they are...

                Comment


                • #9
                  Originally posted by mbriar View Post
                  Why does it mention testing vkd3d with DOOM eternal, that game is native vulkan and doesn't use DX12 at all.
                  Source?

                  Comment


                  • #10
                    Originally posted by avis View Post

                    Source?
                    The screenshot in the article, which is from https://gitlab.winehq.org/wine/wine-...est/definition

                    Comment

                    Working...
                    X