Search Issue Tracker
By Design
Votes
0
Found in
2022.2.10f1
2023.1.0b7
2023.2.0a5
Issue ID
UUM-30653
Regression
No
Player looks different from Game view when using a custom volumetric shader
Reproduction steps:
1. Open the attached project "VolumeLight"
2. Build and Run the project
3. Compare the Game view and the Player
Expected result: the Game view and Player look the same
Actual result: the Player looks different from the Game view and is gray
Reproducible with: 2022.2.10f1, 2023.1.0b7, 2023.2.0a5
Could not test with: 2020.3.46f1, 2021.3.21f1 (Compiler errors, pink texture)
Reproducible on: macOS 12.4 (Intel), Windows 10
Notes:
1. Closing Scene view, then closing and reopening the project will cause the Game view to look like the Player
2. Issue might be caused by Unity #pragma vertex Vert in the second pass
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
- Standalone profiler process is hidden in macOS dock
- Shader warnings are being thrown after building Mixed Reality Template
- Error is thrown when entering play mode with build profiles docked and standalone profiler open
- The Player hangs when activating another maximized application
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
Resolution Note:
The user shader specifies a custom argument structure for varying data between the vertex and fragment stages. This is unlikely to, and definitely not guaranteed to work correctly without a custom vertex shader function that appropriately sets the data (e.g., the `.ray` member of the varying structure will not be set by any built-in vertex function supplied by a Unity render pipeline)