the form and amount of distortion depends on the individual headset and can't be auto-detected
The lens distortion of the Oculus Rift itself isn't perfect - it depends on a lot of factors like the exact position of your eyes inside the headset. The only way to have an bit a control of that distortion is via the Oculus Rift configuration tool.
Quoted from "jeromebg"
because one of my clients had loading problems with a tour I did.
I have indeed a problem on iphone, sometimes some cube face just don't load and I have no errors in the log...
No error would be strange...
When the server is slow or busy and reports a loading error or times-out krpano still tries the loading again retrycount times before reporting an error in the log, no loading and no error is not normal.
What kind of distortion do you mean?
Not the lens-pre-distortion, or?!
Gyro + accelerometer is neededA user reports that on his Smartphone (ALCATEL ONETOUCH IDOL 3) Krpano sends " onunavailable in webvr.
It seems this smartphone has a gyro so what could be the problem ?
THX
All 'cardboard' headsets are requiring lens pre-distortion!In the case of cardboard the viewer parameters should be the same across all headsets. I would guess that when being displayed on a phone in a browser it would be in a cardboard or similar type viewer so KRP could do the correction automatically.
All!What headset / phone / browser combinations require a distorted display?
Please don't mix up the display on the computer with the Oculus Rift with smartphone - in case of the Oculus Rift, it can display the undistorted view on the PC and inside the headset you will get the distorted one. When using the WebVR API the browser is the only one that is responsible for the lens distortion!But still somehow krpano has this distortion/bending while other panoramas don't.
It does...Tell me if I'm wrong,
it seems that toggleVR doesn't call webvr_onentervr ?
Sorry, but I've no problems with the wakelock...will 1.19.4 have a safrai friendly hack for wakelock ?
Please don't mix up the display on the computer with the Oculus Rift with smartphone - in case of the Oculus Rift, it can display the undistorted view on the PC and inside the headset you will get the distorted one. When using the WebVR API the browser is the only one that is responsible for the lens distortion!
When testing make sure on desktop make sure to test the real WebVR API and not the mobile fake mode!
I would recommend testing using the Chromium WebVR build for Windows.
What is your testing environment? (ALL details!)
Maybe try somehow (don't ask me how) to get Chrome working - for me it's WebVR support was always working way better than the Firefox Nightly one...
Sorry, but I've no problems with the wakelock...
The iOS wakelock is just a page-reload-try-and-abort every 15 seconds.
There is no other wakelock hack so far I known. Other scripts are basically doing the same.
Benutzerinformationen überspringen
Wohnort: Netherlands
Beruf: Krpano custom coding / Virtual Tours / Photography / Musician / Recording engineer
: https://pame.virtualtuur.com|
|
Quellcode |
1 2 3 4 5 |
setInterval( function()
{
window.location = window.location; // request a page reload by redirecting to itself
setTimeout(window.stop, 0); // stop the loading one tick later
}, 15000);
|
I will check this in detail and will try improving that for the next release - probably by internally telling the loaders that there is currently an iOS wakelock in progress and to automatically retry/redo the loading in this case.
if the hotspot is an image, it still appear in VR mode,
why?
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »relationcg« (27. Januar 2016, 03:52)