 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
Pages: 1
Please have a look at the picture. In this example I'm trying to stitch an HDR pano with 11 exposures per set. I had the same problem with APG3 B1 and I still wasn't able to try APG3.
I do have HDR spherical panoramas with sequences with 15 exposure per set and doesn't work either!
There must be a solution: it can't really be "not enough memory"!
Also, the odd thing is that there isn't any antighost activated in the "render options tab".
Last edited by marco.lanciani (2012-10-16 15:44:09)
Offline
I've found the solution. I just changed the dimension of 'cache division' from 'Auto' to '4MB'.
Why this huge limitation with HDR panos? The more the number of images per HDR set, the more little the final dimension of the rendered pano.
Offline
The auto mode in cache division is calibrated for standard panorama, not for HDR. The issue with this value, is that this value is global and should be per panorama. So that we could adjust the cache at each new rendering. This is hard to achieve. So decide to go with a value that is more current than 11 image stacks.
But you find the right solution : the cache size value is the value to change to prevent this message.
Offline
Hello,
After a deeper look at your case, we found that the test of the memory capabilities is not as expected, so we opened issue 1549 for that.
Thanks for reporting this issue.
Thomas
Offline
Also, I don't know if this can help but I don't have any problem with large group of images, which involves many images per bracketed set, in APG2.6.3.
Thanks for the support!
Offline
Pages: 1