nanort icon indicating copy to clipboard operation
nanort copied to clipboard

NanoRT, single header only modern ray tracing kernel.

Results 10 nanort issues
Sort by recently updated
recently updated
newest added

Hi! Is it safe to define the #if0 MultiHitTraverse? I need all hit triangles in the ray interval. I found an old issue related to this, which was closed. https://github.com/lighttransport/nanort/issues/33...

Point query feature(find nearest hit surface point for a given point) is useful for physics(collision detection), distance fields(e.g. monte carlo geometry processing) and so on. Here is an example from...

enhancement

I looked at the readme and wiki, but I don't think the performance is really covered that much besides some mentions of "efficient ray intersection finding". Would it be possible...

The call here is different (I suspect old) in which the first two parameters are a min_t and max_t instead of local_t, so the call is invalid. Not sure what...

enhancement

The binning algorithm used in the current version of the library is not nearly as precise as it could be. Right now, it does evaluate the SAH by just cutting...

enhancement

I came across image correlation issue when running `bidir_path_tracer` example on Ryzen Threadripper 16 cores. ![correlation](https://user-images.githubusercontent.com/18676/35264765-4c0e1eb4-0061-11e8-89da-f65eb0935dfa.png) Also I found this correlation issue can be reproducable when setting `OMP_NUM_THREADS=16` on 4...

bug

Currently NanoRT does not utilize SIMD/AVX. Also no quantized BVH support. It'd be better to start to consider optimization and quantization. Fortunately, recent CPU architecture(AlderLake, ZEN4) supports native BF16/FP16 and...

enhancement

C++11 is now widely used(even in embedded devices and emerging architectures), so we are better to deprecate C++03.

C++11 is now widely used(even in HPC industries) and we are better to use C++11 thread instead of OpenMP threading.