Renerabbitt

I never use this feature for my template creation. it affects to many things that I want to remain unaffected. this means I have to be VERY careful about not drawing any rooms. I've never truly understood when or why chief architect rememebers rooms but i find it easiest to just make sure i dont draw one. I then do a practice plan to dial in my layout and links etc, and any changes i make i then either have to import or duplicate into the blank layout and plan.

yall forget that I consider Mark the cabinet master..not the other way around Man is a wealth of knowledge

This conv better in chat most likely but I give 40% off to all previous purchasers. There are update codes in the accounts tab when you login. There's also a bout a billion hours of development since you last purchased, ha...probably some things you might really like.

very cool. this is the system in X18 thats more for spec but can handle any information output to a csv: 260702.mp4

I built this for my X17 templates. it read right from CSV automatically and while in project management mode. I personally loved it, but again was too complicated for scalability. Not only does a system have to be hands off and intuitive but it also has to handle modification and unique parameters if I were to distribute. All in all, even though it was only a few steps to setup, I had user after user wanting to setup unique parameters and naming conventions that would break the system. It was very cool though for my own personal workflow to just tell my ai agent to go look up my last meeting and update my designer/client info based on that into a csv and then open chief up and see it all there.

Your system is not all that different from mine conceptually. You and I just have very different needs. Keep in mind that I distribute my templates, and they need to be workable for beginner to intermediate Chief technicians. Because of that, above everything else, the system has to be user-friendly with very little need for additional process documentation. It also cannot be overly specific to our California code requirements, which would be 10x overkill for most of the rest of the world. It also has to be intuitive from the perspective of someone completely new. Like you mentioned, it took you a long time to build your system. It also took me a long time to discover what is actually intuitive to an end user versus what I personally perceived to be intuitive. Designer, client, and project information all come from a Project Information plan. This allows someone to easily swap out that file with other versions they have built by copying it, which can be used for things like changing the title block, logo, design load criteria, specifications, and so on. This is not just California-specific. The system does have automatic lookup for a few criteria across several states. Previously, I had automatic spec switching based on project city, state, zip code, or country for NBC Canada. But again, even that became a bit too complex for the end user. Now, with X18, the end user simply types the code criteria they want, such as “2025 IRC,” into Project Information, and the spec switches through a macro. So at the base level, all the end user has to do is swap out their logo, fill out their designer information, and enter the code criteria fields. Simple user input. The macros handle the rest. I strongly dislike gathering data from polylines. I find them to be the least intuitive for end users, and they carry the most liability because the user has to manually update them whenever the building model changes. Because of that, my area analysis comes from a room schedule with some macro magic that allows for adjustments. In other words, site analysis is coming from the building model itself. Thats the bulk of what I have on my G1 page or G001 for you maybe I have three template pages: two scaled pages, one at 1/4" and one at 1/2", and one no-scale template page. Switching the template changes the scale annotation and adds a graphical scale. That is all I am including in a base-level plan intended for distribution.

YES YES YES YES YES and more YES Mine also executes as soon as layout is opened, without ever opening the plan file because the polyline is alongside of those information blocks and they are sent to layout 260702.mp4

yeah he posted it here on chieftalk somewhere a long time ago. I have a bunch of pages of notes in onedrive from things all of the macro guys have said over the years. I use it in a plan file. the plan file is setup for all title block info and spec writing on your general sheet so its easy to swap out when i change jurisdictions or who I am drafting for etc. all of this gets sent to different parts of layout and this polyline has all of the captures

