Dermot

Your cabinets are included in your cabinet schedule. Your cabinets also have "Show Schedule Callout" turned off. Your cabinet schedule is setup to only display callouts. So even when you uncheck "Suppress Label" they will not display a label. Do you want to your cabinets to display callouts, labels, or both? Open up your cabinet schedule and choose the appropriate option. Open up your cabinets and uncheck "Suppress Label" for any cabinets that you want to ever show a label. Also, check "Show Schedule Callout" for any cabinet that you want to ever show a schedule callout. In general, you should only check "Suppress Label" for a cabinet that you never want to show a label. For example, something that you are modelling with a cabinet but it is not really a cabinet. In general, you should not uncheck "Show Schedule Callout" unless you have a cabinet in a cabinet schedule but you don't want it to ever display the callout. Most of the time, if you don't want a callout you might not want it to appear in your cabinet schedule either and you can just uncheck "Include in Schedule" instead.

We are not aware of any problems with cabinet labels in X15. As a general rule, cabinet labels would not be suppressed by default so I am not sure why you would have had to uncheck suppress unless you actually suppressed them for some reason. The other thing you might want to check is to see what layer the cabinet label is using. Since labels can be manually placed on any layer, you should check that the actual layer is turned on. One easy way to do this is to select the cabinet and look what layers show up in either the Object Layer Properties dialog or the Active Layer Display Options side window. The other thing you might want to do is to post your plan on this forum. I'm sure someone would be able to figure out the problem very quickly without having to make guesses. Also, please remember that X15 is currently a beta version. If you find any problems at all, you should always report them to our tech support team: https://www.chiefarchitect.com/support/

Probably a video card driver issue related to your Windows update. See if this tech article helps: https://www.chiefarchitect.com/support/article/KB-00106/troubleshooting-3d-camera-view-display-problems-in-chief-architect.html If not, then I recommend contacting our tech support team.

It adjusts the height and is only used when using a reference plan in a camera view. And if you would like to try it out, the X15 beta is now available.

You might want to check out this tech article for some trouble shooting info: https://www.chiefarchitect.com/support/article/KB-00937/license-security.html If that doesn't help then you may need to contact our customer service or tech support team for more help. They will be back in the office on Monday during our normal business hours.

The short answer is that the "custom" option is only enabled for sliding, pocket, or bifold doors. For a more complete answer (including some workarounds), see this prior thread:

Please note that this is just a very small subset of the new features that are coming in X15. As for the reference display, we are going to have the ability to offset and rotate the reference display which will allow some more flexibility in how it can be used.

Yes, it would be possible to add all of the same parametric door controls to cabinet doors, including the ability to adjust the rails and stiles or add divided lites. It just isn't as easy as you might think. The fundamental problem is that the code for the parametric doors was developed specifically for standard doors and we would need to make it more general purpose (and clean it up a bit) in order to use this same code for cabinet doors. This is a project that is currently on our lengthy todo list but I am not sure when we will be getting to it. If you would like to see this happen sooner rather than later, then I would encourage you to submit a feature request. We use the number of people that request a particular feature to help us to determine its priority. The more people that ask, the higher up the list it moves.

Basically, you will need to install X14 on your new computer, activate the license, and then transfer all of the data you want from the old computer to the new computer. This tech article has some more info about managing your license: https://www.chiefarchitect.com/support/article/KB-00956/using-chief-architect-on-multiple-computers.html For more information about transferring your plans, libraries, templates, and other settings from your old computer to your new computer, see this tech article: https://www.chiefarchitect.com/support/article/KB-00001/backing-up-chief-architect-content.html

We are currently testing X15 Beta 1 with a small group of experienced beta testers. We will begin testing X15 Beta 2 with a larger group of beta testers in the near future. If you have already sent in a request to participate in our beta testing program, we should start contacting people in the next week or two with more information. Please note that you will be asked to sign an NDA since this is still a private beta test. We will probably start our Beta 2 test with just our Beta 1 testers and then expand the test team as we progress. Our goal is to make sure the program is fully functional with no known serious problems before we send it out. More information about participating in Beta 2 can be found here: We will also be having a public beta test of X15 that should start some time early next year. This beta test will be open to all users who have SSA active through the end of the beta test period and you will not be required to sign an NDA.

We have no reports of any problems like this. If you can reproduce this problem, then please report this to our technical support team. You will need to include your layout and all of your referenced plan files along with the steps needed to reproduce this problem (such as what you did right before you used undo).

Just trying to confirm that I understood you since I was having a hard time following your posts. I also thought it was important to note that depending on how a person models the panel, reducing the cabinet depth and then stretching it may not work the way they want. I modeled the 3/4" thick raised panel to accurately match my kitchen cabinets. There are a lot of different ways to build doors and this is just one example. A symmetrical profile for the raised panel might work better for a normal door and should work similar whether you use a 3/4" or 1.5" deep cabinet. You would want to remove the back in this case though.

@Scotbow Please contact our technical support team for help with this issue.

Yes, I believe you are correct. If you make the cabinet deeper than 3/4", you will get one or more extra lines along the door edges in vector views (or other line drawings). If removing these lines is important, you can leave the cabinet 3/4" and stretch the symbol instead. This may affect what kind of panel symbol you can use though. If you are using a 3/4 panel symbol like I am, and you are using match front for the cabinet back face, then the panel symbol will overlap itself. This is more obvious if you create a cross section or a glass house view of the door. To prevent this, you could just turn off the back face instead. Since I wanted the door to be the same on both sides, and I did not want to create a new panel profile, I was OK with the extra lines along the edge. BTW, if you would like to see these lines before you create a symbol out of a cabinet, you can turn on the layer for cabinet module lines and they will show up in a vector view. This will also give you a better indication of how the cabinet builds the stiles and rails for the face frame. See the picture below. I have updated the Door Symbol Designer plan in my previous post to turn this layer on. I have also set the cabinet depth for the door to 1.5" to reduce the edge line to a single line.

