krpano 1.16

Quote from nidrig

The system I'm using is Mac OSX 10.8.4 Intel i7 with Intel HD graphics 4000 512MB. The screen resolution is 2560x1440.

Thanks for the report!

This is a Mac retina screen or?
I must admit that I don't have a Mac system with a retina screen for testing.

The problem might be related to the system retina scaling and Firefox - it can be the case that Firefox will internally try to render the WebGL graphic in the twice screen resolution, which would be 2 x 2560 = 5120 - which is larger than the 'Max Render Buffer Size' of 4096 - and that probably results in wrong rendering and/or wrongly returned WebGL 'drawing buffer informations' (which would be a bug in Firefox).

Can I send you a special build with some debug/trace informations for testing this special case?
If the 'drawing buffer informations' on Mac Retina Firefox were known to be buggy, it should be possible to ignore them and use the WebGL canvas size instead (which would be technically not fully correct, but should fix that problem in this case).

Additionally - can please run also this WebGL conformance test here - it can also show bugs related to WebGL canvas scaling, but due the small test sizes that were used there, it will probably pass all test successfully:
https://www.khronos.org/registry/webgl…d-dpi-test.html

Quote from HansNyb

And this is the 16.4 version it was updated from http://virtualdenmark.dk/dnm/kina/

I have all the licenses in both folders and the update tool does not give me any error.

The tour.js in that example consist of a 1.16.4 embedding script, a inline license, and a 1.17 viewer script.
This combination confuses the krpano Update Tool .

The krpano Update Tool thinks the 1.17 viewer script part has the license directly embedded, which leads to the removal of the 'inline-license' in the tour.js. I will try to enhance the update tool in the next versions in the let the tool also handle such mixed files correctly.

Try getting a completely fresh tour.js to fix that problem:

1. drop one image (anyone) once on the MAKE VTOUR (NORMAL) droplet
2. then copy and take the tour.js from that build tour

Best regards,
Klaus

Hi,

Quote from nidrig

What does it mean? that Bing maps won't be used anymore?

No, that doesn't mean that - it means the Bing Maps JS-API will not be used anymore when this plugin is ready. Bing Maps provides also a Tile-API - with that API it's possible to load and display the tiles with own code. This way a lot of bugs and issues can be avoided.

Quote from martyhr

when Goole maps for HTML5 ?
can't use BING for this project - please check "wrong" map

There will be a Google Maps HTML5 plugin together with the release of version 1.17.

Best regards,
Klaus

Hi,

there is another small update for version 1.16:
krpano 1.16.6

Please see here for a list about all changes and fixes:
Release Notes 1.16.6

Best regards,
Klaus

Hi,

Quote from HansNyb

I am confused about your version numbers. Why do you call it 1.17 when the actual version is 1.16.6
And when is the expiredate for this last update. I can not find it anywhere in the release notes.

1.16.x = the current version
1.17.x = the next version (with new features like html5 multires and more)

The next version, the 1.17 one, is still not finished and therefore currently only available as 'pre-release / preview' version. Once this version is fully ready, it will become the normal/current version (then as full release and without any expire date of course).

The 1.17 preview version will be updated from time to time, sometimes also without forum- or news-announcement. The current expire date is 2013-08-31.

For the current version, the 1.16 one, there will be still bugfixed-versions, like the new 1.16.6, until the 1.17 version is ready.

Best regards,
Klaus

Hi,

Quote from nosferatu

found some problems in the browser Chrome 28 on Windows XP.
When viewing pano on desktop in forced HTML5-mode initial level of RAM = 800 kb, but after "refresh" RAM = 1100 kb,
again refresh, RAM = 1400 kb, and so infinitely.

What your are describing can't be a krpano bug, it's not possible for a webpage/Javascript to keep memory after a 'refresh'. So it's either a browser bug (but I can't reproduce it) or just some kind of browser internal caching.

Best regards,
Klaus

Hi,

Quote from nosferatu

Some of my friends have confirmed the memory problem.

Please read above - such can't be a krpano bug. It's impossible for a web-page to keep memory after reloading/after refreshing and also with normal pano viewing it should be not possible to see such increase in memory usage. That means this is probably a specific Chrome bug, maybe related to the operation system...
Please post your problem directly to the Chrome developers (crbug.com), on my side I can't reproduce anything in that direction.

Best regards,
Klaus

Hi,

there is new bugfix release:
krpano 1.16.7
Release Notes 1.16.7

The new release fixes several minor bugs and includes also a workaround for an annoying iOS 7 iPad bug.

In iOS 7 on the iPad the Safari browser sizes the html elemets wrongly so that a part of the html page (and so the pano) is partially off/outside the visible page. The iOS 7 bug itself was reported to Apple, but as it seems it was ignored because the bug is still present in the iOS 7 'Golden-Master' release from today. The new krpano release detects this iOS 7 bug and automatically corrects the wrong sizes.

The 1.17 html5-multiresolution pre-release version has got the same bugfixes and was updated today too:
https://krpano.com/html5multires/#download

Best regards,
Klaus

Hi,

there is a new minor 1.16 update - mainly related to scalechildren and the Flash video problems:
krpano 1.16.8

Please see the release notes here for a list of all changes and fixes:
Release Notes 1.16.8

Best regards,
Klaus

Hi,

another small 1.16.x update:
krpano 1.16.9
Release Notes 1.16.9

The 1.17 html5-multires pre-release was updated too and has got the same fixes. Additionally the showing of the watermark was delayed and the expire-date extended to 2013-12-31.

Best regards,
Klaus