Kbird1

Thanks for posting back on the fix, I am sure it will help someone in the future, it's a pet peeve reading a thread only to find the last post says "tech support fixed it" ...but not how. M.

I thought perhaps the Garage Wall was somehow causing a break in the Attic Wall , there is a setting "allow lower Roof planes" (paraphased) but it doesn't always seem to work for some reason. Tech Support can be pretty quick, they'll send your plan back and usually tell you the fix etc which you should be just able to incorporate into the Plan you are working on, and the Layout should update when refreshed (update all views button). M.

is there perhaps a break in the Attic wall at that point both sides? if and auto attic wall perhaps try drawing your own too. M.

As far as I know, call chief to confirm, transfers have not been possible for 2-3 years, since they changed to a subscription only model. M.

I agree SVPs are very powerful, and it's fairly simple using duplicate to make one for each View needed along with a dedicated Default Set which includes dedicated Layersets etc. M.

sounds like you had a real bad migration experience so I understand not wanting to try that again but have you tried re-installing the Core Libraries from the Library Menu? Another thing I would try if above doesn't work is manually copying the X15 Textures Folder Contents into the X17 Textures Folder. (in the respective Chief Data Folder) M.

I was disappointed when Chief decided not to work directly with D5 to allow a seamless Plugin for us as well as the other Programs D5 supports. M.

Exactly the same no, as Rich said CPU RT has been around in Chief for 10-15yrs and is now deprecated and no longer worked on...... the Big difference is Speed by a magnitude of Order and should be very quick on a 5070 I imagine with sample set at say 250 but with either you will need to learn the basics of PBR as it isn't a single click and boom you have "photo" realistic Camera Views. M.

Worth a try to reset your toolbars as a test, as Rene mentioned, easiest way is to rename the toolbar folder in the X16 Data folder to OLDToolbars (Or whatever) while Chief is closed, then reopen Chief and Chief will copy the backups (in stored in ProgramFiles) to your Data Folder replacing the whole Toolbar folder with a fresh X16 copy. just reverse this to get YOUR Toolbars back if desired. Mick.

Are your toolbars unlock when you 1st start ? I have not seen the red circle no/stop icon doing this myself..... DB maybe right about a Tech Support Case through your digital locker. M.

Try dropping the new place Library icon just after the line of Dots at the beginning of a Custom Toolbar, the 1st Place Library Icon will start a new toolbar that you should be able to continue adding too.... * you can NOT add Icons to Chief's Std. OOB Toolbars , they are hardcoded and non-editable. You can also use the Toolbar Tab to select and delete rouge/unwanted toolbars and even name them as appropriate so you know they are ones you made .... Note my MHD Toolbars in 2nd image. Mick

There are many reports online about issues with the 572.xx series of drivers , including here in the Forum, 566.36 is recommended here is this article below , personally I have gone back to 546.92 for more stability but I had it saved locally , I think Nvidia will only have back to 560.xx. so be careful if you download from other places. https://wccftech.com/game-developers-are-discouraging-users-from-installing-nvidia-driver-572-xx-rtx-40/ Latest Driver Release is NOT recommended as at 31.3.25...see above ..... try 566.36 instead Desktop 566.36 Studio Driver https://www.nvidia.com/en-us/drivers/details/237785/ Laptop/Notebook 566.36 Studio Driver https://www.nvidia.com/en-us/drivers/details/237786/ Mick.

Personally I use a Solid in the same Material as the top of the Curb as that is likely what the Tiler will also use....

You may have a corrupt symbol or something ? if it only happening in 1 Plan file M.

In Preferences > Render tab > Video Card Status you will see what Driver Version Tech Support had you install Levina perhaps you can post a screen snip for others with this Issue... like this one..... ( the Nvidia Driver version is the last 5 digits in the Chief Driver Version No.# : 566.36 in my case currently)