tristandeborde / rt_vox Goto Github PK

At the moment, the compute shader uses ugly, ugly, hard-coded object data to perform the raycasting on. This issue aims at integrating StanEpp's buffering of scene data to GPU using OpenGL.

Checklist:

• Integrate StanEpp's SceneManager class
• Debug corrupted cube struct variable data

We need to write a shell/python script to automate download and installation of:

• glad
• glfw\
• glm
• set env_var to set opengl version major and minor in openGL.Class.hpp
• set version in glsl scripts

From now on, we only want to spawn Cube objects. This will allow us to delete min and max vars in Cube Object. To do this, we have to replace huge and thin box that is used as ground, with a huge cube

We want to add the Octree voxel-space structure to our code.
We need:

• Octree search function,
• include it into the raytracer's render function

We want the player to be able to reset all the cubes to their initial position in the scene.

Rendering was faulty.
The problem was located in the rt.comp shader => center (cube.transMat[3]) was not correctly taken into account.

We want the player to be able to create one object by sticking two cubes together. We are not using flexible joints for now.

Todo:

• Read this discussion on constraint and compound objects
• Implement FixedConstraint (i.e. keep the cubes and stick them) ?

The current SceneManager class makes no sense.
We need a proper abstraction to add cubes, in bullet physics, and in rendering pipeline.
To do:

• Rename the SceneManager class into RenderingManager, PhysicsEngine into PhysicsManager, and create SceneManager class
• Add AddCube class, calling methods from PhysicsManager & RenderingManager

The goal is to integrate Bullet to use its collision and gravity handling. In the next phases we will only keep the relevant functions (OBox-OBox collision, dynamics, etc.).
To check behaviour, we also need to add a shoot-cubes function, on space bar press.

Checklist:

• Add Bullet: single cube collisions
• shoot_cubes

We want to "rasterize each object into the big world texture continuously" 😨
We need:

• Create a v0 using dumb CPU intersection functions
• Implement a fancier GPU version from Nvidia's literature

We want each cube to be composed of a different material. This material will have an impact on rendering, and later on in development, on physics and gameplay.

We want to make our raytracer compute intersections with cubes instead of spheres.
We need:

• A cube class (there's a sphere class from the code we can inspire ourselves from)
• To modify the render function to compute intersections with cubes
• To correct the straight line artifact on the output image!

• Easy way is with AABB, since Octree's voxels are axis-aligned = https://www.scratchapixel.com/lessons/3d-basic-rendering/minimal-ray-tracer-rendering-simple-shapes/ray-box-intersection
• But for the physics and rasterization, the gamr voxels are OBB (not axis aligned) = http://www.opengl-tutorial.org/miscellaneous/clicking-on-objects/picking-with-custom-ray-obb-function/

Scratchapixel's raytracer writes the output to the disk. We want to display it in an OpenGL window.
Ideas:

• Adapt compute shader for CPP
• Debug weird colors output
• Resolve fisheye bug: no eyeray interpolation in shader
• Replace AABB cube check by oriented cube intersection check

In order to let the player know which plane he/she is "focused on", we need to light it up.
To do this, we need the GPU to have one material per face for display.
To do:

• In CPU, raycast starting only from the center pixel, and check with all boxes. Change this box's planes materials.
• Pass 6 materials in Object struct to GPU
• Modify return value of IntersectPlanes in GPU to get plane id in intersection, and choose material based on this plane id

Our raycaster doesn't compute light bounces ! We need to modify our compute shader to compute illumination etc. Source: https://github.com/StanEpp/OpenGL_Raytracing/blob/master/shader/cs.glsl

Todo:

• Integrate CalculateColor func (light bounces + reflections)
• Determine why no visual change

We need to rewrite the compute shader to properly use the transMat attribute of the Cube object.
For this, we have to:

• Replace min and max attributes in cube object, with halfSize attributes
• Use 4th vector of transMat as the cube's position

The current mouse and callbacks do not work in FPS-mode.

• Put focus on mouse cursor