Announcement

Collapse
No announcement yet.

53 Patches Published For Gallium3D's Direct3D 9 Support

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

  • darkbasic
    replied
    Originally posted by vitalif View Post
    New Nine doesn't work with radeon drivers, because radeon drivers miss DRI3, and since recently Nine is based on DRI3 and does not work with DRI2 :-(

    So until someone implements DRI3 for radeon it's useless... There is a patch from iXit, but I've tried it and it's very buggy. Basically unusable.
    I use a DRI3 patched xf86-video-ati ddx since months without the slightest problem (glamor).

    Leave a comment:


  • curaga
    replied
    Originally posted by drago01 View Post
    Well once the modesetting driver gets page flipping support (which hopefully happens before xserver 1.17 is released) you can (and should) just use it on newer radeon hardware. You get dri3 "for free" and it lacks nothing you get when running the radeon driver.
    ..except native 2d acceleration and support for not tearing. Glamor is not enough.

    Leave a comment:


  • pixo
    replied
    Originally posted by Master5000 View Post
    Why all this insanity with making windows games work on linux? Can't you just maintain a windows partition for games and be done with it?
    Some of us use the PC for more than gaming and dualboot is not an option.
    I run Owncloud, HTPC/SteamBP seat, KDE seat and WinConsole8.1 VM.
    Its hard to find proper HW and setup the whole thing just to run WinConsole VM.
    Just finding KVM switch that works with gaming mouse and keyboard was hard, and the damn thing started to have problems with audio

    Leave a comment:


  • drago01
    replied
    Originally posted by mannerov View Post
    It's not true anymore.

    Since Fedora wanted to ship Gallium Nine support, we made patches to have a DRI2 fallback. So it'll work with DRI2 (but there is a small perf hit)
    Well once the modesetting driver gets page flipping support (which hopefully happens before xserver 1.17 is released) you can (and should) just use it on newer radeon hardware. You get dri3 "for free" and it lacks nothing you get when running the radeon driver.

    Leave a comment:


  • deve
    replied
    My nvidia with OpenGL wrapper works faster than your AMD with rather unstable dx9. Not sure if it's sad or funny...

    Leave a comment:


  • magika
    replied
    Originally posted by nanonyme View Post
    Didn't Wine devs already comment CSMT will never be included in Wine but instead they'll build some new thing based on it?
    AFAIK, not new. They just decided to target CSMT and rewrite WINE infrastructure for D3D11 before CSMT makes into master, to save the efforts.

    Leave a comment:


  • nanonyme
    replied
    Didn't Wine devs already comment CSMT will never be included in Wine but instead they'll build some new thing based on it?

    Leave a comment:


  • mannerov
    replied
    Originally posted by vitalif View Post
    New Nine doesn't work with radeon drivers, because radeon drivers miss DRI3, and since recently Nine is based on DRI3 and does not work with DRI2 :-(

    So until someone implements DRI3 for radeon it's useless... There is a patch from iXit, but I've tried it and it's very buggy. Basically unusable.
    It's not true anymore.

    Since Fedora wanted to ship Gallium Nine support, we made patches to have a DRI2 fallback. So it'll work with DRI2 (but there is a small perf hit)

    Leave a comment:


  • brad0
    replied
    Originally posted by bitman View Post
    because these patches wont work on other systems, only on linux. Thats their motive for no interest. Rather dumb reason i would say.
    One of the dumbest posts I have ever seen.

    Leave a comment:


  • Xaero_Vincent
    replied
    Originally posted by Adarion View Post
    I am equally excited with bug fixes as well as new features, normally.
    But the best features are useless when they don't work.

    Anyway, does anybody know why the WINE devs don't use this state tracker?
    IIRC, I think it comes down to Wine devs not wanting two different ways of dealing with Direct3D...OpenGL to Direct3D translation and native Direct3D.

    Furthermore, while D39 helps boost performance and improve some games, it can cause breakage and compatability issues with others. For instance, I remember seeing a youtube video showcasing Gallium 9 Wine running the 2013 Tomb Raider game and it rendered graphics glitches and artifacts on screen while the vanilla Wine didn't, although the framerate was lower. Lastly, it doesn't work with Intel since supposedly they don't have a Gallium driver nor the proprietary Nvidia and AMD Catalyst drivers. I heard it also requires DRI3 which may be broken in the FOSS Radeon driver so it doesn't work even on that and Nouveau driver performance compared to the proprietary Nvidia accelerated driver is a joke (no disrespect to the fine work devs are doing at reverse engineering complex Nvidia hardware).

    With all that said, I welcome the new 50+ fixes and in general think better Wine gaming performance is a good thing. Now Wine devs need to get working on Direct3D 10 and 11 because virtually no new games, with the exception of some low-end Indie games that probably already have a Linux port, are using DX 9 anymore. Going forward, Wine will become less and less compatible with modern games requiring the new graphics APIs if support doesn't get implemented.

    Command Stream (CSMT) is what I use reguarly. It is fully supported in Crossover 14 (which I also use) and CSMT-patched Wine builds are readily available in PlayOnLinux to download; Furthermore, CSMT works with all drivers and offers comparable performance to Gallium 9 with r600 and RadeonSI when coupled with the faster proprietary drivers.
    Last edited by Xaero_Vincent; 08 January 2015, 06:10 AM.

    Leave a comment:

Working...
X