The reality is this:
To display in fullscreen you need a minimum of 3000x1500 to have any chance at decent quality with 4000x2000 being recommended (my view) this doesn't sit well with the download optimum speeds for multi view tours as the file size is too large (typically).
My suggestion is this:
Disable fullscreen mode from your tour totally and size your panorama tour images to suit a normal tour window. Say 500x375 and make the images 2 1/2 to 3 times the height of the viewer window I.E: 1500x750.
If you need the option to show fullscreen you should build a separate tour that default starts in fullscreen mode and link to it from your first tour. 4000x2000 image size. A simple fullscreen button will suffice, opening a completely new tour in fullscreen mode.
The problem with this is computer memory java resources.
Really what is needed is a way to have "both" Hi-Res and Lo-Res images within the single Tourweaver tour.
You really can't expect people to view a tour (wait for download and have enough memory) to cope with half a dozen (or more) pre-loading full screen high resolution panoramas. This easily can be well over 15MB on top of your original tour!
I really personally still think that a normal Java tour with each scene linking to a full screen Quicktime movie is the best option.
Regards, Smooth
|