Too lazy to write up a body for this thread, so I'll just quote the readme and then shorten it.
ShaderView is a program written for one thing. Viewing
Vein .SHADER and .CVS (Compiled Vein Shader) files. When Shader-
View loads a .SHADER it compiles it into a (sometimes) smaller
.CVS file. This CVS file is then decompiled, or loaded, and the
shaders are shown on 5 objects: a cube, sphere, cylinder, sky sphere,
and plane (which is only visible in the 'walk around' mode).
So, to shorten that description, it loads Vein 'shader' (not really shaders, but I like the name) files, reads them, sticks them on a couple of primitives, and lets you view them. It also spits out a compiled version (*.CVS), just for the purpose of converting CVS back to the normal version, a backup copy that is generated based on what is loaded at the time.
No screenshots, sorry.
Download
If there are any problems, I need to hear about them so I can fix them. There was a memory leak in the last version, so right now I'd like to sort out any problems that are really slowing down the program (besides that it forces use of all 8 texture layers [so that shader swapping is possible]).
And if the archive is corrupted, I'm going to shoot myself in the foot. I really hate being on 56k.
ShaderView is a program written for one thing. Viewing
Vein .SHADER and .CVS (Compiled Vein Shader) files. When Shader-
View loads a .SHADER it compiles it into a (sometimes) smaller
.CVS file. This CVS file is then decompiled, or loaded, and the
shaders are shown on 5 objects: a cube, sphere, cylinder, sky sphere,
and plane (which is only visible in the 'walk around' mode).
So, to shorten that description, it loads Vein 'shader' (not really shaders, but I like the name) files, reads them, sticks them on a couple of primitives, and lets you view them. It also spits out a compiled version (*.CVS), just for the purpose of converting CVS back to the normal version, a backup copy that is generated based on what is loaded at the time.
No screenshots, sorry.
Download
If there are any problems, I need to hear about them so I can fix them. There was a memory leak in the last version, so right now I'd like to sort out any problems that are really slowing down the program (besides that it forces use of all 8 texture layers [so that shader swapping is possible]).
And if the archive is corrupted, I'm going to shoot myself in the foot. I really hate being on 56k.