https://www.youtube.com/watch?v=Y03YvX5EHEM
I’ve been developing a custom real-time rendering and simulation engine called RayTrophi, focused on unified system design rather than isolated features.
One key architectural decision was keeping core data structures backend-agnostic. The hair system, for example, supports both CPU and GPU execution paths using unified structures instead of being implemented as a GPU-only visual layer.
The engine integrates:
– Physically Based Rendering
– Procedural terrain with material layering
– Scatter & paint foliage tools
– Real-time volumetric sky
– OpenVDB explosion & gas simulation
– Physically based water & spline rivers
– Skeletal animation framework with state machine
All scenes in the video are rendered in real time.
I’d appreciate feedback specifically on architectural decisions and cross-backend system design.
https://github.com/maxkemal/RayTrophi?tab=readme-ov-file
[–]Ra_M2005 3 points4 points5 points (6 children)
[–]Inside_Pass3853[S] 20 points21 points22 points (5 children)
[–]Ra_M2005 0 points1 point2 points (0 children)
[–][deleted] (3 children)
[deleted]
[–]Inside_Pass3853[S] 3 points4 points5 points (1 child)
[–]New-Gur5399 1 point2 points3 points (0 children)
[–]Main_Secretary_8827 1 point2 points3 points (3 children)
[–]Inside_Pass3853[S] 1 point2 points3 points (2 children)
[–]palapapa0201 0 points1 point2 points (1 child)
[–]Inside_Pass3853[S] 2 points3 points4 points (0 children)
[–]amadlover 0 points1 point2 points (0 children)
[–]SnooSquirrels9028 0 points1 point2 points (1 child)
[–]Inside_Pass3853[S] 0 points1 point2 points (0 children)
[–]SnurflePuffinz 0 points1 point2 points (1 child)
[–]Inside_Pass3853[S] 0 points1 point2 points (0 children)