Search Issue Tracker
Fixed
Votes
0
Found in [Package]
6.9.0
Issue ID
1191141
Regression
Yes
"Setting anti-aliasing of already created render texture" errors thrown in a new URP template project after entering Play Mode
Reproduction steps:
1. Create a new project using a URP template
2. In the Hierarchy, select "Main Camera"
3. Press Play
Expected result: No errors are thrown
Actual result: "Setting anti-aliasing of already created render texture is not supported!" errors are thrown repeatedly
Reproducible with: 2019.2.0b10, 2019.2.12f1
Not reproducible with: 2018.4.12f1, 2019.2.0b9, 2019.3.0b10, 2020.1.0a12
Could not test with: 2017.4.34f1 (no Package Manager)
Reproducible with package versions: 6.9.0
Not reproducible with package versions: 4.1.0-preview, 6.7.1
Comments (2)
-
ahmedaniss
Aug 01, 2020 08:37
problem fixed here : https://youtu.be/t336oGyJ6nA
-
Emme73
Jun 22, 2020 11:40
Still in 2019.4.1f.
Fix: turn off AA in URP pipeline asset.
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note:
Fixed in 2019.2.8f1 and above