• Advertisement
Sign in to follow this  

OpenGL OpenGL to DirectX. Constant buffers.

This topic is 1297 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi.

 

Im busy creating a directX11 renderer for my game. I did the neccesary refactoring to seperate the graphics calls from the rest of the engine by creating an interface and moving all the opengl code into an implementation of the interface. Then i created a directx implementation of the interface and started implementing it bit by bit. Now I pretty much have most of it down except for constant buffers.

 

The interface very much caters towards opengl since thats the first implementation i wrote (and before now I didnt know any directX). As a result the directX implementation looks more like opengl emulation than a proper directx implementation. But thats fine for now. Once i get the game fully rendered in directX il start looking at ways to improve that.

 

So now my implementation has a method named. sendUniform1i (string uniformName, int value) wich would in the opengl implemenation of course set the int uniform named 'uniformName' to the value in 'value' for the current shaders. Im strugling to figure out how i would implement (emulate?) this in directx. Remember this is just my intermediate step i dont care how dirty it is for now. I was thinking along the lines of giving each constant variable in directx its own constant buffer but as far as i can tel the only way to reference this buffer in code would be by its 'buffer slot number' (: register(b0) etc). Whereas i need a way to get a handle on it by its name. The constant buffer as declared in a shader does have a name but i cant seem to find any example of how you can use that name. I might just be mssing it.

 

Any suggestions?

 

thnx in Advance

Share this post


Link to post
Share on other sites
Advertisement

Yes i stil use some pretty old opengl I supose I will first refactor my existing code into using uniform buffer objects before continueing with the directX implementation.

 

Thnx!

Share this post


Link to post
Share on other sites

Just for clarification:

 

 


..as far as i can tel the only way to reference this buffer in code would be by its 'buffer slot number' (: register(b0) etc)..

 

By buffer slot number - true. Register number - maybe, maybe not. Whether the register numbers line up with the slot numbers depends on a couple things, so, as a suggestion, don't associate register numbers and slot numbers in your mind.

 

If you use an effect framework as unbird suggests, you don't need to worry about register numbers anyway.

 

I really don't want to confuse you if you're not fully into D3D11 yet. So read further only at your peril.

 

If you eventually compile shaders separately (e.g., a vertex shader, a geometry shader and a pixel shader) from the same file, the slot numbers associated with a particular buffer are by shader usage, not register number.

 

E.g., if you have a file written in HLSL which includes, for instance, both vertex shader and a pixel shader code, and you compile that file 2 times (once for each shader), the slots for any constant buffers will depend on whether the buffer is used by a particular shader, whatever the register number. Other buffers not needed by the shader will not be compiled with it.

 

For example:

// shader file
buffer VS_stuff
{
  float4 someVariable; // not used by the pixel shader
};

buffer PS_stuff
{
  float4 someOtherVariable; // not used by the vertex shader
};

... VS and PS code

In your rendering code:

context->VSSetConstantBuffers( 0, 1, (..resource reflecting VS_stuff)); // slot 0
context->PSSetConstantBuffers( 0, 1, (..resource reflecting PS_stuff)); // ALSO slot 0
Edited by Buckeye

Share this post


Link to post
Share on other sites

If it is urgent and you don't need the performance gain from cbuffers, you can still use them in the old fasion way(aka. you can fake separate uniform binding)

 

in HLSL

Declare your uniforms as global scope variable, they will be part of the implicitly created constant buffer .

When you Call D3DReflect this function will return the layout of the created cbuffer, its bind slot(should be always the same in that specific case) ect.

 

Create one large enough cbuffer for each shader type. This so all vertex shaders will use that cbuffer and so on for each shader type. When you call your function that updates the uniforms you will update the cbuffer storage behind the scenes.

Also you will have to merge the uniform names and the buffers because in OGL you bind uniforms per program in d3d you bind uniforms per shader stage.

 

Another thing that will cause you headaches is the sampler and texture binding!

 

Hope that will help

 

EDIT:

Another thing that will cause you headaches is the sampler and texture binding!

I've actually cheated here. http://www.opengl.org/wiki/GLAPI/glBindSampler

There are sampler state objects in OGL 

