Optix sdk8 sample optixMeshViewer NOT displaying color

Gaming and Visualization Technologies Visualization OptiX
1

image
image766×800 11.6 KB

but it should be
image
image732×836 31.7 KB

since
image
image869×555 24.8 KB

Processing glTF buffer ‘’
byte size: 149412
uri : WaterBottle.bin
Processing image ‘’
(2048x2048)x4
bits: 8
Processing image ‘’
(2048x2048)x4
bits: 8
Processing image ‘’
(2048x2048)x4
bits: 8
Processing image ‘’
(2048x2048)x4
bits: 8
Processing glTF material: ‘BottleMat’
Using default base color factor
Using default roughness factor
Using default metallic factor
Emissive factor: (1, 1, 1)
Processing glTF mesh: ‘WaterBottle’
Num mesh primitive groups: 1
Num triangles: 4510
Has vertex normals: true
Has texcoords_0: true
Has texcoords_1: false
Has color_0: false
[ 4][ KNOBS]: All knobs on default.

[ 4][ DISKCACHE]: Opened database: “C:\Users\Vector\AppData\Local\NVIDIA\OptixCache\optix7cache.db”
[ 4][ DISKCACHE]: Cache data size: “64.4 MiB”
[ 4][ DISKCACHE]: Cache hit for key: ptx-1192580-key378d8dd83e6f89ff98f40609dabb8670-sm_120-rtc1-drv591.74

[ 4][ COMPILER]:
[ 4][ DISKCACHE]: Cache hit for key: ptx-93-key5e6b7855ad4e2f451283a053187b4e5e-sm_120-rtc1-drv591.74

[ 4][ COMPILER]:
[ 4][ COMPILER]: Info: Pipeline statistics
module(s) : 1
entry function(s) : 6
trace call(s) : 3
continuation callable call(s) : 0
direct callable call(s) : 0
basic block(s) in entry functions : 1049
instruction(s) in entry functions : 68123
non-entry function(s) : 38
basic block(s) in non-entry functions: 84
instruction(s) in non-entry functions: 947
debug information : yes

Returning default camera

2

The “debug information: yes” and the slow performance indicates you’re running this in debug mode. Does the same also happen in release mode? (Same question with the optixHair example in your other post.)

Do you start this from within the Visual Studio debugger or on the command line?

What is your exact system configuration? Your filenames indicate Windows OS with an sm_120 GPU on 591.74, but what version and GPU?

Also that driver version supports the newer OptiX 9.x SDK versions. Could you try that as well? (You can install all OptiX SDK versions side-by-side.)

3

Release mode worked fine for Optix 8.0.0.
Both Debug and Release work fine with Optix 9.1.0.

4

OK, I wonder if that was a PTX vs. OptiX-IR compiler issue in debug mode.

The OptiX cache filienames in your initial post started with “ptx”. It would be interesting to check if the examples actually translated the device code to PTX or OptiX-IR in either case.

PTX doesn’t retain the same debug information as OptiX-IR, so latter is the recommended target for everything.

In any case, this might also be related to the CUDA Toolkit version you used, so that is another system configuration information required to analyze this when necessary.

5 
deviceQuery.exe Starting...

 CUDA Device Query (Runtime API) version (CUDART static linking)

Detected 1 CUDA Capable device(s)

Device 0: "NVIDIA GeForce RTX 5060"
  CUDA Driver Version / Runtime Version          13.1 / 12.9
  CUDA Capability Major/Minor version number:    12.0
  Total amount of global memory:                 8151 MBytes (8546484224 bytes)
  (030) Multiprocessors, (128) CUDA Cores/MP:    3840 CUDA Cores
  GPU Max Clock rate:                            2527 MHz (2.53 GHz)
  Memory Clock rate:                             14001 Mhz
  Memory Bus Width:                              128-bit
  L2 Cache Size:                                 25165824 bytes
  Maximum Texture Dimension Size (x,y,z)         1D=(131072), 2D=(131072, 65536), 3D=(16384, 16384, 16384)
  Maximum Layered 1D Texture Size, (num) layers  1D=(32768), 2048 layers
  Maximum Layered 2D Texture Size, (num) layers  2D=(32768, 32768), 2048 layers
  Total amount of constant memory:               65536 bytes
  Total amount of shared memory per block:       49152 bytes
  Total shared memory per multiprocessor:        102400 bytes
  Total number of registers available per block: 65536
  Warp size:                                     32
  Maximum number of threads per multiprocessor:  1536
  Maximum number of threads per block:           1024
  Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
  Max dimension size of a grid size    (x,y,z): (2147483647, 65535, 65535)
  Maximum memory pitch:                          2147483647 bytes
  Texture alignment:                             512 bytes
  Concurrent copy and kernel execution:          Yes with 1 copy engine(s)
  Run time limit on kernels:                     Yes
  Integrated GPU sharing Host Memory:            No
  Support host page-locked memory mapping:       Yes
  Alignment requirement for Surfaces:            Yes
  Device has ECC support:                        Disabled
  CUDA Device Driver Mode (TCC or WDDM):         WDDM (Windows Display Driver Model)
  Device supports Unified Addressing (UVA):      Yes
  Device supports Managed Memory:                Yes
  Device supports Compute Preemption:            Yes
  Supports Cooperative Kernel Launch:            Yes
  Supports MultiDevice Co-op Kernel Launch:      No
  Device PCI Domain ID / Bus ID / location ID:   0 / 8 / 0
  Compute Mode:
     < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 13.1, CUDA Runtime Version = 12.9, NumDevs = 1
Result = PASS