profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/nvpro-samples/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
NVIDIA DesignWorks Samples nvpro-samples Santa Clara, CA http://www.nvidia.com

nvpro-samples/vk_mini_path_tracer 661

A beginner-friendly Vulkan path tracing tutorial in under 300 lines of C++.

nvpro-samples/gl_occlusion_culling 348

OpenGL sample for shader-based occlusion culling

nvpro-samples/gl_ssao 245

optimized screen-space ambient occlusion, cache-aware hbao

nvpro-samples/gl_vk_chopper 190

Simple vulkan rendering example.

nvpro-samples/gl_vk_threaded_cadscene 144

OpenGL and Vulkan comparison on rendering a CAD scene using various techniques

nvpro-samples/gl_vk_meshlet_cadscene 140

This OpenGL/Vulkan sample illustrates the use of "mesh shaders" for rendering CAD models.

nvpro-samples/build_all 138

GO HERE FIRST: nvpro-samples overview

nvpro-samples/nvpro_core 138

shared source code and resources needed for the samples to run

nvpro-samples/gl_cadscene_rendertechniques 122

OpenGL sample on various rendering approaches for typical CAD scenes

startednvpro-samples/vk_mini_path_tracer

started time in 14 hours

startednvpro-samples/vk_raytrace

started time in 2 days

startednvpro-samples/gl_vk_simple_interop

started time in 2 days

startednvpro-samples/vk_raytrace

started time in 2 days

startednvpro-samples/vk_raytrace

started time in 2 days

startednvpro-samples/gl_ssao

started time in 2 days

startednvpro-samples/vk_mini_path_tracer

started time in 3 days

startednvpro-samples/vk_raytrace

started time in 3 days

startednvpro-samples/gl_occlusion_culling

started time in 3 days

startednvpro-samples/vk_raytrace

started time in 4 days

fork oceanusxiv/vk_mini_path_tracer

A beginner-friendly Vulkan path tracing tutorial in under 300 lines of C++.

fork in 4 days

startednvpro-samples/optix_advanced_samples

started time in 4 days

startednvpro-samples/vk_raytracing_tutorial_KHR

started time in 5 days

startednvpro-samples/nvpro_core

started time in 5 days

startednvpro-samples/vk_raytrace

started time in 6 days

startednvpro-samples/vk_raytracing_tutorial_KHR

started time in 6 days

startednvpro-samples/nvpro_core

started time in 6 days

startednvpro-samples/vk_mini_path_tracer

started time in 6 days

startednvpro-samples/gl_vk_simple_interop

started time in 6 days

startednvpro-samples/vk_raytracing_tutorial_KHR

started time in 6 days

pull request commentnvpro-samples/vk_raytrace

Device adaptation

The latest version has code to run on devices which don't support Ray Query.

BobLChen

comment created time in 6 days

PR closed nvpro-samples/vk_raytrace

Device adaptation

VK_KHR_RAY_QUERY_EXTENSION_NAME not support on TITAN,keep VK_KHR_RAY_TRACING_PIPELINE_EXTENSION_NAME available.

Signed-off-by: chenbo02 chenbo02@cn.net.ntes

+42 -5

1 comment

1 changed file

BobLChen

pr closed time in 6 days

startednvpro-samples/vk_raytrace

started time in 6 days

startednvpro-samples/vk_raytrace

started time in 6 days

issue commentnvpro-samples/vk_raytrace

bugs in pathtrace.glsl

The punctual lights was a quick addition, but this commit 4b0e78d should hopefully fix it. If eventually there are area lights with glTF, the code should be adapted.

bacTlink

comment created time in 6 days

issue closednvpro-samples/vk_raytrace

bugs in pathtrace.glsl

I notice some problems in pathtrace.glsl. I am sorry I have no time to fix them myself. If these problems exist, I hope this issue post can help you out.

  1. The shadow rays of point light sources are not handled correctly. The maximum distance of the shadow rays should not be 1e32 for them.
  2. The environment map evaluation in PathTrace() does not have MIS weight.
  3. The direct light contribution is accumulated after RR. So if RR is activated, the direct light of the last bounce may not be added.

closed time in 6 days

bacTlink

push eventnvpro-samples/vk_raytrace

mklefrancois

commit sha e4462c10f2e05e410763c5ece712f1518d3c9ab7

New scenes

view details

mklefrancois

commit sha c8d3299737ad8eb523229508a7dcfa0b1347b644

Move to src, using host_device.h for shared structs, optional ray query

view details

mklefrancois

commit sha 4b0e78d7fe1c0b59f705ad36857d2ac7b590945c

Simplify access of data

view details

mklefrancois

commit sha 40a6bb06fbadca968c349f4f830847c86b5b1cf9

Use light distance, fix Russian Roulette and some other things

view details

push time in 6 days

issue closednvpro-samples/nvpro_core

context_vk.cpp::vkCreateDevice takes 328 milliseconds on Ubuntu 20.04

https://github.com/nvpro-samples/shared_sources/blob/520a374b290b53acdc8cd7953e54b15fd26278a3/nvvk/context_vk.cpp#L485

Because of this, all example programs which use nvvk have a noticeable lag each time you run them. For comparison, all OpenGL programs start instantly because no init calls take this much time there, I thought Vulkan is supposed to be faster than OpenGL, not slower? :P

closed time in 7 days

procedural

issue commentnvpro-samples/nvpro_core

context_vk.cpp::vkCreateDevice takes 328 milliseconds on Ubuntu 20.04

This is not an issue with nvvk, but I rather an issue with the driver and the version of Ubuntu. Many are using Ubuntu and have not reported this issue. Please try with a more recent driver.

procedural

comment created time in 7 days

issue closednvpro-samples/nvpro_core

M_PI problem in imgui

In the header in imgui, M_PI is defined as 3.14159862f, which is different from common a definition 3.14159265. Is this an intentional design for some special reasons?

closed time in 7 days

bacTlink