Simple raytracing engine implementing a customizable node-based shader description allowing scenes to be represented as JSON data (school project)
Renders tend to just be too long. possible paths: - multithreading: render vertical slices of the image on different threads - seeking optimizations for object intersection (possible noticeable gain on triangles?) - Implementing some kind of K-d tree structure (may be time consuming and out of scope)
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by thetos7 and has received 0 comments.