Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
Issue ID
1066885
Regression
No
[LWRP] Using shader with CameraOpaqueTexture produces a strange interaction between Scene and Game views
To reproduce:
1. Open the QA's attached project
2. Make sure the Scene and the Game tabs are both visible
3. Play the "SampleScene"
4. Right-click the scene view and move the mouse around
Expected result: The shader's preview in the Game tab stays unchanged
Actual result: The shader's preview in the Game tab changes depending on what's visible in the Scene tab
Reproduced with: 2018.2.2f2
Not reproduced with 2018.1.9f1 - LWRP package 1.1.11 is the only version available
LWRP package 2.0.4 is where the regression first appeared. LWRP package 2.0.3 works as expected.
Comments (2)
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
- “Destroying assets is not permitted to avoid data loss” error thrown when creating a second Tile Palette Brush Pick Asset
- The “Copy to clipboard” button has no hover or click animations when hovering and clicking the “Copy to clipboard” button after selecting an issue from the “Code” tab of the Project Auditor window
- Saved Tile Palette Brush List items become malformed causing the list to become cut off when decreasing the Pick size with the slider
- Foldout triangle icons and the foldouts titles are not aligned/centered in the “Assembly” and “Areas” Filter windows of the Project Auditor window
- High MeshSkinning duration when using Vulkan
tom_painter
Nov 10, 2018 21:24
Ive figured out how to reproduce, the PBR node needs to be set to 'opaque'
if you set to transparent it works as expected.
Kind of a bug Id say still as its still not a good reason to randomly show the scene view!
tom_painter
Nov 10, 2018 20:33
hi Im on 2018.3.0b9 and LWRP 4.1.0 and Im seeing this.
it is using the 'scene' viewport camera and not the 'game' camera (only one of those in project)