Search Issue Tracker
Fixed in 6.8.0
Votes
1
Found in [Package]
6.7.0
Issue ID
1154361
Regression
Yes
[Rendering] VFX Graph outputs do not work well with the real values used by HDRP
HDRP scenes by default now start with more physically accurate values, and use post processing to tone down the exposure.
The VFX particles do not work well with these initial settings (img attached, more info below).
Repro steps:
1. Import the attached package
2. Open the Exposure scene
3. Observe how the VFX assets render with the same settings compared to their HDRP and ShaderGraph Lit, Unlit, and Emissive counterparts
Expected outcome:
- Similar look between all
Notes:
- Proper emission will not be possible with the current exposure values (the sun is 100,000 lux, post processing is using exposure of 14, to the particles will need an intensity of around 10 million to look similar)
- Unlit particles are getting completely crushed by the exposure, outputting black. They should probably be set to ignore it, akin to the HDRP shaders
- Lit particles look significantly darker
- Default static mesh shader renders behind the volumetric fog
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment