Skip to content
#

path-tracing

Here are 247 public repositories matching this topic...

ray-tracing-renderer
ToJans
ToJans commented Apr 20, 2020

Context

This engine is intended to be used as a drop-in replacement to Three.js’s WebGLRenderer.

Problem

It tends not to work as a drop-in replacement out-of-the-box, because the renderer crashes when:

  • Meshes contain a THREE.Geometry instead of a THREE.BufferGeometry.
  • It uses materials for which the texture images are not loaded yet.

This might cause people who try to repl

Nabla
devshgraphicsprogramming
devshgraphicsprogramming commented Nov 3, 2021

Description

Right now the MDI ranges are not compacted (having the drawcalls with 0 instances removed).

But the DrawIndirectAllocator and all the resources in on the C++ side are already setup for this

Solution proposal

An additional Dispatch (direct, cause you can have a list of MDIs up front) over the drawcalls that prefix sums their boolean instanceCount!=0u flag

Then another

enhancement good first issue

Improve this page

Add a description, image, and links to the path-tracing topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the path-tracing topic, visit your repo's landing page and select "manage topics."

Learn more