Search Issue Tracker
Fixed
Fixed in 6000.3.0b5, 6000.4.0a1
Votes
0
Found in
6000.0.54f1
6000.1.15f1
6000.2.1f1
6000.3.0a6
6000.4.0a1
Issue ID
UUM-115015
Regression
No
Changes in Output Inspector surface options do not mark the asset as dirty, and after undoing edits to Particle Options values the graph is marked as dirty
Steps to reproduce:
- Open the attached package
- Open VFX and if it is marked as dirty save it
- Select Output and in Output Inspector change Surface Type from Opaque to Transparent
- Observe that VFX is not marked as dirty
- Then tick Cast Shadows bool in Output Inspector > Particle Options dropdown
- Undo the change
- Observe that VFX is marked as dirty even if you've undone the change
Actual results:
- VFX isn't marked as dirty after material property changes in the Output Inspector.
- After a setting is changed in Output Inspector > Particle Options and then undone, the asset remains in a dirty state
Expected results:
- VFX is marked as dirty after material property changes in the Output Inspector.
- After a setting is changed in Output Inspector > Particle Options and then undone, the asset does not remain a dirty state
Reproducible with versions: 6.0, 6.1, 6.2, 6.3
Not reproducible with versions:
Can’t test with versions:
Tested on (OS): macOS
Notes:
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Add comment