Search Issue Tracker
Active
Under Consideration for 6000.4.X, 6000.5.X, 6000.6.X
Votes
0
Found in
6000.3.10f1
6000.4.0b8
6000.5.0a7
6000.6.0a1
Issue ID
UUM-135217
Regression
Yes
Generated Visual Effects Shader Graph code becomes corrupted when a HLSL node contains code with comments
How to reproduce:
1. Open the attached “IN-132659“ project
2. In the Project window, double click the “New VFX“ file
3. Compile the “New VFX“ Shader (New VFX window Toolbar > Compile)
4. In the Project window, expand the “New VFX“ file by clicking the pointer next to it
5. Open the “[New VFX] [Minimal] Update Particles“ file in any text editor
6. Observe the generated HLSL functions (CalculateDamage)
Actual result: The HLSL functions have corrupted parameters
Expected result: The HLSL functions have valid parameters
Reproducible with: 6000.3.0b6 (342471dcaf1d), 6000.3.10f1, 6000.4.0b8, 6000.5.0a7
Not reproducible with: 6000.3.0b5
Could not test with: 6000.0.68f1 (Could not find the “[New VFX] [Minimal] Update Particles“ file)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment