Sign in to follow this  
JulianMcKinlay

OpenGL Errors compiling CgFX effects using Direct3D9 .FX States

Recommended Posts

JulianMcKinlay    118
Hello,

I have recently begun using Cg and CgFX and have read through most of the Cg Tutorial book available at the nVidia Developer Zone. I am specifically interested in migrating an existing rendering effect system that uses Direct3D 9's .FX effect file format to Cg's .CgFX file format to increase portability, as CgFx is compatible with both Direct3D and OpenGL. CgFX seems well suited as according to the Cg Tutorial, it is "identical" to Direct3D 9's .FX file format. This is exactly what I need, as it will save me the effort of re-writing all of my effect scripts.

Unfortunately, my effect scripts are not compiling under Cg, and I am beginning to doubt that .CgFX and .FX are identical. Consulting the documentation, there seem to be places where the DirectX convention is used, such as with the "CullMode" state, which accepts the DirectX enumerants "None", "CW", "CCW", and other times where some other convention is used, such as with the "DiffuseMaterialSource" state that only appears to accept the enumerants "true" and "false". (Whatever that means.)

I am looking for a definitive answer: Should I expect to be able to compile under Cg any .FX script that compiles successfully under Direct3D 9? If so, what do I have to do to make this possible?

Here is an example to illustrate the problem.

My .CgFX effect, the contents of which compile successfuly as a DirectX .FX effect file under Direct3D 9:[code]technique Default
{
pass P0
{
Lighting = False;
CullMode = None;

AmbientMaterialSource = Color1;
DiffuseMaterialSource = Color1;
SpecularMaterialSource = Material;
EmissiveMaterialSource = Material;

LightEnable[0] = True;
LightType[0] = Directional;
LightDirection[0] = float3(0.0f, 1.0f, 0.0f);
LightAmbient[0] = float4(0.1f, 0.1f, 0.1f, 1.0f);
LightDiffuse[0] = float4(1.0f, 0.0f, 0.0f, 1.0f);
LightSpecular[0] = float4(1.0f, 1.0f, 1.0f, 1.0f);

MagFilter[0] = Linear;
MinFilter[0] = Linear;
MipFilter[0] = Linear;

AddressU[0] = Clamp;
AddressV[0] = Clamp;

VertexShader = null;
PixelShader = null;
}
}[/code]


My set up code, which initializes Cg and loads the effect:
[code]CGcontext cgContext = cgCreateContext();
cgD3D9RegisterStates(cgContext);
CGeffect cgEffect = cgCreateEffect(cgContext, "Data/Effects/Default.cgfx", nullptr);[/code]


The errors that are reported when trying to compile the effect in the code above:
[code]error C1056: invalid initialization
error C1008: undefined variable "Color1"
error C1008: undefined variable "Color1"
error C1008: undefined variable "Material"
error C1008: undefined variable "Material"
error C1008: undefined variable "Directional"
error C1056: invalid initialization
error C1008: undefined variable "Linear"
error C1008: undefined variable "Linear"[/code]

The Cg effect compiler is recognizing some of the Direct3D .FX script state enumerants, but not all of them. Why?

I would greatly appreciate any help with this problem.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
       
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now