I was on a training call yesterday and, as I often do, I started by giving you big compliments. But I also mentioned that no one could simply pick up one of your layouts or plans and immediately understand how everything works. The workflow is incredibly specific, with a lot of knowledge required to perform even simple tasks, plus all the unique layers and layer sets involved. You and I wouldnt need this but its nice for end-use All that to say, leaving a macro call inside a value is a smart way for the template to automate a task while still giving the end user one easy place to override that automation when needed. In other words, its great for scalability without the need for unique training. I always hear Kevin Transue screaming from the rooftops "inheritanceeeeeee" Why this dbx was designed in a way that didnt just inherit properties from other similar dbx is what he would be referring to. Why isnt there a "user input dbx standard" module thats just plug and play so that it behaves similarly to the project browser/library browser or the "add lights" dbx? as in a displayed polyline or other object with a label that says %$chief_project_zipcode="%project.zip/postal_code%";""% yeah...same wish +1000

this copies your layout with all of its established linked plan files into a new folder within your existing project. This will be a completely separate layout with linked plan files that will have no links to the originals

260623 (3).mp4

Fairly easy solution: 260623.mp4

Turn off automatic fillers, and select your cabinet and add an extended stile

Not really a Chief-specific issue on either of those fronts, at least not from a software development standpoint. On the rendering side, Chief’s path tracer and other GPU-dependent features rely heavily on the graphics API and driver support available from the operating system and hardware vendor. On Windows, that generally means working through DirectX / GPU driver support from NVIDIA, AMD, and Intel. On macOS, that means working through Apple’s Metal API. If Apple’s Metal implementation or developer support is lacking(WHICH IT WAS), delayed, or not responsive to support tickets, there is only so much Chief can do from their end. They can optimize within the tools Apple provides, but they cannot rewrite Apple’s graphics stack or force Apple to prioritize bugs that affect a relatively small professional CAD/rendering market. Same general idea with LiDAR. Apple has a very mature and well-documented development ecosystem around their LiDAR hardware, including ARKit, RoomPlan, depth APIs, and device-level support. Developers building scan-based workflows have a relatively clear path on iPhones and iPads because Apple controls the hardware, operating system, camera stack, sensor calibration, and API access. Competing platforms are much more fragmented. Even if another phone technically has depth sensing, LiDAR, time-of-flight, or some other spatial scanning capability, the development tools may not be as standardized, consistent, or commercially viable. Android devices vary widely by manufacturer, sensor package, camera pipeline, OS version, and API support. That makes it much harder for a company like Chief to build and maintain a reliable scan-to-plan workflow across a broad range of non-Apple devices. I wouldnt point the finger at Chief is all

you can, its just imported as a fixture. It's very easy to align the walls by nudging them until they are in plane with the obj file. You just need a matterpak

FYI there is a forum dedicated to Home Designer, most of the users here won't be aware of the limitations of the home designer line https://hometalk.chiefarchitect.com/

rotate the 2x4 instead of changing the width and height

Obj

A new computer is not going to solve this issue, I have a slower laptop with far more outdated tech and a massive 14gb library and it is outperforming your machine. Trust me, I train 100's of members, you have either some very high poly count models or a series of pattern from texture material files. This is sequential read/write dependent and CPU, driven, and your existing CPU and hard drive are on PCI4. You are plenty fast enough, so I guarantee you that this is not a computer issue

Food for thought 260611.mp4

FINALLY I am not alone, I knew one day it would happen. Symmbols were broken in X15, I have been reporting it for several years now and I am the only user to report it. please report it, please please please. Any symbol with a negative bounding box spacing, specifically negative, and a stretch plane will NOT resize correctly. It has been broken since they introduced the advanced sizing panel and change the way symbols can be modified. I have been begging them to fix it. @Brian_Beck

more important question is whats the surface count of the model. 4 stories isnt that much. You might want to update your signature to include your machine specs so we have additional context

This smells very strongly of a material file with a custom pattern from texture enabled, causing 100s if not thousands of vector lines. I've reported this before and Chief doesnt believe me but a custom pattern from texture can kill a plan or library.

Some easier methods for you that are snappable: Use points from CAD/Points/Place Points. They are snappable and do not print Use the Snap Grid and snap your drawings to the same points Send your view once, then use the copy with paste hold position to a new sheet to maintain position, then use the relink tool to relink to the view you want. This will maintain position exactly Hope that helps see video: 260602.mp4