search

TVAM / winetricks

Automatically exported from code.google.com/p/winetricks
0 stars 0 forks source link

Shader model registry entries changed between 1.5.22 and 1.5.23 #357

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
See
http://source.winehq.org/git/wine.git/commitdiff/dc214603974132969c9f1bd13b8fe53
3bbb413dc
(wined3d: Replace "VertexShaderMode" and "PixelShaderMode" with shader model 
limits)

So the psm and vsm verbs are setting the wrong registry entries now.

How should we adapt?  Here's my guess:

We should probably keep the old verbs for backwards compatibility,
so that people can continue using the commands they're used to,
but also recognize numerical values.

So now, from the commandline,

 psm=N should set MaxShaderModelPS to N (and disabled means 0 / enabled means 3);
 vsm=N should set MaxShaderModelVS to N (and none means 0 / hardware means 3)
 gsm=N should set MaxShaderModelGS to N

and they should do the same thing they used to when used with wine-1.4,
i.e. somebody with wine-1.4 should not find the new winetricks
no longer supports his version of wine.

The gui should have entries 
 psm=0  Disable pixel shaders
 psm=3  Enable pixel shaders (max model 3)
 vsm=0  Disable vertex shaders
 vsm=3  Enable vertex shaders (max model 3)
 gsm=0  Disable geometry shaders
 gsm=3  Enable geometry shaders (max model 3)
instead of the old ones.

The m now means max :-)

Original issue reported on code.google.com by daniel.r...@gmail.com on 1 Oct 2013 at 3:13