Cindigo 2.0.5 - beta 1

[zeitmeister]

This is awesome, fused!
I suppose in indigo, these are real proxies... But what are they in C4D?
Instances, Xrefs or proxies, too? How many memory do they cause in C4D?

[fused]

In C4D they are proxies, sort of.

They dont generate any geometry and because of that they dont use any extra ram. they just need a few extra GPU cycles. They draw much faster than C4D instances, especially in bounding box mode.

[zeitmeister]

This is fantastic!
So you pushed C4D instances far beyond what MAXON did... I can't remember for how long user asked for real proxies in C4D.

Sell your knowledge to them!

[fused]

nah, its really just a simple thing. also those arent rendered in the c4d internal renderer. its possible but would require copying again. think i could build that in that when the internal renderer is launched the geometry is copied. not sure if i will, tho.

[zeitmeister]

Why should you? It would be a nice feature, indeed, but not a necessary one.
I'm not sure how the VRay4C4D-people solved it.

[fused]

ok, i built it in now that indigo instances can be converted to geometry and will be converted to geometry in the external render (aka rendering in picture viewer).

should be used with caution, tho. ram usage will explode when instancing heavy geometry.

[fused]

some proof

[fused]

! now it draws the real objects, too. no extra RAM usage

[Rafaello]

You are cinema's programming God or ... something like that

[zeitmeister]

[pixie]

! now it draws the real objects, too. no extra RAM usage

What are the difference of cindigo's instances and cinema own instances? Why should we use one and not the other?

[zeitmeister]

Instances are copies of geometry, which are computed all the time, which costs or causes memory.
Proxies are some kind of place-holders of geometry which are computed only during the render process, and so the don't cost any memory.
With proxies you can realize a huge amount of copies of a mesh without any more expense of memory when viewing or editing the scene, or even building the scene in any renderer. They only come out during the rendering.

C4D instances cost the same memory as a simple copy of your mesh... and sometimes even more, because the are updated in realtime.
Proxies don't, because they don't need to be.

That's the real big deal!
It allows you to create millions of copies of a mesh, f.e. a wood, grass, cityscapes, swarms or something like these without having the need for enough memory for that.

[fused]

exactly.

[Zom-B]

This looks really nice fused... I'm sure we will see this feture for C4D Maxwell exporters at least when 2.0 is out

It allows you to create millions of copies of a mesh, f.e. a wood, grass, cityscapes, swarms or something like these without having the need for enough memory for that.

I think your GPU will show you the finger at some point here... but the system RAM should not be affected.

[pixie]

Instances are copies of geometry, which are computed all the time, which costs or causes memory.
Proxies are some kind of place-holders of geometry which are computed only during the render process, and so the don't cost any memory.
With proxies you can realize a huge amount of copies of a mesh without any more expense of memory when viewing or editing the scene, or even building the scene in any renderer. They only come out during the rendering.

C4D instances cost the same memory as a simple copy of your mesh... and sometimes even more, because the are updated in realtime.
Proxies don't, because they don't need to be.

That's the real big deal!
It allows you to create millions of copies of a mesh, f.e. a wood, grass, cityscapes, swarms or something like these without having the need for enough memory for that.

Thanks for the info!

Does anyone know what filetypes are supported and how do I know what materials are applied...