Re: Allow enabling/disabling Direct3D usage of GLSL in Winecfg + update Czech locales for Winecfg
Vit Hrachovy wrote:
Hi, according to thread 'WineCfg and DirectX options' at wine-devel, That thread was heading in the wrong direction...
I'm proposing a patch for winecfg to allow enabling/disabling usage of GLSL for Direct3D applications rendering. Do you want to make it easy to configure GLSL, or make it easy to enable GLSL? In other words, can you enumerate the cases where one would disable GLSL? Should those be in a document somewhere on the wiki as blockers to 1.0 (since GLSL default was pointed out as a 1.0 requirement)? Do we expect this option to be around for a long time?
I don't see consensus to add these options in the referenced thread - if more testing exposure is needed, why not just enable this by default?
On 29/03/07, Ivan Gyurdiev <ivg231(a)gmail.com> wrote:
Do you want to make it easy to configure GLSL, or make it easy to enable GLSL? In other words, can you enumerate the cases where one would disable GLSL? Should those be in a document somewhere on the wiki as blockers to 1.0 (since GLSL default was pointed out as a 1.0 requirement)? Do we expect this option to be around for a long time?
I don't see consensus to add these options in the referenced thread - if more testing exposure is needed, why not just enable this by default?
IMO the only reasons for having this option would be for specifically testing the ARB backend, or working around broken drivers. I don't think either warrants an option in winecfg. The video memory setting could be useful though, since I don't think we're going to solve that soon.
On 3/29/07, H. Verbeet <hverbeet(a)gmail.com> wrote:
On 29/03/07, Ivan Gyurdiev <ivg231(a)gmail.com> wrote:
Do you want to make it easy to configure GLSL, or make it easy to enable GLSL? In other words, can you enumerate the cases where one would disable GLSL? Should those be in a document somewhere on the wiki as blockers to 1.0 (since GLSL default was pointed out as a 1.0 requirement)? Do we expect this option to be around for a long time?
I don't see consensus to add these options in the referenced thread - if more testing exposure is needed, why not just enable this by default?
IMO the only reasons for having this option would be for specifically testing the ARB backend, or working around broken drivers. I don't think either warrants an option in winecfg.
I agree, if you add GLSL why not add everything? DirectDrawRenderer, RenderTargetLockMode, Nonpower2Mode, OffscreenRenderingMode and have a D3D tab? Why not take this a step further and add the ability to force drawStridedFast instead of drawStridedSlow ? This would be really nice :) http://www.winehq.org/pipermail/wine-devel/2007-March/055419.html IMHO if we add one of the many options that are available we should add all of them...
The video memory setting could be useful though, since I don't think we're going to solve that soon.
-- Tom Wickline Respectable computing - Linux/FOSS
participants (3)
-
H. Verbeet -
Ivan Gyurdiev -
Tom Wickline