falcor | Graphistry forks of the FalcorJS family | Runtime Evironment library
kandi X-RAY | falcor Summary
kandi X-RAY | falcor Summary
Graphistry forks of the FalcorJS family of projects in a lerna-powered mono-repo.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- create cache with video videos
- walk the output and build an AST
- Merge a JSON node and return it .
- Match a path .
- Event handler for a material buffer
- Processes node .
- Runs the graph .
- Analyzes a call and adds it to the results array .
- Gets the JSON representation of a model
- De - dereferences the reference from ref to deref
falcor Key Features
falcor Examples and Code Snippets
Community Discussions
Trending Discussions on falcor
QUESTION
After watching videos and reading the documentation on DXR and DX12, I'm still not sure how to manage resources for DX12 raytracing (DXR).
There is quite a difference between rasterizing and raytracing in terms of resource management, the main difference being that rasterizing has a lot of temporal resources that can be bound on the fly, and raytracing being in need of all resources being ready to go at the time of casting rays. The reason is obvious, a ray can hit anything in the whole scene, so we need to have every shader, every texture, every heap ready and filled with data before we cast a single ray.
So far so good.
My first test was adding all resources to a single heap - based on some DXR tutorials. The problem with this approach arises with objects having the same shaders but different textures. I defined 1 shader root signature for my single hit group, which I had to prepare before raytracing. But when creating a root signature, we have to exactly tell which position in the heap corresponds to the SRV where the texture is located. Since there are many textures with different positions in the heap, I would need to create 1 root signature per object with different textures. This of course is not preferred, since based on documentation and common sense, we should keep the root signature amount as small as possible. Therefore, I discarded this test.
My second approach was creating a descriptor heap per object, which contained all local descriptors for this particular object (Textures, Constants etc..). The global resources = TLAS (Top Level Acceleration Structure), and the output and camera constant buffer were kept global in a separate heap. In this approach, I think I misunderstood the documentation by thinking I can add multiple heaps to a root signature. As I'm writing this post, I could not find a way of adding 2 separate heaps to a single root signature. If this is possible, I would love to know how, so any help is appreciated.
Here the code I'm usign for my root signature (using dx12 helpers):
...ANSWER
Answered 2021-Jan-20 at 10:23Dynamic indexing of HLSL 5.1 might be the solution to this issue.
https://docs.microsoft.com/en-us/windows/win32/direct3d12/dynamic-indexing-using-hlsl-5-1
- With dynamic indexing, we can create one heap containing all materials and use an index per object that will be used in the shader to take the correct material at run time
- Therefore, we do not need multiple heaps of the same type, since it's not possible anyway. Only 1 heap per heap type is allowed at the same time
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install falcor
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page