Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.4.0b1
Issue ID
758255
Regression
No
[LPPV] Trail Renderer recieves "incorrect values" from LPPV
Trail renderer doesnt appear to receive the correct values from a Light Probe Proxy Volume (See Image).
Repro Steps:
1) Open attached project and scene "VolumeTest"
2) Notice the positions along X axis of different coloured lights (for reference)
3) Enter play mode
4) Select "Cube" and move it down positive X until the trail renderer is yellow
5) Now move "Cube" down negative X until the trail renderer is red
6) Observe how trail renderer colour does not match light colour positions (and LPPV effect on cube) as it moves along negative X
Further:
7) Now move "Cube" down positive X until the trail renderer is yellow again.
8) Observe how the distance needed from light position is larger than it was in step 5/6 (if you were to repeat steps 5-8 the distance would get greater each time)
NOTE: This issue is amplified by object scale. Bigger objects/distances results in a larger discrepency between cube colour and trail colour
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment