Search Issue Tracker
Fixed
Fixed in 6000.0.27f1, 6000.1.0a4, 7000.0.0a12
Votes
2
Found in
6000.0.0f1
6000.1.0a3
7000.0.0a1
Issue ID
UUM-85733
Regression
No
[RayTracing] Impossible to identify individual instances added using RTAS.AddInstances in a compute shader when using ray queries.
Steps to reproduce:
1. Use a system that supports ray tracing (e.g. Windows 10/11 + RTX GPU).
2. Open the project attached and open ComputeShaderRayQuery scene, switch to Game View.
3. Notice the tall objects in the background using the same light green color which is read in ComputeShaderRayQuery.compute at this line:
{code:java}
outColor.xyz = g_InstanceColors[q.CommittedInstanceID()];{code}
Actual results: All instances added using RTAS.AddInstances have the same color and CommittedInstanceID() HLSL function returns the same value for all instances.
Expected results: Instances added using RTAS.AddInstances have different colors.
Reproducible with versions: 6000.0.23f1
Not reproducible with versions: N/A
Tested on (OS): Windows 11, NVIDIA RTX 4070 Ti SUPER GPU.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 6000.1.0a4):
Fix verified in:
Unity 6.1 Alpha
6000.1.0a4.539
Revision: trunk d15fb92ae383
Built: Sat, 02 Nov 2024 07:49:59 GMT
Resolution Note (fix version 6000.0.27f1):
Fix verified in:
Unity 6
6000.0.29f1.9111
Revision: 6000.0/staging 824cb2369e36
Built: Fri, 15 Nov 2024 19:19:34 GMT