Jump to content

Taproot

Member
  • Posts

    516
  • Joined

  • Last visited

Posts posted by Taproot

  1. Logitech Mx500 - It's an 8 button mouse plus the scroll. I'm intrigued that you're 310 doesn't work with Pan. I have my wheel button set to "advanced click" and then "button number 3" which activates the pan function seamlessly. You might give that a try. The eight buttons is great! It may sound like a lot, but it helps to balance the load between the mousing and the hot keys. A couple tricks that I've learned over the last few years:

    ? I have the right click button activated by the escape key. I also have the selection tool activated by the escape key, so right clicking will drop me out of whatever tool I'm in and re-engage the selection tool.

    ? I've set up the mode groups to buttons on the mouse. Gone are the days of going back and forth to the mode bar ... and operations like offset, I can toggle up the offset distance with a mouse button and type it in with my left hand in rapid succession.

    ? Like Travis, I also have buttons for enter and exit groups - which works seamlessly with forward and back on my web browser.

    I actually bought it because it was the largest most comfortable mouse I could find and will ergonomically support the weight of my hand at rest. But after using it, I'm convinced that it's range of buttons offers great versatility.

  2. You may need to verify the location of the 2D section command. Depending on the workspace you are using, it may be located in another menu. In my setup, it is located under the AEC menu. If you are unable to locate it at all, then edit your current workspace, open the All Menu (flip down toggle) and then add "Cut 2D Section" to the location of your choice. Good Luck!

  3. The eyedropper tool is great. Unfortunately, I use it for two different operations. In "normal" mode, I use it for translating object attributes. However, I also consistantly use it for picking up and setting the attribute defaults. As it is, I'm spending more time in the settings panel than on the objects themselves.

    Ideally, I'd like two different tools (or settings) that I can assign different key commands to. I've tried adding the tool twice to the workspace, "custom tool" seems ill-suited. I'm guessing that there is an easy way to write a vectorscript to do this, but my scripting skills haven't really advanced since the Apple IIe.

    Is there another way? Or can someone with some vectorscript knowledge point me in the right direction?

    Any guidance would be much appreciated.

  4. Christiaan,

    I don't believe there is a way just yet. Note to NNA, it would be most helpful with the "Custom" window layout to be able to assign different heights and #'s of windows to each row of windows.

    A work around that I have had reasonable success with is:

    Make two windows. The first would be your lower sash - set at top of window. Duplicate this window and reassign the elevation value to set at sill height. Then customize it to have provide three lites. Apply the Transom to this window and check the Clerestory function. You can then insert the second window in the wall directly above the first and it will display dashed in plan view. Tweak as needed for trim.

    This will give you a pretty close approximation although not exact.

  5. I'm curious if this is just a Mac phenomenon. If you open a new file, choose an isometric view with Stack layers turned on and open GL rendering on and THEN you hold down the CONTROL key and click with the mouse (the usual method of bringing up the pet pallete)...

    At that point, all of my menu items will become inactive. moving the view sometimes will reactivate them, but more often than not, it doesn't. If it does, try control clicking again. At this point, you can still navigate around the drawing as normal, but you can't cut, paste, delete, save, or even quit VW. I have found that by closing the file window you can force the program into asking you to save your file and then you can force-quit VW.

    Can anyone else replicate the above? If so, I'll submit it as a bug.

    Thanks,

  6. I just updated with the 2/21 version of the updater for the mac and I'm getting A LOT of issues with the doors and windows. This may be user error, but for the time being, I would exercise restraint when installing the latest update.

    Issues:

    Custom window configurations no longer work. Settings are lost as soon as the dialogue box is closed.

    The door PIO no longer applies breaks to the wall even though they are selected (walls run through the opening).

    I'll send a test file to bugsubmit.

    Is anyone else getting these issues?

  7. The intent of this thread is to provide a catch-all for those small nuisance bugs that don't necessarily deserve a whole topic, but ought to be chronicled.

    For Example:

    Stairs now show in 3D regardless of whether the "show 3D" box is activated in the OIP

  8. Thanks Peter,

    Just out of curiosity, what is the advantage of linking the building elements and the site separately? It appears that if you unlock the link, you can move each layer of the link independently.

    Now that I understand the approach, implementing it has been a tad bit harder. Whether it's my file or ... trying to implement the above has not only been crashing the program, but taking down my system as well. When I have more time, I'll follow up with NNA.

    I hope dinner was delicious!

  9. Assuming you have a DTM which has a benchmark elevation of say 100 ft. and you are trying to key it to the level of the First Floor Elevation ... how do you do it?

    My layers are set up so that the first floor is at 0'-0". If I set the DTM at the corresponding elevation, the contour numbers will be off. If I move the whole building up to the 100 ft. elevation, then all of my perspectives are off.

    Whatever insight you've got, I'm all ears.

  10. I thought I'd add more of a layman's "how to" example:

    To create an eave profile like Michael K brought up early in this thread, where the primary framing is something like 2x12 and the eaves are cut down to 2x6, you could try this method:

    Draw a polygon around the perimeter of the building; Create a Roof with a thickness equal to the primary framing. Set the Eave setting to .1 inches, or some other insignificant value (it doesn't like an eave of 0). Once you've got the gables, etc. worked out, Frame it (with the appropriate framing members). Group the rafters together

    Then, go back to your roof object, reset the thickness to that of your eave members (or not, this may not matter, but is a habit from earlier versions of VW). Change the eave setting to that of the overhang (say 24") and check the box that says "apply to entire roof", then Frame it (with the appropriate members). Group these members also.

    You should now have two totally identical roof framing systems. Change your view to elevation and adjust the eave rafter group upward, so that the ridges align with the primary framing rafters.

    Return to your roof object and reset it's thickness to that of the sheathing and the roofing (say 1"). Return to elevation and adjust it so that it sits on top of the framing systems. You can then apply the roofing texture to this component.

    The two framing systems will merge when viewed in Open GL or Final Quality RW. They will also read correctly in plan.

    For the fascias, gutters, barge trim, etc... I typically model all of these as rafers or extrudes, or using the beam tool. Then I class them so that they are on a "model" layer.

    Good luck!

  11. This thread seems like the most relevant place to add my 2 cents on the STAIR tool. I finally found a project where I needed to push the capabilities a little and found that the tool couldn't quite keep up ... for example:

    If you have two stair runs of different widths (say 36" and 44" respectfully) joined by a "U" shaped landing. And, as is commonly the case, the stair runs are separated by an interior support wall ... well, that puts it over the top. Apparently the first flight will align with the EDGE of the landing, but the second flight will not. Any adjustments made to its width are made symmetrically around its centerline.

    Is there a different sequence that could lead me to having both stair flights aligned to the outer edges of the landing, or ... am I back to drawing one flight with the landing as one stair element and then patching a second stair above?

    Thanks,

  12. "On the Archicad subject are there equivilents to this in VWA ?

    To draw a wall of known length the procedure is

    click starting point & drag in desired direction shift+r numerical length enter.

    With Dual monitors

    Draw floor plan view in monitor/window1 & see the 3d view in monitor/window2"

    Drawing a wall with known length: Click to start wall, (tab) toggles you into and through X,Y, and Length fields. You can enter the value into one or more, (return) locks in the value, click sets the vetex and your on to the next wall segment.

    Reviewing 3D progress: VW doesn't have a secondary window, instead ... I, like most people have set up a series of hot keys to change the view to a number of different isometrics. The regeneration time in switching views (at least in wireframe) is almost instantaneous. While in 3D view, you can modify 3D objects (like Archicad). The bonus, is that you aren't constantly regenerating two windows and it improves the overall speed of the program. If you like, you can leave it in 3D and draft in that environment as well.

  13. Q4U:

    I was a VW user (v9), then switched to Archicad (v.8), then switched back to VW (all on a mac) , so I've been there...

    In a nutshell, Archicad is a much tighter constructed piece of software than VW. It's parametric controls over 3D objects are excellent and it has a streamlined interface that is relatively intuitive to use. Most of its functionality works as described, and the components do translate well to and from schedules.

    That said, I found the 2D tools extremely primitive, dimensioning was clumsy, the overall "hand" of the program was pretty sterile, and on my machine at least, the responsiveness of the program was extremely slow.

    By comparison, VectorWorks has the broadest range of capabilities out there. Components like ArchiTerra, ArchiForma, etc... are built right into the base program. It does organic modeling liken to FormZ, landscape design, sketch rendering, and now soft-shadow rendering. So, it's incredibly versatile.

    I would say that about 80% of VectorWorks is totally functional. The other 20% requires a lot of ingenous work-arounds on the part of the user... but the good news is that by and large there are work arounds. In general, if there is something I need the program to do, there is not one, but two or three ways that this can be accomplished.

    In the end, what tipped the balance for me was:

    I looked ahead and saw that at the rate VW was developing, it would rapidly overtake Archicad - each release over the past three years has shown a huge committment to developing the software's capability. I figured that if it didn't do what I needed just yet, that it was coming. Further, I figured that if my firm grows to support several workstations, I'll be able to expand my software $4000 is a lot for one, but x (3) it starts to become prohibitable.

    Perhaps this will help ... If you have more specific questions, I'd be happy to respond.

  14. I hadn't originally intended thsi to be so lengthy. But then I figured "Hey - version 12 just came out this is the time to mention those minor nuisances for version 13 before all of the programmers schedules are set." So, here ya' go!

    Trim Tool:

    ? Add a mode to allow dragged line selection of objects in addition to lasso and square. This would give a lot more flexibility and control.

    ? One flow: Select objects (click), pick trim object (click) resets tool for next trim operation - having to deselect the trimmed objects to then select a new series of objects is a pain.

    ?Trim to break lines and other visible objects would also be a plus.

    Offset Tool:

    ? Mode that allow for symmetrical offset (i.e. two objects equally offset from the original centerline)

    ? Offset distance(s): Being able to preset more than one offset distance i.e. 1/2" ,5 1/2", and 3 1/2" and then being able to toggle between them on the fly with a keystroke.

    ? Like the Trim Tool - Click on a line - engages tool and begins offset, click again to set offset line(s) and DESELECT. This prepares you to launch right into another operation.

    ? Add multiple offset mode: multiple objects continue to offset at the specified distance in the direction of the mouse drag until the mouse is clicked.

    Offset Along Path Tool:

    ? Offset multiple objects from the point on which the original is selected (or be able to select a point on the rectangle - like in the PIO for objects). Arbitrarily duplicating objects beginning at the center is illogical. Typically, you want equal spacing with the outside edge aligned with the start point (not centered on it). Better yet, would be to have an option where you could have all of the objects equal spaced, but the first and last object adjusted so that their outside edges were flush with the start and end points (as in framing layouts).

    Callout Tool:

    ? It's almost perfect! The bezier mode of the callout tool should only have one default adjustment handle (not two) (or at least the option) This would give it a clean look with all of the benefits of SUPER LEADER while keeping the text and the leader together in one object. The current version is awfully squiggly.

    GRAY LAYERS (What's the point to them anyway?)

    ? In my view, gray layers are there for two reasons: Either you want to print them as background data that is supporting information, but not the main focus of a drawing, or you want to use them as a guide to trace other information off of (like a roof plan off of a floor plan or a foundation plan off of a floor plan). Currently VW can't do either. This is a point of major aggravation for me. VW refuses to snap to gray layers, and the shade used is to light to show up on almost all printers. I would suggest that Users be able to control the shade of gray or color criteria used for gray layers. This would allow for individual adjustment for different printer and screen configurations. I would also suggest that layers set to gray would remain snappable!

    OTHER:

    ? Be able to set the PIO defaults to an object. VectorDepot has a menu item that does this, but it works inconsistently. I use it all the time! It's priceless.

    ? Section Perspectives: Allow for perspective view of Live Sections for the objects behind the cutting plane.

    You guys are doing a great job with the development of the software ... Please keep it up!

  15. What if ... you could toggle a setting in the viewport OIP so that it would no longer update automatically. In other words, it would remain rendered and static.

    This would allow you to bypass the whole clumsy process of exporting images and re-importing them. It would allow you to display multiple design versions for evaluation. Even more importantly, at the end of the project when you are tweaking, updating and altering minor notes, it would keep you from having to constantly re-render all of your viewports unnecessarily

  16. A very common procedure is to draw one layer over the top of another. Ideally this would be accomplished by graying out the layer below and being able to snap to the objects on it. However, I can't figure out how to accomplish this. If the layer is grayed (and show snap others is on), snapping is automatically turned off.

    Is there an obvious method that I'm unaware of?

    Thanks!

×
×
  • Create New...