Sie sind nicht angemeldet.

Lieber Besucher, herzlich willkommen bei: krpano.com Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.

HansNyb

Profi

Beiträge: 1 063

Wohnort: Denmark

Beruf: Photographer

  • Nachricht senden

201

Montag, 8. Juni 2020, 08:12

The fullscreen support for iPad is enabled (white-listed) for iOS 13.4 and higher now.


Actually it is activated also with 13.3.1 However it works very bad.

I just bought a new iPad Air which came with 13.3.1 and fullscreen button was activated. The problem was that zooming did not work.
It kind of jumped back when you zoomed in.
After updating to 13.5.1 it works.

While in 13.3.1 I did some testing an found also this weird bug. Tapping on the image gave me this popup. I have not been able to reproduce it in 13.5
It is actually a Zoom image which is opened fullscreen from a popup
https://www.360-foto.dk/fullscreen-bug.jpg

202

Montag, 8. Juni 2020, 10:25

Hi,

Actually it is activated also with 13.3.1
Hmm... the fullscreen support is definitely only enabled for iOS 13.4 and higher...
Do you maybe enable it manually in the xml?
Look for a 'fullscreensupport' code line.


However it works very bad.
Agree, that's why it disabled by default for these iOS versions ;-). That popup is also a part of the strange/bad iOS (before 13.4) fullscreen behavior.

Best regards,
Klaus

HansNyb

Profi

Beiträge: 1 063

Wohnort: Denmark

Beruf: Photographer

  • Nachricht senden

203

Montag, 8. Juni 2020, 14:10

Do you maybe enable it manually in the xml?
Look for a 'fullscreensupport' code line


No I checked 3 of my tours. And I just to be sure checked the skin directly on server.
They all has this


<layer name="skin_btn_fs" url="nav/full.png" align="right" x="202" y="1" scale="0.52" onclick="switch(fullscreen);" devices="fullscreensupport" />

<layer name="skin_btn_closefs" url="nav/exit.png" align="right" visible="false" x="202" y="1" scale="0.52" onclick="switch(fullscreen);" devices="fullscreensupport" />

<events name="skin_events" devices="fullscreensupport"
onenterfullscreen="set(layer[skin_btn_fs].visible,false);set(layer[skin_btn_closefs].visible,true);"
onexitfullscreen="set(layer[skin_btn_fs].visible,true) ;set(layer[skin_btn_closefs].visible,false);"
/>

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »HansNyb« (9. Juni 2020, 20:32)


HansNyb

Profi

Beiträge: 1 063

Wohnort: Denmark

Beruf: Photographer

  • Nachricht senden

204

Dienstag, 9. Juni 2020, 10:30

Hmm... the fullscreen support is definitely only enabled for iOS 13.4 and higher..


I discovered another thing. If I understand it right only Safari has the Fullscreen support on iPad.
I just downloaded Firefox and Chrome and even if none of them can do fullscreen, Firefox shows my Fullscreen button.

Another interesting thing for me is that if you make a Homescreen button in Safari the button is gone, also in my Krpano flat image xoom image.

There are more weird problems which I will come back to when I got all browsers tested.

205

Freitag, 12. Juni 2020, 13:09

Dear Klaus!

Just discovered a potential bug in 1.20.6 and by the looks of it, 1.20.7. When using capturetouch=false (which we use in all tours because we have extensive html layouts), pinch-zooming on Safari/iOS zooms the whole...page. The tour is embedded fullscreen, so I'm not talking about a conventional website with an embedded tour. But 2D layers, buttons etc get zoomed and panned away too. Basically, as if the panorama and everything on it was a 2D image.

I can confirm that rolling back to 1.20.4 solves this, no problem there. Anyone else having this issue?

206

Montag, 15. Juni 2020, 23:39

Bug in bingmaps.js ?

Hi Klaus,

It seems that the plugin bingmaps.js does not treat the layer[skin_map].radar.visible right way:
When using settings.map_type=bing the HTML5 does not toggle the radar.visible attribute. It works well under FLASH and also in the googlemaps.js.
When the radar is hidden at the first scene, there is no way to display the radar anymore. When the radar gets shown at the first scene and I want to hide it next, the radar stays visible on the last instance.
(Win10: Firefox 75.0, Chrome 81, Edge 44, IE 11.0).

Thanks for your great job!
Pavel

207

Mittwoch, 17. Juni 2020, 19:58

Hi Klaus,
Thanks a lot for your work, its really great. Unfortunatley I still have problems to view my vr tours made with VTOUR (VR-OPT) in Oculus Go (Browser 9.2...)
The Oculus Browser (unlike samsung or firefox on Oculus go) does not recognize my tour (made with 1.20.7) as VR. The Button "Enter VR" does not appear. When I set it manualy to VR360, it enters VR-mode, but displays only a distorted 180 degrees picture. I tried to find out something about this issue in the forum, but didnt find anything... Am I the only one with this problem, did I make a basic mistake??
Thx for your help
Try to add webxr: "auto" in embedpano and check that your oculus browser is not simulating desktop device.

I added webxr: "auto" in the tour.html, deleted the browser cache, made sure that the browser is not simulating desktop mode, but the problem is still there... *wacko*

208

Donnerstag, 25. Juni 2020, 07:54

Hi,

I discovered another thing. If I understand it right only Safari has the Fullscreen support on iPad.
I just downloaded Firefox and Chrome and even if none of them can do fullscreen, Firefox shows my Fullscreen button.

