The selection method you describe is very similar to Tekla's Xsteel. We have used Xsteel in our office for 8 years and find it much quicker to define the structure than Revit Structural. When building a model in Xsteel we can sketch the frame without worrying too much about the section sizes. These framing layouts are generally produced with over sized members and are used for discussions with the design team at the concept stage.

Jul 18, 2006. Hi all Just a quick one - currently the Dynamic Blocks library appears to have two options for inserting steel I beams, I Beam Metric and I Beam. The previous chapter has demonstrated the flexibility of AutoLISP and the open nature of AutoCAD which allows new commands to be developed. AutoCAD owes much of its. Services Catalogue available from Autodesk. All relevant addresses. In this section some of the more useful programs are.

Once better design information is available we simply select one member or a number of members and change the section size to the correct one. Mixer Presets In Fl Studio. One object can therefore take on various different predefined shaped including parametric shapes defined by the text string section reference. Parameters also control the position and rotation of the element relative to the defined axis. The object can also be given a curve about its 2 longitudinal axis. One object can take on all different shapes available in the system and is one of the main reasons Xsteel is faster to use.

The main drawback of Xsteel is that it is not so good when it comes to presentation of construction documentation. This is where Revit wins hands down. Revit also models much more than the structure which helps produce drawings which show how the structure relates to other elements.

There is no doubt that one structural element with all available profiles included is the way to go. BTW, what is the difference between a brace and a sloping beam. I don't think these is a need to distinguish between them. Similarly columns are beams standing on end. One object should be able to define all types of member by simply orientating the primary axis in a different direction.

This would be a major improvement. The standard structural families are inconsistent. While the Framing steel has a majority of the sections, it's still missing a few, and the Columns are missing even more. And it gets even less once you start isolating out the localised content. Of the ones that are applicable, the construction of the families differ in how they look and detail.

Some families have the base section. Others have the base section plus a simplified section and a stick representation depending of the detail level. Some families have materials assigned with a hatch pattern for viewing in plan when cut, and others don't. And yes, these are the R8.0 families. Rather than filtering our and changing the existing families, it's proving easier to start from scratch and make them all consistent. Ed: I should also add, that there is also missing content from the localised type catalogues too.

WB's only go up to 500 in the type catalogue for columns, but in reality go up to 1200. There are already Type catalogs that contain all the normal steel sections and sizes for Imperial and metric. Trouble is there's standard and there's 'standard'. I've found in the past I've had to alter TC's for the metric sections because some of the numbers aren't the same as the local suppliers. Beaumark Rice Cooker Instruction Manual on this page. Now we're getting into analytical calculations based on Revit models. Where are the suppliers? Isn't it becoming increasingly important they are supplying the families for the basic structural elements?

Definitely the suppliers need to be made aware of Revit and the data they could be supplying. I remember back in my AutoCAD days, I wrote some LISP programs for drawings steel sections. The data that I used came directly from OneSteel's electronic catalogue which had the sectional properties in a tabulated text file. When they updated their catalogue, all I had to do is get the new catalogue disk and copy the data files over to the LISP program folder. It was always correct and up to date.

This then goes back to the idea of a spreadsheet table interface which I guess you would be able to import manufacturer's data.

Not really thought about selling it. All our dynamic blocks that I have created for our company have the same copyright thing on. If we ever send a drawing out via e-mail we run a macro that explodes all of the dynamic blocks and purges them from the drawing. The copyright thing is just in case one of the blocks slips through the net, however we do have blocks that we are much more protective over than others. The steel one is a simple one to do, its just a copy of the Corus manuals.

Regards, Ben. We do the same thing with our drawings.

We push for.dwf, allow.pdf, and if it still needs to be a.dwg, we run a VB routine to wipe out all of the dynamic blocks. It then purge as well. You have to protect your investment. I'm glad to see someone else out there doing more with these dynamic blocks than adding just a flip state.

Ha-ha wrote in message news:5242960@discussion.autodesk.com. Not really thought about selling it.

All our dynamic blocks that I have created for our company have the same copyright thing on. If we ever send a drawing out via e-mail we run a macro that explodes all of the dynamic blocks and purges them from the drawing. The copyright thing is just in case one of the blocks slips through the net, however we do have blocks that we are much more protective over than others. The steel one is a simple one to do, its just a copy of the Corus manuals.

Regards, Ben. The copyright note is on its own layer. You can just switch it off and it will disappear. As for posting the macro (see bottom of post), its very simple but what it does is a very crude way of doing things. All it does is switches off all layers, switches on the ones that have dynamic blocks then explodes everything, purge, then thats it.

We save it as a temporary file and done. We also get the macro to delete all of the copyright text etc, it really just switches layers on and off and explodes or erases things We run 2006 LT with one copy of Full 2006 so we cant run fancy LISP routines or VB on all the machines so its the best and easiest way I could come up with something that we could all use.