... caused by having Render Instance active on Sphere instance. You can disable it, for it has no role with Corona (feature request - when activated "Use as Proxy")
Whoa man, where did you get that from!? I mean - sure, some things might not work correctly with render instances in IR, but overall, using render instances does have a significant beneficial effect on memory usage in your scenes, so if possible you should use them.
Sorry for jumping into the conversation like this, but would you mind elaborating why you think that render instances "have no role with Corona"? Thanks
Hehe...
Thanks for jumping in. Honestly I really had no clue until now. Was a gut feeling - an assumption, based on older tests when proxies was first introduced to Corona4D last year. At that time it felt like it did nothing & only manually made proxies had proven to be
efficient (excluding time to set it all up).
I did test again just now & it has quite an impact.
In a scene i had prepared for these tests, it 'shaves off' more than ~50% of data.
Render Instances OFF Viewport = 2 GB; Rendering = 6.5 GB
Render Instances ONViewport = 1.5 GB; Rendering = 3 GB
Really great!
Apologies for my ignorance & thanks again for pointing it out :)
Also, is there a list of what will not be displayed/rendered with IR (like mograph effectors, deformers, particles...)? If not, would you care to make one? To get better prepared and prevent any futile tests.
PS
IR starts to behave erratic after some time of continuous use - Exposure resets more & more frequently.