• Advertisement
  • Popular Tags

  • Popular Now

  • Advertisement
  • Similar Content

    • By fleissi
      Hey guys!

      I'm new here and I recently started developing my own rendering engine. It's open source, based on OpenGL/DirectX and C++.
      The full source code is hosted on github:
      https://github.com/fleissna/flyEngine

      I would appreciate if people with experience in game development / engine desgin could take a look at my source code. I'm looking for honest, constructive criticism on how to improve the engine.
      I'm currently writing my master's thesis in computer science and in the recent year I've gone through all the basics about graphics programming, learned DirectX and OpenGL, read some articles on Nvidia GPU Gems, read books and integrated some of this stuff step by step into the engine.

      I know about the basics, but I feel like there is some missing link that I didn't get yet to merge all those little pieces together.

      Features I have so far:
      - Dynamic shader generation based on material properties
      - Dynamic sorting of meshes to be renderd based on shader and material
      - Rendering large amounts of static meshes
      - Hierarchical culling (detail + view frustum)
      - Limited support for dynamic (i.e. moving) meshes
      - Normal, Parallax and Relief Mapping implementations
      - Wind animations based on vertex displacement
      - A very basic integration of the Bullet physics engine
      - Procedural Grass generation
      - Some post processing effects (Depth of Field, Light Volumes, Screen Space Reflections, God Rays)
      - Caching mechanisms for textures, shaders, materials and meshes

      Features I would like to have:
      - Global illumination methods
      - Scalable physics
      - Occlusion culling
      - A nice procedural terrain generator
      - Scripting
      - Level Editing
      - Sound system
      - Optimization techniques

      Books I have so far:
      - Real-Time Rendering Third Edition
      - 3D Game Programming with DirectX 11
      - Vulkan Cookbook (not started yet)

      I hope you guys can take a look at my source code and if you're really motivated, feel free to contribute :-)
      There are some videos on youtube that demonstrate some of the features:
      Procedural grass on the GPU
      Procedural Terrain Engine
      Quadtree detail and view frustum culling

      The long term goal is to turn this into a commercial game engine. I'm aware that this is a very ambitious goal, but I'm sure it's possible if you work hard for it.

      Bye,

      Phil
    • By tj8146
      I have attached my project in a .zip file if you wish to run it for yourself.
      I am making a simple 2d top-down game and I am trying to run my code to see if my window creation is working and to see if my timer is also working with it. Every time I run it though I get errors. And when I fix those errors, more come, then the same errors keep appearing. I end up just going round in circles.  Is there anyone who could help with this? 
       
      Errors when I build my code:
      1>Renderer.cpp 1>c:\users\documents\opengl\game\game\renderer.h(15): error C2039: 'string': is not a member of 'std' 1>c:\program files (x86)\windows kits\10\include\10.0.16299.0\ucrt\stddef.h(18): note: see declaration of 'std' 1>c:\users\documents\opengl\game\game\renderer.h(15): error C2061: syntax error: identifier 'string' 1>c:\users\documents\opengl\game\game\renderer.cpp(28): error C2511: 'bool Game::Rendering::initialize(int,int,bool,std::string)': overloaded member function not found in 'Game::Rendering' 1>c:\users\documents\opengl\game\game\renderer.h(9): note: see declaration of 'Game::Rendering' 1>c:\users\documents\opengl\game\game\renderer.cpp(35): error C2597: illegal reference to non-static member 'Game::Rendering::window' 1>c:\users\documents\opengl\game\game\renderer.cpp(36): error C2597: illegal reference to non-static member 'Game::Rendering::window' 1>c:\users\documents\opengl\game\game\renderer.cpp(43): error C2597: illegal reference to non-static member 'Game::Rendering::window' 1>Done building project "Game.vcxproj" -- FAILED. ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========  
       
      Renderer.cpp
      #include <GL/glew.h> #include <GLFW/glfw3.h> #include "Renderer.h" #include "Timer.h" #include <iostream> namespace Game { GLFWwindow* window; /* Initialize the library */ Rendering::Rendering() { mClock = new Clock; } Rendering::~Rendering() { shutdown(); } bool Rendering::initialize(uint width, uint height, bool fullscreen, std::string window_title) { if (!glfwInit()) { return -1; } /* Create a windowed mode window and its OpenGL context */ window = glfwCreateWindow(640, 480, "Hello World", NULL, NULL); if (!window) { glfwTerminate(); return -1; } /* Make the window's context current */ glfwMakeContextCurrent(window); glViewport(0, 0, (GLsizei)width, (GLsizei)height); glOrtho(0, (GLsizei)width, (GLsizei)height, 0, 1, -1); glMatrixMode(GL_PROJECTION); glLoadIdentity(); glfwSwapInterval(1); glEnable(GL_SMOOTH); glEnable(GL_DEPTH_TEST); glEnable(GL_BLEND); glDepthFunc(GL_LEQUAL); glHint(GL_PERSPECTIVE_CORRECTION_HINT, GL_NICEST); glEnable(GL_TEXTURE_2D); glLoadIdentity(); return true; } bool Rendering::render() { /* Loop until the user closes the window */ if (!glfwWindowShouldClose(window)) return false; /* Render here */ mClock->reset(); glfwPollEvents(); if (mClock->step()) { glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT); glfwSwapBuffers(window); mClock->update(); } return true; } void Rendering::shutdown() { glfwDestroyWindow(window); glfwTerminate(); } GLFWwindow* Rendering::getCurrentWindow() { return window; } } Renderer.h
      #pragma once namespace Game { class Clock; class Rendering { public: Rendering(); ~Rendering(); bool initialize(uint width, uint height, bool fullscreen, std::string window_title = "Rendering window"); void shutdown(); bool render(); GLFWwindow* getCurrentWindow(); private: GLFWwindow * window; Clock* mClock; }; } Timer.cpp
      #include <GL/glew.h> #include <GLFW/glfw3.h> #include <time.h> #include "Timer.h" namespace Game { Clock::Clock() : mTicksPerSecond(50), mSkipTics(1000 / mTicksPerSecond), mMaxFrameSkip(10), mLoops(0) { mLastTick = tick(); } Clock::~Clock() { } bool Clock::step() { if (tick() > mLastTick && mLoops < mMaxFrameSkip) return true; return false; } void Clock::reset() { mLoops = 0; } void Clock::update() { mLastTick += mSkipTics; mLoops++; } clock_t Clock::tick() { return clock(); } } TImer.h
      #pragma once #include "Common.h" namespace Game { class Clock { public: Clock(); ~Clock(); void update(); bool step(); void reset(); clock_t tick(); private: uint mTicksPerSecond; ufloat mSkipTics; uint mMaxFrameSkip; uint mLoops; uint mLastTick; }; } Common.h
      #pragma once #include <cstdio> #include <cstdlib> #include <ctime> #include <cstring> #include <cmath> #include <iostream> namespace Game { typedef unsigned char uchar; typedef unsigned short ushort; typedef unsigned int uint; typedef unsigned long ulong; typedef float ufloat; }  
      Game.zip
    • By lxjk
      Hi guys,
      There are many ways to do light culling in tile-based shading. I've been playing with this idea for a while, and just want to throw it out there.
      Because tile frustums are general small compared to light radius, I tried using cone test to reduce false positives introduced by commonly used sphere-frustum test.
      On top of that, I use distance to camera rather than depth for near/far test (aka. sliced by spheres).
      This method can be naturally extended to clustered light culling as well.
      The following image shows the general ideas

       
      Performance-wise I get around 15% improvement over sphere-frustum test. You can also see how a single light performs as the following: from left to right (1) standard rendering of a point light; then tiles passed the test of (2) sphere-frustum test; (3) cone test; (4) spherical-sliced cone test
       

       
      I put the details in my blog post (https://lxjk.github.io/2018/03/25/Improve-Tile-based-Light-Culling-with-Spherical-sliced-Cone.html), GLSL source code included!
       
      Eric
    • By Fadey Duh
      Good evening everyone!

      I was wondering if there is something equivalent of  GL_NV_blend_equation_advanced for AMD?
      Basically I'm trying to find more compatible version of it.

      Thank you!
    • By Jens Eckervogt
      Hello guys, 
       
      Please tell me! 
      How do I know? Why does wavefront not show for me?
      I already checked I have non errors yet.
      using OpenTK; using System.Collections.Generic; using System.IO; using System.Text; namespace Tutorial_08.net.sourceskyboxer { public class WaveFrontLoader { private static List<Vector3> inPositions; private static List<Vector2> inTexcoords; private static List<Vector3> inNormals; private static List<float> positions; private static List<float> texcoords; private static List<int> indices; public static RawModel LoadObjModel(string filename, Loader loader) { inPositions = new List<Vector3>(); inTexcoords = new List<Vector2>(); inNormals = new List<Vector3>(); positions = new List<float>(); texcoords = new List<float>(); indices = new List<int>(); int nextIdx = 0; using (var reader = new StreamReader(File.Open("Contents/" + filename + ".obj", FileMode.Open), Encoding.UTF8)) { string line = reader.ReadLine(); int i = reader.Read(); while (true) { string[] currentLine = line.Split(); if (currentLine[0] == "v") { Vector3 pos = new Vector3(float.Parse(currentLine[1]), float.Parse(currentLine[2]), float.Parse(currentLine[3])); inPositions.Add(pos); if (currentLine[1] == "t") { Vector2 tex = new Vector2(float.Parse(currentLine[1]), float.Parse(currentLine[2])); inTexcoords.Add(tex); } if (currentLine[1] == "n") { Vector3 nom = new Vector3(float.Parse(currentLine[1]), float.Parse(currentLine[2]), float.Parse(currentLine[3])); inNormals.Add(nom); } } if (currentLine[0] == "f") { Vector3 pos = inPositions[0]; positions.Add(pos.X); positions.Add(pos.Y); positions.Add(pos.Z); Vector2 tc = inTexcoords[0]; texcoords.Add(tc.X); texcoords.Add(tc.Y); indices.Add(nextIdx); ++nextIdx; } reader.Close(); return loader.loadToVAO(positions.ToArray(), texcoords.ToArray(), indices.ToArray()); } } } } } And It have tried other method but it can't show for me.  I am mad now. Because any OpenTK developers won't help me.
      Please help me how do I fix.

      And my download (mega.nz) should it is original but I tried no success...
      - Add blend source and png file here I have tried tried,.....  
       
      PS: Why is our community not active? I wait very longer. Stop to lie me!
      Thanks !
  • Advertisement
  • Advertisement
Sign in to follow this  

OpenGL Writing an OpenGL rendering backend for a left-handed DX11-engine

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

Hey,

 

I recently started studying OpenGL with the intention of adding an OpenGL 4.X rendering backend to my, currently DX11-only, engine. Before I started I want to get a better picture of what "DX is left-handed, OpenGL is right-handed" means in the modern APIs. To my understanding, modern OpenGL has done away with the LookAt() functions and similar functionality (that heavily depended on a certain handedness) in the same way as DX no longer has these things built in. I have built a very simple vector and matrix library that I use with DX11 and it assumes a left-handed coordinate system. I would like to use the same library with the OpenGL rendering backend. Where do I need to do any conversions? Does the modern OpenGL API still assume I am working with right-handed coordinates, or was that only in the old API?

 

Some things I do know (and correct me if I am wrong):

 

- My matrices are row-major and OpenGL wants them as column-major, so that's a transpose call.. (I am using the FX-framework for DX11 and I am going to get rid of that too. I actually think that DX11 wants them as column-major too but the FX-framework has done a transpose for me, so that might be one difference that will go away once I ditch the FX-framework?)

- The NDC z-axis goes from 0->1 in DX and -1->1 in OpenGL, so I have to take that into account, but that's just using a different projection matrix, right?

 

Anything else that needs to be done for this to work in OpenGL? For now, I am going to hand write all shaders as separate HLSL and GLSL versions, ie. no automatic translation or higher-level language. Is there something that needs to be reversed in the shader code with regards to the handedness of the coordinate space?

 

Cheers!

 

 

Share this post


Link to post
Share on other sites
Advertisement

My matrices are row-major and OpenGL wants them as column-major, so that's a transpose call

HLSL matrices are column-major by default. You have to write row_major float4x4 blah; to get a row-major one. GLSL is the same -- there's keywords to force one array storage order or the other, but by default it will choose column major storage order.
Note that row/column major array storage order and row/column major mathematics are two completely different things.
 
A mathamatician might look at a matrix on paper that looks like:
Xx Xy Xz Xw
Yx Yy Yz Yw
Zx Zy Zz Zw
Wx Wy Wz Ww

And tell you that the basis vectors are stored in the rows of the matrix, therefore it's using the row-major convention...
But a computer scientist will say that this matrix is row-major if it's stored in memory as [Xx Xy Xz Xw Yx Yy Yz Yw Zx Zy Zz Zw Wx Wy Wz Ww] and column-major if it's stored in memory as [Xx Yx Zx Wx Xy Yy Zy Wy Xz Yz Zz Wz Xw Yw Zw Ww] (while the on-paper representation is unchanged).
 
The column_major / row_major keywords in HLSL (and layout(column_major)layout(row_major) in GLSL) specify the computer science array ordering convention.
The mathematical convention is determined by whether you write mul( matrix, vector ) or mul( vector, matrix ).
 
In any case, there's no reason to do anything differently between GL and D3D here, both of them support both of the comp-sci-majorness conventions and both of the mathematical-majorness conventions, so you can/should use the same conventions everywhere.

The NDC z-axis goes from 0->1 in DX and -1->1 in OpenGL, so I have to take that into account, but that's just using a different projection matrix, right?

Correct - typically you'll construct your projection matrices differently for GL.

Alternatively you can use glClipControl to use D3D's conventions in GL.

Share this post


Link to post
Share on other sites

Before I started I want to get a better picture of what "DX is left-handed, OpenGL is right-handed" means in the modern APIs.


In the context of the modern versions of the APIs it means absolutely nothing since nothing in either API enforces either handedness on you.

 

The matrix library you use may enforce a handedness on you, but any good matrix library should be capable of supporting either.  So far as the API is concerned it's just a matrix * vector (or vector * matrix) operation and the mathematics are exactly the same irrespective.

 

However, by convention, OpenGL sample code may still assume a right-handed co-ordinate system whereas D3D sample code may still assume left-handed.  But this is just a convention based on historical usage.  So if you're using any sample code you will need to be aware of it's handedness, and unless explicitly stated otherwise you can use this convention as a rule of thumb to guess which handedness it uses.

Share this post


Link to post
Share on other sites
As others have said.

The things to watch out for that GL does differently than D3D are mostly just two things:

- the GL NDC has a depth range of -1..+1 rather than 0..+1, so you have to construct your projection matrices accordingly to get full precision. This one is easy to ignore but you shouldn't.

- GL has inverted texture coordinates from D3D, requiring textures to either be flipped when loaded or shaders to invert the access. This is the most obvious issue you run into when porting and the internet is filled with questions and answers about it.

Hypothetically there may be extensions to correct these issues, though there weren't the last time I subjected myself to OpenGL.

Share this post


Link to post
Share on other sites

GL_ARB_clip_control exists for NDC conventions.  It doesn't affect viewports, scissor rects, etc, however, so that is something you need to watch out for.  There is a rationale given for this in the extension spec, and I'm sure that the reasons were important to someone somewhere sometime, but IMO it's Not Good Enough.  Either do it fully and consistently across the whole API, or don't do it at all, whichever, but don't half-ass it so that sometimes we have to use one convention and sometimes the other.  Rant over.

 

For texture coords it's not actually that bad.  Because you also load textures from bottom-left in GL, the two bottom-lefts cancel each other out and you can use the same texture coords and image data in GL as in D3D, unmodified.  Where you may need to adjust is texture coords for render targets (or any other similar source).

Share this post


Link to post
Share on other sites

For texture coords it's not actually that bad.  Because you also load textures from bottom-left in GL, the two bottom-lefts cancel each other out and you can use the same texture coords and image data in GL as in D3D, unmodified.  Where you may need to adjust is texture coords for render targets (or any other similar source).

 

Hmm, I don't quite understand what you mean. What is the 'also' referring to in "Because you also..."?

 

If I have a texture loaded into D3D using the [0,0 == left,up] convention wont loading that texture into OpenGL make it appear upside down?

Share this post


Link to post
Share on other sites

OK, this might be complicated.
 
glTexImage2D (other texture specification calls work the same) specifies the following with respect to it's data pointer:

The first element corresponds to the lower left corner of the texture image. Subsequent elements progress left-to-right through the remaining texels in the lowest row of the texture image, and then in successively higher rows of the texture image. The final element corresponds to the upper right corner of the texture image.

 
So when you provide an array of data to glTexImage2D, data[0] is not actually the top-left of the texture image, it's the bottom-left of it.
 
So an image loaded through glTexImage2D will be upside-down by comparison to what you might expect.
 
However, OpenGL texture coords also work from bottom-left; i.e. {0,0} is the bottom-left corner of the texture.  So this effectively undoes the upside-down load and everything comes out the same.

 

w2dlrb.png
 
What this means in practical terms.
 
You need to change nothing in your engine when dealing with textures loaded from system memory pointers.  You give the same data to glTexImage2D as you would give to your D3D11_SUBRESOURCE_DATA::pSysMem pointer, you use the same texture coordinates when drawing, and everything just works.

Share this post


Link to post
Share on other sites

Thanks for the explanation :)

 

However, after reading your and Sean's post I have seen several posts on the internet about this particular issue and many suggestions on "how to solve it", eg. flip the image in memory before passing to OpenGL, flip it beforehand as part of the asset pipeline etc. If the texture coordinates are flipped too I don't see why people would be upset about it. Is there something I am missing here?

Share this post


Link to post
Share on other sites

Thanks for the explanation :)

 

However, after reading your and Sean's post I have seen several posts on the internet about this particular issue and many suggestions on "how to solve it", eg. flip the image in memory before passing to OpenGL, flip it beforehand as part of the asset pipeline etc. If the texture coordinates are flipped too I don't see why people would be upset about it. Is there something I am missing here?

 

You'll find that the people flipping the image are also flipping the texture coords.

 

In other words, they're looking at the two differences in isolation from each other rather than putting them together and realising that they cancel out.

Share this post


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

  • Advertisement