Jump to content

J. Franks

  • Posts

  • Joined

  • Last visited


0 Neutral

Personal Information

  • Occupation
    Stage Designer
  • Homepage
  • Location
    Dallas, TX

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm working with a fresh install of VW 2017 on a new MacBook Pro in Sierra, and Inner Boundary Mode just doesn't do anything. I've never had it fail to create a polygon of some ilk before, even if it wasn't the one I intended. Is there a preference somewhere that deals with the behavior of this tool? I can't pinpoint anything different about the way I'm trying to use it now vs. how I've always used it in the past.
  2. Thank you. I had a feeling a discrete graphics card would be the way to go. I have no issues with moving to VW 2017, so it looks like I'll end up going with the new MBP, since after spec'ing everything out there's not much cost savings to be had by going with last year's.
  3. So I've been plugging along on my mid-2009 MacBook Pro (3.06 GHz Intel Core 2 Duo, 8 gb RAM, NVIDIA GeForce 9400M 256 MB graphics), but it's gotten to the point where it just can't handle the things I'm trying to throw at it. I still run VW2015 because 2016 just won't run briskly enough (haven't even attempted 2017). Not being able to upgrade the operating system past El Cap is the final straw - it's upgrade time. Now that new MBPs have been announced, I'm looking at possibly snagging one of last year's models for a little less money. However, the mid-2015 models Apple still sells have only the integrated Intel Iris Pro graphics, and that worries me from a rendering perspective. (I draft mainly in 2D but occasionally draw and render in 3D, and I'd like to do more of that - my current machine just can't handle it). It appears I can still order a mid-2015 machine configured with the AMD Radeon R9 M370X graphics in addition to the Iris Pro, and I'm assuming that would be the better option, but I don't really know enough about how these GPUs work to understand how much I need. (VW is also only part of what I'll be doing on this machine - I'll need to render in After Effects/Motion, FCP/Premiere, and run Photoshop and other graphics/sketching programs.) Do I need the additional graphics card? Do I need to max out the CPU? Do I just need to bite the bullet and go for the 2016 hardware? I don't know that I can reasonably expect to eke 7 years out of the new machine like I have with my current one, but I'd hope it to last at least 4.
  4. Hmmm...not sure what I'm missing, but I can't find a "Palette Options" in the menu. Under Window I see "Palettes" (which just allows me to select which ones are viewed), "Data Bar Options" and "Edit Group Options," but no "Palette Options." I'm having the same problem as stueey, where I can't get multiple files to open as additional windows. When I first opened 2016, I undocked the palettes manually (didn't know where the menu option was), but that doesn't change the document behavior. Now, I did go through the migration process to import my 2015 settings to 2016; might that be a problem? Do I need to trash preference files and start over? Jeff
  5. I have a 15" Macbook Pro linked to a larger monitor/TV display. I've successfully used this dual-monitor setup for Vectorworks in the past, with the main drawing on my laptop display and the palettes shuffled over and arranged on the external display. The palette positions were saved and they more or less always stayed there, unless of course I disconnected the monitor. I've rearranged things and want to use the larger monitor as my main drafting window, so today I set up the document and moved all my palettes over to the MacBook display. They won't stay there. If I click out of Vectorworks to another program, the palettes move themselves over to the other display when I come back. The only way I can keep my palettes on the Macbook display is if my drawing window is there too. This behavior occurs regardless of whether or not I have "Displays have separate spaces" checked. I upgraded to VW 2015 SP4 today, but it was happening in SP3 as well. Running OS 10.9.5. Am I missing something? Am I trying to do something that won't work?
  • Create New...