Game development presentations - a useful reference
- Thread starter liolio
- Start date
High-Performance Graphics 2019 presentation slides.
https://www.highperformancegraphics.org/2019/program/
Some very interesting papers.
RTX Beyond Ray Tracing: Exploring the Use of Hardware Ray Tracing Cores for Tet-Mesh Point Location
Distortion-Free Displacement Mapping
and so on.
https://www.highperformancegraphics.org/2019/program/
Some very interesting papers.
RTX Beyond Ray Tracing: Exploring the Use of Hardware Ray Tracing Cores for Tet-Mesh Point Location
Distortion-Free Displacement Mapping
and so on.
Wavefront path tracing. Interesting algorithm that attempts to solve gpu occupancy issues in path tracing.
https://jacco.ompf2.com/2019/07/18/wavefront-path-tracing/
https://jacco.ompf2.com/2019/07/18/wavefront-path-tracing/
It can't ... rendering is a messy business. The only way to make it slim is with trash performance.
Pre-filter or go home.
http://advances.realtimerendering.com/s2019/index.htm
The program of advances in realtime rendering conference next monday the 29th july 2019
The program of advances in realtime rendering conference next monday the 29th july 2019
Last edited:
siggraph course: path tracing in production 2019
.. whoa. 'I know path tracing.'
Just huge amounts of information and ideas.
Wetas Manuka seems to shade first and shoot rays later, etc.
..
Oh this and few others were in here. (IE. Fresnel Equations Considered Harmful)
Graphics Programming weekly - Issue 95 — July 28, 2019
--
And Strand-based Hair Rendering in Frostbite slides are online.
http://advances.realtimerendering.com/s2019/index.htm
.. whoa. 'I know path tracing.'
Just huge amounts of information and ideas.
Wetas Manuka seems to shade first and shoot rays later, etc.
..
Oh this and few others were in here. (IE. Fresnel Equations Considered Harmful)
Graphics Programming weekly - Issue 95 — July 28, 2019
--
And Strand-based Hair Rendering in Frostbite slides are online.
http://advances.realtimerendering.com/s2019/index.htm
Last edited:
http://advances.realtimerendering.com/s2019/Mesh_shading_SIG2019.pptx
Mesh shading Nvidia presentation
Mesh shading Nvidia presentation
http://advances.realtimerendering.com/s2019/SIGGRAPH_GOW_WIND_day_of.pptx
God of of war wind presentation
God of of war wind presentation
Last edited:
They should beg for ray differentials while they are at it, so it can more usefully select them.@JoeJ the one presentation mentions wanting LOD in DXR!
http://advances.realtimerendering.c...ng Multiscattering BRDFs and Area Lights.pptx
Multiscattering BRDF and area lights
Multiscattering BRDF and area lights
Yeah, i'm surely not the only one requesting this. But how should it look like? I think it's mainly two related questions:@JoeJ the one presentation mentions wanting LOD in DXR!
1. Do we finally want / need continuous LOD?
I say yes. E.g. the image in one presentatio0n shows a edgy shadow of a distant round object with low tessellation.
As we approach more realism in lighting, the shadow will be soft and setting LOD just by distance (ignoring shadows or reflections) would be fine.
But a hard transition between fixed LODs would still cause popping, and with realistic lighting this could become visible in shadows, reflections and GI. Not sure how hard transitions affect denoising as well.
Further continuous LOD would help to distribute details to screen better. Actually we often see low details close up, but higher detail than necessary in the distance. Static level geometry often has no LOD at all.
2. Do we want compatibility with Mesh Shaders?
Curious if this question could be the motivation for NV to support LOD for RT quickly, but not sure if it makes so much sense.
If we need to store the geometry in main memory anyways to support RT, it might be better to just write our own geometry processing with compute, update in a time sliced manner and use it for both RT and rasterterization, without a need for mesh / tessellation shaders?
But the approach "mesh shading -> raster and generate BVH automatically" could make sens too. IDK.
I wonder how far we could get already now on current hardware.
What i want is to have static BVH, enlarging the bounds so any continuous or hard change of contained triangles is possible without recalculating BVH from scratch.
This would require a dynamic number of triangles per node, and the ability to disable BVH nodes at the bottom when decreasing LOD.
FF units for faster BVH generation would not be necessary.
Similar threads
