Search Issue Tracker
Fixed in 2019.4.9f1
Fixed in 2019.4.X
Votes
0
Found in
2019.3.0f1
2019.3.0f6
Issue ID
1215229
Regression
Yes
[URP] entering Play Mode with Scene window open and Camera selected in a new project throws errors in the Console
Repro is not 100% consistent
Reproduction steps:
1. Create a new URP Template Project
2. Make sure that Scene view, Game view, Inspector, and Console windows are open and follow the layout in "image1.png"
3. Select the Main Camera in the Hierarchy
4. Enter Play Mode
Expected result: there are no errors in the Console
Actual result: errors "Setting anti-aliasing of already created render texture is not supported!" start flooding the Console
Reproducible with: URP 7.1.5 (2019.3.0f1), URP 7.1.8 (2019.3.0f6)
Not reproducible with: LWRP 4.10.0 (2018.4.16f1), LWRP 6.9.2 (2019.2.19f1), URP 7.1.8 (2020.1.0a21)
Could not test with: 2017.4 because no Package Manager
Notes:
1. Restarting the project resolves the issue
2. Reproducing the issue in Unity versions (2019.3.0f1 - 2019.3.0f4) was inconsistent (the issue would only reproduce sometimes)
3. New URP Template project is needed to reproduce the issue
4. Exiting Play Mode does not stop the errors appearing
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment