a selective problem, meaning sometimes it works, sometimes it doesn't. Just wondering if this is commonly encountered: checking out gallery sites, and various examples taken from the Forum, I find that on about half of the sites I get an "unable to load the XML" message. Of course, the Viewpoint test cube works fine... does this sound like anything obvious or familiar?...

Hi Robert,

It could be that some of the pages from the gallery are no longer available. Some people post their content their for peer review and some weeks or months later it's taken offline. The older the link the more likely that it's been removed, as is usually the way.

If you could post the URLs to a few examples, we can see if it's a problem you're having, a problem they're having or if it's just no longer available content.

I recommend you also try the demos from the viewpoint site, you shouldn't find any outdated links there.

If you're having problems from the viewpoint website demos also then please give us more information regarding your machine's configuration. OS version, browser version, viewpoint media player version and installation history would be most useful.

Thanks,

-Derek

some examples from the first page of user's gallery, these were all posted by 39clocks: triizon.com, vizitech.com, kythe.com. I am running into this XML doesn't load thing so often I really doubt that it is dead links. On the other hand, the Eddie Bauer site works fine, the demos on VP main page work fine. Just for background, I am a longtime RayDreamStudio user and had done quite a bit of Metastream... my browser is IE5 on Win 98/P3600/ASUS/ATI.

let me just add this follow-on regarding the player installation: I had installed the player a couple of months ago (not sure what #) but asssuming there may be an update, I used your auto-install feature the other day - you presumably have this engineered so that it works to check/refresh/update... anyway, the cube appears, functions fine, which I take as a good-to-go. How does your player handle this inevitable issue of the user having to update/overwrite the plug-in version?... presumably a transparent process, right?