[little bug+question] render size+Indigo 4 linux
[little bug+question] render size+Indigo 4 linux
Hi all! I've recently encountered some limitations launching a rendering, so i decided to post a question here.
My problem is render size: i try to render a scene at 1750x1200 and it all goes ok. But if i try to render the same scene even 1800x(xxxx) indigo crashes for a C++ problem, even if i don't exceed my available RAM. The fact is that a very simple scene DOES render at the same size and more (even 2552x xxxx), so i don't know what it is...You guys have an idea?
(I use Indigo+SkIndigo)
Second thing is the request: does indigo for linux support a Linux Live CD? I mean: could i launch linux from a cd, then read my exported igs from a folder in a memory stick with an indigo put in the same memory stick? Just to know if
My problem is render size: i try to render a scene at 1750x1200 and it all goes ok. But if i try to render the same scene even 1800x(xxxx) indigo crashes for a C++ problem, even if i don't exceed my available RAM. The fact is that a very simple scene DOES render at the same size and more (even 2552x xxxx), so i don't know what it is...You guys have an idea?
(I use Indigo+SkIndigo)
Second thing is the request: does indigo for linux support a Linux Live CD? I mean: could i launch linux from a cd, then read my exported igs from a folder in a memory stick with an indigo put in the same memory stick? Just to know if
Hey Pibuz...
The issue you described is related to RAM usage...
As long as you use 32bit Indigo, the app will crash before reaching 2GB of RAM usage!!
You can somehow patch Indigo to be LAA able and use 2GB RAM without crashing on 32bit...
I can't remember who told me how-to-do this :/
The issue you described is related to RAM usage...
As long as you use 32bit Indigo, the app will crash before reaching 2GB of RAM usage!!
You can somehow patch Indigo to be LAA able and use 2GB RAM without crashing on 32bit...
I can't remember who told me how-to-do this :/
polygonmanufaktur.de
In theory optimized Applications can use a max of 2GB in 32bit!Pibuz wrote:So my guess is: is this 2GB ram a limitation of the program itself?
But afaik Indigo isn't this way optimized and crashes beneath this 2GB RAM usage :/
I think BbB was the guy who told once on how to patch Indigo to use LAA and handle 2GB of RAM in 32bit mode!?
try to use console mode, reduce Super Sampling or force Bounding Interval by reducing "bih_tri_threshold" to 1 to save more RAM!
polygonmanufaktur.de
Hi again! I'm trying to launch a render with Indigo4linux64bits, but i can't find how... 
SO sorry to bother you again...
Can anyone post a screenshot or a simple short tut showing how to launch an indigo render with linux64bits? I have already exported my .igs scene (within Windows OS), so i have my 1.igs and 1-settings.igs files (and the texture folder..
..sorry again guys...

SO sorry to bother you again...



Can anyone post a screenshot or a simple short tut showing how to launch an indigo render with linux64bits? I have already exported my .igs scene (within Windows OS), so i have my 1.igs and 1-settings.igs files (and the texture folder..
..sorry again guys...
Oh, and since you exported in Windows, your texture paths and nk data paths are going to be hosed, more than likely.
Manually go into your IGS and find all the file paths you can see to be relative and use a forward slash (so remove drive and folder from the reference: C:\Indigo\Textures\texture.jpg becomes simply textures/texture.jpg - then put the textures folder directly inside your Indigo directory)
Manually go into your IGS and find all the file paths you can see to be relative and use a forward slash (so remove drive and folder from the reference: C:\Indigo\Textures\texture.jpg becomes simply textures/texture.jpg - then put the textures folder directly inside your Indigo directory)
Who is online
Users browsing this forum: No registered users and 4 guests