Jump to content

RGyori

Member
  • Posts

    374
  • Joined

  • Last visited

Posts posted by RGyori

  1. As my ever patient wife frequently points out (which says more about me that her), "Dear, there are no problems , only solutions". And Jim is a proven master of directing us to those solutions. Much appreciated!

  2. 13 hours ago, Francisco J. D. Rogers said:

    Im working with VW in a MacBook Pro and an iMac with High Sierra. All works fine except an issue in the Info Palette

     

     

     

     

    Thanks Francisco. It is encouraging that it generally works with VW2017 which I expect will extend to next months anticipated release of VW2018.9_9

  3. 3 hours ago, Dave Donley said:

     

    Hi RGyori:

    Top/plan view already takes advantage of multiple CPU cores.  The final frame drawing (after zooming or panning etc.) is divided up among however many cores you have, to speed up the drawing operation.  The multi-threading also allows Vectorworks to more quickly respond to any user actions before the drawing operation is finished.

     

     

    Thanks Dave, just when I thought i knew it all! 9_9  A part of my question came from considering the $ vs performance value of the upcoming iMac Pro . 

     

  4. Hello iEscape, I don't know if I can add much to what  has already been said so, if you haven't already, upgrade to the latest version of MouseWorks (1.3.0 I believe) would a first step. 

     

    Regarding my earlier post, rather than restarting the computer to escape odd Expert Mouse behavior, I now just unplug/replug the USB cable. Immediately corrected my problem. Perhaps analogous to whacking a stuck starter motor with a wrench. 9_9

     

     

  5. I believe if you go to the Windows menu and uncheck "Use Application Window" VW will revert to the conventional 2017 layout.

     

    HTH.

     

    Just to add: I too was a bit put off by the new Applications Window setting but have grown to prefer it. It allows auto docking of pallets for instance and moving between open VW files is simpler. You can dismiss the window without closing VW by double clicking the in the menu bar. I have assigned this double click to a key on my track ball.

  6. Unfortunately I am not familiar with being able to use that button combination + trackball to zoom in and out. I just checked the button combination options for "applications" in the TrackballWorks preferences and found no mention of zoom. In any case I will look into upgrading my TrackballWorks to 3.0 and see what happens!

  7. Hello Gtown,

     

    First of all you should note the OS and VW versions you are using in your signature... (find the drop down menu under your name in the upper right corner and select settings to add this info tour signature)... essential information in many cases 9_9.

     

    I too have upon occasion experienced odd behavior with my Expert Mouse forgetting specific actions I assigned to particular keys. To no rhyme or reason that I have been able to determine. The  only reliable solution I have been able to find is to restart the computer. Hasn't happened often enough to warrant further investigation for me. I use TrackballWorks version 1.2.1 and is true for my work and home machines which run OS 10.10.5 and 10.11 respectively.

     

    Hope this helps.

     

    Bob

    • Like 1
  8. I would like add: If you experience difficulty acquiring, for instance mid points of walls or other objects at smaller scales, it might help to disable Master Snap Points (found in Smart Cursor Settings > Objects). Avoids having to regularly zoom in using the Z key to find the desired edge or point. At least it helped me. 9_9

  9. I'm a single seat, I work every day using VW in both 2D and 3D, but have experienced no significant problems. No more crashes than I had with 2016 and earlier which means roughly once every 2 or 3 weeks. 

     

    Graphic performance (using good performance and compatibility setting) is stable, i.e.and no worse than 2016.

     

    With that said here are several oddities that I attribute to working on files that started out as 2016 or earlier files. For instance Batch Convert works most of the time but I have experienced  the situation where some files won't translate unless individually opened in 2017 and then saved one at a time. Also have experienced the situation where a newly created or copied object did not show up in the OIP.  Did not reoccur after copying (laboriously) each design layer + objects over to a new 2017 file.

     

    On the whole I'm doing just fine.

     

    Bob

×
×
  • Create New...