Image resolution

[Proupin]

That's what shift does, likewise zooming in and out does not distort as long as you don't move the camera. Just try it, do a render, zoom in like 3x factor, and use shift to render a 3x3 grid, it's exactly the same

[p3taoctane]

ill def try that
thanks

[p3taoctane]

I'm a little confused and maybe a little SLOW TOO
I see how the lens shift works great. Depth of field etc all kept in tact. BUT if you have a 1000x1000 res and you lens shift ONLY your only generating portions of a 1000x1000 right? So when you piece it together and crop you will end up with same thing.

If you zoom in at all are you not changing everything about your camera view and hence dof etc?

[p3taoctane]

yeah mate just tried it .... no autofocus or vigneting etc... when I zoom in the whole DOF gets radically whacked. Maybe I am messing up with something...

I realize it is probably my user error... But I can't seem to get it going

Any chance you can send me a scene that works for you with something really basic like a sphere or something... ?

Must in my moron mode

[Proupin]

ok, i read ur post... zoom in by changing the FOV, not by middle mouse button dragging in and out, that moves the camera and ruins everything (doing a proper test right now)

[p3taoctane]

Yep Im a moron

Thanks that did it

Appreciate the feedback

Peter

[p3taoctane]

Thanks Proupin

Saved my bacon... have to do a wall.... and was wondering how the heck to do it big enough...

Draft attached

[roeland]

You can indeed decrease the FOV value and use the lensShift to render the image in tiles. Some more remarks on this:
- If you set the FOV to 1/3 of the original value and render 3×3 tiles the FOV of the stitched image will be slightly less than the original image. For instance to get a 60° FOV you need to set the FOV to 21.79° instead of 20°.
- A lens shift of 1.0 means the image will shift exactly one time the image with or height, so if you render 3×3 tiles you need the values -1, 0, 1; for 4×4 tiles use -1.5, -0.5, 0.5, 1.5 .

If you want to calculate the exact FOV value for the tiles (for example the total FOV is 60°):
- divide the angle by two and calculate the tangens : tan(60° / 2) = 0.577
- divide this by the number of tiles: 0.192
- calculate the arctangens and double the number. 2 * atan(0.192) = 21.79°.

--
Roeland

[p3taoctane]

Cool
Thanks Roeland

Peter

[rappet]

Yes, thanks indeed to Roeland.
I have making use of this splitting and it workes perfectly.

I have not tried bi res in octane 2 yet.
Is the maximum res of 8192 still there?
and if so, will this maximum resolution of 8192 be there for a while?

Is the limit it about the total max of 8192x8192 a safeguard for users not to use too much ram,
Or is it not possible yet to program more then 8192 in numbers.
If the first one is the reason, why Is then i.e. 16x4k or 32k2k pixels not possible?
Or is it?

Greetz,