tiny_engine

Info

Libraries Used:

• OpenGL by Khronos Group
• GLAD by David Herberth
• GLFW
• miniaudio by David Reid
• GLtext by Christian Vallentin
• imgui ImGui by Omar
• Assimp
• metadesk Metadesk by Dion Systems
• Bullet Bullet by BulletPhysics

Installing Dependencies

This project is currently built and maintained for windows. vcpkg is recommended for installing dependencies

Run vcpkg install in the root directory of this project (same directory as the vcpkg.json file)

Features/Included Implementations

• Postprocessing
• Job System (multithreading)
• deterministic randomness
• sprite rendering
• spritesheet parsing/animating
• .obj file parsing/mesh rendering
• particle system
• 2d and 3d vector shape drawing (squares, circles, lines, spheres, cubes)
• 3d model loading/rendering (w/material support)
• shadow mapping
• skybox
• Shader hot reloading & #include parser
• custom allocator(s)
• custom container types
• custom build system (backed by Ninja)
• compile-time reflection / type metadata generation system (backed by Metadesk)

Written with this engine:
Part Of The Pack

Simple nature scene I used to implement & test 3D features

QuadTree Implementation:

2023-02-06.00-28-41.mp4

Outline/Sketch Effect

Untitled.video.-.Made.with.Clipchamp.3.mp4

Simple physics

2024-02-02.02-02-49.mp4

Lethal Company inspired posterization effect:

2024-05-29.01-43-03.mp4

TODO:

• deferred renderer
  • proper deferred lights. Cluster? Light volumes(outdated....)?
• Now that we have a centralized renderer, passing in raw shaders to be draw into Model is a design bug
  • user-authored shaders need to be additive to the default shaders the engine uses. user shader code would be injected into prebuilt engine shaders this leads us to the question of a custom shading language for user shaders.... honestly tho that would be kinda overscoping. If that's really necessary in the future im super down, but I just am not at a scale where that kind of thing would be useful. I'd rather user shaders be something like normal glsl where they just provide a main function and we pass in all the inputs in a struct and call that user function
• Bloom
• PBR
  • proper brdf
  • proper hdri/skybox
  • irradience map (is this just a skybox?)
  • screen space reflections
• weird idea: splines through colorspace. Imagine using control points on a 2d color wheel visualization to define a palette
  • number of segments on the spline defines the steps in the palette
• "entities"/serialize objects...
  • Big refactor - move types to the type reflection system
  • rel pointers to make all entities one big blob?
• entity picking
• shader reflection (spriv-cross or sokol's sdhc?)
• Texel-perfect pixel art sampling/scene
  • https://colececil.io/blog/2017/scaling-pixel-art-without-destroying-it/
• ImGuizmo
• Resource system
  • load from filesystem
  • store things like Shader, Mesh, Model, etc
  • allow access to these things through ids
  • would let me "unify" my current subsystems.. each of these subsystems rn has it's own map would be neat to have those all under the same umbrella like d4's SNOs
• Scene graph/frustum culling
  • https://learnopengl.com/Guest-Articles/2021/Scene/Scene-Graph
  • https://learnopengl.com/Guest-Articles/2021/Scene/Frustum-Culling
• Space partitioning
  • OctTree (?)
  • BVH
    • raycasting
• animation
  • basic skeletal
  • IK
• get linux build on feature parity
• Event system
• Portals! (And utilizing that to make "non-euclidean" spaces)
• 3D World Wrapping (I.E. Manifold garden)
• (Visualizing) L-Systems

Personal Notes:

• OSX Retina Screen 1/4 render bug: http://disq.us/p/1osvm46: "For OSX retina device users, you may have to double the screen height and width when you create a framebuffer. Otherwise when you want to draw the screen using a framebuffer, some weird thing may occur (like I found only 1/4 of the previous content is rendered on the screen, which is the left corner). The reason of this might be that OSX uses 4 pixels to represent one under retina display. And GLFW aware of this problem while some other functions do not. So when you create a 800 x 600 window, it might actually be a 1600 x 1200 window..."

• MTL File Format: Ka: specifies ambient color values between 0 and 1 for the RGB components. Kd: specifies diffuse color Ks: specifies specular color Ke: emissive coefficient (rgb emission color) Ns: focus of specular highlights. normally range from 0 to 1000, with a high value resulting in a tight, concentrated highlight. Ni: defines the optical density (aka index of refraction) values can range from 0.001 to 10. A value of 1.0 means that light does not bend as it passes through an object. d: (dissolve) specifies alpha (0 = fully transparent, 1 = fully opaque)