OTOY Forums

Hi guys!

We've got a pretty big scene here and since we had a lot of problems with them recently, we decided to buy 1080Ti's to use a lot of vram they've got.

We had a setup of 2 workstations with 4x 980Ti's each on Win10. Our scene grew and grew, and it started this weird behaviour of replacing materials on some objects in PV - in LV everything was ok. We started exceeding the available VRAM, so we installed Win7 to utilise the rest of it. We started optimizing it crazy - making proxies out of everything and minimizing the number of materials, but nothing helped. The problems persisted and we had more and more trouble with crashing and - what we thought - too big of a scene.

Of course we tried it on 2 machines, couple versions of octane and plugin and 2 versions of drivers.

Now that we have couple of 1080Ti's and upcoming deadline, we had the same problem. So we went back a couple scene versions to the latest one that didn't have any errors, and started adding meshes and materials one by one. Now we have the same errors, can't find what causes them and it's quite possible we invested in 1080Ti's for nothing :/

Attaching 2 renders (4K, VR) and log of one of those. Can't attach scene because it's 600MB of super secret client-secrecy stuff.

If anyone knows what's going on - please share - we're wasting a lot of time to repair what we have and we still have to animate a lot :/

How is render settings? Any screen from whole parameters.

Hi Aoktar!

Oh man, we just found the issue. I can't believe we didn't check it sooner because it happened with a lot of objects, but only with the specific ones. It appears you can't have instances inside instances :/

For example we had a window which had 16 cloned instances of screws, and then this windows was instanced a couple times. Everything OK in LV, but crazy shit happens in PV.

We're changing everything in the scene and I guess we don't need those instances because we've got 1080Ti's anyway :/

it's not supported but will not be different for LV vs. PV. Make sure you are using "all movable" or "auto detect" in PV settings. These are noted in manual and adviced to read. Pls let me know if you cannot still solved the issue.

Just to let you guys know, we had this issue again without nested instances.

It appeared again on the same instanced objects and we just didn't instance them no more at all (they heavy though :/ )

byMELT wrote:Just to let you guys know, we had this issue again without nested instances.

It appeared again on the same instanced objects and we just didn't instance them no more at all (they heavy though :/ )

Are you using default values for render settings? How is your parameters?
Have you tried with 3.05.3?