You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project rendering pipeline uses Universal RP v14.0.11. When I use a 360 camera to record videos, selecting the Capture Worldspace UI option causes the post-processing rendering filters to display incorrectly (not matching the editor's screen effect). Conversely, if the Capture Worldspace UI option is unchecked, the rendered screen filters are correct (matching the editor's screen effect).
Video Presentation
Here is the video presentation. The second image shows the expected effect.
This is the filter effect of the screen in the editor.
Log output
No response
The text was updated successfully, but these errors were encountered:
Unity Version
2022.3.30f1
AVPro Movie Capture Version
5.3.0
Which platform(s) are you using?
Windows
Which OS version(s) are you using?
Windows 11 Enterprise
Which rendering API(s) are you using?
Direct3D 11
Hardware
Computer Information:
Processor Information:
Operating System Version:
Video Card:
Sound card:
Memory:
VR Hardware:
Miscellaneous:
Which capture component are you using?
Capture From Camera 360
Capture mode
Offline
Which output mode are you using?
Video file
Video codecs
H264
Audio source
Unity
Audio codecs
AAC
Any other component configuration
No response
The issue
Issue Description
The project rendering pipeline uses Universal RP v14.0.11. When I use a 360 camera to record videos, selecting the Capture Worldspace UI option causes the post-processing rendering filters to display incorrectly (not matching the editor's screen effect). Conversely, if the Capture Worldspace UI option is unchecked, the rendered screen filters are correct (matching the editor's screen effect).
Video Presentation
Here is the video presentation. The second image shows the expected effect.
This is the filter effect of the screen in the editor.
Log output
No response
The text was updated successfully, but these errors were encountered: