Hi,
On 23/12/10 04:19, Blake Mason wrote:
If you just need to create a high resoultion rendering from of a single
frame, you can modify the camera's projection matrix to capture many
smaller segments, something like this:
camera-setProjectionMatrix(projMat * osg::Matrix::scale(xSegments,
If you just need to create a high resoultion rendering from of a single
frame, you can modify the camera's projection matrix to capture many
smaller segments, something like this:
camera-setProjectionMatrix(projMat * osg::Matrix::scale(xSegments,
ySegments, 1.0) *
Hi Geoff,
I don't believe that OSG enforces any type of image size limit. I
suspect that your computer is simply running out of memory trying to
allocate that much contiguous memory (over 5 GB for that image).
The good news is that OSG does have a framework in place that can help
you handle
Hi Geoff,
I let you do the sums... 64250x22500x4=...
Then work out how much memory do you have on your computer... the
exception will be a memory exception...
The OSG itself doesn't limit most OSG data structures including
osg::Image, so it's very much a case of garbage in, garbage out. If
Did you step into the code and see why is failing ?
I don't have access to OSG right now to look at the source myself but your
probably limited to the max size support by Openly and your graphics card
and driver.
Which is likely to be 4096x4096 and on many newer cards thatÂ’s 8192x8192
Or if a
Hi,
Thanks for the response. For some reason I never thought about running out of
memory, and I am only catching a general exception. I've been playing around
with Photoshop, and just assumed that since it could open the image of that
size, that it should be fine. Guess it uses a lot of the
On 12/21/2010 12:54 PM, Geoff Rhodes wrote:
Hi,
Thanks for the response. For some reason I never thought about running out of
memory, and I am only catching a general exception. I've been playing around
with Photoshop, and just assumed that since it could open the image of that
size, that it
7 matches
Mail list logo
