• Advertisement

• ### Popular Now

• 10
• 10
• 12
• 12
• 14
• Advertisement
• ### Similar Content

• By racarate
Hey everybody!
I am trying to replicate all these cool on-screen debug visuals I see in all the SIGGRAPH and GDC talks, but I really don't know where to start.  The only resource I know of is almost 16 years old:
http://number-none.com/product/Interactive Profiling, Part 1/index.html
Does anybody have a more up-to-date reference?  Do people use minimal UI libraries like Dear ImgGui?  Also, If I am profiling OpenGL ES 3.0 (which doesn't have timer queries) is there really anything I can do to measure performance GPU-wise?  Or should I just chart CPU-side frame time?  I feel like this is something people re-invent for every game there has gotta be a tutorial out there... right?

• By Achivai
Hey, I am semi-new to 3d-programming and I've hit a snag. I have one object, let's call it Object A. This object has a long int array of 3d xyz-positions stored in it's vbo as an instanced attribute. I am using these numbers to instance object A a couple of thousand times. So far so good.
Now I've hit a point where I want to remove one of these instances of object A while the game is running, but I'm not quite sure how to go about it. At first my thought was to update the instanced attribute of Object A and change the positions to some dummy number that I could catch in the vertex shader and then decide there whether to draw the instance of Object A or not, but I think that would be expensive to do while the game is running, considering that it might have to be done several times every frame in some cases.
I'm not sure how to proceed, anyone have any tips?
• 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
• Advertisement
• Advertisement

# OpenGL Bizzare Lightmap Problem

This topic is 3580 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. I've been working on a simple 3D engine the past few weeks using OpenGL and have started working on calculating dynamic lightmaps. I followed the code outlined in this tutorial. I've modified it to use multiple light sources, account for surface normals (called lambertian I think?). It also uses triangular faces for surfaces rather than quads. Everything in the calculation seems to be working fine, from what I can tell, but the lightmaps aren't being mapped correctly to their faces, they instead come out like in this image. That is using the following coordinates: p_fLightMapCoords[0].x = 0.f; p_fLightMapCoords[0].y = 0.f; p_fLightMapCoords[1].x = 0.f; p_fLightMapCoords[1].y = 1.f; p_fLightMapCoords[2].x = 1.f; p_fLightMapCoords[2].y = 0.f; It appears that each lightmap needs to be rotated within the triangles' vertices. But if I change the mapping coordinates to this: p_fLightMapCoords[2].x = 0.f; p_fLightMapCoords[2].y = 0.f; p_fLightMapCoords[0].x = 0.f; p_fLightMapCoords[0].y = 1.f; p_fLightMapCoords[1].x = 1.f; p_fLightMapCoords[1].y = 0.f; I get these results. It's as if it is now using a different section of the lightmap, which is absolute insane since I didn't actually change any of the coordinates, I just changed the order of them. I've tried building the data in the lightmap bitmap at a 90 degree angle, flipped horizontally, vertically and both, etc, but nothing gives the correct result. I find it extremely puzzling that the mapping info causes such a total change to the lightmap, when in theory it should be completely independent of it. Does anyone have any ideas? [Edited by - Biax on July 7, 2008 9:58:46 AM]

#### Share this post

##### Share on other sites
Advertisement
I seem to have fixed the problem by systematically trying all combinations of coordinates and flipping the image on the x axis. I still have no idea why I needed to do this, but as long as it works I won't complain.

There are a few little artifacts present in the map, however. These include things like visible seams, and lines of light along edges where there shouldn't be any. Take a look.

It's like the translation of positions to lightmap coordinates suffers a slight round off error or something that causes the lightmap to be shifted' slightly away from ideal. That's what it seems like to me at this point, anyway...

EDIT: Fixed this too, it's due to bi-linear filtering being turned on.

[Edited by - Biax on July 7, 2008 2:34:58 PM]

#### Share this post

##### Share on other sites
Can you post screenshots of the fixed seams ? From the last screenshot it doesnt like its just a bilinear filter issue, since that would mean just offset of half texel. The lightmap looks like its got much higher resolution.

Although if the resolution is the same as on the bottom quad, it might be the case. It just seems the left and right lightmaps have higher res than the bottom one.

#### Share this post

##### Share on other sites
Yeah, It would be helpful if you posted pics of the lightmap texture itself, not pics of the room.

#### Share this post

##### Share on other sites
actually, you need both since it might be a combination of filtering, wrong coords and possibly less/wrong texels

#### Share this post

##### Share on other sites
This looks very much like you have one lightmap per triangle, and that those walls made up of two triangles don't have their lightmaps aligned properly. It's easiest to fix this with good precision by using only one lightmap per plane, and stretch it over the area covering every triangle sharing that plane. Then let each triangle in the plane use the same lightmap texture, and give them the appropriate lightmap coordinates within the lightmap.
If you have large maps with small triangles sharing the same plane, and large distances between them, you might have to fix this by using more than one lightmap per plane. Perhaps you can use one lightmap for all triangles sharing a plane and touching each other or similar.
In this simple case it would be enough to have just one lightmap per wall, not one per triangle.

#### Share this post

##### Share on other sites

• Advertisement