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.
Thanks for the report!The system I'm using is Mac OSX 10.8.4 Intel i7 with Intel HD graphics 4000 512MB. The screen resolution is 2560x1440.
The tour.js in that example consist of a 1.16.4 embedding script, a inline license, and a 1.17 viewer script.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.
.hi,Thanks for the report!The system I'm using is Mac OSX 10.8.4 Intel i7 with Intel HD graphics 4000 512MB. The screen resolution is 2560x1440.
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/s…d-dpi-test.html
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.What does it mean? that Bing maps won't be used anymore?
There will be a Google Maps HTML5 plugin together with the release of version 1.17.when Goole maps for HTML5 ?
can't use BING for this project - please check "wrong" map
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
1.16.x = the current versionI 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.
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.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.
Zitat
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.
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »nosferatu« (3. September 2013, 21:57)
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...Some of my friends have confirmed the memory problem.
Benutzerinformationen überspringen
Wohnort: Netherlands
Beruf: Krpano custom coding / Virtual Tours / Photography / Musician / Recording engineer
: https://pame.virtualtuur.com