Tour loading/Pano sizesSome of you will remember me from a few years back when I was far more active on the site. Alas been tied up with other stuff but am starting to rollout pano work again and am creating 4 new tours to Demo next week. They'll still be in TW5 demo mode however I'll appreciatte any comments. Looks like I'll be waiting for the bugs in TW6 to be ironed out before an upgrade becomes viable. However i have a few questions in the meantime...
This may be a dumb question... but do TW5 and 6 tours load the skin and elements and all the panos and photos before the tour stars or do the individual panos and photos get loaded individually by request from the serverfile? Large tours would obviously take a wee bit to load otherwise.
I've been experimenting with Pano sizes and is a well discussed topic. I've been outputting 4000x2000 px panos which look good in the 900x600 screenviewer format I prefer as well as in full screen. However am happy for advice and views. (obviously we can't make everyone happy and I've been trying to keep images files at 1-1.3MB) I also noticed that the image sometimes judders and will experiment with slower turning speeds... but if anyone has any ideas here. (I tested on basic PC laptop and Mac book 17' pro without issues... it was on the topend MAC with huge 1900 screen res where then problem lay which may just arise due to the masive screen size.)
Also has anyone any thoughts on photos? I tend to sharpen etc. images so that they look great at a given resolution eg 900x600 but whilst the images still look OK in fullscreen... they're not great. Am I right in asuming that EP doesn't allow us to image dump in DB and then auto-resize to screen res with appropriatte sharpening to image size?
If I only had an hour to chop down a tree... I'd spend 45 mins sharpening the axe.