Indigo 1.1.14
- Borgleader
- Posts: 2149
- Joined: Mon Jun 16, 2008 10:48 am
I think I ran out of memory
Was trying to build an indigo scene with the stargate model from LotRJ and... I got this

I'll try again at home on my desktop with twice the RAMIndigo.exe wrote:Fatal Error: IndigoDriverExcep: ObjectExcep: Exception while building tree: Memory allocation failed.
Stopped.
benn hired a mercenary to kill my sig...
indigo error
I use indigo 1.1.14 and blendigo 1.1.13 when run render indigo show me this message:
Fatal Error: IndigoDriverExcep: SceneLoaderExcep: Syntax error while parsing Vec3 from '-1.#IND00 -1.#IND00 -1.#IND00'
Stopped.
Can help me?
Fatal Error: IndigoDriverExcep: SceneLoaderExcep: Syntax error while parsing Vec3 from '-1.#IND00 -1.#IND00 -1.#IND00'
Stopped.
Can help me?
- Attachments
-
- Immagine.jpg (13.16 KiB) Viewed 7340 times
actually it's a question for Blendigo/Exporter thread.
share your scene
share your scene
Last edited by SmartDen on Thu Nov 06, 2008 3:46 am, edited 2 times in total.
Check normals, dude!




I have the same kind of data sometimes from procedurally generated geometry (obj files), when a vertex position could not be determined (or out of range ?) by the objExport plugin.
I thought I would request OnoSendai to somewhat handle that kind of undetermined data, but didn't until today
The workaround for obj files is to manually edit the undetermined value from:
toor any values actually.
I thought I would request OnoSendai to somewhat handle that kind of undetermined data, but didn't until today
The workaround for obj files is to manually edit the undetermined value from:
Code: Select all
v -1.#IND -1.#IND -1.#INDto
Code: Select all
v 0 0 0obsolete asset
ok, after some major changes to the export routine i got Cindigo to export 160.000 instances (with the "Indigo Instance"). Im sure it can handle MUCH more (if your graphics card can handle the ammount of stuff that needs to be drawn in the viewport)
Some infos about the renderings:
rendered for 6h in 3200x1600, resitzed to 1600x1200.
exactly 160.000 instances, each 28.05 million polygons.
making a total of 4.889.187.200.000 polygons (4.8 trillion polygons).
for the large version click on the image.


Some infos about the renderings:
rendered for 6h in 3200x1600, resitzed to 1600x1200.
exactly 160.000 instances, each 28.05 million polygons.
making a total of 4.889.187.200.000 polygons (4.8 trillion polygons).
for the large version click on the image.


- Borgleader
- Posts: 2149
- Joined: Mon Jun 16, 2008 10:48 am
- Phr0stByte
- Posts: 395
- Joined: Wed Nov 22, 2006 5:07 am
- Location: Centreville, VA
- Contact:
Who is online
Users browsing this forum: No registered users and 14 guests


