Stuck on Calculating Displacement

[BigAl3D]

So I've worked with this scene before. I even posted about the best way to get a rug texture into a PBR material. Now using Substance Sample which does a pretty nice job. Anyway, I was even able to use the Interactive Viewport with enough speed that it was usable. Yesterday, I downloaded several furniture assets from Cosmos and added to this scene so I could do a quick render with good lighting to show someone. It seems to get stuck on Displacement now. I've let it go for overnight (12 hours) with no success. I then deleted all the proxies of the new models and romoved their materials. Same thing. Stuck on Calculating Displacement. I quit any app that uses a lot of RAM. Rebooted for a fresh start. Same thing. Downgraded from v9 Daily to v8 Hotfix 1. Same problem. Tried two versions of C4D. No luck.

I can easily go back to the original scene so it's not the end of the world. I'm just looking for advice on troubleshooting this problem for any future project that I can't afford to start over.

iMac Pro, 128 GB RAM
OS Montery 12.5.1

[burnin]

Check Render settings > Performance Settings > Displacement> Screen Size (px): 2 <<< go ^ XXL, to see where you're at. Then gradually lower, until you find your sweet spot.

--------------------
Q. for devs:
Is there a "String option" to globally disable Displacement (switch it on/off)?

[BigAl3D]

Looks like it's at the default of 2. OK, so after changing this to 8 and trying again, I got a new error. Something about the Scene Bounding Box Being Too Large. So I checked the scene scale. All good. Then I selected all objects and hit the letter O. This will zoom the view to include all objects in your current selection. Curiously, everything disappeared. Long story short, I repeated this process, but only selecting one group of objects at a time. Everything worked until I hit one object, the Main Walls, then everything disappeared again. Progress. I had modified this object the other day. So I selected all the point and hit Optimize. Now when I hit O, boom. Back to normal and I can see the objects again.

Now it renders again! Yahoo! Your tip got me in the right direction.

Now I need to learn more about the pixel size setting and, aside from RAM usage, why I would need to adjust it. Would it render faster? I know there is probably a loss of detail at some point.

[burnin]

I assume your "runaway point" made bounding box "too large" (out of bounds for safe computing) and too small of a displacement value made machine too compute that long & far... it's unable to think "OoB" :) in this regard it's worth knowing about FPP - float-point precision, which defines hard limits for "virtual" worlds, and brings lots of incomprehensible issues for hairless apes, which is even more cumbersome handling it on GPUs (half size;) so "View Clipping", "nanites" & ultra fast EEC memory units are coming to rescue... in short, render-time micro-poly adaptive displacement is similar stuff in "off-line" rendering with more virtual space/numbers to  maneuver, also more complex thus slower, yet more precise still and relative. In both, user can define "View Clipping".

Hope you can sum it up and extract some to further find directions in this meandering matrix...

[busra]

I have the same problem but I couldn't fix this situation. Is an object in the scene causing this? Can you help me?

[BigAl3D]

Read my last post above. Did you check that you don't have any objects or axis point very far from your scene center? Is there a specific error? Hard to tell without see the scene. If you can share privately, I'd be willing to take a look if no one else has any ideas. You would have to collect with assets of course.

[busra]

max only shows these errors

[BigAl3D]

There is that one large EXR texture file, but if you have the RAM still shouldn't be a problem. In your first image, it is calculating displacement? I don't see it shown.

I think my issue was I used a purchased model and I modified it. Deleting some parts, but there was one vertex point sitting by itself VERY far from the model. This made the scene too large and either stopped rendering or caused the long calculation times. Don't know what your Object Manager looks like or how it's organized, but if you have a parent with a munch of mesh objects,