Program Defaults in lieu of Project Defaults?

Is there a way to set program defaults so I get the same project defaults with every new project? Most of the default values are not set right for me (wind speed, ground snow, wall weights, story heights, etc.) and therefore I just skip them altogether.

Yes, I realize I could copy one project to the next, but then I have to change other things. Or I could create a project with nothing in it but defaults. But then that file would have to be positioned near the top of my project list and remain there so I could find it. Maybe thatā€™s the workaround for nowā€¦

Most of my calcs are for just a few beams and it would be real convenient if there was a default template that I could have saved that would fit my region.

Hi @WilsonEngineers, thank you for reaching out again! I understand how setting a main Project Defaults would greatly benefit your workflow, we also have other users requesting the same feature. While we currently have other priorities and wonā€™t implement this soon, I recommend using the workaround you mentioned - creating default projects that you can easily copy when starting a new one.

Regarding your query about positioning the default project at the top, you can use the filter box to quickly locate your default project regardless of its position. Simply type a keyword or name associated with your default project in the filter box, as shown in the screenshot below.

If you have any further questions or need assistance, please donā€™t hesitate to reach out. Weā€™re here to help!

1 Like

I have a ā€œtemplateā€ project file that Iā€™ve used to duplicate for every new project. However, as another user noted, it fails to copy the preferred sections which is another time consumer for each new project (typical shapes that are available in my area).

1 Like

@WilsonEngineers weā€™re looking to implement ā€˜pinnedā€™ or tagged project templates that can sit in a tab or at the top to address this. The challenge with doing one global set of program defaults is that many of our users have varied needs by client or jurisdiction, so it makes the most sense for them to make it varied. Per Lucasā€™ point the workaround most use right now is naming things ā€˜templateā€™ or ā€˜defaultā€™ which is coincidentally where weā€™ve taken inspiration for the tagging concept!

@MaxStability great note re preferred sections - this was initially not enabled as we had some system limitations for copy speed that forced us to make the trade off but weā€™ve resolved this now - Iā€™ll work with the team to get this in.

1 Like

Templates with tabbed/tagged access would be great!

This thought may be a subset of the template discussion or maybe it is different, but it would also be handy to be able to organize projects and sub-projects, not unlike the way Hilti Profis does it.

The first tier project level could be a contractor name, a residential development with multiple houses, a location/office grouping, or any other organizational option. The subprojects would then be the individual jobs, be it one house per subproject, or one task, or whatever. Each project group could then have its own defaults.