OTOY Forums

[gk] wrote:You got savable mesh position, light position, camera position and resolution from the scripts.
It should be a simple task to render a 10k image with this approach.

I don't think that this is as easy as you think.

As soon as you move the camera, you will get a different perspective on the scene.

Not with proper offset and shift type movements. It's the same plane and focal origin (sensor or camera pivot doesn't move, lens around it does), just a different section, even if you could manually combine them later, it's possible.

true, but shift planes aren't supported yet in octane afaik.

I'll send this topic link to my engineers at Cubix Visual, and ask them to test a dual C1060 configuration this week with a file that's greater than 4K x 4K resolution. Once completed, we'll post the results here and at Cubix for review.

EricNV

what would be possible is some kind of panorama job (stichable with stitcher or photoshop)

Thanks Eric, looking forward for the results of your tests.

Posted the same question on the demo thread before purchasing and got some good feedback about resolution limits.

the hardware maximum a video card can render : 4096x4096
4096x4096 takes up 320MB of video card memory.

did the math and it works out to .078125 MB of memory needed for every pixel (it's linear). So you could load a scene and figure out how large a render your card can handle with the remaining memory.

Raidance said they were looking at solutions for larger rendersizes, so it's on the radar

maudeeb wrote:Posted the same question on the demo thread before purchasing and got some good feedback about resolution limits.

the hardware maximum a video card can render : 4096x4096
4096x4096 takes up 320MB of video card memory.

did the math and it works out to .078125 MB of memory needed for every pixel (it's linear). So you could load a scene and figure out how large a render your card can handle with the remaining memory.

Raidance said they were looking at solutions for larger rendersizes, so it's on the radar

While it has been discussed on a few threads, there seems to be some confusion on this matter. Some members are stating that there is a hardware limit, while others seem to be stating that they can go above this limit.

As far as I know, there has never been an official statement on this issue.

It would be good to hear from Octane on this issue...

Is there a render limit size? If so, what is the limit and what is imposing the limit (Octane or graphics card)?

I noticed, Arion also has same limitation. And it is solving this issue with network rendering.
If this issue is too hard to implement in a system, network rendering would be another solution to solve this issue, as Arion did.