Announcement

Collapse
No announcement yet.

Mesa Beginning To Need Application Workarounds

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

  • #16
    Originally posted by curaga View Post
    Unigine folks already said these are fixed? Carry on on the general case though
    Depends if it just OilRush or if they are planning on releasing new versions of the benchmarks too.

    In other news, Super Meat Boy and Shank still doesn't run on Mesa out-of-the-box, because it is "asshole correct".

    Comment


    • #17
      i think workarounds should be handled off-tree in a seperate package, maybe through api.
      that way its easy for users to choose if they want only specification compliance or compatibilty, maybe even easily switchable by configs files.

      Comment


      • #18
        i (half seriously) propose charity bug bounties.

        "I pledge to donate x to charity y when bug #z is fixed."

        This should help solve all the worlds problems.

        Comment


        • #19
          Originally posted by lopho View Post
          i think workarounds should be handled off-tree in a seperate package, maybe through api.
          that way its easy for users to choose if they want only specification compliance or compatibilty, maybe even easily switchable by configs files.
          Anholt's proposal already addresses that, I think. The idea is that although the workarounds are in the Mesa code base, they're individually enabled/disabled/mapped to applications via drirc. This is far better than a global "quirks mode / standards mode" switch.

          Comment


          • #20
            Originally posted by siride View Post
            You really want to make sure that nobody targets Linux, eh?
            You really want to make sure that Linux is as sloppy as Windows, eh?

            Comment

            Working...
            X