rcmcdougle

I have done this, both in the current plan and in a new plan to save as template. These settings do not stick and I must (most of the time as my preferences sometimes linger) click through all the screens each time I render a walkthrough. I even need to double check the resolution each time as that seems to change at random intervals. It would seem we need to save that info on a per walkthrough basis just like saving a camera. It is really annoying to go through this selection process every time as I tweak lighting and/or camera angle on a 4 or 5 node walkthrough.

How do I set my defaults for a PBR render in record Walkthrough? Every time I click the record walkthrough button I must toggle through a few screens to get the render settings I want. Every time I select PBR, the dialog shows 1000 samples and the Cap option is not checked. I want 50 samples with Cap option. Ideally, PBR would be my default for Walkthrough render mode going forward. Is there a way to set this in X15?

"Could it have something to do with the recent issues with Intel processors?..." Many thanks for this Brett. That indeed was the case. My new high performance build came with a BIOS that was pre 14th gen processors. This in spite of the ads saying it supported those 13 and 14 gen processors. Asus Prime Z790-P arrived with BIOS1645 and it wasn't until #1680 something that they actually supported those processors. After MUCH hassel trying to flash the new #1805 BIOS, the system now passes the Intel processor test you pointed me to. When I initially ran that test it failed just like Chief did when it started the stress test. After updating the BIOS I have now run those walkthrough renders perfectly. I can see the temps getting high and the CPU slowing down but the renders are just as fast in PBR mode as they were in standard mode before the update to the BIOS. I have ordered an additional high speed case fan to help in those moments of stress.

When it crashes, everything is going along fine then Chief just disappears. The file is saved but incomplete. I have run this walkthrough multiple times and it always crashes in approximately the same placeI. I suspected the graphics driver so updated the driver with no change in crashing. It is always about the same location on each of 2 (out of 4) walkthroughs in that plan. The settings are the same for all of the PBR walkthroughs and 2 of the 4 complete fine. I then suspected overheating so loaded Libre Hardware Monitor to see what was going on with temps. The CPU temps maxed at 100° C frequently -.GPU stayed under 85° C. I aimed a hairdryer set to high blowing cool air directly at the CPU and it stayed under 80° C. It still crashed in approximately the same place. I can't undersatnd the differences in the performance of one walkthrough vs another in the same plan that succeeds.

Rebooting and re running the walkthrough with no other software running did not help. This on a recent VERY robust machine per my signature.

X15 is crashing halfway through PBR walkthrough. This has happened now 3 times with different paths that have previously rendered perfectly in standard view. Any thoughts?

It took a LOT of fiddling but I finally got it to reconnect there on the 4 way corner. All good now. Thanks for your help..

I tried to reconnect that railing and it does not reconnect. still showing the connection error.

Here is the plan file for investigators. I see that it actually started in x10. Long history on that project. Huyler-File4.zip

I have a weird railing problem on a plan brought forward from x14 to x15. The complex deck plan is defined and the heights are good. The client requested that I change the railings to cable rails which worked as expected. We then decided to go with a system that has posts and cables as a kit. I can change all railings to show that difference except the one that is different in that image below. ANY change (including just changing the color) to that railing results in the loss of that lower deck extension, all posts and framing, and the railing goes up to the height of the main deck per the second image. How can I make the required change? What setting might be creating this issue?

I have exposed rafter tails on a fairly some simple gable roofs. I want the siding to extend to the underside of the roof surface. How to do this?

I just installed x14 on a new computer (specs below) and many default items are wonky. The biggest problem is when I attempt to change materials on any object - roof, wall types, refrigerator - Chief goes dead. Endless blue wheelie with task manager showing no CPU utilization. I must "End Task" and restart. I usually get a more recently saved version prompt available; so I don't lose much work. I really dislike the ongoing anxiety this creates in a work environment that was rock solid previously. I have built the new box with drives and installations mapped exactly like previously. I still have the previous box sitting next to the new one. I'm wondering if there is some Chief configuration file I could bring over from the old box that would address all the wierdness. Old box was Windows 10 Pro - new box Windows 11 Pro updated.

Not sure how that all got changed but Locate was set to none for those dimension tools in the 1/4" scale dimensions in plan view. I'll now need to dig through my template plan to see what else is awry.

I just installed Chief x 14 on a new computer and some of the dimension tools are not working. Manual Dimension and End to End snap but fail to generate numbers or anything else. All other dimension tools seem to be OK. Any thoughts?

Thanks Renerabbitt. I missed that sample rate setting as I have set PBR samples to be capped to 100 in Preferences. It is now running about 10 frames a minute @100 samples. Is there a way to save the walkthrough settings in the same way you can save a camera? Given that there are 4 other floors above this apartment it did not occur to put a roof over it. I was wondering how to fix the light bleed. Do you have any sense of the impact of sharing the PCI lanes might have on the walkthrough render times? If it were meaningful, I would consider swapping the M2s for SSDs. Thanks again.