Suchergebnisse
Suchergebnisse 1-20 von insgesamt 1 000. Es gibt noch weitere Suchergebnisse, bitte verfeinern Sie Ihre Suche.
Basically yes, but it also depends on what the browser actually reports for window.devicePixelRatio - that's not always (or by default) the full native resolution.
Zitat von »Yang yumin« I know the reason, and now I will use the webvr.js in verson 1.20. That's actually not the right solution! Have you tried viewing in a VR headset? One solution would be setting a proper startup viewing point (view.tx/ty/tz). And if you want the doll-house view in non-VR mode, you could add: <events webvr_onexitvr="view.oz=1200;" /> Best regards, Klaus
Hi, the reason is that in 1.21 the view.oz value (= the viewing offset for the dollhouse view) will be set to 0 when entering the VR mode. That's intentional because when wearing a VR-headset, a view-offset would be wrong: looking around would rotate the model instead of actually looking around. And that leads to an 'invisible' model from your current point-of-view in your case. When looking upward or moving upward (view.ty) you would see your model. When exiting the VR mode, the view.oz value i...
I don't see a speed difference and there should be also not one...
Hi, the maxpixelzoom relates to the device-pixels (the physical resolution). The CSS pixels could be anything depending on the page-zoom and wouldn't be a useful reference... About a good value - I think that's individual and depends on the pano. When the image is crisp-clear and has many details, then even a maxpixelzoom=2 (or more) could be good to allow exploring these details. On the other side when the source image is already at 100% not very detailed anymore, than maxpixelzoom=1 could be a...
Hi, note - when defining a JS-function in an action and calling that action again and again - then each time NEW functions are created. And because then these functions are different ones, the removeListener will not work. That means the functions would need to be stored after creating (like the last example here: 'krpano.tuur.sync1 = sync1;') and then be reused. ... In the meantime I thought about and a more automated and universal solution that could be used to sync any number of viewers: Quel...
Hi, sorry, but I don't understand your intention in your example, but your removeListener usage is wrong! The removeListener function would need to be called with the SAME function that was used in addListener. Try to think this way: - addListener can be called multiple times and with different functions. - So to remove the assigned function, it also need to be called with the function that should be removed. Best regards, Klaus
Hi, a flat pano is defined with a field-of-view of 1 degree by default. And hotspots with zoom=true or distorted=true are using 90 degree ^= 1000px as reference. That means hotspots would be extremely large in such case and would require a small scale value to become visible. And the ath/atv values should be also within the -0.5 to +0.5 range. Try adding scale="0.001" to your hotspots. Best regards, Klaus
Hi, use the screentodepth() and/or raycastdepth() actions: https://krpano.com/docu/actions/?version=121#screentodepth https://krpano.com/docu/actions/?version=121#raycastdepth The depthmap_measure3d.xml is also just doing this: https://krpano.com/viewsource.html?relea…p_measure3d.xml E.g. (Javascript code): Quellcode 1 2 3 4 5 var hit = krpano.actions.screentodepth(krpano.mouse.x, krpano.mouse.y); if (hit) { ... } Best regards, Klaus
Hi, yes, but only by adjusting the depthmap_navigation.xml file. E.g. search for this line: Quellcode 1 if ((mouse.leftbutton && mouse.shiftkey) || mouse.middlebutton || mouse.rightbutton) here: https://krpano.com/viewsource.html?relea…_navigation.xml There you could use the already there defined 'is_dollhouse_view' variable to check if in dollhouse-view, for a 'floorplan-view' you would need a custom check. Best regards, Klaus
Hi, this is a bug. It will be fixed in the next release. Best regards, Klaus
Hi, just use the krpano Testing Server: https://krpano.com/docu/tools/testingserver/#top Best regards, Klaus
Hi, hmm... that doesn't happen when I test it... Beside that - that would mean that Safari was putting that text with the surrounding the html code into the clipboard... and when pasting then just that text was inserted... Somehow filtering pasted content would be a bad idea, what if such code was intended to be pasted? Best regards, Klaus
Sure, just like in any other Javascript code - the code only need to be inside a 'async' function: Quellcode 1 2 3 4 5 6 7 8 9 10 <action ... type="js"><![CDATA[ async function asyncCall() { ... inside a async function you could use await ... } asyncCall(); ]]></action> or just run directly an anonymous function: Quellcode 1 2 3 4 5 6 <action ... type="js"><![CDATA[ (async function() { ... inside a async function you could use await ... })(); ]]></action> But note - async, await is only syntacti...
Hi, e.g. add these lines anywhere in the tour.xml: Quellcode 1 2 3 <action autorun="onstart"> skin_hideskin(instant); </action> Best regards, Klaus
Hi, the left and right images are slightly different! Best regards, Klaus
Hi, the view-limitations are getting disabled by default when enabling gyro-control or the VR-mode. There is a way to re-enable them, but if that result would be acceptable depends on the actual pano - please see here for more: vlookatmin / vlookatmax not working with gyro2 before the first loadscene call Best regards, Klaus
Hi, either check for the current mouse button - e.g: Quellcode 1 if(mouse.button == 1, ...); or Quellcode 1 if(mouse.leftbutton, ...); See: https://krpano.com/docu/actions/#mouse.button https://krpano.com/docu/actions/#mouse.leftbutton or change the control.panomousebuttons setting to 1: https://krpano.com/docu/xml/#control.panomousebuttons E.g. Quellcode 1 <control panomousebuttons="1" /> Best regards, Klaus
Mittwoch, 18. Oktober 2023, 20:26
Zum Seitenanfang
