VTour Editor hotspot problem

  • Greetings Klaus *cool*

    The question is the following: when in vtour editor you create hotspots to connect panoramas, you get such situations that creating a new hotspot, using 3dtransition, can overwrite existing hotspots in the scene to which the current one is connected.

    This happens, as I understand it, from the logic of automatic generation of hotspot names when creating them. When a scene has spot1, spot2, spot4 - editor can create spot3, and then spot4, which will be overwritten.

    Maybe think about generating a non-ordered sequence in the name, something like generating a unique combination of letters or numbers?

    Or if you leave the sequential numbering, then add the logic of creating names so that the number is taken not from the current number of spots in the scene, and analyze the already occupied values of the number in the name and exclude them from the auto selection?

    Or generate a new name and check if it is already in the scene or not. If it is, generate a new one and check again)

    In general, this on large projects is very inconvenient when hotspots already created disappear ))))

    Hope there will be a solution)

    Thanks *thumbsup*

  • I decided not to wait and made a simple hotspot editor )

    I tried to do as few actions as possible when creating a hotspot.

    1. Point the crosshair at the place where the hotspot will be;
    2. Run a function specifying the name of the scene with which you want to connect the current one (I did it in the console to make it faster and to substitute for scene names *cool*);
    3. Automatically opens the scene with which you want to connect, at which you need to specify the position of the first scene with a crosshair;
    4. Call the second function (or with a button on the keyboard), which will automatically create a hotspot on each of these two scenes, automatically calculate the offset value for 3D transishen, and return to the original panorama).
    5. And so you can continue to arrange hotspot further as in the native editor. The main thing is not to refresh the browser page ))))

    And to save the changes, the third function is called, which copies the layout of all the scenes in the tour to the clipboard. And then it remains to replace the copied scenes in xml *g*.

    For me it was objectively faster to create a spot with transitions. In the native editor I needed to create about ~30sec, and with this only ~5-7sec ))))

    Here is a link to a video of the hotspot creation process: https://youtu.be/EBsWAsWAHqM

  • Custom tour creating is (imo) very labour intensive, and anything that can help to make the process faster / more easy is very welcome. That is why the user interface is so important for creating tours: if the UI is not fluid enough, people will stop using it cause it is too cumbersome to edit / link the panoramas.

    Thanks for sharing your ideas. Replace the javascript console by some UI buttons and you will have an even more streamlined process...

  • Yes, I understand that the user needs an interface *thumbup*

    But at this stage it is a forced measure to speed up the current task) And so yes, I agree that if you design normally need to add a form with an input field, which will be automatically substituted the name of the scene when you enter. And it's not hard to do)

    But what was interesting and new for me was that it turns out that there is a way to add elements to the tour in the browser, which will be saved when moving between panoramas and will not be lost. Thus you can fully implement the editor krpanotools.exe in the browser, and expand it to suit your needs *cool*

  • Nice thinking!

    Now I need to run a test: what if we have a way to :

    - open the tour in krpanotools

    - add elements using javascript

    - SAVE the tour using the krpanotools: will it save the things we added to the tour? *confused**confused*

    Then we could implement adding hotspots (like you did) in javascript, but still keep the "save" functionality (as browsers cannot save directly to local disk).

  • So with the script there is no need to open krpanotools. All the work happens inside the browser and only.

    Quote

    as browsers cannot save directly to local disk

    Who said that there are no options to save changes in the browser via js?) I made saving changes on js, where the script generates an xml file and gave to save with a request to save where to save. Here you just need to specify the file with replacement and that's it *cool*

  • Hi lastromantik, I really like your idea that saves the step of defining the point of view for the transition. *thumbsup*

    Please could you share the code with me? Sorry, I know I should try it myself based on your explanation and video but I would like to try your idea right now and I'm really stuck on another task at work. Thanks for your help. *smile*

  • Please could you share the code with me? Sorry, I know I should try it myself based on your explanation and video but I would like to try your idea right now and I'm really stuck on another task at work. Thanks for your help. *smile*

    Yes, basically no problem. I’ve long had ideas to make the editor convenient for everyone and free), so when I get to my computer I’ll download the current version of the editor for testing. I hope to receive feedback and suggestions to improve the editor)

    Or maybe it would be better for me to move this into a separate new topic? And put the sources there?

  • Hi lastromantik, thank you very much for sharing free!

    I think it would be better to have a new topic for the subject and to work together to perfect a hotspot editor.

    Actually the version that comes with krpano has problems when several scenes are linked. I also have compatibility problems between my GPU driver and the chrome version of krpanotools that crashes right in the hotspot editor. *confused*

    Please, if you have a preliminary, basic or incomplete version, it doesn't matter, you could send it to me so I can work on it. I was willing to make a code similar to yours to be able to enable my GPU driver, work with two monitors again.*g*

    Basically I had been thinking about the idea of placing 2 hotspots with the same name of the scene to which it is linked or perhaps automatically adding a prefix to these names. At the time of creating these hotspots, the initial view of each scene would also be saved and it would be a very efficient process. The calculation for the transition would be based on the difference in angles between the ath of hotspot 1 and hotspot 2.

    I'm sure there will be many comments and feedback from all of us on your final proposal that would help refine it and create a very useful tool.*thumbsup*

    Once again, thank you for your help.

    Greetings from Havana.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!