Skip to main content
L
LineP
Known Participant
September 24, 2018
Question

No response when I click on 360 hotspots

  • September 24, 2018
  • 2 replies
  • 1004 views

Hi,

I'm the lucky owner of a 360 camera. But in Captivate I have a little issue getting it to work properly on LMS-servers and Chrome generally.

When I upload my project to our LMS or SCORM Cloud there is no response when I click on the hotspots on a 360 photo no matter which browser. When I preview it in Captivate there is no problem running it in either Chrome or Firefox.


When I export and run the project locally, the hotspots only react in Firefox.

Any ideas?

Kind regards,

Jacob

    This topic has been closed for replies.

    2 replies

    F
    focused_Charm0D45
    Participating Frequently
    April 12, 2019

    Same problem for me, too.  Preview using HTML5 Browser from within Captivate allows the hotspot (set to continue, jump to slide, etc.) to function.  But playback of the published to computer version (pubbed as HTML5) in either Chrome or Edge does not work - the hotspot is non-functional.  Something isn't getting translated into the published version, I think.  Edge should work, at least, since the Preview in Captivate is using Edge to playback, in my case.  My Chrome and Edge browser versions are very up-to-date.  I downloaded and installed the first update to Captivate 2019, as well.  I need the hotspots to work, else there is little use for them for our learners from the LMS.  Help!

    Lilybiri
    Lilybiri
    Legend
    April 12, 2019

    Did you test the published file after uploading to a LMS or webserver?

    F
    focused_Charm0D45
    Participating Frequently
    April 12, 2019

    Yes, the published file (zipped first, then unzipped to a folder, then launched using the index file) did not work locally in Edge, Chrome.  Nor did the file play the hotspot from Cornerstone LMS.  If it won't work locally, it probably won't work from the LMS either.

    I have not tried pubbing without zipping, but I will do that next, to be sure it isn't something in the zipping process.  I saw something about not using the scalable switch also, because of some problem with the active hotspot location misregistered with the hotspot icon, but we absolutely must use scalable, because of the various sizes of our viewing devices and viewing full screen.

    L
    LinePAuthor
    Known Participant
    October 1, 2018

    Hmmmm

    THREE.ImageUtils.loadTexture is being deprecated. Use THREE.TextureLoader() instead.

    Seems that there are some call back errors with the js?

    Am I right?

    /Jacob

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices