Announcement

Collapse
No announcement yet.

Ubuntu Needs To Improve OpenGL Drivers For Gaming

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

  • #16
    Originally posted by Hamish Wilson View Post
    Well, Fedora will never make something like Jockey as it is opposed to shipping patented or proprietary drivers and codecs. Does that mean Steam will not work with it?

    Now, they could just make Steam look for it and then not complain when it does not find it, but still.
    I suppose it's kinda hard to say at this early juncture. They could make Steam check the proprietary drivers and if it only find the open ones just pop up a message that game performance will be limited, but allow you to continue. This probably would work fine for older or 2d games. The reason they would tie it to Jockey would be so a newbie user could install the proprietary drivers easily to get them working. I'm sure a Fedora user could do the same with few manual command lines.
    Last edited by tweak42; 10-30-2012, 07:17 PM.

    Comment


    • #17
      Let's make some sensible assumptions here

      GL 2.x (es) will be a reccomendation. Games that need features available in GL 3 or 4 will use those versions (or GL2 and the relevant extensions).
      PA is optimised for power usage rather than low latency, 20ms is concidered acceptable limit for pro audio production, Ideally I would like to see pulse below that. (is this with or without using pulse with realtime capabilities).

      I don't think it's any great secret that Valve is targetting Ubuntu specifically rather than Linux in general. I personally think this is a sensible approach at least initially. It can't be that hard to package the library versions needed by steam needs in other distros.
      Last edited by kayosiii; 10-30-2012, 08:52 PM.

      Comment


      • #18
        Usually the libs are not the problem, but when they use something newer as u 11.10 then binaries will not work on Debian wheezy. Basically some Linux devs at Valve should know how to work around that, lets see if they did or not.

        Comment


        • #19
          Originally posted by tweak42 View Post
          I suppose it's kinda hard to say at this early juncture. They could make Steam check the proprietary drivers and if it only find the open ones just pop up a message that game performance will be limited, but allow you to continue. This probably would work fine for older or 2d games. The reason they would tie it to Jockey would be so a newbie user could install the proprietary drivers easily to get them working. I'm sure a Fedora user could do the same with few manual command lines.
          On Fedora repository, Ur Quan Masters, a fork of Star Control 2,and Quake 3 package include an autodownloader that allow to install audio and theme. Gaming publisher can keep track on RPM Fusion which remains as much closer to the Fedora package guideline.

          Comment


          • #20
            Originally posted by Kano View Post
            Usually the libs are not the problem, but when they use something newer as u 11.10 then binaries will not work on Debian wheezy. Basically some Linux devs at Valve should know how to work around that, lets see if they did or not.
            Why would they care about non-Ubuntu distros? everyone knows how they could work around things, but there'll be 50,000 things you have to workaround to cover everyone's insane choice of distro and desktop, etc. I think Valve would at some point care to make some money rather than cater to everybody's private distros, if I was a Linux engineering Valve, I don't think I'd be worrying about any distros except the ones Valve told me to make it work on.

            so far I hear they use libappindicator.so which I think is fairly Ubuntu specific.

            Dave.

            Comment


            • #21
              When you look at the first "trial" Linux client then it was working like the win32/osx one, i expect the final client will work similar. If you don't remember:

              http://store.steampowered.com/public...m_client_linux

              That file was used to update/install the client. The win/osx installers are stubs only as well. So i don't see the point why the binaries should be Ubuntu specific, maybe the steam installer will be in the U repository but thats all.

              Comment


              • #22
                Originally posted by airlied View Post
                Why would they care about non-Ubuntu distros? everyone knows how they could work around things, but there'll be 50,000 things you have to workaround to cover everyone's insane choice of distro and desktop, etc. I think Valve would at some point care to make some money rather than cater to everybody's private distros, if I was a Linux engineering Valve, I don't think I'd be worrying about any distros except the ones Valve told me to make it work on.

                so far I hear they use libappindicator.so which I think is fairly Ubuntu specific.

                Dave.
                I don't think Valve just orders their engineers to just make stuff work, well not without a good reason to. There's a interesting blog post by Valve’s Michael Abrash where he says that Valve has no formal management and hierarchey. Given that, it means the engineers working on the linux steam project have to have mad techinical skills as well as some personal stake in getting the project off the ground or else they wouldn't be working on it. This pretty much can explain why Valve sometimes takes forever to get stuff out the door, but also why them make some pretty polished stuff that works pretty damn well.

                Comment


                • #23
                  @airlied

                  That's what i mean:

                  http://phoronix.com/forums/showthrea...622#post123622

                  Can be tested with wine or osx as well:

                  http://phoronix.com/forums/showthrea...688#post123688

                  It can be done a bit smarter and somehow something must be differnet than 2 years ago, but that could not be much.
                  Last edited by Kano; 10-30-2012, 10:17 PM.

                  Comment


                  • #24
                    For all of the discussion/wishing on whether or not our preferred distro or drivers will work, this is all I have to say:

                    I would rather boot into Ubuntu with proprietary drivers to get my gaming fix than boot Windows.

                    Comment


                    • #25
                      The drivers can not be different when you use the same binary drivers.

                      Comment


                      • #26
                        I do see it reasonable and possible to have OpenGL 2 and the ES 2 version as minimum baseline for modern development. It's new enough for doing a lot and old enough for older graphics cards to support most of it. Hopefully they can get good drivers (the r300 for some radeon cards could become a very good example once matured a bit more).
                        And having newer cards using OpenGL 3.x and 4.x.

                        Comment


                        • #27
                          Originally posted by Ancurio View Post
                          I'm so thirsty already for all the tears of people still using dmix and expecting Valve & co to give one flying shit about them
                          Except: DMix, being transparent to the implementation, just works. Right way to do things, perhaps no. But it DOES WORK. Last I checked, Dmix worked with Steam + Wine with no modifications to config necessary. Any time I've tried to use > 1 thing with PulseAudio (not even simultaneously), I've had breakage.

                          And I'm sure I'm not alone, either.

                          As for the people "still using dmix" (including myself): PulseAudio put them there. When PulseAudio actually works, I'll switch.

                          Comment


                          • #28
                            Originally posted by kazetsukai View Post
                            Except: DMix, being transparent to the implementation, just works. Right way to do things, perhaps no. But it DOES WORK. Last I checked, Dmix worked with Steam + Wine with no modifications to config necessary. Any time I've tried to use > 1 thing with PulseAudio (not even simultaneously), I've had breakage.

                            And I'm sure I'm not alone, either.

                            As for the people "still using dmix" (including myself): PulseAudio put them there. When PulseAudio actually works, I'll switch.
                            That's because there are wine plugins for dmix/alsa audio. If the source engine runs natively,
                            I doubt they would make the extra work to support two audio APIs.

                            Unless someone decides to write a PA->dmix/alsa compat layer, it's looking grim for you guys.

                            Comment

                            Working...
                            X