Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
3.0.0
Issue ID
REC-164
Regression
No
[Recorder] 360 degree video is not equirectangular when using Physical Camera
How to reproduce:
1. Open the attached project ("case_1205635-RecoderPhysicalCamera.zip")
2. Open the repro scene ("SampleScene")
3. Select "Main Camera" and make sure that "Physical Camera" checkbox is
4. Open the Recorder tab and start the recording
5. Stop the recording and check the newly created video
Expected results: Output is equirectangular
Actual results: Output is not equirectangular and cannot be played as 360° video
Reproducible with: 2018.4.16f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a21
Couldn't test with 2017.4 (package is not supported)
Reproducible with package versions: 2.0.3-preview.1, 2.1.0-preview.1
Fogbugz [https://fogbugz.unity3d.com/f/cases/edit/1205635/]
All details and sample project is there: [https://stackoverflow.com/questions/59239336/record-360-video-in-unity-is-not-equirectangular/59283732#59283732]
This issue happens on all Render Pipelines, see screenshots below for current behavior. Every face of the 360 cubemap appears too "zoomed in" as if the Physical Camera attribute was not taken into account:
!360_physicalCam_LEGACY.png|thumbnail!
!360_physicalCam_URP.png|thumbnail!
!360_physicalCam_HDRP.png|thumbnail!
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
This will not be fixed