http://bugs.winehq.org/show_bug.cgi?id=30232
--- Comment #12 from julusp@gmail.com 2012-04-03 07:59:38 CDT --- (In reply to comment #10)
It's probably hitting the software fallback that hack was originally supposed to avoid, which is stupid because the hardware can easily run these shaders. You should probably ask Apple to fix the drivers, one way or another.
Just to make things clear. The hack was rewriting value from GL_MAX_PROGRAM_ENV_PARAMETERS_ARB to value from GL_MAX_PROGRAM_NATIVE_PARAMETERS_ARB.
so in the wine code (before hacking) limits.arb_ps_float_constants = 128 (windows and linux reporting 256) limits.arb_ps_native_constants = 256 limits.arb_vs_float_constants = 256 limits.arb_vs_native_constants = 256
will become: limits.arb_ps_float_constants = 256 limits.arb_ps_native_constants = 256 limits.arb_vs_float_constants = 256 limits.arb_vs_native_constants = 256
but if thats true, then NVIDIA (9600GT M and others) was affected as well - the limits.arb_ps_float_constants (128) was overwriten by limits.arb_ps_native_constants (1024). For reference: limits.arb_ps_float_constants on win and linux was detected to 256.
also the number of mismatch of windows/linux and macos GL capabilities are... well. insane http://feedback.wildfiregames.com/report/opengl/device/Radeon%20HD%204850