Designers_Ink

In the IAMDesign Catalog is some cable railing. When you are in the railing dialog box, change your railing type to "Panels", then click on the Newel/Baluster tab on the side and under the Panels area click on the library button. You can type in cable and it should bring up all of your cable railing options. You can then add top and bottom rails if you prefer and change your newel posts to something appropriate.

Same here. Are you using a laptop or desktop? What kind of video card are you running?

When you pull up a camera view, look at the bottom of the screen, and it should tell you how many surfaces you have in the model (i.e. Done: 146857 surfaces). If the number goes away, just rotate the camera view, and it will come back up. I'd be interested to see if you have a high number of surfaces in your model, which could slow things down. You can always do a "Backup Entire Plan" to a zip file and post it. That way we can pull up your model with your materials and see if it is model related or maybe a computer related issue if it opens fine in our systems.

It is the "my house.plan" file. If you click on the size header twice, it should sort by file size and bring it to the top of the list.

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.