(12-15-2012, 08:19 AM)NaturalViolence Wrote: He's getting a shader compiler error that nobody else is getting. If that doesn't point to drivers then I don't know what does.Shaders aren't compiled* on the driver side. It's in the d3dcompiler.dll, which is part of the DirectX runtime. So basically, about everything points more to the drivers than that. I can see the point why people would think "shader stuff" failing is linked to gpu driver issues, but well... no.
*compiled as in: Compile hlsl code to the common bytecode, which is handed over to the gpu drivers later
(12-15-2012, 08:19 AM)NaturalViolence Wrote: Seriously how many AMD specific driver issues are we up to at this point if you count the texture filtering issue and the MSAA d3d11 issue?Do you mean the texture filtering issue which does not affect Dolphin but only the pcsx2 crowd? Then, that one doesn't count over here I guess.
No idea what you're talking about with the msaa thing.
Also, keep in mind that there are basically just two drivers which work well with Dolphin (NV and AMD), so it's not that terribly hard to make things work with the one while breaking the other. Dolphin's GPU core has been mostly written by people with no graphics development background (not AFAICT, anyway), so don't expect any of the stuff we do to be what the standard specifies. The shader generator expecting "normalize(0)" to return any specific value while it's explicitely noted to be undefined in the msdn docs is a good example of this.
tl;dr: Get your facts straight, please. Don't make me post rageface pictures here
