Re: [Dri-devel] gl extensions on/off
I think the point is (but I could be wrong) whether this is user-configurable without recoding/recompiling anything, and it seems the answer is no. That's bad. Definitely this is not high-priority issue, but it would be nice to have ability to enable/disable extensions without recompiling apps/drivers/etc. Well written apps should be able to determine which extensions are available (shouldn't them?) so it could be interesting to play with apps using different subsets of extensions. Anyway, thanks to everybody for comments. Sergey ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] gl extensions on/off
Leif Delgass wrote: On Tue, 11 Dec 2001, Brian Paul wrote: Sergey V. Udaltsov wrote: Hi all Is it possible to turn on/off some particular GL extenstions in Mach64 driver? Is mesa.conf in any help here? I would like to play with texture-related extensions (probable, turning GL_ARB_multitextures off would solve my problems in celestia?) You can call the _mesa_enable/disable_extension() functions in the context-init code in the driver, like other DRI drivers do, to enable or disable various extensions. I'm not sure the mesa.conf stuff works anymore. I think the point is (but I could be wrong) whether this is user-configurable without recoding/recompiling anything, and it seems the answer is no. The driver can enable/disable extensions for all apps using the driver, or an app using GL through the driver can choose to enable or disable extensions supported by the driver. So it's up to the application (in this case celstia) to let the user configure which are used, right? Sure, an app can always elect whether or not it uses particular extensions. Maybe I'm missing your point. -Brian _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] gl extensions on/off
On 12 Dec 2001, Sergey V. Udaltsov wrote: I think the point is (but I could be wrong) whether this is user-configurable without recoding/recompiling anything, and it seems the answer is no. That's bad. Definitely this is not high-priority issue, but it would be nice to have ability to enable/disable extensions without recompiling apps/drivers/etc. Well written apps should be able to determine which extensions are available (shouldn't them?) so it could be interesting to play with apps using different subsets of extensions. I should point out that with the mach64 driver, there are some things still left to be implemented in the Mesa code, as it's still in development. I've also had problems with multitexturing and texture blending modes in other apps with this driver. So although the extension is currently exported by the driver, it probably still needs some work to get it working right: AGP texture uploads are not yet supported, for example. Many apps have a way to disable certain GL extensions, so that can be used as a workaround when available. At this stage though, it's probably best to try and find problems and fix the driver where possible. If an extension is exported, but doesn't work to spec, it's a bug. The ability to have the driver hide supported gl extensions could be useful too, but the app could always just refuse to work without them. :) --Leif --- Leif Delgass http://www.retinalburn.net ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] gl extensions on/off
Sure, an app can always elect whether or not it uses particular extensions. Maybe I'm missing your point. An app? Probably. But some particular (very nice, BTW) apps still very dumb in terms of configuration so I'd like to have ability to turn extensions on/off myself, without modifying the app code (as a user). Anyway, this RFE has priority 0.0001 (where 1.0 is Normal). Cheers, Sergey ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: [Dri-devel] gl extensions on/off
Why force any application to implement some more or less wide set of external shell varibles to query while the same is much easier to maintain if its part of a gatekeeper library? Exactly! That's what I meant! Sergey ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] gl extensions on/off
On Wed, Dec 12, 2001 at 04:30:56PM +, Sergey V. Udaltsov wrote: Why force any application to implement some more or less wide set of external shell varibles to query while the same is much easier to maintain if its part of a gatekeeper library? Exactly! That's what I meant! Quake3 allows a user to selectively enable or disable its *use* of certain GL extensions. If this is the behaviour you want, then it's more an application thing than a driver thing. Look at some of the Mesa demos -- you may bind the 't' key to toggle multitexturing, for example. Environment variables in the driver are good for driver development, when the implementation of a certain extension may be buggy and thus disabled by default for instance. -- Gareth ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] gl extensions on/off
Hi all Is it possible to turn on/off some particular GL extenstions in Mach64 driver? Is mesa.conf in any help here? I would like to play with texture-related extensions (probable, turning GL_ARB_multitextures off would solve my problems in celestia?) Cheers, Sergey ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] gl extensions on/off
Sergey V. Udaltsov wrote: Hi all Is it possible to turn on/off some particular GL extenstions in Mach64 driver? Is mesa.conf in any help here? I would like to play with texture-related extensions (probable, turning GL_ARB_multitextures off would solve my problems in celestia?) You can call the _mesa_enable/disable_extension() functions in the context-init code in the driver, like other DRI drivers do, to enable or disable various extensions. I'm not sure the mesa.conf stuff works anymore. -Brian _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] gl extensions on/off
On Tue, Dec 11, 2001 at 07:28:54PM -0500, Leif Delgass wrote:
I think the point is (but I could be wrong) whether this is
user-configurable without recoding/recompiling anything, and it seems the
answer is no. The driver can enable/disable extensions for all apps using
the driver, or an app using GL through the driver can choose to enable or
disable extensions supported by the driver. So it's up to the application
(in this case celstia) to let the user configure which are used, right?
Make the enable/disable configurable by an environment variable, like
so:
if ( getenv( LIBGL_DISABLE_MULTITEXTURE ) ) {
gl_extensions_disable( ctx, GL_ARB_multitexture );
}
if ( getenv( LIBGL_ENABLE_TEXTURE_ENV_ADD ) ) {
gl_extensions_enable( ctx, GL_EXT_texture_env_add );
gl_extensions_enable( ctx, GL_ARB_texture_env_add );
}
Then, a user/app can just do something equivalent to:
export LIBGL_DISABLE_MULTITEXTURE=1
./my_app
And you're done. Variable naming left as an exercise for the user.
-- Gareth
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: [Dri-devel] gl extensions on/off
Make the enable/disable configurable by an environment variable, like
so:
if ( getenv( LIBGL_DISABLE_MULTITEXTURE ) ) {
gl_extensions_disable( ctx, GL_ARB_multitexture );
}
if ( getenv( LIBGL_ENABLE_TEXTURE_ENV_ADD ) ) {
gl_extensions_enable( ctx, GL_EXT_texture_env_add );
gl_extensions_enable( ctx, GL_ARB_texture_env_add );
}
Then, a user/app can just do something equivalent to:
export LIBGL_DISABLE_MULTITEXTURE=1
./my_app
And you're done. Variable naming left as an exercise for the user.
-- Gareth
Extensions do get detected by browsing a lengthy string.
Entry point adresses are retrived via a single GL API call.
Extensions constants and alikes simply get used and
will possibly get hounoured by the misc GL calls.
Therefore i would call this hide and reveal in the first row
when some intermediate layer does remove or add
the repsective strings or bases addresses.
Regards, Alex.
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
