Search Issue Tracker
Fixed in 7.1.7
Votes
1
Found in [Package]
6.7.1 - preview
Issue ID
1163125
Regression
No
[HDRP] The Game Object is invisible in the Scene and Shader Graph prieview when the Transform node set World to Object position
How to reproduce:
1. Open the attached 'HDRPBrokenThings.zip' project
2. Open and observe 'WorldToObjectSpaceTest' Shader Graph
3. Create a Cube
4. Assign 'WorldToObjectTest' material to Cube
5. Observe Cube
Expected result: Cube stays at the same place
Actual result: Cube is invisible
Concern: Directly changing the behavior of "World" transform space may break the projects of people who have already implemented a workaround for this bug. Possibly add a new transform space that works as expected (if one doesn't exist)
Reproducible: 2018.4.2f1, 2019.1.7f1, 2019.2.0b6, 2019.3.0a6
Can't reproduce:
- 2017.4, because HDRP was not introduced
- 2018.3.0a1, because of Fatal error when creating HDRP project
Comments (1)
-
fherbst
Jun 18, 2019 19:38
The actual issue is a wrong naming - "World Space" is now "Camera Relative Space" and Transform Node should probably get that as an additional option. Right now it's very confusing that some nodes that say "world space" are in camera space and some are actually world space.
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
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Resolution Note (fix version 7.1.7):
Fixed in 7.1.7 HDRP package version