Announcement

Collapse
No announcement yet.

DXVK 2.4.1 Released With Many Improvements, More Robust Direct3D 8

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

  • #11
    Originally posted by Rccero
    DVXK devs discarded the idea due to the amount of work it would require implementing and maintaining it... and it isn't a feature very requested, as there already are some wrappers (WineD3D, DGVoodoo2, DXGL). AlpyneDreams (the guy behind D8VK) studied the idea, but gave it up later for the same reason, too much work.

    Maybe someone will one day start a DirectDraw/D3D7-to-Vulkan wrapper, but it won't happen soon, and it will probably be a independent project or fork from DVXK.
    I'd say the task seem impossible. As WINE keep progressing it follow the windows footsteps and breaks the retro compatibility as well. Many retro games programmed with a certain DX and desktop behavior of the time, they abusing certain driver features. It may happen there is no common ground possible for them at all. Like, for very recent example, the fresh DPI scale changes in WINE have wreaked havoc on my fine tuned retro collection. In-game graphics is broken, mouse pointer misbehave... All of this happen for a games and API's that have not a slightest idea about DPI, compositing, fancy controls. IMO each retro game should come with it's own set of "properly" broken drivers. Each of the game I complement with a bunch of wrappers to ensure their specific tricks, controls, art design, midi style, audio acceleration and so on. Per game approach seem the only right way to go, because most of this solutions are too "unclean" and hack-ish to be the generic solution.

    Comment


    • #12
      Originally posted by SilverBird775 View Post
      Like, for very recent example, the fresh DPI scale changes in WINE have wreaked havoc on my fine tuned retro collection. In-game graphics is broken, mouse pointer misbehave... All of this happen for a games and API's that have not a slightest idea about DPI, compositing, fancy controls.
      Have you reported these regressions on bugzilla?

      Comment


      • #13
        Testing lastest master (memory rework part 1 and 2 merged) show this:


        2.4.1





        Lastest Master





        At simple seek vram usage down around 200mb

        Comment


        • #14
          Originally posted by pinguinpc View Post
          This dxvk version in my case run some newer games: memory usage and gpu usage remains similar


          2.4




          2.4.1




          in other things can run other newer titles





          ​​
          What is the name of the game with the chainsaw girl?

          Comment


          • #15
            Originally posted by siyia View Post

            What is the name of the game with the chainsaw girl?
            Lolipop Chainsaw RePoP

            Back to test another progress of memory rework part 1 and 2 appear in CarX Street

            2.4.1




            Memory Rework



            in this title vram usage down around 200mb with similar gpu usage but fps up around 5-6fps

            Comment


            • #16
              Originally posted by eszlari View Post
              Have you reported these regressions on bugzilla?
              It's useless. Nothing to report because everything is broken. This changes have an impact of the atom bomb for the retro gaming. The official WINE stance on the matter: "DPI awareness, not something that Wine can fix". So, blurry windows are good because that's how windows behave. These changes greatly complicate the ways of running older games, especially ones that depends on custom wrappers\hacks of none WINE origin. Including DXVK, that bypass this DPI awareness bullshit. But it does not help to bypass the DPI-adjusted input for the matter...

              This activates the new DPI scaling, and stops pretending that every window is per-monitor DPI aware. It uses the GDI scaled surfaces for DPI-unaware windows, instead of the...

              I will wait for a switch to turn this "feature" off again - alike windows app compatibility tools. As for the present moment... Already stressed enough with other issues, let the dust settle.
              Last edited by SilverBird775; 26 September 2024, 05:15 PM.

              Comment


              • #17
                Originally posted by SilverBird775 View Post
                It's useless. Nothing to report because everything is broken. This changes have an impact of the atom bomb for the retro gaming. The official WINE stance on the matter: "DPI awareness, not something that Wine can fix". So, blurry windows are good because that's how windows behave. These changes greatly complicate the ways of running older games, especially ones that depends on custom wrappers\hacks of none WINE origin. Including DXVK, that bypass this DPI awareness bullshit. But it does not help to bypass the DPI-adjusted input for the matter...

                This activates the new DPI scaling, and stops pretending that every window is per-monitor DPI aware. It uses the GDI scaled surfaces for DPI-unaware windows, instead of the...

                I will wait for a switch to turn this "feature" off again - alike windows app compatibility tools. As for the present moment... Already stressed enough with other issues, let the dust settle.
                Aka another example of anything other than 100% scaling still causing issues

                I intentionally force app-side scaling on Windows (no DPI awareness) regardless of what I OS scale at; games can't even handle scaling consistently-enough on Windows where it's expected to work. On Linux I only do 100% nowadays but didn't notice anything odd with 200% at 4K a few years ago.

                I've only ever seen HiDPI work consistently on macOS, which makes sense with Retina and art.

                Comment


                • #18
                  Originally posted by davidbepo View Post

                  wdym older, literally everything from this millennium is supported on DXVK(except D3D12 which is handled by VKD3D)
                  DX7 is missing and it's a big one since 32-bit OpenGL can't work properly with new wow64 (yet).

                  Comment


                  • #19
                    Everything before DX8 requires many workarounds or different dll's, if you are interested you may be able to get some of the games to work with DXWrapper and DD7to9 (both projects are open source). At least some games worked for me when using the right dll's/settings combined with DXVK in wine/proton.

                    Fixes compatibility issues with older games running on Windows 10/11 by wrapping DirectX dlls. Also allows loading custom libraries with the file extension .asi into game processes. - elishacloud/...

                    Comment


                    • #20
                      Mount and Blade and Warband have both DirectX 7 and 9 options in their launcher, if that helps testing. Warband (2011) is the latest game I know of to release with DirectX 7.

                      Comment

                      Working...
                      X