Jump to content

HP Sauce

  • Posts

  • Joined

  • Last visited

Posts posted by HP Sauce

  1. Hello,

    I've used it to render for a few years. To start with I was modelling in VW (as I was already comfortable with the 3D workflow of it) and exporting to C4D for final renders/tweaks. Since then I've switched completely to C4D/vRay and don't use VW for 3D at all.

    This transition started out due to something rather silly; I disliked the capabilities of VW when it came to vegetation. Eventually I realised there are some more sensible benefits such as speed of modelling/tweaking, material control, and lighting options.

    It's an amazing tool and I'd highly recommend giving it your time.

    Here's a couple shots showing progression:-

  2. The problem is hit & miss, here is the usual workflow:

    1) open PDF of drawing

    2) rasterise to PNG

    3) import to VW

    If the rasterization process turns white areas to transparent, those areas are then black on import. If white is rendered white, no worries.

    Next time it happens I will come back and attach it.

  3. Here's some further findings on Mountain Lion in a VM for running unsupported versions of Vectorworks.

    Parallels Desktop 9:

    + Vectorworks runs fine. OpenGL support

    - No drag & drop functionality

    VMware Fusion 6:

    + Drag & drop works

    - No OpenGL support

    VMware Fusion is a no-go, currently.

  4. You can use Console to check for crash logs titled Vectorworks listed on the left hand side under DiagnosticReports.

    Better still, when VW crashes, open Console, ensure you have "All Messages" selected on the left-hand side, then type "vectorworks" sans quotes into the search box top-right. You should see a few messages - and probably the same messages repeat each time VW crashes. Take a screenshot of these messages and post them here (use command-shift-4 to take a screen shot). An example is below. Clicking the paperclip icon next to a message opens the relevant log, and will further detail the crash.

  5. I have had to do a fair bit of estimating recently, which i obviously use Vectorworks for. I reckon Nemetschek could make a pretty penny by releasing a takeoff-only version of Vectorworks.

    All you need is the object info palette, scale/polyline/rectangle/circle/locus tools and the ability to import pdf/jpeg/dwg files. Job done... Profit!

  6. Might anyone be able to shed some light on this? I realize it is no longer supported but if anyone out there knows of what is broken, please let me know.

    Crashed Thread: 9

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)

    Exception Codes: KERN_INVALID_ADDRESS at 0x000000007b05379e

    VM Regions Near 0x7b05379e:

    __LINKEDIT 00000000495bb000-000000004961a000 [ 380K] r--/rwx SM=COW /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/GeForceGLDriver


    __TEXT 000000008fedb000-000000008ff0e000 [ 204K] r-x/rwx SM=COW /usr/lib/dyld

    Dyld Error Message:

    Symbol not found: _OTInitInetAddress

    Referenced from: /Applications/Vectorworks 2009/Vectorworks 2009.app/Contents/MacOS/Vectorworks

    Expected in: /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices

  7. Vectorworks 2009 no longer works in Mavericks. Crashes on startup. Such a shame!

    Have been running it in a VM to see if it's a viable alternative to buying 2014. It works fine, but certain aspects are a little cumbersome (no drag and drop between systems for example - yes even with PT installed).

    To be completely honest I am totally let down - both with Mavericks and the 2014 trial I've been toying with. Neither are leaps and bounds ahead of their predecessors. And I might add, 2D performance is clunky compared to 2009, which is snappier even in a VM than 2014.

  8. Due to VW 2009 no longer working in Mavericks we are testing 2014 (which I might add, does not exhibit 5 years of improvement) and deciding whether to upgrade.

    Importing PNG files now doesn't work correctly, transparency renders solid black. Is there a fix for this/have I missed some related option?

    Tried disabling Enhanced Nav Graphics/Quartz etc, no difference.

  9. I believe the reason VW does not inherit OSX's system-wide spell checking feature is because most of VW is still written in Carbon. Correct me if I'm wrong.

    It is incredibly simple to add OSX's built-in spell checking to a Cocoa application, so much so I could run off and write a text editor from scratch in 10 minutes with this function and many others included by default no less. If memory serves, all new NSTextView elements are already set to use continuous spell checking.


    AndiACD: "Another "Basic Essential" loosing out to Racing Stripes and Bells and Whistles."


    Indeed. Expect VW 2011 to ship with LEED??? tools, yet still no spell check or X fence type.

  • Create New...