Hey thanks both of you for the feedback and looking into this! I wonder if you have a minute, could you help me understand a few things?
Hopki- 1) you point at that several icon files are missing. When I output the project, I went through and deleted some of the media files that I ended up not using in the tour, as well as all of the skin icon files that I knew were not being used (eg the fisheye.svg, etc). There was no real reason I did this, other than I thought it would be tidier and slightly reduce the size of the overall project to be uploaded by our site vendor.
Was this a mistake? Should I have left those unused files in the project?? I'm wondering if this is causing the tour not to work properly in Internet Explorer?
2) You also mentioned that the tour is single resolution. I had originally created the tour using multi-resolution set to 500px tiles. The overall project (10 nodes) was huge- around 500mb. When I switched to single resolution, w cube faces at 3500px, the project size was reduced by more than half. Was this a mistake as well? My concern was that the larger the total project, the more potential data would be consumed by visitors and could incur costs, but perhaps I'm not understanding multi-res well enough.
360Texas- can you explain those cookie errors? I've just done some quick googling, and the only info I can find says that these are not technically 'errors' but rather Chrome warning about a standard that should be adopted.
Hopki, please let me know if you'd rather I email all of this to support. I'll still aim to send you a single node tour to check that other glitch.
I really appreciate your guys help on this! It is the first project using Pano2VR I've used at this museum, and we are keen to adopt this across other uses in our local district council, so if I can get to the bottom of these issues and make things work more smoothly it will only encourage the higher-ups to use Pano2Vr and perhaps purchase more licenses
Yeah I have no idea about that one my friend. If no one else replies today I will check to see if I can duplicate the issue on my end when I get home. 
