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.
That means the system doesn't allow the krpano Tools app to load the krpanotools.exe. For some reason the system blocks it.
Thanks, Klaus!
The problem was with Avast antivirus.
Should we open a specific post for Panotour update ?
There will be very soon a fixed version.The encrypt tool does not crash anymore with v1.20.1 but, apparently, it does not correctly encrypt files which contain comments, so the problem is worse !!
Do you mean Chrome and Firefox on iOS?I can´t get krpano 1.20 to switch to fullscreen in landscape-mode anymore on newest Chrome and Firefox. Only Safari on iPhone works so far. And even the VR-mode in the examples on krpano.com are´nt working anymore :-(
Why? That would only fake the detected browser support. But when the browser itself is not supporting the HTML5 fullscreen mode API, then faking the detection result will not help of course.I did try your <set var="device.fullscreensupport" val="true" />-switch, but without any luck.
Not that I know.Is there a new trick/hack necessary to switch to fullscreen-mode in Chrome and FF?
Does the old krpano support gyro2.js on ios13? After updating ios13, gyro2.js of krpano tour made with old version does not work
Dieser Beitrag wurde bereits 4 mal editiert, zuletzt von »indexofrefraction« (21. Oktober 2019, 10:47)
What is the best practice when updating krpano? I have version 1.20 and have edited some of the config files and xml templates to suit my workflow. Do I need to re-edit the same files for each update or can I use my edited version 1.20 config files in version 1.20.2. Hope this makes sense. Sorry if such a noob question.
Thomas
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »vope« (29. Dezember 2019, 11:32)
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »Guernegor« (16. Januar 2020, 22:59)
That will be fixed soon in version 1.20.3.ReferenceError: process is not defined
When registering by command-line the krpano files inside the viewer folder doesn't get automatically updated/replaced by registered version (as when using the GUI tool).I then successfully ran
./krpanotools register #my new license code#
as I have done many times with my old license without issues.
.krpanotools license file was created in home directory and in the working directory on another trial. I restarted the console several times.
I'm still getting the "demo version" watermark. No luck on the local machine or on the server.
|
|
Quellcode |
1 |
./krpanotools protect -o=krpano.js |
Sorry, can't reproduce such.I noticed that view.ry, view.rx and view.rz leave css3d hotspots pinned to the screen and not to the panorama (during movement). There is no problem with webgl hotspots.