Jump to content

former Revit user

Member
 View Profile  See their activity

  • Posts

    55

  • Joined

  • Last visited

 Content Type 

Posts posted by former Revit user

    Best Practices: Exploading PIO's

    in Architecture

    Posted

    All I know is that when I ungroup the PIO, some pieces that I select say Extrude in my oip and some say Multiple Extrude.

    So ungrouping in plan view gives me different results than ungrouping in 3d, or elevation?

    Where can I find the Engineer's intentions, rules and regulations for those objects, or does that reside in the Garden of Eden?

    Best Practices: Exploading PIO's

    in Architecture

    Posted

    Thanks for the advice and troubleshooting:

    When I ungroup the cabinet, there is a seemingly random breakdown of objects. Some are regular 'simple' extrudes and others are multiple extrudes - both objects being a rectangular box. The problem I have w/ the m.extrude occurs when I go to render it. I need to convert it to something else to get the texture to apply correctly. Unless I'm doing something wrong w/ the textures ie. multiple extrude being more of a circular object and I am mapping with planar/perimeter?

    The other problem I am having w/ M.extrude is how to chamfer the edges?

    So...is the 'random?' breakdown of PIO pieces caused by the method used to construct it in the first place, and if I begin to script my own PIO's can I set them up to Ungroup how I best see fit?

    Changing doors

    in Architecture

    Posted · Edited by former Revit user

    I have a door in a wall that I picked and dropped from the Resource browser. I want to now change that door to a different door but leave it in the same place.

    Is there anyway to select the door in the wall, and then change it to another size door from the resource browser?

    or

    Do I have to drag the size of the door I want from the resource browser to the model space and insert as such to switch them out?

    This goes for all PIO's windows, cabinets, etc.

    thanks in advance

    Best Practices: Exploading PIO's

    in Architecture

    Posted

    Hello all,

    Yes, I'm still here, poking away at VW,

    I was wondering what people found as the best method of un-grouping /breaking apart PIO's.

    I ungrouped a cabinet and am left w/ a bunch of Multiple Extrudes which don't seem as versatile a modeling block as a simple extrude.

    I specifically am having trouble chamfering the Multiple Extrude.

    Any help or advice is always welcome!

    user defined 'objects' ?

    in General Discussion

    Posted

    Maybe I'm missing something...

    For the 'extensive' 3d library let's use the doors as an example: Ea. door is simply a variation on the parameters of one door PIO, correct? It simply automates the arduous task of having to place ea. door PIO in the project then go through ea. parameter and change it?

    This holds true for everything in the library? windows, cabinets, etc.?

    user defined 'objects' ?

    in General Discussion

    Posted

    Well it isn't hard to find something negative to say about New Jersey,

    but it also isn't hard to simply read the posts and the responses to the questions asked.

    I'm not sure who you're referring to as mr. expert but I thought the general gist was laid out in several extensive posts.

    If you want further information, go to the autodesk website and follow the links.

    user defined 'objects' ?

    in General Discussion

    Posted

    Yeah, sorry for the un-informed 'add-ons' comment. I did see the price for the Windoor.

    The comment came from a general impression (subject to change) I got from reading through the forums and seeing links from users to pay-only websites, much of if for tutorials though(which is standard) but also many scripts that help to extend the functionality. Not all adding up to a whole lot of money so....

    The real point is that the majority of architects & architecture students out there have very little if any knowledge of code, and to offer that as the only point of departure from the norm 'library' seems.....

    user defined 'objects' ?

    in General Discussion

    Posted

    The primary differences between the two methods of creating unique objects then are:

    Revit uses a graphical interface to construct and constrain the objects.

    VW uses a scripting interface to construct and constrain the objects.

    BTW, the same 1-in all PIO can be achieved in Revit but doesn't always make sense. This means you must construct the object w/ future unknown variables that will inevitably need to be updated and revised.

    It is simply a matter of organizing. I have 1 window design w/ a variety of sizes. It isn't that bad. A window category, door, etc. Folders, organization?

    My point is that from an architecture/design/intuitive thought process point of view, being able to graphically 'build' the PIO seems a much better approach than having to mediate fluid thought w/ a non-intuitive programming language. Once learned I assume it becomes relatively fluid but it still seems stifling.

    All this being said I guess I'm on to learning that language which may inevitably change my current thoughts.

    user defined 'objects' ?

    in General Discussion

    Posted

    Hmmm, I'm listening,

    Thanks for the advice too,

    Yeah, there is a large library of objects, and then a variety of sizes for ea. object so....

    If you have 1 file (called a family in Revit) that comprises say, a double hung window. You model the geometry and constrain it and give the dimensions logical names like width, height, etc. and then load that into the 'Master' model ie. the project file. From there you have a drop down list of the various sizs for that double hung window, 3040, 2640, etc.

    There are then 'family' files for ea. different object such as, Awning window, slider, etc. This holds true for doors and any other object you have.

    So yes, there are a considerable number of 'objects/files' but then again you don't have to pick through as long a list of options that you do when using the PIO's.

    The reason for explaining the Revit process in such detail is to try and get an accurate comparison.

    I would say a matter of preference between the two?

    What one gains with Revit's pre-defined way of organizing the project could be considered a hinderance by those who want complete customization.

    VW maybe has a stronger foundation w/ which to grow, so with a little work, a better program?

    user defined 'objects' ?

    in General Discussion

    Posted · Edited by former Revit user

    Yes, Yes, Yes,

    I'm not familiar w/ script/code and would like to learn it - I'm hoping learning it for VW will provide the groundwork for other programs I would like to learn where a solid knowledge of scripting is very useful, i.e. Flash, Catia, etc.

    Anyway, to the question,

    My current understanding of the primary difference between the two programs is the amount of effort required to set up an efficient work flow/presentation/modeling environment where one continues drawing/editing/designing in the three typical architectural views - (plan, section, elevation) but is actually constructing the 3 dimensional model.

    Revit was initially conceived for this and won't allow you to 'draft' in the traditional sense, you must build, but you can layer drafting details over views, similar to annotations, so that not every screw need to be modeled. This allows you to physically construct the 3d model to the level of detail the project requires, in 3d, and then any additional details can be added over this framework.

    As for the actual question,

    One basically sets up reference planes and then dimension them. The dimensions then control/constrain the reference planes. You then model the actual geometry and constrain it appropriately to the reference planes. The dimensions can then be 'parameterized' using booleans and if,and,or,then, statements.

    This is all done using 'palettes' or a database type interface where the names I assign to the dimensions are listed and I can simply change the values and stretch the object within the larger project file. Similar to the VW doors and windows and objects, it is just a lot easier to create your own user defined objects, from scratch and set them up with very limited scripting knowledge.

    Long story short, my current impression is that VW requires considerably more expertise and time to set it up 'intelligently' to the level that Revit comes out of the box. So while it may seem more expensive, the time saved initially is certainly worth it.

    Why am I using VW then? Job, Job, Job

    My optimistic side tells me that I will learn something from this less than desirable situation.

    Hope this answers the question somewhat, without offending any die hards of course!

    viewport scale referencing

    in General Discussion

    Posted

    I guess it's one of those things that when it's gone you miss it, when it's there you take it for granted.

    I would be interested in learning how to do this using VS, even if it isn't the most useful tool in the bag it is a step for me towards understanding the program better.

    Do you then have any suggestions as to where I might find/learn this relatively simple script?

    thanks

    viewport scale referencing

    in General Discussion

    Posted · Edited by former Revit user

    Thanks a lot for the quick response,

    Two more points though:

    When I change the name of the viewport, how do I maintain that connection with the drawing label?

    Another question, the answer to which might hold the key to the previous question;

    If I copy a drawing label into the viewport, how do I get the information to "update" or "reconnect" to that viewport? (where's the connection?)

    And finally;

    How would I go about editing the presentation of the scale, say to remove the scale text so that it only read a numerical value?

    Thank you again

    viewport scale referencing

    in General Discussion

    Posted

    Hello all,

    I was wondering if there's a way to link the Viewport scale to a drawing label or other reference marker so that when I change the scale of the viewport, it will automatically update the scale in the label?

    Thanks again for any help or direction

×
×
  • Create New...