Search Issue Tracker
Fixed
Fixed in 6000.5.X, 6000.5.0a5
Votes
0
Found in
6000.0.62f1
6000.2.13f1
6000.3.0f1
6000.4.0a5
6000.5.0a1
Issue ID
UUM-126895
Regression
No
"ArgumentException" error when using CameraCaptureBridge with post-processing off and when rendering to a RenderTexture
How to reproduce:
- Open the “CameraAttachTest.zip“ project
- Open the “Test“ Scene
- Enter Play Mode
- Observe the Console
Expected result: Nothing is logged
Actual result: “ArgumentException: Trying to use an invalid resource (pass Capture Camera output).“ error is logged
Reproducible in: 6000.0.0b13, 6000.0.62f1, 6000.2.13f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a1
Not reproducible in: 6000.0.0b12
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Note: The issue seems to be specific to URP projects
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Resolution Note:
SRP Core: Fix Camera Capture pass crashing RenderGraph when used with an offscreen camera and an output RenderTexture
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.5):
SRP Core: Fix Camera Capture pass crashing RenderGraph when used with an offscreen camera and an output RenderTexture