• 11
• 14
• 12
• 10
• 11
• ### 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

• 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!

• Hello guys,

How do I know? Why does wavefront not show for me?
I already checked I have non errors yet.

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 !

# OpenGL orbit camera

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

## Recommended Posts

can you recommend to me a good orbit camera that i can include in a my project opengl 4?
may be based on the math library glt that i have already integrated?
thanks

##### Share on other sites

The math itself is relatively simple:

1.) Rotate the camera into the new orientation.

2.) Translate it in direction of the forward vector by the negated desired distance between camera and point of interest.

3.) Add the world position of the point of interest.

How to implement point 1., however, depends on how your camera control works.

##### Share on other sites

The math itself is relatively simple:

1.) Rotate the camera into the new orientation.

2.) Translate it in direction of the forward vector by the negated desired distance between camera and point of interest.

3.) Add the world position of the point of interest.

How to implement point 1., however, depends on how your camera control works.

only a question: why many people uses quaternion on point 1?

##### Share on other sites

only a question: why many people uses quaternion on point 1?

In principle there is no reason for this perhaps until knowing how the camera control is done. Performing a rotation is simpler when using a matrix. A quaternion may have advantages as intermediary during computing the rotation, especially is it fine if rotational interpolation is to be done. The technical reason then is that a quaternion with its 4 parameters is closer to the 3 parameters (what's needed for a rotation) compared to the 9 parameters of a matrix, so the additionally required constraints (count just 4-3=1 for quaternions, but 9-3=6 for matrices) are far easier to maintain for quaternions than for matrices.

However, as said, the preparation of point 1. depends heavily on how your camera control works. Maybe quaternions are advantageously there, maybe not.

##### Share on other sites

only a question: why many people uses quaternion on point 1?

In principle there is no reason for this perhaps until knowing how the camera control is done. Performing a rotation is simpler when using a matrix. A quaternion may have advantages as intermediary during computing the rotation, especially is it fine if rotational interpolation is to be done. The technical reason then is that a quaternion with its 4 parameters is closer to the 3 parameters (what's needed for a rotation) compared to the 9 parameters of a matrix, so the additionally required constraints (count just 4-3=1 for quaternions, but 9-3=6 for matrices) are far easier to maintain for quaternions than for matrices.

However, as said, the preparation of point 1. depends heavily on how your camera control works. Maybe quaternions are advantageously there, maybe not.

A question: with the mouse how i can obtain an angle of rotation for the pitch and the yaw?
I get a mouse position in x and y .
I would understand, not only copy from an example.

with atan2 i can get the angle , but 1 angle and what angle i use for pitch and for roll?

i use math library glm .
Thanks

Edited by giugio

##### Share on other sites

ok, this is my code:

void Camera::updateMouse(double x, double y)
{
glm::vec3 mouse_position = glm::vec3(x, y, 0.0);
if (m_mousePressed)
{
m_mousePosition = mouse_position;
m_mouseButton = false;    }
if (m_mouseButton){
glm::vec3 mouseDelta = mouse_position - m_mousePosition;
if (mouseDelta.length() < 0.1f)
{            return; // don't do tiny rotations.
}
float angle = glm::atan(mouseDelta.y, mouseDelta.x);
glm::degrees(angle);
if (angle < 0) angle += 360;
}


i obtain an angle , but what is the angle for yaw and what is the angle for roll ? I need two angles?

thanks

##### Share on other sites

i obtain an angle , but what is the angle for yaw and what is the angle for roll ?

When you calculate an angle that way, it is most obviously interpreted as rolling.

There are some ways to compute 2 angles from mouse movement, but all of them suffer in the one or other way. The very basic ways are these:

a) Use the delta in mouse movement along x axis, scale it by some factor, and add it as delta yaw. Do the same with the y direction and pitch. Here screen axes and rotation axes are related only logically. The rotations are relative because only deltas are used.

b) Think of a hemisphere centered on the screen, having a radius so that the circumference is close inside the screen borders. The point under the mouse and inside the projected circle of the hemisphere is then projected onto the hemisphere. This is then interpreted as spherical coordinates, hence giving you 2 angles. This method gives an orientation rather than a rotation. It returns one angle with [0,2pi] and the other with [0,pi/2] only (matching a hemisphere, of course), and suffers from inaccuracies when pointing close to the border of the projected circle. (Lookout for "turntable" implementations.)

##### Share on other sites

i obtain an angle , but what is the angle for yaw and what is the angle for roll ?

When you calculate an angle that way, it is most obviously interpreted as rolling.

There are some ways to compute 2 angles from mouse movement, but all of them suffer in the one or other way. The very basic ways are these:

a) Use the delta in mouse movement along x axis, scale it by some factor, and add it as delta yaw. Do the same with the y direction and pitch. Here screen axes and rotation axes are related only logically. The rotations are relative because only deltas are used.

b) Think of a hemisphere centered on the screen, having a radius so that the circumference is close inside the screen borders. The point under the mouse and inside the projected circle of the hemisphere is then projected onto the hemisphere. This is then interpreted as spherical coordinates, hence giving you 2 angles. This method gives an orientation rather than a rotation. It returns one angle with [0,2pi] and the other with [0,pi/2] only (matching a hemisphere, of course), and suffers from inaccuracies when pointing close to the border of the projected circle. (Lookout for "turntable" implementations.)

thanks

##### Share on other sites

