Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f3
Issue ID
996712
Regression
No
Setting a single blend mode of an MRT modifies the blend of the other RTs
To reproduce:
1) Open attached project and scene
2) Open RenderDoc and inject it into process
3) Get a capture (you can also check screenshots in the project folder
4) Navigate to Pipeline tab -> Output Merger and check the following: Camera.Render > Drawing > Render.OpaqueGeometry > RenderDeferred.GBuffer > last 3 calls.
- cube 1 uses One Zero on all RTs, which is the default
- cube 2 uses One OneMinusSrcAlpha on all RTs, as expected
- cube 3 uses One OneMinusSrcAlpha on RT0 as expected, and One SrcAlpha on RT3
but RT1 and RT2 use One Zero: that is NOT expected!
Reproduced in 2017.3.0f3, 2018.1.0b6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Add comment