• 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 Turning to Computer Graphics again, after years of abstinence - Where to go, what to read?

Recommended Posts

Howdy.

I have done some 3D graphics programming many years ago, some simple software rendering stuff and then Fixed Function OpenGL. I have not written one shader program.
I'm interested to get into that subject again, learning how things are done today.
It's not fixed that it has to be OpenGL (or Vulkan?) - I heard D3D has become a nice API, OO and all. OTOH, I guess it's still true that OpenGL/Vulkan opens doors to more platforms, which is a could-be-nice thing, but the main thing will remain desktop, and if D3D is so much nicer of an API, also debugging wise (?) ...
But *if* I were to go the "open software" route - is OpenGL a dead end now, because of Vulkan? I'm not sure I'd like to "do everything myself" as is said about vulkan, with pages of boilerplate for everything. Let's face it, I won't create the next Cry engine, I probably won't need extreme control of everything. As it's spare time stuff, one of the most important aspects here is not spending too much time for not very good reason (cost / benefit). But investing time into a dead end would be bad.
 

Sorry for seeming / being a bit confused here, I have not yet made up my mind about some things, apparently ;-)

So, what kind of resources do you suggest I consume on those subjects?
Is there some "best book", or really good online resources - something allowing me to start from zero again, and get some results?
 

As an aside: Are there concepts, functions in old OpenGL which are still valid today? Next to my job of quite some years as a degree-less developer, I am also working on actually getting a BSc degree*.
They offer a computer graphics course which uses really old OpenGL (< 2.0), ok it gets credit points, but otherwise probably a waste of time?
 

* (it does matter, at least here in Germany. For those wondering: Their program allows me to do only some cources in a semester, spreading the whole thing over more years... but less work load next do day job)

Regards,
- unshaven

Share this post


Link to post
Share on other sites
Advertisement
t's not fixed that it has to be OpenGL (or Vulkan?) - I heard D3D has become a nice API, OO and all. OTOH, I guess it's still true that OpenGL/Vulkan opens doors to more platforms, which is a could-be-nice thing, but the main thing will remain desktop, and if D3D is so much nicer of an API, also debugging wise (?) ...

IMO the available tools in D3D/Windows are preferable to what's available for OpenGL or Vulkan right now. But stuff like RenderDoc means you're certainly not out in the cold with GL.

But *if* I were to go the "open software" route - is OpenGL a dead end now, because of Vulkan? I'm not sure I'd like to "do everything myself" as is said about vulkan, with pages of boilerplate for everything. Let's face it, I won't create the next Cry engine, I probably won't need extreme control of everything. As it's spare time stuff, one of the most important aspects here is not spending too much time for not very good reason (cost / benefit). But investing time into a dead end would be bad.

GL is definitely not a dead end, and I would not recommend Vulkan or D3D 12 as the way to get back into things from effectively zero current knowledge. That would be a pretty long road to take and there's a lot of code out there right now built on the "old" stuff.

So, what kind of resources do you suggest I consume on those subjects? Is there some "best book", or really good online resources - something allowing me to start from zero again, and get some results?

Hopefully someone else has some good info here, as I'm a bit disconnected from that. Choosing an API will help narrow down resources.

As an aside: Are there concepts, functions in old OpenGL which are still valid today? Next to my job of quite some years as a degree-less developer, I am also working on actually getting a BSc degree*. They offer a computer graphics course which uses really old OpenGL (< 2.0), ok it gets credit points, but otherwise probably a waste of time?

Probably a waste of time. I mean... there are a couple relevant functions. Textures still upload pretty much the same, and handful of render states that are still relevant (blend modes, depth, stencil) work mostly the same. That's about it. You can use some of the other old stuff, but you shouldn't.

Edited by Promit

Share this post


Link to post
Share on other sites

Vulkan isn't as crossplatform as you'd think since apple isn't supporting it.  As far as opengl being a deadend, I don't think so.  First of all the modern low level api's (d3d12 and vulkan) weren't meant to replace the older api's they were meant to exist side by side with them.  Second, extensions are still being released for opengl making its performance on par with vulkan.  For example bindless extensions and command lists ( http://on-demand.gputechconf.com/siggraph/2015/presentation/SIG1512-Tristan-Lorach.pdf ).  I am not sure about debug tools.  If you choose the DX route I'd suggest you start with D3D11.  I don't know much about opengl so I can't give any opinion other than ver 4.4.and 4.5 seem on par with D3D11.

Share this post


Link to post
Share on other sites

Ah, I see. Thanks for the pointers so far. RenderDoc looks like something I'd really would have loved to have when I was using OpenGL 13 years ago or so :-D

As for "not as cross platform as I think". Well, to be frank, although it's a big market, I'm kind of "meh" about the whole Apple thing. You know, those people, with their, what I call "developer harassment program", thinking they can make you jump through all sorts of hoops all the time to be granted the privilege to (continue to) take part in their oh so magnificent platform, well I feel like I kinda rather take a pass on that. I've been through a good taste of it at work. Luckily, there is no economic pressure for me to succumb to their BS, nor buy their ivory coated products (they got to be, right?) /rant

Share this post


Link to post
Share on other sites

If you already did OpenGL, then why not continue with OpenGL. Just create an 'oldy' context and use extensions, and remove deprecated calls progressively.

The easiest thing to my opinion: start with an old OpenGL 1.x program (even with glut, or quickly learn glfw), then start to learn shaders (you just need a couple of extensions for that).

Once you're good with it, then move forward. To avoid harmful things, don't do any glBegin, glColor... things at all. Start with vertex pointers and glDrawArrays.

Share this post


Link to post
Share on other sites

 

I would not recommend Vulkan or D3D 12 as the way to get back into things from effectively zero current knowledge.

I would. I've just started digging into Graphics Programming since new year, and I'm doing pretty good so far. I've implemented a fully working ray tracer & am now working on implementing a realtime path tracer.

The tutorials out there are still very few, but mostly, the ones there are, are quite good. Apart from that, Vulkan is basically really simple. (can't tell you something about dx12 unfortunately) it's just very explicit. That is, you will have to specify alot, the specification however describes most of the stuff pretty good.
I can also recommend the Vulkan Programming Guide, it's not a good book, but rather another reference with some more explanation.
Sascha Willems also has a huge, open git repository with all kind of Vulkan Samples.

 

Vulkan isn't as crossplatform as you'd think since apple isn't supporting it.

That's only partly true. You can not develope with Vulkan on OS X, but you can ship Vulkan builds to OS X.

Edited by Life Is Good

Share this post


Link to post
Share on other sites

That's only partly true. You can not develope with Vulkan on OS X, but you can ship Vulkan builds to OS X.
wat

Vulkan isnt there in OSX. Neither for developing nor for running. 

Share this post


Link to post
Share on other sites

D3D11 is a brilliant API. It's been slimmed down and had all the cruft removed from it (unlike GL where there's multiple ways to accomplish a task, and endless deprecated functions), driver stability is rock solid, and the dev tools are good. Part of the momentum behind it is that the vast majority of Windows games use it, which keeps the focus on D3D drivers over GL... When google wanted to support OpenGL|ES on PC (which doesn't exist), they chose to implement it on top of D3D11 rather than on top of OpenGL, which is really saying something...
D3D11's approach to varying hardware via "feature levels" is also a hell of a lot easier to use than GL's fragmented extension mechanism. It also has a great validation layer that you can enable, which tells you about invalid API usage during development and lets you catch any problems in your code (D3D12/Vulkan also have this feature, but OpenGL doesn't quite). I would definitely recommend it as a starting point for anyone wanting to get into graphics programming.

I would not recommend Vulkan or D3D 12 as the way to get back into things from effectively zero current knowledge.

I would. I've just started digging into Graphics Programming since new year, and I'm doing pretty good so far. I've implemented a fully working ray tracer & am now working on implementing a realtime path tracer.
The tutorials out there are still very few, but mostly, the ones there are, are quite good. Apart from that, Vulkan is basically really simple. (can't tell you something about dx12 unfortunately) it's just very explicit. That is, you will have to specify alot, the specification however describes most of the stuff pretty good.

The main reason why D3D12/Vulkan aren't great for non-experts (and D3D11/OpenGL are better) is that Vulkan/D12 don't at all abstract away the fact that the GPU and CPU are running asynchronously. In other words, the user is given the burden of writing "thread safe" code that manually synchronizes ownership and access of memory buffers between those two co-processors.
D3D11/GL do abstract away this detail, so it's really hard to create any kind of "thread safety" bugs.
Parallel programming across multiple processors, without the use of any kind of high level framework or language (just raw, low level, manual, shared memory programming) is one of the most error prone tasks for any programmer, and worse, errors often aren't noticable as incorrect synchronisation code often just happens to work by chance, most of the time :(

One of the main areas where this matters is in sending dynamic shader parameters to your draw calls. In D3D11 you just update a constant buffer, draw something, update the constant buffer and draw something else -- the API makes it look like the draw calls are occurring on the CPU timeline and there's no problem updating a resource like this. OpenGL can be even simpler of setting a particular uniform variable, drawing something, setting that variable again, and drawing something else.
On the other hand in D3D12/Vulkan, once you issue a draw-call that will use a particular resource (e.g. a constant buffer), you cannot modify that resource at all until the draw-call has completed (otherwise you have a race condition)... so you have to implement your own ring-buffers, etc, to manage the memory allocations for these dynamic data blocks. Worse still, the validation layers for D3D12/Vulkan will not catch these kinds race condition bugs and tell you that your code is wrong, so you're on your own in proving the correctness.

Besides that, Vulkan/D12 expose many other areas of "undefined behaviour" where slightly incorrect code may seem to work, yet in the future could have disastrous consequences :(
If you want to get up to speed on GPU programming, D3D11/OpenGL let you focus on how GPU programming APIs work, without having to face these extra burdens :) That said, sure, there's something to be said for diving straight into D3D12/Vulkan and dealing with the harsh reality of CPU<->GPU communication right from the start!

Edited by Hodgman

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  

  • Advertisement