Resource:Shadermanager: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Added info about the defaultState setting) |
||
| Line 5: | Line 5: | ||
==Proposed Features== | ==Proposed Features== | ||
* Adoption of a "type='shader'" standard to allow shadermanager to find all the shaders on a server. | * Adoption of a "type='shader'" standard to allow shadermanager to find all the shaders on a server. | ||
* Adoption of the #shadername.defaultState setting to determine whether or not to enable the shader by default (0 for no, 1 for yes, 0 by default). | |||
* Minimalistic GUI to allow for the enabling/disabling of shaders. | * Minimalistic GUI to allow for the enabling/disabling of shaders. | ||
** Small log to allow for viewing of shader-specific errors. | ** Small log to allow for viewing of shader-specific errors. | ||
Revision as of 02:24, 29 April 2012
|
Warning: This is a planned resource (it's not ready yet!) |
Shadermanager is a planned resource to facilitate the managment of shaders in MTA, analogous to mapmanager for maps. This page is simply here to serve as a place to share the proposed system. To discuss, contact John on #mta.
Proposed Features
- Adoption of a "type='shader'" standard to allow shadermanager to find all the shaders on a server.
- Adoption of the #shadername.defaultState setting to determine whether or not to enable the shader by default (0 for no, 1 for yes, 0 by default).
- Minimalistic GUI to allow for the enabling/disabling of shaders.
- Small log to allow for viewing of shader-specific errors.
- Exported functions to allow shadermanager to function as a backend for other scripts (allowing someone else to implement their own GUI, for example).
- getShaderFromName, getAllShaders, setShaderEnabled, isShaderEnabled, isShaderCompatibleWithClient
- Adoption of certain exported functions for shaders to allow shadermanager to control all the shaders on a server.
- setShaderEnabled, isShaderEnabled