Designers_Ink

https://www.dropbox.com/scl/fi/yf0hojdjgwbnacdt9zjak/MyHouse-Saved-Camera-View.zip?rlkey=ox562d0dceck1dc4hmkjuil44&dl=0 I did some tweaking on the camera settings and added some light sources. You should be able to see the settings I used when you open up the saved camera in the living room.

Do a Backup Entire Plan into a Zip file and upload it so we can open the model up and take a look.

Try turning your sunlight setting way down to about 1200. In the camera dbx, make sure your Lighting setting is set to light set and not automatic with all the lights on you want to see in the camera view. This will help Chief by ignoring the rooms so that you get light in the distant rooms and not just the room and floor the camera is located in. In a two-story room like this, this will let all the lights show up in the camera view correctly. You can also turn down the backdrop intensity in the PBR settings until you can clearly see your background. If those suggestions do not work, post the plan and we can play with it about to troubleshoot the problem.

Generate your framing. Then in your camera view inside the room, select the Delete Surface button which is an S with an X through it. Then click on the drywall. It will just delete that surface. Then if you have other layers between the drywall and framing, just keep clicking until you are down to framing exposed. It is like peeling an onion.

There were actually several which touched on the issue that had the same solution mentioned. Some also discussed tweaking the voltage, but that wasn’t necessary to fix my issue. I just googled “14900k crashes” can the first several ones contained good info. Some were Reddit Gamer groups that had good info. Let me know if you have trouble finding them, and I will go back in my history at the office and send you the specific ones. Jeff

There apparently is an issue with the 14900K and even in some cases the 13900K with the default settings on most motherboards. When I started having issues, the first thing I did was reset all of the settings on my motherboard to the defaults hoping that would cure the issue. I even replaced the ASUS motherboard with an MSI motherboard, but the issue persisted. I spent many, many hours on the phone with various tech support centers to try to find a solution, as well as just trying everything I could to ensure there was not a faulty piece of hardware on the computer. It was extremely frustrating. Yesterday, I was reading some gamer forums since gamers tend to spend a lot of time tweaking their systems. I found a thread that dealt with crashes with the 14900K i9 CPU. They were having crashes in several games when the GPU (graphics card) kicked in with a high load on the power, especially when an RTX 4090 card was in use. They had found that the default settings for the Performance Active-Core Ratio (P-Core) on most motherboards was set to around 57x. They suggested backing that down to 54x to resolve the issue using the Intel Extreme Tuning Utility App. I downloaded the software and changed each P-Core from 57x to 54x and rebooted. After about 6 hours of continuous use and many refreshes of the plot line elevations, I have not had any crashes. I hope this helps someone who might be having similar issues, so they don't spend an exhaustive number of hours trying to pinpoint a solution like I did.

Make sure you have checked the Automatically regenerate deck framing box in the Room Specs.

Today I switched out Motherboard, but the problem did not resolve. I also switched out RAM and the power supply to see if that helped to narrow down the issue, but no changes. I then switched out my 4090 for a 3090 I had in another company that opens the files just fine. With the 3090 in the new computer, the problem was just the same. I am also getting more crashes just moving around the model with full camera, both in standard and PBR mode. Sometimes Chief just shuts down, and sometimes it locks up the whole computer.

It seems to do it on all of my plans. I keep my patterns pretty simple with no material generated patterns because I found those always seemed to slow things down. I was hoping it was something as simple as a bad RAM module on my new build, but I have done several Memory Diagnostics checks with no errors found. I have also switched the slots the memory is in hoping it might just be a bad slot or a poorly seated module. When I looked at the Windows event log today, I found that the crash events all had different modules it says was the problem child. They were the UCRTBASE.DLL, NTDLL.DLL, QT6CORE.DLL, ASTRALRENDER.DLL, TKERNAL.DLL, CONCRT140.DLL and CACOMMON.DLL. It seems like it is not just one thing, but the crashes all seem to happen when I am either updating a plot line elevation view, or still sometimes when I am editing the model in a 3D view. Today it crashed twice doing a 360 panoramic view save. So frustrating... I appreciate the advice.

