ComputerMaster86

I have fought with this for several versions now and it is beyond frustrating and annoying. I have wondered if this is a bug that has never been addressed or resolved. When using "Lower Wall Type if Split by Butting Roof" Chief doesn't like to honor your chosen wall type. I find it will typically change the wall chosen to the default interior wall type. The work around is to make sure your default interior wall type is the same as what you want for "Lower Wall Type if Split by Butting Roof". If you need to use more than one wall type in different "Lower Wall Type if Split by Butting Roof" scenarios then your screwed.

I just renewed my SSA and paid the same price I did about a year ago. My SSA renewal / expiration date is always in the middle of January. For me December is a great time to put some that Christmas $$$ towards renewing my SSA.

is there a limit to how many nestled folders the steam deck can have? (A folder inside a folder inside a folder)

I often send my plans views to layout with color turned off. There is a setting in preferences that controls whether turning color off does pure black and white or gray scale. I didn't know if this was anything related to the original issue but, I thought I would mention it.

Can't the Chief installation file be run choosing the repair option to get the font back. That's what I would try, if I mistakenly deleted the font that comes with Chief Architect .

Currently if you are using "Managed Mode" Chief Architect will not let you import PDF files, images, DWG's, etc. into your plan or layout file that are stored within a project. I have complained about this on the forum and requested that chief allow us to import things that are stored in our projects. If you import the item into the "Asset Manager" first, you can insert from the "Asset Manager" into a plan or layout file.

I will use my custom SFF computer as an example to give you an idea of what you may want to look for with specs. Right now I am running a computer that has an... AMD Ryzen 7-7700X 8-Core 16-Thread Socket AM5 CPU Rated at 4.5 Ghz This has been a great CPU overall but, you will may want to go with something with more cores. 64 GB's of DDR 5 6,000 Mt/s Memory via (2) 32 GB Modules (I am using the AMD Expo Profile) Some people will do just fine with 32 GB's of ram. This is probably overkill for me. 1 TB Samsung Pro NVME M.2 SSD I recommend bumping up to a 2TB drive or higher. nVidia RTX 3070 Super with 12 GB's on Board Memory This is OK and has served me well but, if you are doing lots of renderings you may want a more powerful graphics card. Many recommend a 4080 / 5080 or higher or something like the AMD Radeon 7900 XTX.

I have witnessed that several times in the past and would have to say the tool is far from perfect. It seems manual adjustments don't never want to stay. I struggle with complex roof/wall intersection points and wish for X18 chief could bring some improvements to that area.

Doesn't the "Edit Wall Layer Intersections" edit toolbar tool do what you are asking? I am not sure if it does anything for Grade beams at the wall. It's not perfect but, I have used this tool several times to manually clean-up wall intersections.

I almost always have "Walls" set to "Wall Dimension Layer" option and I notice I don't get that behavior when using the "Point to Point" dimension tool. Setting "Walls" to "Surface" I was able to replicate the same behavior but the behavior was replicated in both X16 and X17.

I just noticed another quirk with the same image. Man, I didn't even catch this yesterday. Below is the original export from Chief.

I just can't get over how many people think chat GPT is the greatest thing in world for generating these cool groovy renderings. I tried my hand at it just the other day but, I keep noticing little quirks. Fore example, in the picture below, a shingle ridge cap for a G-Rib steel panel roof. I didn't even notice it at first with my poor vision. Now I can't unsee it. Of course I have to be real and say how would chat GPT know that was a sheet metal roof. I didn't specify that in my prompt. With my limited knowledge of A.I., I wonder if I wrote a very lengthy prompt would it do a better job or would I confuse it more.

What I am having an issue with is the legacy Temporary Dimensions in X16 would reference the wall dimension layer when I would click on a door or window. It's doesn't seem to be doing that in X17.1 release. Its referencing the interior edge of the main layer of the wall. Below the screenshots were taken from X16.