setting viewing limits not working
If Top and Bottom are both set these define an implicit Max vertical FOV. Ideally P2VR viewer would compute the implicit limit at run time and use the lesser of the implicit value or value set in the design tool. Looks like I will have to do this manually, but will need to define it as vertical FOV because I don't know the aspect ratio on the user's screen.
In both Pano2VR v4 and v5, I keep having trouble setting setting Viewing parameters FoV and Min and Max zoom. When I set Viewing parameter to 120 degrees (as an experiment), when viewing the html5 version I get an FoV of 95 and it does not want to go wider than that. When I type in 20 Min zoom and click on "set" to the right of the num field, The 20 gets replaced by 120 degrees. When I type 120 for Max FoV and click on "set", the num field shows 120, but when I view the html5 version of the pano, I cannot go wider than 95 degrees. Finally - when I look at the XML file, I see Start fov 143.025 (??) and Max fov 120. I am attaching the xml file.
- Attachments
-
- tufa-redo2018-night-fade2.xml
- (1.99 KiB) Downloaded 151 times
- 360Texas
- Moderator
- Posts: 3684
- Joined: Sat Sep 09, 2006 6:06 pm
- Location: Fort Worth, Texas USA
- Contact:
Are you working with a spherical image? eg 6000 w x 3000 h px 2:1 ratio ?
You will get mixed results if you are using a cylinder 5999 w x 3000 h [edit - note 1 pixel off]
Pano2vr is image size aware and responds accordingly.
You will get mixed results if you are using a cylinder 5999 w x 3000 h [edit - note 1 pixel off]
Pano2vr is image size aware and responds accordingly.
That was fast
I do not think I have ever made anything but spherical panoramas. The problems with setting viewing parameters and min max zoom have plagued me for years, so I assume it is not a bug but user error. But what am I doing wrong..? And where is the mysterious initial FoV of 143.025 (in the xml file) coming from??
I do not think I have ever made anything but spherical panoramas. The problems with setting viewing parameters and min max zoom have plagued me for years, so I assume it is not a bug but user error. But what am I doing wrong..? And where is the mysterious initial FoV of 143.025 (in the xml file) coming from??
- 360Texas
- Moderator
- Posts: 3684
- Joined: Sat Sep 09, 2006 6:06 pm
- Location: Fort Worth, Texas USA
- Contact:
Occasionally, when editing a spherical the image dimensions get changed... that is why I asked about the image physical dimensions. In pano2vr I sometimes cube a 6000 x 3000 image then work with the nadir... then convert back to a equirectangle and Pano2vr trims 1 pixel off the width... meaning its now 5999 pixels wide but still 3000 pixels high.
Pano2vr thinks my image is now a cylinder which will oddly play with the FOV settings.
Pano2vr thinks my image is now a cylinder which will oddly play with the FOV settings.
Possibly because the image is not an exact 2:1 ratio dimension hence my question regarding the size.initial FoV of 143.025 (in the xml file) coming from??
I checked the image size and it still is 8000x4000. I also made a Flash version, just to see what would happen, and there the Max FoV 120 is displayed correctly. So it must be a limitation of html5 panos. The weirdness with setting Min FoV (where it jumps to Initial view FoV when pressing set) remains.