Error rendering with a bigger size in pixels

Xamo · Post by **Xamo** » Fri Sep 19, 2008 3:14 am

Hello everybody.

First: Congratulations to everybody. The software is amazing.

But I need help!

I'm a new user of Indigo.
I need to render to scenarios with an output of
3840x2160 pixels.
One of the scenes have more or less 1,5 million triangles. the igs file is about 240Mb.
I have successfully render an image of 800x450 of that scenario. Low spp, about 200. but when i want to render the full size image, Indigo reports a fatal error.
I did everything the same way as in the low resolution but change the size in pixel.
The last line of text in the log (when the fatal error occurs) is:
AutoFocus: setting camera focus distance to 74.27560 m. * the next line should be *
Master buffer size: xxxxxxxxx MB

Question...

Do you think is a problem of hardware? I have a adm 64 3200 and 1gb RAM and 90gb of free hard disk.
Any way I'm having problems to do the pigs also.

Ahh...
I'm using Sketchup 6 and skindigo 1.0.9 on windows xp 32

thanks

Jambert · Post by **Jambert** » Fri Sep 19, 2008 3:24 am

You need more ram and xp64 and indigo 1.0.9 64

or maybe try the ranch if it's professionnal work

http://www.ranchcomputing.com/I_index.php

Xamo · Post by **Xamo** » Fri Sep 19, 2008 3:37 am

Yes i believe that could be but, I can't even make the paked .pigs to send it to the ranch. In fact I'm planing to send it, at last one of them.

What i can't figure out is why if i'm only changing the size of the output image I cant pack it

thanks any way!

Jambert · Post by **Jambert** » Fri Sep 19, 2008 7:37 pm

Don't know, I never use packing

Pibuz · Post by **Pibuz** » Sat Sep 20, 2008 1:27 am

I think that's a RAM usage issue too..
Files too big to be stored in the RAM... sadly...
A workaround should be downloading and installing UBUNTU64bits (linux open source, so no additional costs...) and install indigo-64bits version. There, you could export your scene from windows and then render in linux..
If even the 64 bits version doesn't work, then i fear it's time to buy more RAM...

kwistenbiebel · Post by **kwistenbiebel** » Sat Sep 20, 2008 2:26 am

Yes, a RAM issue.
I was able to render images bigger than the one you state.
(8GB RAM vista 64 8core)

suvakas · Post by **suvakas** » Sat Sep 20, 2008 8:54 am

There is just no excuse of having only 1 GB of memory in our days.
You can barely run the latest windows version with that amount of mem.
Memory is currently very, very cheap.

Xamo · Post by **Xamo** » Sat Sep 20, 2008 9:16 pm

I agree. Is a ram problem. I bought 2Gb of memory, but can't render it anyway. The good news is that i can do the packing process.

I try to reduces the polygons until renders it, but i'm not satisfy with it.

Then I did a Blitz in the Ranch to check.
(I can't post it because i don't know how. Any body can tell me? I will try to find out later)
_________________________________________________________
And here comes another story. By the way Thanks to support, Fred at RanchComputing nice work around.

The think is: I packed the scene. I did fallowed all the advices in the users guide.
but,

1 I left the packed.igs default name.
2 I used NK_data

when I submit the work I received the scal email with the terrifying bad news:

"We are sorry, but your project "_artevileBLITZ" is not a valid Indigo project and cannot be processed.
Reason: the .vui archive does not contain a valid Indigo scene (.igs)."

I emailed support because I knew it had to be OK. !!

The conclusion was that they had a parse problem because my packed.igs name. They are changing his automated parse program to not jump the "packed" names. I guess that's not a problem any more.
when they ran it again came the second problem:

2 The NK_data is not right packed.

There is a bugg in the packaging process. I have observed two issues:

1 the files AL.nk, PL.nk, etc. don't appear in the package. but they are in the scene TX_folder of the unpacked scene.

2 issue, the address where the program looks for the data is absolute... Of course that couldn't work on a package you want to send to somebody else to render. They have to be converted to relative address or just look for them in the root folder where the other textures are and make sure that the *.nk data is there (point 1)

(Maybe these bugg issue deserve a particular post.):arrow:

__________________________________________________________
Well back to my renders...

Do you think that if I could render a packed scene with 1000x500 and ranch too, when i pack the exactly scene but 3000x1500 and send it to ranch without checking if it renders properly because my computer just can't do it, will have problems in the ranch render farm? it could change that much or just the xml file statement: With and height? I don't know how complex this could be?
If i have to be the first to try,then i will have to take the risks!

Kram1032 · Post by **Kram1032** » Sat Sep 20, 2008 9:19 pm

click on "post reply" for more options than you have with "quick reply"

Xamo · Post by **Xamo** » Sat Sep 20, 2008 9:20 pm

Pibuz. I will try UBUNTU64 too.
Thanks

jambe · Post by **jambe** » Thu Nov 27, 2008 5:10 am

I am having the same problem in with SkIndigo_1_1_12, but not a problem with SkIndigo_1_0_9. Does the new version handle RAM differently.

Error rendering with a bigger size in pixels

Error rendering with a bigger size in pixels

Who is online