Hi, with 1.22.3 there is a bug when using set3dtransition (might be a KEEPMOVING issue, not sure).
If I dynamically add hotspots onnewscene they are not always removed when loading a new scene using set3dtransition, I had the similar issue a few days ago without set3dtransition but I was using KEEPMOVING and the issue was solved removing this flag.
Barebone : https://www.360images.fr/barebone_3dtransition/
If you click on "google style hotspots (the one added onnewscene) it works as expected.
If you click on "krpano style" hotspots using set3tdtransition then google style hotspots are not always removed between scenes.
set3dtransition bug
-
I think to remember that this was already mentioned and will be fixed in next release..
Unsure though
Tuur
-
- New
- Official Post
Hi,
the problem in this case example is the 'hs_to_googlenav' action - it creates new hotspots based on the current existing ones.
But some of previous hotspots can be still there during blending when this gets called.
There is even an explicit state variable that informs about that hotspot state:
krpano.com - Documentation - XML ReferenceThat means the 'hs_to_googlenav' action would need to check for the hotspot isblending state and create new hotspots only when this is not set.
Best regards,
Klaus -
- New
- Official Post
Without KEEPMOVING the old pano and its hotspots are getting immediately removed.
During blending then only a kind of 'screenshot' of the old pano is used.With KEEPMOVING the old pano and the old hotspots are still there and rendered during the blending.
And the hotspots still need be addressable by xml to allow that dynamic stuff still can work (e.g. animated hotspots or scripts that dynamically change/animate the hotspots).Therefore the hotspot blending setting and the isblending state.
-
Hi all, so please explain to remove this (same) problem. Hotspots in the project are generated dynamically... I use tips isblending true... NO RESULT.... removed MERGE etc. nothing helped. There was another function that (supposedly) instantly removed hotspots from the previous panorama (I forgot the exact syntax)... but it didn't seem to help either. Please finally solve this problem, it's a real pain... now I'm just solving it via 'delayedcall' but this is not good a solution... in versions 1.20... it worked without problems
-
set hotspot.blending to false : https://krpano.com/docu/xml/#hotspot.blending
Hi. oh yeah, I mentioned it above (which I forgot). Doesn't work for my solution. I have a modified Arrows Plugin https://krpano.com/plugins/userplugins/arrows/, a clone similar to GArrows (hotspots that are getting constantly updated) In versions 1.20.xx such problems were not observed starting with some 1.21.. problems arose... I already described this somewhere on the forum. I believe that the developer's duty will provide at least some 98% compatibility for legacy players and scripts, otherwise most of the developments, plugins, knowledge bases simply fly out into the trash
-
The problem lies in the NEW transition itself (3dtransition)... something needs to be changed in it for compatibility or a 'сrutch' needs to be adding that allows avoiding this trouble...
-
- New
- Official Post
Either add blending="false" to the hotspots or in the code that dynamically generates the new hotspots (based on existing hotspots), a check for the isblending, e.g.
Codeif(hs.isblending == false, ... generate the new hotspot ... );
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!