No, it wouldnt it needs to stitch the tiles together so would need memory for that. Same with save multiple in order for it to tonemap the image the entire buffer needs to be in memory.
Regards
Paul
Would Distributed rendering be a way to bypass this problem?
Ivo Blaauw= = = = = = = = = = = = =Look what the CAD dragged in...
Hi,
The issue is that to display the image in the luxology dialog for a 28800x28800 image requires 3gb of memory. Microstation is a 32bit application and cant allocate that much memory. The upcoming 64bit version of microstation will be able to display this.
Paul Chater
So even the latest Luxology update can not still remove the limits on the image size and resolution in the process of image rendering, right? Wow, hope there is a better and faster way to render high-resolution image.
On a previous project and an older version of luxology we had the same issue of (then) too large renders crashing.
The workaround that got us through was to set up and save the view as required, rendering a small sample image to get the "adapt to brightness" correct and saving those settings. Dragging the border of the view port halfway (allowing for some overlap), rendering at full resolution then recalling the view and dragging the opposite border to halfway, and rendering. Finally using photoshop to stitch the two halves together.
The few images we did this way were very nearly pixle perfect at the overlap...
Hope this helps