Edited by imoogiBG

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Now

  • Advertisement
  • Similar Content

    • By khawk
      We've just released all of the source code for the NeHe OpenGL lessons on our Github page at https://github.com/gamedev-net/nehe-opengl. code - 43 total platforms, configurations, and languages are included.
      Now operated by GameDev.net, NeHe is located at http://nehe.gamedev.net where it has been a valuable resource for developers wanting to learn OpenGL and graphics programming.

      View full story
    • By TheChubu
      The Khronos™ Group, an open consortium of leading hardware and software companies, announces from the SIGGRAPH 2017 Conference the immediate public availability of the OpenGL® 4.6 specification. OpenGL 4.6 integrates the functionality of numerous ARB and EXT extensions created by Khronos members AMD, Intel, and NVIDIA into core, including the capability to ingest SPIR-V™ shaders.
      SPIR-V is a Khronos-defined standard intermediate language for parallel compute and graphics, which enables content creators to simplify their shader authoring and management pipelines while providing significant source shading language flexibility. OpenGL 4.6 adds support for ingesting SPIR-V shaders to the core specification, guaranteeing that SPIR-V shaders will be widely supported by OpenGL implementations.
      OpenGL 4.6 adds the functionality of these ARB extensions to OpenGL’s core specification:
      GL_ARB_gl_spirv and GL_ARB_spirv_extensions to standardize SPIR-V support for OpenGL GL_ARB_indirect_parameters and GL_ARB_shader_draw_parameters for reducing the CPU overhead associated with rendering batches of geometry GL_ARB_pipeline_statistics_query and GL_ARB_transform_feedback_overflow_querystandardize OpenGL support for features available in Direct3D GL_ARB_texture_filter_anisotropic (based on GL_EXT_texture_filter_anisotropic) brings previously IP encumbered functionality into OpenGL to improve the visual quality of textured scenes GL_ARB_polygon_offset_clamp (based on GL_EXT_polygon_offset_clamp) suppresses a common visual artifact known as a “light leak” associated with rendering shadows GL_ARB_shader_atomic_counter_ops and GL_ARB_shader_group_vote add shader intrinsics supported by all desktop vendors to improve functionality and performance GL_KHR_no_error reduces driver overhead by allowing the application to indicate that it expects error-free operation so errors need not be generated In addition to the above features being added to OpenGL 4.6, the following are being released as extensions:
      GL_KHR_parallel_shader_compile allows applications to launch multiple shader compile threads to improve shader compile throughput WGL_ARB_create_context_no_error and GXL_ARB_create_context_no_error allow no error contexts to be created with WGL or GLX that support the GL_KHR_no_error extension “I’m proud to announce OpenGL 4.6 as the most feature-rich version of OpenGL yet. We've brought together the most popular, widely-supported extensions into a new core specification to give OpenGL developers and end users an improved baseline feature set. This includes resolving previous intellectual property roadblocks to bringing anisotropic texture filtering and polygon offset clamping into the core specification to enable widespread implementation and usage,” said Piers Daniell, chair of the OpenGL Working Group at Khronos. “The OpenGL working group will continue to respond to market needs and work with GPU vendors to ensure OpenGL remains a viable and evolving graphics API for all its customers and users across many vital industries.“
      The OpenGL 4.6 specification can be found at https://khronos.org/registry/OpenGL/index_gl.php. The GLSL to SPIR-V compiler glslang has been updated with GLSL 4.60 support, and can be found at https://github.com/KhronosGroup/glslang.
      Sophisticated graphics applications will also benefit from a set of newly released extensions for both OpenGL and OpenGL ES to enable interoperability with Vulkan and Direct3D. These extensions are named:
      GL_EXT_memory_object GL_EXT_memory_object_fd GL_EXT_memory_object_win32 GL_EXT_semaphore GL_EXT_semaphore_fd GL_EXT_semaphore_win32 GL_EXT_win32_keyed_mutex They can be found at: https://khronos.org/registry/OpenGL/index_gl.php
      Industry Support for OpenGL 4.6
      “With OpenGL 4.6 our customers have an improved set of core features available on our full range of OpenGL 4.x capable GPUs. These features provide improved rendering quality, performance and functionality. As the graphics industry’s most popular API, we fully support OpenGL and will continue to work closely with the Khronos Group on the development of new OpenGL specifications and extensions for our customers. NVIDIA has released beta OpenGL 4.6 drivers today at https://developer.nvidia.com/opengl-driver so developers can use these new features right away,” said Bob Pette, vice president, Professional Graphics at NVIDIA.
      "OpenGL 4.6 will be the first OpenGL release where conformant open source implementations based on the Mesa project will be deliverable in a reasonable timeframe after release. The open sourcing of the OpenGL conformance test suite and ongoing work between Khronos and X.org will also allow for non-vendor led open source implementations to achieve conformance in the near future," said David Airlie, senior principal engineer at Red Hat, and developer on Mesa/X.org projects.

      View full story
    • By _OskaR
      Hi,
      I have an OpenGL application but without possibility to wite own shaders.
      I need to perform small VS modification - is possible to do it in an alternative way? Do we have apps or driver modifictions which will catch the shader sent to GPU and override it?
    • By xhcao
      Does sync be needed to read texture content after access texture image in compute shader?
      My simple code is as below,
      glUseProgram(program.get());
      glBindImageTexture(0, texture[0], 0, GL_FALSE, 3, GL_READ_ONLY, GL_R32UI);
      glBindImageTexture(1, texture[1], 0, GL_FALSE, 4, GL_WRITE_ONLY, GL_R32UI);
      glDispatchCompute(1, 1, 1);
      // Does sync be needed here?
      glUseProgram(0);
      glBindFramebuffer(GL_READ_FRAMEBUFFER, framebuffer);
      glFramebufferTexture2D(GL_READ_FRAMEBUFFER, GL_COLOR_ATTACHMENT0,
                                     GL_TEXTURE_CUBE_MAP_POSITIVE_X + face, texture[1], 0);
      glReadPixels(0, 0, kWidth, kHeight, GL_RED_INTEGER, GL_UNSIGNED_INT, outputValues);
       
      Compute shader is very simple, imageLoad content from texture[0], and imageStore content to texture[1]. Does need to sync after dispatchCompute?
    • By Jonathan2006
      My question: is it possible to transform multiple angular velocities so that they can be reinserted as one? My research is below:
      // This works quat quaternion1 = GEQuaternionFromAngleRadians(angleRadiansVector1); quat quaternion2 = GEMultiplyQuaternions(quaternion1, GEQuaternionFromAngleRadians(angleRadiansVector2)); quat quaternion3 = GEMultiplyQuaternions(quaternion2, GEQuaternionFromAngleRadians(angleRadiansVector3)); glMultMatrixf(GEMat4FromQuaternion(quaternion3).array); // The first two work fine but not the third. Why? quat quaternion1 = GEQuaternionFromAngleRadians(angleRadiansVector1); vec3 vector1 = GETransformQuaternionAndVector(quaternion1, angularVelocity1); quat quaternion2 = GEQuaternionFromAngleRadians(angleRadiansVector2); vec3 vector2 = GETransformQuaternionAndVector(quaternion2, angularVelocity2); // This doesn't work //quat quaternion3 = GEQuaternionFromAngleRadians(angleRadiansVector3); //vec3 vector3 = GETransformQuaternionAndVector(quaternion3, angularVelocity3); vec3 angleVelocity = GEAddVectors(vector1, vector2); // Does not work: vec3 angleVelocity = GEAddVectors(vector1, GEAddVectors(vector2, vector3)); static vec3 angleRadiansVector; vec3 angularAcceleration = GESetVector(0.0, 0.0, 0.0); // Sending it through one angular velocity later in my motion engine angleVelocity = GEAddVectors(angleVelocity, GEMultiplyVectorAndScalar(angularAcceleration, timeStep)); angleRadiansVector = GEAddVectors(angleRadiansVector, GEMultiplyVectorAndScalar(angleVelocity, timeStep)); glMultMatrixf(GEMat4FromEulerAngle(angleRadiansVector).array); Also how do I combine multiple angularAcceleration variables? Is there an easier way to transform the angular values?
  • Advertisement