I have done something similar in the past and was demonstrating this in the recent advanced training class at the Chief Academy. - I used a counter top with an edge molding profile to create a simple raised panel. You could do this using many different tools but I like the counter top because I can swap out the molding profile to create different raised panels. This counter top can then be converted into a cabinet door symbol. You will need to rotate it and setup stretch planes for it to work well. - You can use this new symbol as the panel symbol for a 3/4" deep cabinet with no back. The big advantage of using a cabinet for this is that you have full control over the width of your stiles and rails and you can create basically any configuration for a raised panel door using the cabinet face editing tools. The split and equalize tools are super helpful. Once you have a door style you like, you can convert it into a cabinet door symbol for use on other cabinets. - You can also use this technique for creating normal doors by making the 3/4 deep cabinet thicker and using match front for the back. Again, as a cabinet you can configure the face however you like. It's also easy to extend this to create a garage panel as well. An X14 plan demonstrating the technique attached. Door Symbol Designer.plan

We released an update to X14 (24.2.2.1) yesterday that should correct the issue with the program "freezing" or "locking up". Please note that you may not receive an automatic update notification right away depending on your preference settings and when you last ran the program. If you would like to get the update now, you can find it along with the update notes here: https://www.chiefarchitect.com/support/updates.html If you continue to experience any problems in X14, then please contact our technical support team: https://www.chiefarchitect.com/support/

As far as I know, there is nothing wrong with the update notifications. You should not assume that the notifications are not working just because you did not get a message less than 24 hours after we posted the update.

As far as I know, there is nothing wrong with the update notifications. You should not assume that the notifications are not working just because you did not get a message less than 24 hours after we posted the update.

We have just posted an update for X14 (24.2.1) that should correct this problem. You can find the update here: https://www.chiefarchitect.com/support/updates.html You can find the update notes here: Chief Architect X14 Update Notes - 7/20/2022 If you continue to see any problems after downloading and installing this update, please contact our technical support team: https://www.chiefarchitect.com/support/

We have received a number of reports about this problem and are currently looking into it. When we have a fix for this problem we will try to get an update out as soon as possible. As far as I can tell, it is only a problem when your monitor scaling is set to something other than 100%. You may be able to temporarily work around this problem by resetting your monitor to 100%. Please note that if you have multiple monitors, you may need to reset all of your monitors. If this does not solve your problem, then please contact our technical support team for further assistance. The other solution would be to uninstall the 14.2 update and install the prior 14.1 update instead. If you need help doing this, then please contact our tech support team. I apologize for any inconvenience that this is causing.

I will stand by my statements. I will qualify them though by mentioning that we will be releasing an update to X14 in the near future that does address a number of issues in X14, some of which are new issues in X14 that were not in X13. I am not aware of any problems that are a direct result of bringing a legacy plan or template forward though. I have seen a number of posts on Chieftalk speculating that bringing plans forward is a problem but that certainly doesn't make it true. I do not think these random layout lines has anything to do with bringing a plan forward. And, as far as I can tell, no one has actually reported this to us. I have not been able to reproduce any problems like this myself, so unless someone actually reports it to us, there is really not much we can do about it. And if someone does report it to us, and tech support asks them for more information, and they don't follow up with them, then it probably won't get solved any time soon. Oh, and on a side note, I was not the person that gave Mick the downvotes, although I fully expect that I will be accused of doing it.

There are no known issues bringing plans forward.* *Other than the ones that we have documented in the X14 Migration Guide: https://cloud.chiefarchitect.com/1/pdf/documentation/chief-architect-x14-migration-guide.pdf If you think you have found an issue bringing a plan forward from any previous version of Chief Architect, then you should report this to our tech support team. You will need to include the original plan that was saved in previous version along with a good description of the problems/differences that you have found in X14. As for bringing your template plans forward, I have said this before but maybe it needs repeating, if we didn't think you should bring templates forward, we wouldn't include them in the migration tools. See this thread for some of my previous comments about this:

Newel posts on landing corners can sometimes be "finicky". If the lower stair does not have a railing, then the upper stair probably won't put a post on the landing the way it maybe should. Regardless, adding a newel post manually is probably way easier than trying to trick the stair/landing to build one for you when it doesn't want to. If there is a situation where you think the program should do something that it isn't, then you should probably report this to our tech support team and include the plan that demonstrates the problem.

Yes, shift-select the stair you want to change and then open the stair dialog.

Please don't turn off the behavior indicators in your preferences. Most of the time, the better solution is to solve the problem that the behavior indicator is showing. In Joe's case above, there is no good reason to turn off auto rebuild floors and ceilings and it sounds like he didn't do this on purpose. Turning off all of the behaviors will just hide the fact that this automatic behavior was accidently turned off. This can lead to lots of other problems, most of which are much harder to figure out. We put the behavior indicators in for a reason. Turning them off is like disconnecting the Check Engine light in your car. Sure the light might be annoying but not nearly as bad as having your engine fail when you are driving down the interstate in the middle of the night. If you find a problem with how the behavior indicators work, then please report it to our tech support team. If you would like for them to work differently, then please submit a feature request with your ideas.