Renerabbitt

Lol you used all the exact right combinations of render settings for that to not show up. Raster views it will show correct and vector elevation should show but may need the pattern offset and scale adjusted

A user came in posting Ai responses for Revit and I mentioned that it was the wrong forum for that. Then the user got downvoted and the admin removed his post. I think he thought that I caused that so they started going to all of my recent posts and adding downvotes. That user is now gone, but the negative votes dont retroactively get removed

Turn auto-build terrain on by opening up your terrain perimeter. Also while selected in plan view, convert your closed polyline to a road(perimeter) using the convert tool in the edit toolbar. Recommend turning your terrain perimeter into a rectangle see video: 260529 (8).mp4

This will handle that elevation, just delete any intermediate newels when you use it: Custom Railing For Allen.calibz

This just needs normal map to show the relieve between the slats

260528 (5).mp4

responding to be notified when posted

please post your plan so we can illustrate a fix. You can use a free service like wetransfer or if you have cloud storage to share the plan file

I think it should be built exactly as the search attributes editor window is built

see video 260519 (2).mp4

yes 24gb of unified memory is really low. This is shared memory, so much of that gets hogged by loading textures regardless of raytrace being turned on or not. Thats like running with 15gb of RAM and 9 gb of VRAM..that is really low in this program especially if you are running other programs. For instance, i have 8 browser tabs open, some standard services running and chief open with no plan open and my system shows 28% utilization on 128GB of RAM

totally different development departments and different animals. It's very easy for the content team to pump out cabinet lines vs touching the extremely complex window code that none of the dev team wants to touch. (Supposedly one of the most difficult and complex bits of code in the whole software) I agree though that I would love some window improvements

This is unified memory, so without your specs its hard to say but I would venture a guess that youre hitting mem limits. Also the Pro chip is not going to be anywhere near the max chip with double the raytrace speed...for what you do, I would upgrade

Your current machine is totally fine for chief. I would venture a guess that you either have a corrupted model or you need a driver update. I would update the driver and create an example project using the OOTB template to test your machine, a 3070 is good enough. Set your raytrace settings to use DLSS