One note - all these browsers now have also a 'Destkop Mode' (sometimes enabled by default) where they are faking their detection-information. So for krpano they look like a desktop browser and there is no information about the iOS version available anymore. So checking for the iOS version and removing the fullscreen support when known to be not usable anymore is not possible in this case. Additionally the iOS Firefox browser always reports that is fullscreen support, but when calling its APIs nothing happens.

The next krpano version will have some improvements here for even better detection, even when in fake Desktop-Mode, but to work everywhere the correct behavior from the browser itself is also a requirement.



Just discovered a potential bug in 1.20.6 and by the looks of it, 1.20.7. When using capturetouch=false (which we use in all tours because we have extensive html layouts), pinch-zooming on Safari/iOS zooms the whole...page.
Hmm... but that's the intended behavior of capturetouch=false - the touch events will be NOT captured by krpano and so the browsers default processing can happen...

Actually there was a bug in older krpano version (before 1.20.6), there the capturetouch=false setting was fully applied in all browsers. E.g. in iOS only the scrolling was blocked and only in some cases.

Here a quote from the 1.20.6 release notes:

Zitat

Fix: Allow the browsers default handling (panning, zooming) when using capturetouch=false.

So what behavior do would you actually use?


I added webxr: "auto" in the tour.html, deleted the browser cache, made sure that the browser is not simulating desktop mode, but the problem is still there... *wacko*
As there is no known problem, please share a link.

Best regards,
Klaus

HansNyb

Profi

Beiträge: 1 063

Wohnort: Denmark

Beruf: Photographer

  • Nachricht senden

209

Sonntag, 28. Juni 2020, 16:21

One note - all these browsers now have also a 'Destkop Mode' (sometimes enabled by default) where they are faking their detection-information. So for krpano they look like a desktop browser and there is no information about the iOS version available anymore.


Both Chrome and Firefox Claims that ituses desktop as i Desktop.
Only Firefox shows the fullscreen button (which does not work.)
But both shows correctly my mobile help popup.

The weird thing is that if I request the Firefox mobile version it shows my Desktop Help screen.

210

Donnerstag, 2. Juli 2020, 18:38

Hi all!
xml.scene return scene index not scene name when deeplinking="true" (this add /?startscene to URL and startscene variable is used). Is this old bug appeared again or there is some tricks?

211

Freitag, 3. Juli 2020, 11:26

Hi,

xml.scene return scene index not scene name when deeplinking="true" (this add /?startscene to URL and startscene variable is used). Is this old bug appeared again or there is some tricks?

Currently the xml.scene variable always contains the value loadscene() was called with...

If you always want the scene name, use:

Quellcode

1
scene[get(xml.scene)].name


But I will consider doing that automatically in the next release to ensure that xml.scene always contains the name of the scene.

Best regards,
Klaus

213

Mittwoch, 8. Juli 2020, 17:16

Hi,

When using droplets with 1.20.7 Mac, multires or vr-opt with Ricoh Theta Images, the tour wont go VR into Oculus (old and latest version).

The enter VR button appears, once clicked, the VR stays framed into the oculus browser window.

Thanks

214

Freitag, 10. Juli 2020, 09:41

ok found out this happens when testing on a non https server

regards

215

Montag, 13. Juli 2020, 13:46

While experimenting with the webvr plugin in 1.20.7 I realized that the zoom option does not work for Oculus Quest (dont know about other headset). However the webvr zoom option works nicely in the simulated vr mode (e.g. in firefox) on my desktop machine.

To test this I just added zoom="4" to the plugin settings in the webvr.xml file.

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »lizard.king« (13. Juli 2020, 15:30)


216

Dienstag, 14. Juli 2020, 08:12

Hi,

ok found out this happens when testing on a non https server
The WebXR browser API is only available on HTTPS.

While experimenting with the webvr plugin in 1.20.7 I realized that the zoom option does not work for Oculus Quest (dont know about other headset). However the webvr zoom option works nicely in the simulated vr mode (e.g. in firefox) on my desktop machine.
Right, in the WebXR API support, the applying of the custom zoom is missing. Will be fixed in the next release.

Best regards,
Klaus

217

Mittwoch, 5. August 2020, 11:15

Future versions / What's next

Better multi-resolution for depthmap-panos / 3D-models.
Depthmap improvements.
Build-in 3D-object support.




Is there a rough ETA for these?

yasarcan

Schüler

Beiträge: 52

Wohnort: Türkiye

Beruf: Computer Teacher

  • Nachricht senden

218

Freitag, 7. August 2020, 21:06

Hello ,

I have :
Update Check Results
Licenses ordered with the email address yasarcanturk@hotmail.com:
krpano License(old license) Orderdate: 2013-08-26
krpano Maps Plugin License
Upgrading your license is possible:

krpano License Upgrade
  • Upgrade to the latest krpano version license. 35 € plus sales tax/VAT*
My license status is as above now.

Can I update krpano to create a virtual tour like in this example? Do I have to buy averpano?
https://krpano.com/releases/1.20.7/viewe…l-tour/tour.xml

thank you.
The best of people, the most beneficial to people. Hz. Mohammed

219

Freitag, 14. August 2020, 19:09

@yasarcan:

everpano is not a product by krpano, it must be purchased separately
https://everpano.com/buy

for everpano you need a krpano 1.20 license
but it is highly recommended to update anyway (everpano or not)

Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von »indexofrefraction« (15. August 2020, 11:12)


ramirox3

Fortgeschrittener

Beiträge: 354

Wohnort: La Ceja, Colombia

Beruf: photographer

  • Nachricht senden

220

Freitag, 14. August 2020, 19:46

everpano is not working properly and development appears to have ceased. It can be a waste of money to buy it right now

Ähnliche Themen