Jump to content

PVA - Admin

Vectorworks, Inc Employee
  • Posts

    12,808
  • Joined

  • Last visited

Posts posted by PVA - Admin

  1. 8 minutes ago, BenG said:

    @JimW 

     

    Jim,

     

    My VW18 SP6 program is sort of  having a meltdown.  I get a spinning beach ball (about 5 min) somewhat at random after selecting a function (dimension, rectangle….).  The flyover tool has stopped showing the origin point and may rotate about a global axis rather than the selected point.  I get the VISION Library dialog randomly.  The Snapping window will not stay open.

     

    I followed all the suggestions for clearing out .plist files - twice - and the problem just moved around.  I have reloaded the .dmg with cold boot.  No improvement.

     

    I tried to follow the instructions in this thread about deleting the RunTimeCache folder, but I can't find it (see attachment).  

     

    What do I do now?

    Screen Shot 2019-02-01 at 10.10.39 AM.png

    MacBook Pro.spx


    In that case, contact tech@vectorworks.net directly. They can walk you through the process step by step.

  2. This is what I found with the cloth shader as well. This, along with a few other values like blur quality, are too strongly tied to the overall AA setting and need to give the user more direct control. For instance, some rendering applications let you set the AA value for different effects independently, which may be a good solution. I'll check and make sure I filed a formal request (I came across this kind of this before the summit during prep) for it.

  3. I honestly like the effect, reminds me of The Matrix.

    But in all seriousness, theres a really cool tech that can almost do this we've been experimenting with:
     



    And I can almost guarantee that engineer's moment of inspiration was looking at one of these half finished light phase renders!

    • Like 1
  4. On 1/26/2019 at 10:41 AM, bobhs said:

    Hi,

    VW Architect  2018, Imac 27" Mojave 10.14.2

     

    When I start to dimension in a viewport annotation using either chain dimension or single dimension the program freezes and I have to force quit.

     

    I opened a new file and pasted in the object hat I want to dimension and have the same issue.  I can use chain dimension for a longer period of time (two or three dimensions) before VW freezes again

     

    Interestingly, the file will not show up in " open recent" when I restart VW even though it is saved and appears on the desktop.

     

    Has anyone else had that problem? Any ideas?


    I recommend performing a backup and full reset as described here:


    I have had quite a few users on Mojave need to do this after the 10.14.2 and 10.14.3 updates.

  5. Welcome! No, the educational version is functionally identical to the full professional version other than it's watermarks.

    You may just need to go to View > Rendering > OpenGL to get the view you're expecting.

  6. @M5dThe benchmarking referred to in this thread is not the benchmarking of hardware nor the effect of hardware on the software, but the benching of versions compared directly against eachother.

    As suggested further above, in identical files on identical hardware, to give an idea of whether the software itself is slowing down as releases progress. I plan to do this testing and post it, I hypothesize that for things like geometry calculation and duplication, we will see speeds increase for 2015, and then remain very much the same until today on the same hardware under the same test conditions, we will see if that pans out. This information is as valuable to me in working to improve the software as it is to you all in your decision of whether to purchase in the first place, upgrade regularly, or to choose another package entirely. I don't want anyone using Vectorworks that doesn't feel it is worth its cost, and I am not personally willing to deceive people in order to drive sales.

    Whether I like a tone or not is immaterial. It is imperative that this forum be kept clean of false accusations and misinformation. If there is information I posses that I do not release, it is because that information is still covered under NDA. The things you are saying are incredibly important and need to be said, thank you for saying them, it is only the tone and the accusation of intentional deception that I have to take issue with. Lets just drop this portion of the debate entirely and keep working to make things better.

  7. 12 minutes ago, line-weight said:

    I know specific queries about that graph are probably exactly not what you wanted to encourage by posting it - but is it indexed to number of users? That is, if in a certain week you see a similar number of crashes in 2018 SP5 and 2019 SP2, but there are at that point 10 times as many users sticking with 2018 as have moved to 2019, then that means 2019 is crashing ten times as much, if you see what I mean.

    That chart isnt, no, it's strictly volume of crashes in total.

    When we do the mega charts internally this is shown followed by comparisons like crashes-per-day-per-user. We also have to account for other things like time of year (December and January are generally quiet in terms of how many people are using the software) as well as things like OS compatibility. For instance, there were a huge load of crashes related specifically to Mojave, but we can also separate the Windows and Mac data to see if it really is a spike just because of the OS or if crash rate is raising or lowering independent of the OS.

    I actually love the heck out of our analytics tracking, and engineering has been repeatedly doubling down on it. For instance, I got a real morale boost when we started discussing how "Quality is not a Switch" and not something that will simply exist or not exist within a version, but something that must be tracked and catered to as much as any other aspect. We always cared before of course, but now we care AND have tools to back up our decisions with data.

     

    1 minute ago, mjm said:

    Can that chart be drilled down to show filtered by machine type (MBP 15" late 2015, for ex) or by os, etc?

    It doesn't go by machine year that I am aware of, but we can indeed peel off and look at JUST iMac Pro configurations, or MacBook Pro, etc and then effectively sort out specific ones by CPU or GPU options. It's less easy on the Windows side since there are so many configurations, but on that side we can also split it up by GPU or CPU to see if there's a hardware specific trend. We have a lot of alerts set up now to warn us ASAP if something like "Anyone with a GTX 9800 is doomed" happens after an update for instance. 
     

    I can share and discuss these metrics to some extent, but there are things I am not permitted to reveal because of our user privacy rules, which I am more than happy to abide by. Too many companies let that stuff slip these days. I will gladly answer all questions related to it that I can within that ruleset.

  8. On 1/12/2019 at 12:42 PM, Zeno said:

    Sorry Jim, but if you have 86 bugs fixed related to Space Objects, why do not you release them now without waiting for sp3?

    We cant just send the fixed ones back one at a time, they have to be pushed in a build. 

    Eventually, we want to be able to correct them piecemeal and then send the updates out and have it patch in the background so you never even know you had a bug, but our tech and process aren't ready for that yet.

×
×
  • Create New...