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
Comments (1)
-
Lorcanpro23
Mar 20, 2023 17:47
Are you using URP?
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
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)