Papers › Proceduray -- A light-weight engine for procedural primitive ray tracing
Proceduray -- A light-weight engine for procedural primitive ray tracing
Vinícius da Silva, Tiago Novello, Hélio Lopes, Luiz Velho
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
We introduce Proceduray, an engine for real-time ray tracing of procedural geometry. Its motivation is the current lack of mid-level abstraction tools for scenes with primitives involving intersection shaders. Those scenes impose strict engine design choices since they need flexibility in the shader table setup. Proceduray aims at providing a fair tradeoff between that flexibility and productivity. It also aims to be didactic. Shader table behavior can be confusing because parameters for indexing come from different parts of a system, involving both host and device code. This is different in essence from ray tracing triangle meshes (which must use a built-in intersection shader for all objects) or rendering with the traditional graphics or compute pipelines. Additionals goals of the project include fomenting deeper discussions about DirectX RayTracing (DXR) host code and providing a good starting point for developers trying to deal with procedural geometry using DXR.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections