For those interested in utilizing the IFC Simpson models, I have some tips that may be useful. If your interest is a product that the IFC formatted model is not available, you can contact Simpson Technical Services and request the IFC format (use Technical or Product Use Questions Section).
You can use the Drawing Finder to locate the specific product. Drawings in various formats exist for >46K products with >2500 IFC drawings.
Recently, I submitted a request for an IFC drawing and it was available within a week. Even received an email providing the link. Great customer service !
When importing a Simpson IFC model, it comes into SU as a nested component/non-solid.
I prefer to use solid groups/components in my models. A fast, simple method to convert to a solid is through the SU Outliner (multiple use of explode).
And with a solid you have the flexibility to transform the component into various configurations to meet your requirements. Enjoy !
The keywords, âCustomâ and âSubtractâ are great new additions to the Medeek extension family. Now, we can add manual edits to our models, which opens up new possibilities as to how we use these extensions.
How to use these features, with examples, is covered in numerous other posts and a Medeek tutorial here:
I do want to share a tip on âhowâ we use these new features. Typically, the sequence follows this pattern:
Select
Cut
Open for edit
Paste in Place
Add keyword
Regen
Which produces a workflow like this:
But, how about streamlining this workflow with an alternative set of steps:
Select
Add keyword
Move solid instance into the target group using the SU OUTLINER
Regen
Which would produce the same result, only faster with fewer steps, and fewer possibilities of mistakes:
Try using the Outliner with the Medeek extensions (and SU in general) in this manner. I think you will agree, it saves time. Enjoy
After upgrading SU today (Version 21.1.298), this behavior started when using the wall extension (2.2.1). The missing graphics will re-appear upon terminating the wall assembly. This is on MacOS. Anyone else seeing this behavior on either Mac or Win?
Yes, and there are many, many, many reasons why âClippingâ occurs. I was using the Medeek Wall Extension immediately before the SU update without the clipping. Immediately after the update, the clipping started. Maybe a coincidence? Really interested in feedback from other Medeek Wall Extension users.
Just for comparison, the Medeek Truss Extension, does not display any clipping behavior. Also, tried the Foundation Extension, again no clipping noted.
I was able to reproduce the clipping on a Windows PC. This PC has the latest SU and Wall Extension updates.
For me, more of a nuisance than a show stopper !
A more important question is how/why this SU update adversely affects these extensions? Is it entirely up to the extension developers to ensure compatibility with SU updates? Would seem appropriate for SU to communicate upcoming code/feature changes with developers ahead of the update launch.
This question if for MacOS only. This scenario works without issue on Windows (see 4th GIF and 5th image for comparison). My workflow creates wall sections individually (to ensure exact distance measurement). I start the wall tool, type in the distance (VCB, lower right) and press enter. Then click on the âendâ mark (first wall, center point) and create the second wall assembly. This creates a misalignment in the âendâ and âstartâ marks of the two wall segments (see 1st GIF and 1st image). If I then move the second wall so the âstartâ mark aligns with the âendâ mark of the first wall segment, the corner is incorrect (see 2nd image). Aside from the first scenario, it recurs if a wall segment is deleted and replaced. I did turn off âAuto Corner Configâ and toggled other settings in the âWallsâ and âWall Cornersâ tabs of the Wall Global Settings, no help. The 3rd image is when the two segments are created using a mouse click (in a continuous manner) at the corner. Alignment and corner correctly generated.
Is there a problem when manually entering wall lengths or is this outside the scope of the extension? Or possibly a conflict/incompatibility in MacOS. Thanks for your suggestions.
Until there is a solution to this Mac only issue, Iâve developed a work around. It involves using the Grid Tool Extension (Free, by SU Team). @medeek also highly recommends this extension !
Use the Grid Tool and set the grid spacing to your liking in the VCB (lower right). In this example, I have it set for 2â. Draw out a grid larger than your wall length dimension (example is 20â x 20â). The example wall segments are 10â. Start the wall tool at a convenient grid intersection, then mouse click at the desired 1st wall segment length (see length in VCB, snap in grid increments), continue onto the next grid intersection and so on. This method will produce correctly aligned wall segments and corner configurations. Enjoy.
I am struggling to find a workflow that creates âHeel Blockingâ in the Truss extension. In the process outlined below, the heel blocking does not appear as expected. I am using Truss extension version 2.9.1, with SU Pro 2021 (Version 21.1.298). I have reproduced the issue on Mac and Windows versions. I even tried SU 2017, same result. Since the result is so consistent, I must be making an error in the process, but have failed to find it. I have included the test model for reference. As always, thanks for any and all help.
Hey @medeek I was wondering, if I switched to a subscription now, and then a year later I cancel it, will I have to go back to using the last version available in my permanent license or will I be able to use the last one I had access to in the subscription?
You can have both a subscription and a permanent license, in fact you have multiple permanent and subscription licenses/serial numbers.
Each one is independent of the other. If you renew a permanent serial/license that license can then be used with the latest versions of the plugin until it has expired and then later versions of the plugin will not work with it (only versions released prior to the exp. upgrade date).
You cannot apply a subscription license to a permanent license, there is no mechanism for that. If there were then there would be no reason to have a renew option for the permanent license, one would just purchase a subscription license.
The permanent license renewal prices have gone up by 50% (ie. $50.00 â $75.00). This is why I have been telling people to renew now and future proof rather than wait later when the prices have gone up. I do periodically run specific sales for renewals to encourage people to renew but those are not guaranteed and I donât have a specific date or schedule in place, it is kind of a seat of the pants thing.
The problem is that my renewal rate is rather abysmal lately, I donât know if this is because I havenât added enough new stuff to the plugins recently or just that some users only use the plugins for a short while and then donât need them anymore. Either way the subscription model lowers the bar significantly for casual users ($50.00 vs. $95.00) and the higher prices with the permanent licensing model puts more of the development burden on shoulders of the power users.
I may revisit the renewal pricing, currently it is exactly 50% more than the subscription cost for all plugins.
@medeek, thanks for the tip. Trying to unravel why/how the wall cladding field was blank. In the first image the wall cladding field is set to âNOâ, and the wall cladding material is blank. The second image shows the wall cladding field is blank. I assume this is the reason the cladding field was blank after creation, is that correct? I did not change the global settings, so still not sure why this happened.
Using the default settings, should there be empty fields? What about a default value that would prevent the empty field?
After populating the cladding material field, the heel blocking worked correctly. However this strange behavior occurred (3rd image). No Ruby console errors. Model attached. Any suggestions?
@medeek, not sure if I understand the html menus. In this example I draw out the roof with arbitrary length and width. In the subsequent dialog boxes, I change the length/width to 10â. In the final result only the width is 10â. If I then regen, the length reverts to the original arbitrary length. Shouldnât the html entered values be the final measurements? No Ruby console errors. Model attached.
