I know this is a stretch, but has anyone been able to make a workaround for controlling some aspects of a VR project:
Firstly, I've realised that it's better to create a regular project and insert VR slides, but that aside...
OK I've answered one item from my list above:
The icon images can be found in the published folder in dr/ (as they always have been)
I've also noticed a bunch of console errors - the THREE JS library is throwing dozens of deprecated errors. It'd be great if these were updated!
because I'm too into Captivate VR projects and looking to extend the basic workings of those I want to reach out to you for an exchange of experiences.
The most interesting and challenging point of your post is No. 5) how to assign Actions or JS to hotspots. Well, I'm trying the same. But there isn't much to go on.
That's all greyed out. I named my hotspots in one project with logical Ids but it is impossible to locate them as elements in the HTML structure. There's a <canvas> and that's it. It doesn't go any deeper to attach any eventlisteners and such. If there would be something like I know from Adobe Animate HTML5 canvas where one can utilize createJS to control elements for triggering events that would be wonderful. Though it doesn't look like that in Captivate.
You are saying "that I've managed to achieve some of this using the A-Frame JS library" - well, I looked at A-frame which is based on three.js I believe - could you describe in a few words how and what you've managed?
Your point "Zooming in / out on a VR slide - how is this possible?" - I fear it's not. At least for now and the current version of CP.
From your own reply: "the THREE JS library is throwing dozens of deprecated errors" - these warnings are actually written into the CPM.js which CP itself publishes with one's project. So in my project there is for example in line 51234 this code in CPM.js:
console.warn( 'THREE.ImageUtils.loadTexture has been deprecated. Use THREE.TextureLoader() instead.' );
All of the deprecated warnings (not errors) which I encounter are all coded in CPM.js in this way.
In the end, please bombard Adobe with Feature Requests in this matter. I'll plan to do the same. If CP VR remains as poor as it is now I would have to consider another way (like A-frame perhaps) for my VR experiments.
Stay in contact if you like