Joe_Carrick

Rene, Are you saying the problem exists with the 3D connexxion mouse too? So it's not just Logitec? If that's true then it is more likely Chief that's at fault.

Brian, Isn't it interesting that the "Automatic Scrolling" setting in Preferences being on vs off makes a difference? That indicates to me that something in Chief's software just isn't compatible with the mouse driver.

We keep finding problems to report - which is I understand holding up the official release of X18

Yes, I reported it to Brian. Here's what I told him: Yes, a corded mouse works. Perry suggested that I should turn off automatic scrolling in Preferences. I did that and the Logitec mouse worked correctly as well. The only problem is the loss of the X18 drag & scroll feature. So evidently there' something in the automatic scrolling code that messes with the logitec mouse software. Hopefully one of Chief's software engineers can figure out a fix.

Thanks Perry. That's the key. However, it also turns off the X18 sceen scrolling when dragging.

Doesn't appear to make any difference. The problem for me is only occurring in Chief. It's just the left mouse button The right mouse button works correctly. I submitted a ticket with support. My mouse is a Logitec M185 wireless with a new battery.

Ed, when in TMM you can highlite a set of macros and export them. The named exported file (.json) will be placed in the current Chief Data, Scripts folder but you can actually create sub-folders within that. If you don't select any macros then the entire set will be exported. That's one way to organize but TMM is just alpha-numeric of the currently installed macros in Plan or Layout.

I've been noticing recently that when I select an object with a left mouse click and try to move that object often it immediately opens the object's dbx. Is anyone else having this issue? What could cause this and how do I fix it?

The only way to organize macros in TMM is alphabetical. Objects with embedded macros that are stored in the library will automatically be added when they are placed in a plan. It's notable that the Layout and Plan have separate sets of macros. Some macros will work in both but it's best to keep separate sets.

I still think it's either the OS or an App that's doing it. I seriously doubt it's Chief.

I think that's a new feature of the latest Windows 11 update.

When adjusting the values you should note that a 30 degree riser should result in a Rise Angle of 45 degrees. That will make it easier to set the overhang (about 4" for a 7" riser height.)

Yes, but it's a little tricky. Specify tread detph as 8.5" (General) Specify tread overhang as 3 (Style) Specify "Open Risers" (Style) You might need to adjust those dimensions a bit but it will essentially make the stairs steeper while maintaining a total tread depth of 11.5". I You can play with those values as needed. Assuming you will need a maximum length of about 84" (or 77" with a landing at the bottom) adjusting the numbers for treads, riser heights, top and bottom heights, etc will all have an effect.

No, that doesn't work because it's always the wall's layerset is always the layers_et it was created on. Walls in section and elevation views don't have different layer_sets.

I figured it out. X18 has a special label that can be quite effective.

I use a set of macros to display different wall labels base on the view. Plans get the Wall # & the direction the wall faces relative to North Exterior Elevations show the Exterior Wall Layers Interior Elevations show the Interior Wall Layers This system works in the Layout because I can check the referenced_view_layer_set of the Layout Box. But in a Plan file there isn't any way to determine what the view type is. Does anyone know of a way to do that?

Hi Gene, Manually create a truss and then edit the profile. The truss should then be able to be copied over the stairway

I am offering my Coordinated Callout System for purchase. I virtually get all callouts created automatically, It provides the following: In the Layout Interior Elevations Callout -> room_number.elevation_number -> 203.3 Exterior Elevations Callout -> N,S,E,W name in the Project Browser Cross Section Callout -> match the Cross Section name of the Project Browser A,B,C,D,etc Plan Views -> Floor Number -> (0orB,1,2,3,etc) CAD Details -> automatically numbered based on size and position on the page. 1-30, etc. In the Plan Detail Callout automatically match the linked CAD Detail in the Layout The macros can be assigned to existing objects and can also be assigned to the defaults for new objects. The system consists of 5 macros in the Layout 3 macros in the Plan. Defaults for Callouts in both Layout and Plan Installation consists of simply importing the above. Price for the system is $200 which can be paid to my Venmo account Joseph-Carrick-6 Make sure you include your email address so I can send it.

John Henry was a steel drivin man - said "I'll die with a hammer in my hand."

Turn off the auto driver update for Nvidia. It will save you a lot of grief until this get's fixed.

This thread is a replacement for the previous one which was hijacked by some users who just wanted to complain about what didn't get into the X18 public beta. If you have a feature in X18 you especially like please feal free to mention it. If you aren't sure how to use one of the new capabilities please ask. X18 has some great new features. Here are my favorites: Project Information. Project Designer Client Custom - additional consultants, etc 3D Profiles User defined to add to Walls, Roofs, etc 2D Moldings - Board & Batt, Standing Seam Roofing, etc Lots of options using 2D Molding Profiles 3D Moldings - Mission Tile Roofing, Shingles, Shakes, etc Note that profiles should be as simple as possible to avoid redraw slowdown and file bloat. Don't attempt to create either 2D or 3D profiles with extreme accuracy. Fewer surfaces will provide better performance while still enhancing the 3D rendering. Room Labels with controls for what is displayed for various view types Wall Intersection editing & Wall Layer Fills Corner Board "Recessed to Sheathing Layer" option Replace Identical Objects in Plan (from Library) Numerous Framing and Truss improvements Schedules (Include from Floors options - much more flexibility) Obviously, a couple of the user's who were guilty of hi-jacking didn't like that I had wiped out the garbage and gave down-votes. So childish !!!

I generally only have them in my Layout Templates. Anything previously saved in those Templates is there when I start a ne project but I'm not using "Project Mode" so I can't say it would be true in that case. I would assume the answer would be yes. OTOH you can import any such values from an existing Plan or Layout

You and I have a different way of dealing with project specifics. If I understand correctly you generally deal with client specifics for projects while I deal with projects specifics. My title sheet - example has virtually all of it's information supplied by text macros that reference the Project Information. Deferred Subittals has individual macros for each item and where a specific jurisdiction is needed it comes from one of those fields. General Notes and Building Performance are likewise macros that get specific data from those fields Project Name and Address - %project.info% fields Copyright - macro with %desigher.info% fields Property Details - Rich Text with %project.info% fields Building Codes - %code_list% derives the location, etc from %project.info% and constructs the list accordingly. This macro is designed to provide the correct codes per the city,state,etc without any reference to client or contractor. It automatically updates the current code year and code name depending on the project location (city, county/province, state). Designer & Consultants: %info_Designer% %info_Engineer% %info_Surveyor% %info_Soils_Investigation% %info_Energy_Consultant% %info_Geologist% %info_Builder% Scope of work relies on data taken directly from the Plan itself. Sheet Title Block including Sheet Index, Revisions, Designer, Client, etc are all on the Default Template Page(s). The Layout contains only 27 macros to handle all of the above plus 6 for Layout Box Labeling 2 of which determine the number or letter of details and sections I have separate Layout Templates (different sheet sizes) with all of the above ready to go. Basically I treat the Layout separtely from the model, just sending plans, sections, elevations, details, schedules images, etc to the Layout. Project Information categories>fields is the source for all of the project specific information so I only need to edit those in order to change what's displayed on the Title Sheet. I never need to change the layout macros since they are universal. It's taken a long time to develope this system but it saves me thousands of hours.

Mine is in the label of a polyline on my Layout Template. That way it's executed as soon as the Layout is opened. ps: The polyline dbx really needs to have a label box with at least 10 lines of space to prevent the need for so much scrolling.

I do like the sort and macro suggestions. I'm not sure however that I would need to insert macros into field values. In most cases I will just enter the values as text - or copy the macro results from TMM into the field value. For the most part it's pretty easy to duplicate classes and copy field values. To be honest, I am so happy to get this as provided that I basically overlooked the slight annoyances you outlined above. What I really want is for the field values to be returned as actual data strings. Currently I have use a bit of ledgerdemain to get editable values.