Jump to content

joelhufford

Member
  • Posts

    24
  • Joined

  • Last visited

Posts posted by joelhufford

  1. I know this is an old thread, but for anyone who comes across it, I was also as of September 2018 (and VW 2018 SP4) still experiencing this bug. Very happy to report that VW2019 SP0 appears to have addressed this issue - specifically with Tekton Pro! 

     

     

  2. "I don't know what Screen Aligned is, so that's still freaking me out"

     

    That's exactly how I feel! I know it's been months since asking this question, and I'm sorry to have abandoned it, but I wanted to come back to say that video does do a great job of illustrating why VW has both the Automatic and Layer Plane functionality and when you know where to use each, I think they can both be very powerful tools. When you showed the plumb bob orienting itself perpendicularly to the bullseye in Automatic Plane mode, I think it did the best job of explaining how what I was seeing was most likely a "Works as Designed" phenomenon. In automatic mode, VW treats the highlighted planar face as the "ground plane" and orients symbols with respect to that "ground plane" my shape, like your plumb bob was perpendicular to the actual ground plane when it was first drawn, so again, when in automatic mode, the symbol orients itself to be perpendicular to the target planar surface.

     

    If that's really what's going on here, then at least now that I know, it can be worked around, but it does strike me (for us anyway) that every time we create a drawing in Vectorworks, our X, Y and Z axis are always the same. Top is top, front is front, side is side and I feel like it would be nice if symbols could be told to respect a global orientation when being placed.

     

    Certainly not something that would make it to the top of the wish list.

     

    Also I'd like to say I've watched several of your tutorials / youtube videos and think they're all incredible helpful and your drawings look awesome.

     

    Thanks again,

    Joel

     

  3. I've been converting 2d lines to dimensions for some time now. I find it helps when trying to dimension something in a view other than Top/Plan as the 2d line stays on what is effectively the screen plane of the drawing and you don't run into odd snapping to obejcts in 3d space.

     

    What happens in the video below has been happening I think ever since updating to VW2017, I've just never taken the time to document it until now. When converting a line object to a dimension, Vectorworks displays an angry dialog box saying "This command requires that one of the following objects be selected : line, circle/arc" What's more bizarre is that after hitting okay a few times, the conversion does happen...and usually the same dialog box pops up a few more times after the conversion has happened!

     

    Anyone else ever seen this? Something I'm missing here?

     

    Thanks! 

    line_to_dimension.mov

  4. Every time a screen gets dropped in one of our drawings, we need to know the optical center of the screen to optimize the projection scaffolding setup. It would be outstanding if the OIP of the screen object would just tell you what that measurement was instead of having to draw a 3D dimension in a front elevation (which can be a chore in and of itself) or worse yet, having to actually do foot and inch math in your head!

     

    The way I see it, the plugin is already calculating the center of the screen, because the projector position can be set to "Screen Center." All we need is an entry showing what that dimension is!

     

    Thanks,

    Joel

     

  5. Hi Jonathan,

     

    Happy New Year!

     

    Thanks for taking some time to look at the video. It would appear that the shifting of the active plane is what's causing this. It's just something I've not had much experience dealing with and strikes me as unexpected behavior. Firstly, I though that only planar (2D) objects could be aligned to the screen. Clearly that's not a factor here, so I've misunderstood that. Perhaps I'm confusing a "screen aligned object" with one that's drawn on the "screen plane?" I was doing some reading on this thread

     

     

    and at least I'm not the only one confused by the "Screen Aligned Plane" 

     

    I'm also curious about some other behavior I've observed while experimenting. If I begin a drawing in normal perspective view and place a 3d symbol, the active plane is "Screen Aligned," and can only be "Screen Aligned" or "Automatic" however after I place the first symbol and zoom in or out, the active plane switches to "Layer Plane" and the 3D symbol rotated 90 CW about the X axis and its orientation matches the orientation as drawn in the symbol's 3D definition. I'm sure this is working as designed, I just can't understand why it would be designed to work this way!  In other words, when placing a 3D only symbol into a drawing, why isn't the symbol's default behavior to orient itself in the drawing relative to its own 3D orientation? 

     

    Actually, that's the wrong question, because the symbol does place itself into the drawing with the "correct" orientation when placed from a top/plan view. It's only when trying to place the symbol into the drawing from a front elevation (when the drawing's Active Plane becomes "Screen Aligned") that I sigh to myself silently, think about grabbing another beer out of the fridge and just drawing this whole thing up on a cocktail napkin.

     

    I suppose the real question is, "Why does the 'Screen Aligned' Active Plane mode exist, and when would anyone want this kind of behavior?"

     

    I've attached a video showing the Active Plane shifting after zooming in and back out again. It's hard to tell, but around 13 seconds when the active plane shifts, I'm zooming out and then back in again. I don't know...seems weird...

     

    Thanks!

     

     

    Screen_Aligned_then_Layer_Plane.mov

  6. Can someone kindly explain to me why a 3d symbol would change its insertion orientation based on the view being used when the symbol is inserted? I've attached a video showing the same 3d symbol being inserted incorrectly when placed in the drawing from a front view, and correctly (rotated 90 degrees about the x axis) when inserted from an isometric view.

     

    This feels like a bug to me, but I'm sure there's more to it than that.

     

    Thanks!

    Joel

     

    symbol_orientation_change.mov

  7. I'm wondering if anyone else is using Box.com as a platform for 2016 Project Sharing and if so, if you're experiencing the same issues with Box duplicating the Project File with user names append to it every time you commit a change?

    Seems like this makes Box unusable with Project Sharing and I don't see anyway to modify the behavior.

    Is there something I'm doing incorrectly?

    Image attached below showing the duplicates. It appears that changes made in my working file are only registered with the latest duplicate project file. Other users opening the original project file don't see any of my edits, even after a Save and Commit command.

    Google Drive appears to be working correctly for us now, but I was curious if anyone else is experiencing this?

    gi9nhlq6krpl0id3huvj6qq8p5w56c7a

  8. For anyone tired of fighting the palette layouts when switching between different monitor setups, I wanted to share the success I've recently had with a program called Stay. https://cordlessdog.com/stay/

    It's only available on Mac OS X, but it does a great job of restoring palette locations when switching between multi display setups. Just layout your palette positions the way you want them, and then tell Stay to record the positions. The next time Stay recognizes that monitor setup, it restores the layout.

    This works across every application on the computer, but I'm currently only using it for VW2015 and so far, it's been awesome.

  9. Hi,

    Wondering about something I'm running into in VW2015 - although I expect this happens regardless of which version you're on.

    I'm cleaning up a drawing and when I go to delete a class that's no longer in use, occasionally I'm shown this dialog box.

    [img:center]https://www.dropbox.com/s/2yns4hfspseu5dn/deleting%20classes.png?dl=0[/img]

    So I'm wondering if there's a quick way to have Vectorworks tell you how many objects are currently assigned to the class? Using a custom selection of this old class, as well as the visibility tool to temporarily make every class visible doesn't cause anything new to show up.

  10. If you need something down and dirty, you could also just make a custom selection in the document, selecting an instance of the symbol you're wanting to count. The other suggestions are perhaps more thorough, however, if you're just wanting to find out how many of a specific symbol are in your current drawing, the custom selection option only takes a few seconds.

    Tools >> Custom Selection >> Select Only

    Hit Enter

    Select :

    "Symbol" >> "Is" and then a drop down box allowing you to choose the symbol you'd like to select.

    The Advantage (or disadvantage depending on how you look at it) is that this will only select symbols on the active design layer. To search through the entire drawing, make sure you've selected "Show/Snap/Modify Others" in the Layer tab of the Navigation Palette.

    Just another way to skin the cat!

  11. This seems like a simple thing... hopefully its something obvious that I'm just missing, but there are times I'd like to move the position of an element to a point in the drawing relative to the document origin, but the element doesn't have the option to modify the X, Y, Z coordinates in the OIP. Groups of objects are a great example of this.

    Is there a way to take a group or other element that does not have the X, Y, Z coordinates in the OIP and move it relative to the document origin?

    For example, in a front elevation, I'd like to take a group of 3D polygons or symbols, and move them such that the bottom of the group rests at 0' 0" off the floor.

    Hope that makes sense!

    Thanks,

    Joel

  12. Lo and behold!

    seems i am able to reproduce the crash consistently with the attached file. It appears to happen when selecting a color from the color palette while the palette is scrolling, but before the scrolling animation has completed.

    Also I just opened a new file and was able to reproduce the same behavior.

    I suppose the solution in the mean time is to just slow down when picking colors!

    Please let me know if you're able to reproduce this, or if this is a viable excuse I can use to tell my boss it's time to upgrade to one of them shiny new MacPros!

    Thanks,

    Joel

    Dropbox to Crashing VW2015 File

  13. Hi Jim,

    Thank you for once again for being so quick to respond in this thread! So awesome!

    I'm afraid the crashing is very sporadic and all of the documents I lost to a crash were brand new documents I had not saved when they crashed. I'd love to send you a crashing document, but I can't seem to replicate this!

    I was just reading the other thread about the eyedropper causing some problems and am wondering if somehow these two problems could be related?

    It does look like the last 8 crashes that I've experienced using VW 2015 SP2 have involved a call to net.nemetschek.vectorworks.ColorPalettes and then crashed with the same call to libobjc.A.dylib method: objc_msgSend + 23.

    This also shows up in the application specific portion of most, but not all crash logs:

    Application Specific Information:

    objc_msgSend() selector name: collectionView:cellForIndex:

    Performing @selector(menuItemSelector:) from sender NNAMenuItem 0x6100002d0680

    Not sure if that's helpful at all.

    As soon as I encounter a problematic file, I'll be happy to send it your way.

    Thanks,

    Joel

  14. I'm wondering if anyone else is experiencing VW2015 crashes after attempting to change the color (fill or stroke, doesn't seem to matter) of an object in a drawing? I had not suffered from this before the SP2 update, but it seems now that every drawing I work on is prone to this behavior.

    When I upgraded from 14 to 15 I did not do a fresh install so I thought that might be the issue, but after a clean install yesterday I've just had another drawing crash! I'm confused because 2015 has been so stable up to this point. I suppose it's worth noting that in the last 6 weeks I've also updated my computer to Mavericks, but according to Nemetschek, VW2015 and Mavericks are supposed to place nice together.

    Computer info and crash log for crashed thread pasted below:

    Model: MacBookPro9,1, Intel Core i7, 2.3 GHz Quad Core

    Graphics: NVIDIA GeForce GT 650M, 512 MB + Intel HD Graphics 4000, Built-In

    Memory: 16 GB, DDR3 1600 MHz

    Mac OS X 10.9.5

    Vectorworks 2015 SP2

    *** CRASH LOG ***

    Process: Vectorworks [7211]

    Path: /Applications/Vectorworks 2015/Vectorworks 2015.app/Contents/MacOS/Vectorworks

    Identifier: net.nemetschek.vectorworks

    Version: 20.0.2 [240846] (20.0.2)

    Code Type: X86-64 (Native)

    Parent Process: launchd [337]

    Responsible: Vectorworks [7211]

    User ID: 503

    Date/Time: 2015-01-10 21:49:53.879 -0700

    OS Version: Mac OS X 10.9.5 (13F34)

    Report Version: 11

    Anonymous UUID: 1E3D402E-C419-99ED-C3F1-324EB50606B1

    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)

    Exception Codes: EXC_I386_GPFLT

    Application Specific Information:

    objc_msgSend() selector name: collectionView:cellForIndex:

    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

    0 libobjc.A.dylib 0x00007fff85540097 objc_msgSend + 23

    1 net.nemetschek.vectorworks.ColorPalettes 0x00000001249bcb20 0x124994000 + 166688

    2 com.apple.Foundation 0x00007fff83b7c93e __NSIndexSetEnumerate + 1316

    3 net.nemetschek.vectorworks.ColorPalettes 0x00000001249bcac5 0x124994000 + 166597

    4 net.nemetschek.vectorworks.ColorPalettes 0x00000001249bce43 0x124994000 + 167491

    5 com.apple.CoreFoundation 0x00007fff86199e0c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12

    6 com.apple.CoreFoundation 0x00007fff8608d82d _CFXNotificationPost + 2893

    7 com.apple.Foundation 0x00007fff83b25e4a -[NSNotificationCenter postNotificationName:object:userInfo:] + 68

    8 com.apple.AppKit 0x00007fff86d4f935 -[NSView _postBoundsChangeNotification] + 179

    9 com.apple.AppKit 0x00007fff86d4f748 -[NSView translateOriginToPoint:] + 294

    10 com.apple.AppKit 0x00007fff86bf7270 -[NSClipView _immediateScrollToPoint:] + 4292

    11 com.apple.AppKit 0x00007fff86bf616a -[NSClipView scrollToPoint:] + 237

    12 com.apple.AppKit 0x00007fff86d4ebae -[NSScrollView scrollClipView:toPoint:] + 203

    13 com.apple.AppKit 0x00007fff86bfadc9 -[NSClipView _scrollTo:animateScroll:flashScrollerKnobs:] + 1688

    14 com.apple.AppKit 0x00007fff86d249c8 -[NSClipView _scrollTo:animate:] + 28

    15 com.apple.AppKit 0x00007fff86eaff5f __68-[NSScrollingBehaviorLegacy _scrollView:snabRubberBandWithVelocity:]_block_invoke_2 + 831

    16 com.apple.AppKit 0x00007fff86eaf205 ____NSPeriodicInvokerScheduled_block_invoke + 58

    17 libdispatch.dylib 0x00007fff8bdae1bb _dispatch_call_block_and_release + 12

    18 libdispatch.dylib 0x00007fff8bdab28d _dispatch_client_callout + 8

    19 libdispatch.dylib 0x00007fff8bdb2ef0 _dispatch_main_queue_callback_4CF + 333

    20 com.apple.CoreFoundation 0x00007fff861324f9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9

    21 com.apple.CoreFoundation 0x00007fff860ed714 __CFRunLoopRun + 1636

    22 com.apple.CoreFoundation 0x00007fff860ece75 CFRunLoopRunSpecific + 309

    23 com.apple.HIToolbox 0x00007fff8b4b5a0d RunCurrentEventLoopInMode + 226

    24 com.apple.HIToolbox 0x00007fff8b4b57b7 ReceiveNextEventCommon + 479

    25 com.apple.HIToolbox 0x00007fff8b4b55bc _BlockUntilNextEventMatchingListInModeWithFilter + 65

    26 com.apple.AppKit 0x00007fff86b9124e _DPSNextEvent + 1434

    27 com.apple.AppKit 0x00007fff86b9089b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122

    28 net.nemetschek.vectorworks 0x0000000104396b01 0x104225000 + 1514241

    29 com.apple.AppKit 0x00007fff86b8499c -[NSApplication run] + 553

    30 com.apple.AppKit 0x00007fff86b6f783 NSApplicationMain + 940

    31 net.nemetschek.vectorworks 0x0000000104227784 start + 52

  15. Just an FYI, I know Blender has native support for UV mapping and is free. Actually it's quite amazing that it's free considering how powerful it is. That said there is a significant learning curve to Blender, but you can find some excellent tutorials online with a quick google search.

    I've had success importing .3ds files exported from Vectorworks into the latest version of Blender to transfer geometry.

    www.blender.org

  16. I'm wondering if anyone else is having a similar experience with Vectorworks 2015.

    I took a 2014 file into 2015 and started drawing in it. After switching to a 3d view, the geometry in the drawing appears and disappears as pictured in the video below. switching between wireframe, open gl, or final quality renderworks does not appear to eliminate the problem.

    Very strange.

    I'm hoping someone else is experiencing this so we can compare notes!

    [video:youtube]

    VW 2014 SP4, VW 2015 Spotlight, Renderworks

    Mac OS X 10.8.5

    Late 2012 Macbook Pro Core i7 2.3GHz

    NVidia GeForce GT 650M 512MB

    16 GB RAM

×
×
  • Create New...