Everything working ok on PC with IE, Chrome, FF, Safari, Opera and Mac with Safari, Chrome and FF. Android phone ok, but some problems the bottom menu not staying pinned to bottom if you have overlay content that needs you to scroll down (same in Anroid browser, Dolphin, Opera, but FF much better). However, big problem is with iOS (iPhone 4 and iPad 1) as have some pages with only few images and supersize works great, but two pages that crash. Only difference is these two pages have lots of images. To recap, all ok in all other browsers but iPad and iPhone crash. Site is under development so will see lots od dead links but here is the main page: www.fantasticnorth.no/startup.html (ok), also ok are www.fantasticnorth.no/omgivelser/index.html and www.fantasticnorth.no/rorbu/index.html, but problem is on these two: www.fantasticnorth.no/landhandel/index.html and www.fantasticnorth.no/bolighus/index.html

Hello Ian.

I see the problem. I will discuss your issue with our developers and will notify you here in the thread about the possible solutions.

Best Regards: Vulcho.

I have been testing. I get considerably better results (number of slides that can be in show without crashing) if I turn off thumbnail view and thumbnail navigation. With these on then iOS can only handle about 12 pictures. I also tested for file size and results are same if images are 640x480 or 1200x800. I was also using a Spry Collapsible Panel on the page (std component in DW) and swapped this out with a jqrey equivalent so eveything was on jquery, but this did not affect test results or improve performance with respect to limitation on number of slides when dmx supersize played on iPad/iPhone.

After working with and around the limitations in Supersized's number of images limitation for iOS and crashing in iOS, the site is now final and live. You can see it here: www.fantasticnorth.no - despite the limitations/problems with Supersized the site is still quite an eye catcher! :-)

Fantastic work Ian. And yes, there are limitations on IPhone,Ipad. We will try to find a workaround for the next update of the product.

Regards:Vulcho.