Search:

There's a good chance that's because you have an old (32-bit) libxcb that doesn't include http://cgit.freedesktop.org/xcb/libxcb/commit/?id=23911a707b8845bff52cd7853fc5d59fb0823cef, although that...

That clearly proves it then, we added support for a couple of OpenGL extensions written by nvidia between Wine 1.0 and 1.2. We also love nvidia so much we infiltrated Mesa to sabotage the free...

Yeah well, lots of people read something on a forum somewhere and then repeat it. Unfortunately none of them actually know what they're talking about, and it's complete BS.

(Yeah, I'm obviously biased here.)


That's only true if such a port is actually done by skilled developers. If a port is done by people not terribly familiar with the target platform you can...

Those look like two different issues. The ME2 problem is probably due to Wine not having a HLSL compiler yet, installing native d3dx9 may help. The SC2 problem is probably because Wine actually...

Probably. What driver / hardware are you actually using? This sounds like the kind of thing that would happen if you either don't have properly installed 32-bit GL drivers, or are using a fairly old...

For a minor performance improvement, with Wine 1.3.27 try setting the "AlwaysOffscreen" Direct3D registry setting to "enabled". It avoids a fallback in the driver related to depth copies. The same...

To me it seems obvious that Martin's intent was to express that as a person he values expressing his opinion / making issues he's running into known over avoiding potentially offending other people....

No, that's pretty much just wrong. Please read the (entire) thread at http://lists.freedesktop.org/archives/mesa-dev/2011-April/006870.html. The commit in question is...

Yeah, texture_rectangle gives you NPOT textures with limitations, but no normalized coordinates.

Yeah. Though in the specific example you mention, I think everyone would have been much happier if ATI at the time had just created some kind of "conditional NPOT" or "normalized texrect" extension.

I'll probably regret replying to this, but oh well. It seems most people didn't bother reading the actual mailing list thread.



Except that that isn't what he actually said. Here's the actual...

I mostly agree with that, though I also think that with r300g hardware you're a bit more likely to end up being GPU limited.

I imagine lots of people weren't using Linux yet back then, but the wayback machine still has a copy of TransGaming's old website with that promise:...

Yeah, Maarten did that fix. Note that in principle you should only be affected by that regression if you explicitly disabled GLSL though.

There are regression tests, yes. The issue is on one side that Win9x is missing lots of things that are present on later versions. For example, Win9x has practically no support for Unicode, so if you...

A couple of points:
- The article seems fairly clueless about what reflection support means, and how it fits in with the rest of Wine.
- Wine using the d3d1x state tracker simply isn't...

For development I just use appropriately set LD_LIBRARY_PATH and LIBGL_DRIVERS_PATH environment variables.

If you run Wine with WINEDEBUG=+wgl it should tell you what GL renderer it's using, among others. E.g.:



If you didn't explicitly compile 32-bit r600g yourself, you're probably using whatever...

That doesn't sound like r600g. You should only get that FIXME if the driver doesn't support the ARB_framebuffer_object extension, but r600g supports that, while r600c doesn't.