• Advertisement
Sign in to follow this  

OpenGL Up axis problem with 3d Models [OpenGL]

This topic is 1999 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

Hello all,

I am having a problem with a discrepancy between a set of 3D models which I have purchased and the OpenGL coordinate system. All of the models were exported with the Z axis pointing up, while OpenGL by default has the Y axis pointing up. The way I see it there are two options:

1) Modify the OpenGL coordinate system so that the Z axis points up
2) Modify the 3D models so that the Y axis points up

Neither task sounds like fun (option 1 forces me to modify the way OpenGL works by default, which I take no pleasure in doing, option 2 forces me to use a program like Maya, which I know absolutely nothing about). I'm just trying to get a sense of what is more commonplace in the game industry. Is it up to the programming team to make the coordinate system match the 3D models, or is it on the art team to make sure that the 3D models come in the proper coordinate system? Additionally, which of the 2 possibilities is the recommended path to take?

Thanks,
-Adam

Share this post


Link to post
Share on other sites
Advertisement
In my 3D studio max exporter I have a flag that makes Y up because Max's up is +Z. What the flag does is applies a +90 rotation about the +X axis (right handed) to the object (or models skeleton root) transform, this rotates Max's +Y (my Max forward convention) to align with opengl +Y up, and swings the Max -Z (down) up to become the opengl forward (-Z is forward in opengl for me). If the objects transform is translated away from the origin you may have to swap its z and y, and then negate the new z.

There are many places where you can solve it. Flag it on export if you can. Flag it on the model when loading. Manually rotate the object before exporting. I wouldnt mess with opengl, Id rather tweak the data. I do it this way because it doesnt have an impact on animations, its just an additional transform at the root so that objects are not on their side (or face down on floor). Overall its just a pain.

I think maya is Y up by default but can be changed, Max doesnt allow it to be changed, in case you do import into Maya, initially you might have the same problem as with opengl.

Share this post


Link to post
Share on other sites
Thank you for the reply, this makes a lot of sense. I wish I knew more about 3D studio max, since I have absolutely no idea how to apply a transformation on export. Are there any resources you recommend that can help me set up this modification to the exporter?

Share this post


Link to post
Share on other sites
The exporter is one that I wrote for Max, I added the Y up functionality because Max +Z is up, so of course any transforms or data that comes out of Max by default will be laying on its back, its face or side.
If you have models already made and dont want to or cant re-export, then the simplest way would be to rotate them in code by manipulating the objects world matrix that gets used for rendering. If you have some sort of scene graph like transform hierarchy, you can just apply the transforms i mentioned to the objects local transform then when you calculate the objects world transform for rendering it will draw correctly.
If you decide to re-export, apply the appropriate transforms at the end just before exporting. Which might mean (in the case of 3DS max) rotating the object to be face down (or up or whatever) just before exporting. I doubt anyone working on the models would want to build objects on their side, so do the flip at the end before exporting once the models done.
Which ever way you do it is gonna produce the same result, if you do and 90 degree correction in Max/Maya just before export using the rotate widget after selecting the object, the underlying operation is the same 90 degree rotation you'd be doing in code on the objects local transform.

Share this post


Link to post
Share on other sites
[quote]All of the models were exported with the Z axis pointing up, while OpenGL by default has the Y axis pointing up.[/quote]
OpenGL does not specify a default up axis. It depends soley on your camera transform.

[quote]Is it up to the programming team to make the coordinate system match the 3D models, or is it on the art team to make sure that the 3D models come in the proper coordinate system? Additionally, which of the 2 possibilities is the recommended path to take?[/quote]

Both. The artists need to make sure they model things the correct way up, however the programmers should make sure that they can transform geometry. We are just talking about a 90 degree rotation around X here, so assuming you have a matrix transform for each mesh, it's not actually a problem. Mind you, writing a tool to rotate some vertices & normals in your files, is something that should only take you a couple of minutes.

[quote]I added the Y up functionality because Max +Z is up,[/quote]
Because the changing the up axis in the 3ds max properties is too hard?