Another piece of the puzzle.... The problem only occurs when the view has plot lines. If I go to a non-vector view with live updates, even with line overlays, it is not a problem. But if I update the plot lines, it crashes immediately. We have tried uninstalling the current driver, and going back a couple of different versions for both Studio and Game Ready versions. A new driver just came out, and I was hopeful it would solve the issue, but no luck. I worked through every solution NVIDIA Tech Support had to offer, and they finally gave up saying it had to be related to Chief. I even tried switching out my 4090 to my older 3090, and the problem persisted. Oddly enough, the issue with editing while in a 3D camera resolved (for the most part) when I ran Chief in Compatibility Mode. I could at least work on my files (other than updating an elevation view in my .layout file) without it crashing every few minutes. I have to take the file over to my draftsman's computer to update the view in layout, but at least I can work without it crashing every few minutes.

For the past couple of weeks, Chief has been crashed on my computer when I attempt to update an elevation view. I was also seeing an issue where Chief crashed when I tried to edit the model in a 3D camera view. Sometimes Chief just expectedly closes and somethings I get the Blue Screen of Death with various error messages. I am running a new computer that is about six weeks old with all updated drivers. I have tested each component with the help of my computer manufacturer (Digital Storm) and NVIDIA tech support with no issues found in the hardware. The computer is not overclocked, and I have done a complete re-install of Windows 11 Pro and all my software. My BIOS is set to all of the default settings, and my NVIDIA RTX 4090 is set to all of the default settings. The files work fine on my other computer, so I don't think the .plan or .layout files are corrupted. I thought I was alone in this, but I found a post today on a Chief Facebook site where someone else was experiencing the same issue. I have been working with Chief Tech Support for awhile now, and they were going through my logs to attempt to find the source of the problem. I am just curious if anyone else is having this issue in hopes of finding others so we can compare notes to try to troubleshoot the problem more easily. If you are having a similar issue, I would encourage you to contact Chief Tech Support as well. Thanks,

Select one wall, the click on the Select Similar Objects button. It looks like a cross with 4 dots and a mouse arrow. Mine is on the bottom toolbar. Then just draw a square around your whole model. It will only select the walls. Then click the Open Object (door) button to open the dialog box.

You have at least one wall that is marked "No Room Definition" in the wall DBX. Just select all of the walls and open the dialog. There will be a dash next to that setting. Click it until the box is empty, and you should be good.

I just bought the Cigman CD-60 which has the dual lasers. It works really well, and it is about $100 on Amazon.

Give this a shot 65030LF-PC1.skp

See if this works for you. Brizo Faucet.calibz

When I first got my system, I had similar problems with overheating. I finally resolved the issue with buying a larger power supply than what came with the system. I haven't had an overheating issue since.

Kuula.co is what I use to create walk through 360 panoramics. It works pretty well. https://kuula.co/share/collection/7PXyr?logo=1&info=0&logosize=114&fs=1&vr=1&zoom=1&initload=0&autorotate=0.38&thumbs=1 https://kuula.co/share/collection/79HxW?logo=1&info=0&logosize=114&fs=1&vr=1&zoom=1&initload=0&autorotate=0.38&thumbs=1

Turn your sunlight down to about 300 and see if that fixes it.

Instead of adding them in using the door dbx, go to the library browser and manually place the rail, handle and wheels in the plan. They will show up in plan view, and you can adjust the locations in elevation view. You can still use the hardware in the door dbx so it shows up correctly in 3D when opening and closing, and just change the layer of the manually applied hardware to a CAD layer and turn it off in 3D view so it only appears in plan view.

Stole it from another recent project for a classic car collector. Didn't figure he would mind me joyriding it to another project.

I threw it down on an as-built model I'm working on before starting the addition and remodel. It definitely makes a difference in the grass realism.

One you have the image like you want it, go to File, then Export Picture. You can then change the format to .jpg, .png, or other options before you save it.

https://www.rabbittdesign.net/shop/p/rabs-closet-shelf-system This has been worth every penny for me. Simple to use, and very you can customize things so many different ways since it is based on cabinets. I also still use the old Canyon Creek - Closets Plus catalog. It goes away if you update their catalog, so you have to install an older version of it and rename it so it doesn't get overridden in the next update.

https://www.stonecurators.com/stone-designer/ This site has a pretty good collection of stone textures and patterns which can be customized and downloaded for use in Chief. Just thought I'd share in case it is useful to someone else besides me.