i obtain an angle , but what is the angle for yaw and what is the angle for roll ?

When you calculate an angle that way, it is most obviously interpreted as rolling.

There are some ways to compute 2 angles from mouse movement, but all of them suffer in the one or other way. The very basic ways are these:

a) Use the delta in mouse movement along x axis, scale it by some factor, and add it as delta yaw. Do the same with the y direction and pitch. Here screen axes and rotation axes are related only logically. The rotations are relative because only deltas are used.

b) Think of a hemisphere centered on the screen, having a radius so that the circumference is close inside the screen borders. The point under the mouse and inside the projected circle of the hemisphere is then projected onto the hemisphere. This is then interpreted as spherical coordinates, hence giving you 2 angles. This method gives an orientation rather than a rotation. It returns one angle with [0,2pi] and the other with [0,pi/2] only (matching a hemisphere, of course), and suffers from inaccuracies when pointing close to the border of the projected circle. (Lookout for "turntable" implementations

only two questions :

1)the quaternion need only one angle for create a angular displacement , is correct? why now two angles?for the two quaternions that must be interpolated?

2)i see the squad and there is two quaternion and a variable t time? then i must get the time for each step ? and how i can convert the t to [0-1]

thanks and sorry for my ignorance

ps. and how i can transform the position of the mouse to the hypersfere? i must project? how? do you have a link on google.

thanks again

Edited by giugio

##### Share on other sites

I had some problem to decipher your post (no offending), so bear with me if I misunderstood what you meant ...

1)the quaternion need only one angle for create a angular displacement , is correct? why now two angles?for the two quaternions that must be interpolated?

A quaternion, in fact a unit-quaternion, is a kind of representation for rotations. As such it encodes an axis of rotation and an angle of rotation (and it has a constraint that its 2-norm is 1, else it would be a unit-quaternion and shearing would appear).

Interpolation means to calculate an in-between, having 2 supporting points (or key values) at the limits. Whether these 2 supporting points are spatially or temporally or whatever related plays no role for the interpolation. What "2 quaternions" do you want to interpolate? The control schemes described above do by themselves not have an urge to use quaternions. If you speak of a smooth transition of the current orientation to the next, then the one support point is the last recently used quaternion and the other is the newly determined (from mouse position / movement) one.

2)i see the squad and there is two quaternion and a variable t time? then i must get the time for each step ? and how i can convert the t to [0-1]

The 2 quaternions are the said support points, and the free variable (you used t, I will use k below) denotes where the in-between is located between the support points. You can compute an in-between only when you provide a value for k, yes. (But, as said, t need not be a time value.) How to determine a suitable k depends on what you want to achieve. For example, if you want N interpolation steps that are equally distributed within the allowed range [0,1], then you would use

kn := n / N   with   n = 0, 1, 2, …, N

where kn is the value for k at step n. Notice that n increments by 1 from 0 up to N, inclusively; this would be implemented as counting loop, of course. So you get

k0 = 0 / N = 0

kN = N / N = 1

as is required for the interpolation factor by definition.

If, on the other hand, you want the interpolation run over a duration T and started at moment in time t0 (measured by a continuously running clock), now at a measured moment t, then

k( t ) := ( t - t0 ) / T   with   t0 <= t <= t0+T

so that, as required by the interpolation factor definition,

k( t0 ) = ( t0 - t0 ) / T = 0

k( t0 + T ) = ( t0 + T - t0 ) / T = 1

As you can see in both examples above, the allowed range [0,1] is achieved by normalizing (division by N or T) and, in the case of the timed interpolation, by first shifting the real interval (subtraction of t0) so that it originates at 0; the latter part was not necessary in the first example because it already originates at 0.

and how i can transform the position of the mouse to the hypersfere? i must project? how? [...]

Well, a hemisphere (half of a full sphere) is luckily not a hypersphere (a sphere in more than 3 dimensions)!

Let's say the mouse position is the tuple (mx,my) and the screen size is given by (w,h) in the same co-ordinate system as (mx,my). Then the relative mouse position is

s := min( w, h ) * 0.5    << EDIT: must be halved to yield in a proper [-1,+1] normalization, hence the 0.5

x' := ( mx - w / 2 ) / s

y' := ( my - h / 2 ) / s

The position is within a circle as described in a previous post only if
x'2 + y'2 <= 1
otherwise the mouse is out of the range of our gizmo! If inside, then the tuple (x',y') denote a normalized position within the projected circle.

A point (x,y,z) on a hemisphere is described by spherical co-ordinates by
x := r * sin( theta ) * cos( phi )

y := r * sin( theta ) * sin( phi )

z := r * cos( theta )

Due to normalization we can ignore the radius because it is 1.

If we divide y by x we achieve

y / x = sin( phi ) / cos( phi ) = tan( phi )

and hence we can compute phi' for our relative mouse position (x',y') using the famous atan2 function as

phi' = atan2( y', x' )

For theta or z, resp., we have 2 ways. One of them is derived from the fact that each point on the unit sphere is 1 length unit away from its center. That means for use

x'2 + y'2 + z'2 == 1

so that for our z', considering that we use the "upper" hemisphere, have

z' = +sqrt( 1 - x'2 - y'2 )

This is valid due to our above formulated condition that the mouse position is within the circle.

Hence we can calculate

theta' = acos( z' )

Now we have 2 angles, phi' and theta'. What is left over is how to map that onto yaw and pitch, a question you need to answer.

Edited by haegarr