Indigo Renderer Forum

Hi everyone,
I am currently trying to get a high quality image file of a render, I'm after 3500 x 2480 pixels. However, when I set render settings to this size I get the following error message:
Microsoft visual c++ runtime library runtime error!
Program:(location of indigo on my comp)
This program has requested the runtime to terminate it in an unusual way. Please contact the application support team for more info
So here I am support team!

Also, can someone tell me how to get a 300dpi rendered image file? Apparently it is possible as I have SU pro.

Thanks in advance for your help

As far as I can find out on other forums, I can't adjust above 72 dpi directly but can increase the output resolution bigger than I need and then shrink it in photoshop afterward to get a better effective dpi. However, whenever I render an output file above 3000 x 3000 pixels i get the error message as above. Does indigo not support images above this size??

I will be so grateful if someone can solve this for me, its likely that I have missed something obvious.

the problem is the amount of memory in your computer. Basically if you want to render that large you'll need to buy more memory or borrow someone else's computer and render on that.

this is unconnected to the 3000x3000 sketchup thing.

Ok, thanks for that remus, so what you're saying is that its terminating because it doesn't have enough resources??

yeah, pretty much.

ok, cant wait for my new machine to arrive then. Thanks for your help.

Can anyone else shed any light on the 300dpi thing?

0. get new computer, install 64bit operating system and use 64bit indigo
1. set supersample factor to 1 in settings file (not a problem with 300dpi)
2. render

little question for the experts and coders: why to set supersample value > 1?

Sorry for the naive question...

You could make use of shift lens, and render a quarter of the size at a time. You would have to tune the camera to the correct exposure first and, obviously, know hot wo use shift lens.

doesnt shift lens do strange things to the dof as well?

Pibuz wrote:little question for the experts and coders: why to set supersample value > 1?

Sorry for the naive question...

it's not a naive question at all, the effect is quite subtle! basically when you have very bright and sharp features in your image, not using supersampling can result in aliasing (jagged edges, as if there is no antialiasing).

so really there are two types of anti-aliasing, the normal splatting aa that produces the basic image (usually very smooth already), and then also a full-image supersampling that will clean up any remaining aliasing.

the reason i suggested not using supersampling (default is "2", which actually means 2x2 supersampling i.e. 4x) is because the usual aa is fine most of the time, and with a print at 300dpi you certainly won't be looking at individual "pixels" and really need that 75% memory reduction.

lyc wrote:0. get new computer, install 64bit operating system and use 64bit indigo
1. set supersample factor to 1 in settings file (not a problem with 300dpi)
2. render

Can someone explain to me what changing the supersample actually does? Sorry for being such a noob

you should apologise for not googling, not being a noob: http://en.wikipedia.org/wiki/Supersampling

haha good call

lyc wrote:0. get new computer, install 64bit operating system and use 64bit indigo
1. set supersample factor to 1 in settings file (not a problem with 300dpi)
2. render

Where is the settings file lyc? I feel I have missed something....