Anything?
Edit: I ended up figuring out both problems:
- There was an action in the main included XML that was forcing the control.mouse parameter to "moveto" regardless of the setting in the control tag. (set(control.mousetype, moveto);). I don't know why I ended up with that in the first place.
- In the view tag, the presence of the old "fisheye" parameter in addition to the new "distortion" parameter was apparently causing the issue in Microsoft Edge. Removing it fixed the problem.
Hello,
I am running the latest 1.19 version.
Encountering the following issues:
- I cannot set a panorama to drag on a desktop (not a mobile). All it can do is "moveto". I use the whole <control> tag definition from the xlm reference, with mouse="drag" but there is no change no matter what I use. I can change other settings such as draginertia, movetoaccelerate and others, but the mouse setting has no effect.
- the view.distortion (formerly view.fisheye) setting seems to not be working in Microsoft Edge. Any info?
These 2 issues appear in both HTML5 and Flash renderings. No difference.
Basically, I am trying to get certain panoramas to render exactly like they do on the Ricoh website, but in krpano, like this (not my panorama):
https://theta360.com/spheres/sample…-064087ff3472-1
This is not what I normally do, but I'm also using a Theta in addition to my normal panorama setup, and for some of them (essentially close quarters with people involved) I would like to display them that way. It seems that distortion="1" and stereographic="true" does the trick, but as sais above, I cannot get the drag to work, and the view is not working in Edge.
Thanks for any help.
What is the easiest and quickest way to update to this from the previous 1.0.8.15 release? I find the updates pretty painful with regards to loss of personal settings and custom templates, the paths change, things stop working. I'd love a better update process. In terms of manual updates, are there a handful of files that can be copied in order to get the latest functionality (like the full screen HTML5 support) without touching my config settings?
Thanks.
I've read that part, however, that doesn't really describe the issue or allow you to figure out if what you are seeing is normal or not, especially since the following sentence says that everything else is working correctly and with good performance. If there are giant clipping black empty spaces, I wouldn't say that anything is working correctly.
Mine is not working locally either. I get the same error message as Hans.
I found the culprit.
I had this in my XML settings, in the <view> tag:
hlookatmin=""
hlookatmax=""
vlookatmin=""
vlookatmax=""
Those settings have been in there for months and were not a problem for previous versions, but they are now apparently.
So with those removed, the panorama is spînning freely in HTML5/Javascript. However, Chrome on Android 4 is still displaying huge empty black zones while moving around. I know that its support of CSS3D is not great. Is that result to be expected or another wrong setting?
No limitations on the panning. The settings for that pano haven't changed, only updated to the new version. It worked fine before, and it still works fine in Flash.
Hello,
I recently discovered an issue with the HTML5 player on my site.
First of all, I realized that something was not working when I tried with Chrome on my Xoom tablet in Android 4.0. I had the Flash error message. I updated to the latest version of krpano and Javascript files. The Flash error disappeared and the pano is now rendering in HTML5 in Chrome. However, the rendering is terrible. It moves only up and down and displays a lot of black.
Anyway, I chalked it up to Chrome not supporting this very well yet in Android. However, I had someone try it on a new iPad in Safari, and there as well, movement is limited to up/down, but no left and right (although tiles are not missing there).
I also tried in Safari on my Mac desktop, forcing it to identify as iOS, and the result is the same. I am positive that the HTML5 version worked very well previously on this panorama, including iPad and Safari desktop.
What can I do or look into to fix this? I updated to 10.0.8.15 and used the update tool to update the krpano files, and replaced them all on my website, including the other JS support files and license file.
is there anything else I should have changed, settings that need to be updated for the new version?
Thanks.
Thanks Michel. Hopefully they'll fix their browser with a proper user agent.
Thanks for the code, I'll try that.
Listen Hans, I appreciate your trying to help, but no, my Android phone doesn't need the zoom buttons. That's my choice and I don't want them there. Clicking on buttons on such a small device is awkward, and I don't need the zoom. Nothing in this helps with my original request to have more ways to differenciate accurately between devices.
How could it show both the visible and invisible if the plugins are defined with the same name?
In any case, don't you see how that makes my point? I'm trying to make a difference between a plugin that will work on a flash desktop and one that will work on an html5 desktop. If I use devices="flash" or devices="html5", then they are going to show up also on an android phone, which I don't want. I don't know how else to explain this.
Actually, the theory doesn't seem to work.
I have a button defined for desktop|tablet. I want to not have that button for an html5 browser. If I redefine the same button to visible="false", it's still there.
Not all desktops have Flash and with Safari 5 supporting CSS3D transformations, more clients will not have flash. I am a web developer and know that issue pretty well.
The android reacts to mobile, but so will the iphone. You're assuming the android tablet reacts to tablet but it is not confirmed, and it's a bit confusing since the other option is "android". If the android tablet reacts to tablet, and the ipad as well, we again have a problem there, because they are definitely not the same.
I know I can scale the zoom buttons. I just don't want them there on a small device. But that's not a problem, I don't have them on my phone. The issue is I don't know if they have also disappeared in the case of an android tablet.
I do not care about the zoom button on a mobile phone. I am not interested in a 5gb panorama. Actually I could probably solve my problem by removing the zoom buttons everywhere since I don't need anyone to be zooming in or out anyway.
As fas as zoom working on an HTML5 device, it would be nice to have some documentation from the developer about that. My zoom buttons are defined with plugins and do ondown="set(movevectorz,+1);". That works with Flash but does absolutely nothing on Safari 5.
I'm curious about zooming on your 5GB panoramas on an HTML5 mobile device though, since the documentation on this site mentions that multi-res is not currently possible on HTML5. You also won't have enough memory on those devices to load anything that large.
Yes, but this still doesn't completely answer my questions:
- how can we tell an android phone from an android tablet?
- using the "desktop" setting will make something appear on all desktops, flash and HTML5, that's not good.
This also means that we have to write everything in a certain sequence to make sure one overwrites the one above, as I mentioned in previous post, but we should have a finer control with devices to avoid having to overwrite definitions.
I don't find the zoom buttons useful on my android phone. They are too small to press reliably, or take too much of the screen. On a phone, I use only the fullscreen button. On a Javscript/HTML5 browser it seems that zooming doesn't work, so I'd rather get rid of the icons there too.
Perhaps I didn't explain well enough.
My point is that I want certain plugins to be available in Flash only on a desktop (and a tablet) but not on an Android phone. How can I use the devices setting to differentiate a dekstop/tablet flash from an Android phone flash. And does devices="android" concern only a phone or a tablet as well?
Hello,
Perhaps I'm missing something here but I'd like to figure out how to have more control using the "devices" flag.
I'm trying to juggle with settings for several different configuration:
- desktop with flash
- desktop *without* flash but with HTML5
- Android mobile (flash)
- Android tablet
- iPhone and iPad mobile
How can I activate something only for flash on a desktop or an Android tablet, but not for flash on an Android phone?
An example: I want to have zoom buttons, but only on Flash (since it doesn't seem to work with HTML5), preferrably on an Android tablet as well, but *not* on an Android phone (because it's just too small). I don't see a combination that allows me to do that.
If I use devices="desktop", it will be also available on HTML5 desktop, which I don't want.
If I use devices="flash", it won't be available at all on HTML5, which I want, but it will also be available on an Android phone, which I don't want.
How can we get more specific than that? What's the setting for an Android tablet as opposed to an Android phone?
I've thought about defining the plugins 2 times this way:
<plugin name="zoomin" devices="flash" blah blah blah visible="true">
<plugin name="zoomin" devices="android" visible="false">
But the question is: does the "android" setting work only for a mobile phone or for a tablet as well?
Thanks,
David
It does the same on my machine (Win7 x64) with brand new version of Chrome, and my video card is an ATI 5850.
