Re: [PanoToolsNG] ptviewer loading to only 80%, but not all the time
- We ran into this problem too. When a JVM is started in a browser, it
has a maximum memory size of about 60-80MB depending on browser.
Since PTViewer fully decompresses the file in memory to do it's
thing, this puts an upper limit on the pano size unless you change
the JVM memory size, which isn't practical unless you're the only one
viewing the pano. This is discussed further here:
In practice, the best way to maximize the size of image you can
display with PTViewer (and probably any java viewer for that matter)
1) Slice the image into 10 slices (this reduces the amount of memory
needed while initially loading the pano. AFAIK only PTViewer 2.8
2) Don't make a pano have more than about 3,500,000 pixels.
I spent hours playing with these parameters testing in multiple
browsers, and these are the settings that maximize pic size for any
Here's an example of the output of such an image. Click "Full
Screen". Looks and works great even on my 24" iMac.
On Jun 17, 2007, at 9:30 AM, stryker wrote:
> Some time ago I started a project I've returned to; a collection of
> shots taken on a trip last year which includes several panoramas.
> I started out with ptviewer and got the first few panos done to my
> satisfaction, but hit a bit of a wall when I tried to get partial
> panoramas to display. At the time the consensus among more
> experienced people assisting is the file sizes were too big for java.
> This is still a problem I'm wrestling with but not the main reason
> for this post.
> What I'm finding is that even my 360 degree panoramas intermittently
> don't load past 80%. The documentation says this means the file has
> loaded but not been decompressed. I've converted them to .ptv format
> with a greyscale 25% low res preview. One that suffers this is a
> 1,836kB file. Is this typical/common? Should I scale it smaller still?
> Thanks for your advice,
[Non-text portions of this message have been removed]