[quote]Neither task sounds like fun (option 1 forces me to modify the way OpenGL works by default, which I take no pleasure in doing,[/quote]
Again, you can use any up axis you want. This is not a limitation of OpenGL.

[quote]option 2 forces me to use a program like Maya,[/quote]
No it doesn't. It means you need to use some trivial matrix maths. Using Maya/Max et al, is just over-complicating a trivial problem.

[quote]I'm just trying to get a sense of what is more commonplace in the game industry.[/quote]
Transformation matrices, and a consistant approach to working.

Share this post


Link to post
Share on other sites
[quote name='RobTheBloke' timestamp='1343385773' post='4963591']
[quote]option 2 forces me to use a program like Maya,[/quote]
No it doesn't. It means you need to use some trivial matrix maths. Using Maya/Max et al, is just over-complicating a trivial problem.
[/quote]
Exactly, I agree.

[quote]
OpenGL does not specify a default up axis. It depends soley on your camera transform.
[/quote]

Just some nit picking, but you can program OpenGL without any matrices or transforms at all, if you want. OpenGL no longer has a "camera transform" concept, and 'y' is up on the screen as default.

[quote name='Geometrian' timestamp='1343506211' post='4964080']
glRotated(90.0,1.0,0.0,0.0); or glRotated(-90.0,1.0,0.0,0.0)
[/quote]

This is deprecated OpenGL functionality, please don't recommend it. And if you would use it anyway, it is not recommended as it use double precision. That may cost a lot of performance. Edited by larspensjo

Share this post


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

  • Advertisement
  • Advertisement
  • Popular Now

  • Advertisement
  • Similar Content

    • By Balma Alparisi
      i got error 1282 in my code.
      sf::ContextSettings settings; settings.majorVersion = 4; settings.minorVersion = 5; settings.attributeFlags = settings.Core; sf::Window window; window.create(sf::VideoMode(1600, 900), "Texture Unit Rectangle", sf::Style::Close, settings); window.setActive(true); window.setVerticalSyncEnabled(true); glewInit(); GLuint shaderProgram = createShaderProgram("FX/Rectangle.vss", "FX/Rectangle.fss"); float vertex[] = { -0.5f,0.5f,0.0f, 0.0f,0.0f, -0.5f,-0.5f,0.0f, 0.0f,1.0f, 0.5f,0.5f,0.0f, 1.0f,0.0f, 0.5,-0.5f,0.0f, 1.0f,1.0f, }; GLuint indices[] = { 0,1,2, 1,2,3, }; GLuint vao; glGenVertexArrays(1, &vao); glBindVertexArray(vao); GLuint vbo; glGenBuffers(1, &vbo); glBindBuffer(GL_ARRAY_BUFFER, vbo); glBufferData(GL_ARRAY_BUFFER, sizeof(vertex), vertex, GL_STATIC_DRAW); GLuint ebo; glGenBuffers(1, &ebo); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, ebo); glBufferData(GL_ELEMENT_ARRAY_BUFFER, sizeof(indices), indices,GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, false, sizeof(float) * 5, (void*)0); glEnableVertexAttribArray(0); glVertexAttribPointer(1, 2, GL_FLOAT, false, sizeof(float) * 5, (void*)(sizeof(float) * 3)); glEnableVertexAttribArray(1); GLuint texture[2]; glGenTextures(2, texture); glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, texture[0]); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); sf::Image* imageOne = new sf::Image; bool isImageOneLoaded = imageOne->loadFromFile("Texture/container.jpg"); if (isImageOneLoaded) { glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, imageOne->getSize().x, imageOne->getSize().y, 0, GL_RGBA, GL_UNSIGNED_BYTE, imageOne->getPixelsPtr()); glGenerateMipmap(GL_TEXTURE_2D); } delete imageOne; glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, texture[1]); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); sf::Image* imageTwo = new sf::Image; bool isImageTwoLoaded = imageTwo->loadFromFile("Texture/awesomeface.png"); if (isImageTwoLoaded) { glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, imageTwo->getSize().x, imageTwo->getSize().y, 0, GL_RGBA, GL_UNSIGNED_BYTE, imageTwo->getPixelsPtr()); glGenerateMipmap(GL_TEXTURE_2D); } delete imageTwo; glUniform1i(glGetUniformLocation(shaderProgram, "inTextureOne"), 0); glUniform1i(glGetUniformLocation(shaderProgram, "inTextureTwo"), 1); GLenum error = glGetError(); std::cout << error << std::endl; sf::Event event; bool isRunning = true; while (isRunning) { while (window.pollEvent(event)) { if (event.type == event.Closed) { isRunning = false; } } glClear(GL_COLOR_BUFFER_BIT); if (isImageOneLoaded && isImageTwoLoaded) { glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, texture[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, texture[1]); glUseProgram(shaderProgram); } glBindVertexArray(vao); glDrawElements(GL_TRIANGLES, 6, GL_UNSIGNED_INT, nullptr); glBindVertexArray(0); window.display(); } glDeleteVertexArrays(1, &vao); glDeleteBuffers(1, &vbo); glDeleteBuffers(1, &ebo); glDeleteProgram(shaderProgram); glDeleteTextures(2,texture); return 0; } and this is the vertex shader
      #version 450 core layout(location=0) in vec3 inPos; layout(location=1) in vec2 inTexCoord; out vec2 TexCoord; void main() { gl_Position=vec4(inPos,1.0); TexCoord=inTexCoord; } and the fragment shader
      #version 450 core in vec2 TexCoord; uniform sampler2D inTextureOne; uniform sampler2D inTextureTwo; out vec4 FragmentColor; void main() { FragmentColor=mix(texture(inTextureOne,TexCoord),texture(inTextureTwo,TexCoord),0.2); } I was expecting awesomeface.png on top of container.jpg

    • 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?
  • Advertisement