Announcement

Collapse
No announcement yet.

Does WINE work well with radeon drivers for D3D games?

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

  • Does WINE work well with radeon drivers for D3D games?

    Hi,
    I have an ATI X1650 Pro.
    I read that the OSS radeon driver supports 3D acceleration on it, so I think I could give it a try if it supports WINE any better than fglrx.

    So my question is, how well would WINE work with radeon driver in D3D games? (The ones that keep crashing or not running with FGLRX even with a good rating in AppDB)

    Also, does radeonhd support 3D acceleration? And how similar is it to radeon?

    Sigh.. I should've gotten me a nVidia for the time being.. The time I spent trying to make Wine/Cedega work with games that supposedly work with WINE was far too long, and it makes me want to format my Linux partition

    Thanks!

  • #2
    I think the issue is that a lot of the games need full OpenGL 2.0 or 2.1 to support DX9 and AFAIK none of the open source drivers are doing a good job of that yet.

    The radeonhd driver has supported 3d for a couple of months, and as of the last week or so is now supporting 2d and 3d acceleration simultaneously (before that you had to disable 2d acceleration when you ran with 3d acceleration). The accel code in the two drivers is now pretty similar.

    Comment


    • #3
      Originally posted by bridgman View Post
      I think the issue is that a lot of the games need full OpenGL 2.0 or 2.1 to support DX9 and AFAIK none of the open source drivers are doing a good job of that yet.

      The radeonhd driver has supported 3d for a couple of months, and as of the last week or so is now supporting 2d and 3d acceleration simultaneously (before that you had to disable 2d acceleration when you ran with 3d acceleration). The accel code in the two drivers is now pretty similar.
      I see.. but wouldn't that mean that those with Intel cards can't use Wine?

      Also, is the whole wine-fglrx thing caused from wine or from fglrx?

      Comment


      • #4
        Well wine works fine with fglrx 8-5 and with nvidia drivers

        Comment


        • #5
          I see.. but wouldn't that mean that those with Intel cards can't use Wine?
          I don't remember seeing many posts about running Wine on Intel graphics - good *or* bad. My *guess* would be that Wine on Intel open source drivers would be a bit better than on our open source drivers, if only because the driver support has been available for longer, but I don't really know for sure.

          My understanding is that the Intel open source drivers are around GL 1.5 while the ATI open source drivers are "1.3 with nearly all of the 1.4 features". Not sure exactly how that maps into which apps run well on Wine.
          Last edited by bridgman; 07-31-2008, 05:29 PM.

          Comment


          • #6
            Originally posted by bridgman View Post
            I don't remember seeing many posts about running Wine on Intel graphics - good *or* bad. My *guess* would be that Wine on Intel open source drivers would be a bit better than on our open source drivers, if only because the driver support has been available for longer, but I don't really know for sure.

            My understanding is that the Intel open source drivers are around GL 1.5 while the ATI open source drivers are "1.3 with nearly all of the 1.4 features". Not sure exactly how that maps into which apps run well on Wine.
            So the wine issue is not from a problem of fglrx's new 3D stack?

            Comment


            • #7
              We're trying to find out -- specifically to find a better way for "Wine problems" to get translated into "OpenGL problems" to make it easier for the core OpenGL team to work on them. I suspect that some of the problems will be fglrx-related in that they are caused by changes in the OpenGL functionality, and others will turn out to be wine-related in the sense that they are caused by assumptions made by the wine devs about how our driver stack behaves which are not related to the OpenGL API.

              Comment


              • #8
                Any progress on this front Bridgman?

                Curious to know when the "needed OGL extensions" required by many games run in WINE would be available in the open source Radeon driver?
                Last edited by fermulator; 05-06-2009, 04:54 PM.

                Comment


                • #9
                  In theory the higher GL levels will come "for free" once a Gallium3D driver is available. It obviously won't be that easy but it does mean that OGL 2.x support is mostly likely to come after Gallium3D has replaced the current hardware driver layer in Mesa for ATI/AMD parts.

                  Gallium3D in turn relies on DRI2 and GEM/TTM support, and it's GEM/TTM where most of the "development pressure" is being felt today (since having a solid GEM/TTM implementation is also a pre-requisite for enabling Kernel ModeSetting (KMS) by default.

                  Getting GEM/TTM into the upstream kernel is really what will gate most of the other bits. Once it is accepted into the kernel that means the upper level drivers (the X driver and Mesa) can rely on having kernel video memory management, which in turn allows developers to focus their efforts on getting DRI2-based drivers (including Gallium3D) ready for shipped in distros.

                  Fedora is already shipping most of these bits, but that requires it to run ahead of the upstream kernel in a number of areas.

                  Comment


                  • #10
                    Any news on how Intel works now that it supports GL 2.1?

                    Comment


                    • #11
                      Intel support for Wine is spotty at best. I have filed quite a few bugs. Some are specific to the i965 driver (such as Portal being broken) others seems to be specific to Mesa as a whole.

                      I doubt Wine (and gaming in general) is a priority for the Intel developers at the moment. But given time, I hope things will improve.

                      Comment


                      • #12
                        i test some of my games no directX game work for me on the radeon opensource driver.

                        it always tells me that i need to install the directX9 sdk but i do have install all dx stuff.

                        i think openGL3.2 is needed by wine.

                        Comment


                        • #13
                          Originally posted by Qaridarium View Post
                          i test some of my games no directX game work for me on the radeon opensource driver.

                          it always tells me that i need to install the directX9 sdk but i do have install all dx stuff.

                          i think openGL3.2 is needed by wine.
                          Nope. Either the games you're trying to run isn't well supported, or you're Doing Something Wrong™.

                          Comment


                          • #14
                            Originally posted by whizse View Post
                            Nope. Either the games you're trying to run isn't well supported, or you're Doing Something Wrong™.
                            sure something wrong.. But what?

                            OFP for example:

                            wine ./FlashpointPreferences.exe'
                            err:wgl:has_opengl Failed to load libGL: libGL.so.1
                            err:wgl:has_opengl OpenGL support is disabled.
                            err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
                            err:d3d:InitAdapters Failed to get a gl context for default adapter
                            Direct3D8 is not available without OpenGL.

                            why there is no libGL.so.1 ?

                            ok now i installed the 32bit libgl but now i get software rendering:

                            wine./FlashpointPreferences.exe
                            err:winediag:X11DRV_WineGL_InitOpenglInfo The Mesa OpenGL driver is using software rendering, most likely your OpenGL drivers haven't been installed correctly (using GL renderer "Mesa X11", version "2.1 Mesa 7.12-devel (git-2175634 oneiric-oibaf-ppa)").
                            fixme:d3d_caps:wined3d_guess_card No card selector available for GL vendor 0x4 and card vendor 0000 (using GL_RENDERER "Mesa X11").
                            fixme:win:EnumDisplayDevicesW ((null),0,0x32f5e4,0x00000000), stub!
                            fixme:d3d_caps:wined3d_guess_card No card selector available for GL vendor 0x4 and card vendor 0000 (using GL_RENDERER "Mesa X11").
                            fixme:win:EnumDisplayDevicesW ((null),0,0x32f608,0x00000000), stub!
                            fixme:d3d_caps:wined3d_guess_card No card selector available for GL vendor 0x4 and card vendor 0000 (using GL_RENDERER "Mesa X11").
                            fixme:win:EnumDisplayDevicesW ((null),0,0x32f3f4,0x00000000), stub!
                            err:d3d:context_choose_pixel_format Can't find a suitable iPixelFormat

                            edit: ok now i find the missing pieces:

                            wine ./FlashpointPreferences.exe'
                            fixme:win:EnumDisplayDevicesW ((null),0,0x32f5e4,0x00000000), stub!
                            fixme:win:EnumDisplayDevicesW ((null),0,0x32f608,0x00000000), stub!
                            fixme:win:EnumDisplayDevicesW ((null),0,0x32f3f4,0x00000000), stub!

                            Edit: ok to ground textures:
                            "fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported.
                            Please configure the application to use double buffering (1 back buffer) if possible.
                            fixme:d3d:resource_check_usage Unhandled usage flags 0x28.
                            fixme:d3d:resource_check_usage Unhandled usage flags 0x28.
                            fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
                            fixme:d3d:wined3d_buffer_preload Too many declaration changes or converting dynamic buffer, stopping converting
                            fixme:d3d_draw:drawPrimitive Using software emulation because manual fog coordinates are provided"
                            Last edited by Qaridarium; 12-27-2011, 11:28 AM.

                            Comment


                            • #15
                              I, for one, compile and install mesa/wine inside a 32 bit chroot. This way it's easier to manage and dependencies stay up-to-date (no more waiting for ia32-libs to catch up on debian)

                              Also regarding the last bit, most games I've been playing around with will crash if 2 monitors are running and in order to work around this, one must be disabled:
                              $ xrandr --output DVI-1 --off

                              Also note, the only game I've tried that is playable at all is CS: Source. Every other game experiences its own set of bugs/crashes. However you may have better luck. My sample size is quite low, consisting of all the GTAs and the 2 Halos out for pc

                              Comment

                              Working...
                              X