Collective3D Modern Home

HI. I'm just seeking confirmation for what I'm experiencing with this product.
When loaded along with a single G2F character, the viewport becomes sluggish. When I switch to Aux Viewport and try to render with IPR, it stalls completely at 5%. Attempting a 3Delight render is incredibly slow compared to any other scene I have rendered recently.
I have a 2012 iMac with 24GB RAM and a 2GB GPU. I have tried turning off visibility of the areas that are not in view (the interior contents, walls and floors) but this has made no difference at all.
I have searched this forum but can't find any recent reference to this vendor's products. Any suggestions?
Comments
From the Product Page:
Leaving the grass out, should cut the poly total in half. It is a very large scene, and is equal to about 12 Genesis 2 Female figures at High Resolution.
You could try Edit > Preferences > Interface, and set Display Optimization to 'None'
Does hiding the grass (or deleting it from the scene) make any speed difference? (if so, have you any other grass options for rendering?).
I forgot to mention that I had already turned off the polygon grass - as in not loaded.
Here's the odd thing. I used the same product for a Luxrender scene about two weeks ago and it rendered quite quickly (for Lux). I've just cancelled a 3Delight render which was sitting at 10% after 40 minutes. At that rate it would take twice as long as the Luxrender scene (and that one had two characters - a G2F and a Genesis 1 - both fully clothed).
Just to be sure - does hiding (turning off visibility) make a difference or is it essential to delete items from the scene. I'm thinking about all the interior stuff that I made invisible.
"Removing from scene" is preferable to just making things "not visible". Simply put there is less to calculate.
So the render still calculates the polygons even though they will not be rendered? Seems a bit inefficient to me.
If they are actually hidden they will not affect renders, though they are still in memory and therefore having an imapct. But if they are simply made transparent they will affect renders as the only way to decide they are having no effect is to calculate their effect.
So hidden means turning the visibility off in the Scene tab as opposed to transparent meaning turning opacity to zero in the Surfaces tab, right?
So hidden means turning the visibility off in the Scene tab as opposed to transparent meaning turning opacity to zero in the Surfaces tab, right?
Yes, exactly.
Just turning down opacity isn't enough, there are other parameters (e.g. reflections, refractions) that can still have an effect until they're turned down to zero as well. Remember that glass, eye surface and water effects use an almost completely transparent material. It depends on the shader used, some parameters will still have a more obvious effect, some can be safely ignored. Switching things off in the scene tab is a one-click solution.
Exactly what I thought when I did switch those objects off in the Scene tab. However, it did not appear to speed up the render.
I checked with my RAM utility and I still had 9GB of my 24GB system RAM available so I was not out of memory. I had a single light which was a image on a sphere (UberEnvironment2).