Jump to content

zeno

Member
  • Posts

    971
  • Joined

  • Last visited

Posts posted by zeno

  1. 3 hours ago, line-weight said:

    More fun times in VW2021 today - and a new record of >50GB being used by VW on my 16GB M1 mini.

     

    147255985_Screenshot2022-03-21at14_45_56.jpg.528c49bf0c9bac8db3176d3d3168903a.jpg

     

    I don't really understand how it can need that much memory. In this case, I was looking at a single sheet layer (file opened looking at it, so it's not cached anything on other layers from this session), on which were 9 perspective view renderworks viewports. All un-rendered - so showing the model as wireframe.

     

    A few JPG images on the sheet too - but their size is measured in 10s or 100s of MB only.

     

    If VW needs 50GB of memory to show me 9 viewports, that suggests it needs around 5GB for each viewport. That's for a model the entire file size of which is <2GB.

     

    One thing I noticed, once I updated the class visibilities for each of those VPs (so they each were viewing a smaller number of objects) then on next file opening, memory was sitting around 20GB and I was no longer getting constant beachballs.

     

    My understanding of how memory works in these scenarios is no doubt naive but I just don't get how it can need that much.

     

    Take this! 118 GB!!!

    126470449_Schermata2022-02-22alle00_03.24-2.thumb.jpg.11f61d534cedbc1c11922e22b82170a2.jpg

     

     

     

    Schermata 2022-03-21 alle 21.21.17.jpg

    • Like 4
  2. Il 17/3/2022 alle 22:57, Kazemester ha detto:

    @zenoSP3 non ha ancora risolto questo problema. È un po' meglio, ma comunque...

    come dovrebbe essere.png

    com'è.png


    hello. You can’t render pointclouds on hidden line. Only shaded mode. But you need to see it clearly so i suggest you to render the cloud on max 90-100 dpi (maybe less 60-70) and then duplicate the viewport if you need to do something else. The bug talked about the issue on sp2 where you can’t render the cloud whit shaded mode on 2022. 
    but i’m not sure i’m understand what what you need exaclty.

    • Like 1
  3. 8 hours ago, line-weight said:

    I'd like to give a couple of examples of things where I have found the performance of Vectorworks 2022 on M1 disappointing.

     

    These are both "everyday" tasks which, having been told that VW2022 has native support for Apple Silicon, I might have hoped would see improved performance compared to VW2021 on the same computer. But in fact what I see is either no improvement or actually *worse* performance.

     

    They are both tasks that I might be commonly carrying out in a repetitive manner and therefore have a significant impact on speed of working. And although this is a large and complex file, I don't see that the tasks themselves are ones that ought to be computationally difficult.

     

    This is VW2022 SP2.1 on an M1 mac mini with 16GB RAM. The VWX file size is around 2GB.

     

    First, moving a single viewport on a sheet layer, then undoing the action:

     

     

     

    Second, double clicking on a group to edit within that group, then double clicking a symbol to edit the symbol, then exiting the symbol, and exiting the group. This doesn't happen as painfully slowly as the previous example, but in real world use it's something you might do repeatedly and it all adds up. To me it doesn't feel unreasonable to expect that something like this (entering and existing a container object) should happen instantaneously.

     

     

    Someone may tell me that this is all down to lack of memory.

     

    You can see that VW is occupying a lot of memory - about 30GB, which in my limited understanding means it's swapping a lot of stuff in and out of some kind of cache somewhere. But why is it using so much memory when the exact same file in VW2021 seems to use up about half that amount?

     

    I meet the "mid level profile" hardware requirements listed here

    https://www.vectorworks.net/sysreq

    although I don't meet the "high level profile".

     

    Therefore I might expect that I am pushing things a bit with this file which is quite complex, so I would forgive things being a bit sluggish if I want to navigate the whole model in 3d with shadows on, or something like that. But these seem quite simple tasks to me. Or is it that the file size is simply one that an M1 machine with 16GB RAM can't be expected to handle efficiently?

     

    Hi

     

    what happened on CPU tab on same process?

  4. 22 hours ago, Anders Blomberg said:

    The performance increases for other software are reported to be 3x or 4x but for VW it peaks at 1,6. I'm guessing this is because performance increases for processors these days seem to come mainly from more cores, and Vectorworks only use a single core in many tasks, as I understand it.

     

    Absolutely agree.

    • Like 1
  5. 1 minute ago, Anders Blomberg said:

     

    Thanks for engaging in this @SteveJ! It's nice that Vectorworks is taking advantage of multiple CPUs in some tasks but from my experience the typical CPU load looks as below. The task that triggered this single core spike was changing the name of a landscape ares style, reflected in roughly 120 landscape area objects. While VW might be able to utilise multiple cores for many tasks I see these single core spikes for so many tasks in my day to day use. It is a little frustrating having to sit and wait for tasks to compute and at the same time seeing all those other cores not being utilised. I'm glad for the improvements VW have done in this area and look forward to further improvements!

     

    image.png.6921a5dbd9bb812be7d80b47bb037383.png

     

    That's why M1 ultra show 1,6x and M1 max 1,3x?

     

    731224309_Schermata2022-03-10alle08_42_08.thumb.jpg.f9197ae36ea69abceb380aaa4a0084b2.jpg

  6. 7 minutes ago, Wesley Burrows said:

    And honestly I never saw VW use anything egregious in the ram department.

     

    Because you've probably never tried to merge point clouds in the same file. 🙂
    May I ask you what level of virtual memory can you reach? The maximum memory footprint indicated by the apple activity tool.

    I ask you because in the tests I did here

     I was unable to do things that I could do with an old imac and several times I thought it was both a vector and maveriks problem

  7. 24 minutes ago, line-weight said:

     

    Do you mean graphics performance is affected?

     

     

    I don't write software codes but whit a m1max with 64 GB if I can see a drastic performance reduction and with tools like iStat I can control that almost 40% of machine performance are busy.. I can suppose that the issue is somewhere into a code. Something like "don't ask more to the machine but split the original process into x part". But off course I can't confirm because I'm an architect not a software engineer 

  8. Same situation on VB-172889 created on 2020-07-27 09:05 AM and rated as Moderate

     

    Actually same problem persist and users can't create any views if stairs and clip cube are present

     

    510819230_Schermata2022-01-19alle10_02_45.thumb.jpg.fdbf811866b4650d733b54dfda1f5220.jpg1968566934_Schermata2022-01-19alle10_17_10.thumb.jpg.e2ef962d6b00eb0de691fc932d6246be.jpg

     

     

    • Like 4
  9. 6 hours ago, Matt Panzer said:

     

    I've been looking at the file but cannot get the viewports to render using RedShift at all.  Perhaps my hardware is not up to snuff...

    In any case, it surely looks like a bug with Redshift since the other modes render correctly.


    sorry matt,

     

    but both viewports are rendered with redshift with same settings and same class and layer visibility. Even hidden lines have the same issue only on section viewports. Seems it is something between symbols in walls and section viewport.

     

    thanks

  10. On 12/10/2021 at 8:28 PM, zoomer said:

     

    Ciao @zeno

     

     

     

    Hmmh,

     

    I have never seen this kind of Setup before.

     

    Basically you are using just VW Stories but no Levels (?)

    (You are using a few Levels, but 80% of them are at 0.00 Offset to Story)

    Therefore no way to bind PIOs to different Levels like

    "Bottom of Structure Story above"

     

    And you still need to Assign Layer Wall Heights.

     

    So the only advantage using Stories+(no)Levels for changes is,

    that neighbored Stories (and their bound Layers)

    will intelligently react to a change of an intermediate Story Z change.

     

    In case of a Story's overall height change, you would still need to manually adapt

    Layer Wall heights selectively (?).

     

     

    EDIT :

    OK, automatic Layer generation by Stories.


    exactly. This work was setted in this directions. Actually i use a lot of levels

    for better detail

  11. 3 hours ago, gfebres@gfarch.ca said:

    After updating to 2022 SP2 many windows and doors stop "cutting" walls in shaded view (only in shaded view).

    I went back to SP1 and after removing and reinstalling the doors and windows, everything works OK. In a version of 2022 - SP2 I tried to fix the walls, checked for duplicate walls, deleted door and reinstalled door. One way of replicating the issue  to change the label of a door; the wall stoped working.

    I am attaching several scree shots with 2022 - SP2 and one with 2022-SP1. I also tried opening the file (in 2022- SP2) after fixing it with 2022- SP1 and it displays properly in 2022-SP2.

    I can not update to SP2 in my main computer (iMac 27 inch 2017), until this issue is resolved, do not want to have to rework files again.

    494365469_ShadedView2022SP2.thumb.png.063f74e8a5ccc523d0623c264c005111.png

    Top Plan View 20222 SP2.png

    Wireframe View 2022 SP2.png

    Shaded View  2022 SP1.png

     

    I had the same issue. Try to remove and reinsert the doors and windows, let me know if it works

     

×
×
  • Create New...