Try vp40/fp40 profiles to generate assembler code for the GF6/7 series. The “glslf” profile is not to compile GLSL code, it’s for generatin GLSL code from a CG shader. But cgc is usefull to get an overview about the assembler code. GLSL shader code should be compiled just in time. With cgc you are a little bit on the wrong track: So, a specific shader IDE isn’t really the right solution here as I’d have to shoehorn the rest of the application development into the shader IDE framework. The shaders also don’t do anything interesting without a lot of CPU support. So most of my time is spent inside Visual Studio working on the main code, and shader development is a small part of that.
That looks like a pretty slick environment, but not really what I’m looking for - I’m writing large applications that include a GPGPU component for offloading some processing.
Later you can load them together with models from a (XML) file. You could use it to write the shaders and test them. You could try my project at I wrote to test shaders without setting up a complete C/C++ program. glsl gets this build step applied…Īnyway, I imagine lots of other people are in a similar situation - what are your solutions? How do you make GLSL development as painless as possible? Unfortunately, I have to use Visual Studio 2005 (I miss developing in linux) so alternatives aren’t an option for me…Thanks! I’d much rather define a rule that any file with a suffix of. glsl file and add custom build steps to each one. Currently, I have NVIDIA’s cgc filling the role with “-oglsl -profile glslf” options, but it’s a poor solution (e.g., I’m currently getting a “warning C7506: OpenGL does not define the global function dot” message which is just silly).Īlso, to do the cgc compilation I currently have to go to the properties of each. Is there a (reference) GLSL command line compiler? I found 3DLabs GLSLValidate program, but that’s a GUI which really is not what I’m looking for. Has anyone done this for GLSL? If not, maybe I can convince my boss to let me spend some time on it.įor compilation support, I’d like to compile my shaders as part of the build process so I can get errors in the GLSL before I run the program. Things that would be great: language support in the form of syntax highlighting, auto indenting, etc., and compilation support.įor syntax highlighting, I’ve seen a few websites about extending Visual Studio with your own custom parser to define a custom language. I’m looking for ways to improve the integration between the two, beyond Visual Studio thinking the. Right now I’m writing GLSL shaders and using them within a Visual Studio 2005 C++ / OpenGL project, and the experience is a bit lacking.
0 kommentar(er)
