-
Posts
971 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by zeno
-
-
Il 17/3/2022 alle 22:57, Kazemester ha detto:
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.- 1
-
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?
-
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.
- 1
-
- Popular Post
- Popular Post
24 minutes ago, Anders Blomberg said:Me too. We are architect and we use software to manage project etc. I'm year light to understand how difficult is rewrite a code command or similar. But not from now, maybe even from 2009 when I was using my matte 17 inch MBP unibody that it was possible to take advantage of a multicore architecture.
The transition from intel based to universal software was truly fantastic. However, there are points where the project encounters slowdown points that compromise all the work done, even with many tools that exploit the GPU and therefore, if they are very large, the difference can be seen.
The section viewport, at least from my experience, and therefore the public command, are two tools that in the calculation are still too slow, and exploit too little the performance of the hardware, I think.
I would like to buy an Apple Studio with m1ULTRA and 128 GB of RAM, and I will probably repeat the test I did here and I'll post the results.
But you know, in my opinion discussions can be useful, and this forum proves it. But if currently with the publish command you can export PDFs in different sizes and JPGs or images in one size only, the section viewports are calculated at 1 thread, you can make the projects beautiful and huge, but you find yourself (like me) that in phase of layout seems to you to move huge stones using a spoon when you have the keys of a tractor in your hand. Having a huge tractor to keep using a spoon, in my opinion, is not the best way to go, even if you can go faster than before.- 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!
That's why M1 ultra show 1,6x and M1 max 1,3x?
-
- Popular Post
- Popular Post
15 hours ago, SteveJ said:Recall the single M1Max is quite fast - some might chime in here. We will get our hands on ultra asap - and share what we find! I would not expect it to be slower than M1Max. and you have the 128GB option. If you currently use 128GB for your projects, this is very nice news!
Dear Steve,
here a section viewport example I'm working on my m1MAX with 64 GB. I need every time turn off Vectorworks to calculate a second one.
I understand that ULTRA will open new doors but maybe can be something to do on section viewport memory request?
One way to better machine, one way to better software. And yes: section viewport should be a multi CPU process, like Publish command, spec for Big BIM files. Let me if I'm wrong: are publish command and section viewport process single thread CPU process actually?
Looking forward to see ULTRA in action with VW
Thanks
- 5
-
The bug is resolved. I suggest waiting sp3
- 2
-
I have already created a VB 184521 on Jira as Betatester and pointcloud user. 2022 doesn’t render viewport well. There are no update from 2 January 2022
- 4
-
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
-
-
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
-
2 hours ago, line-weight said:
In what way?
Connecting a 27" dell 4k monitor and creating a floating view
-
Found a issue, seem resolved with last beta
- 2
-
-
-
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
-
@Matt Panzer hello Mat, hope everything's well
please could you take a look to my Z88_Redshift hide symbols only on section view VB-184497?
It seems that with my symbols in wall there are important issue on section viewport. Same object are rendered correctly on iso views but not on section viewport
-
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 levelsfor better detail
-
- Popular Post
Working on very big buildings required a lot of patience. Referencing layers is a good solution for geometry but VW is not ready for this. Every time you need a worksheet or you getting in something complicated you lost every reference. Same with symbol. I switched from DLVP to “all in place” because i’m getting crazy. Actually the big problem is that if you use big symbols for apartments or similar you lost EVERY stories references. you have to be able to “run on eggs without breaking them” (we say in Italy) to handle complex parametric models. it can be done, I'm doing it and a beautiful job is coming. but it has become so complex to escape from all limits that sometimes I too find it hard to understand what I am doing and it is very dangerous
- 6
-
2 minutes ago, Matt Panzer said:
If you can create a reproducible case of this where the wall hole shows and then goes missing, please let me know.
While I see the problem in the file, I cannot make the problem happen.
Thanks!
On my files I resolved after the sp2 b2or3 but yes, I'll let you know
- 1
-
5 hours ago, Mark Aceto said:
This times a million. I hate Apple so much for this. Would it kill them to release the new hardware with the most stable version of macOS?
hello Mark, how is going with the new mac and VW? -
7 minutes ago, rjtiedeman said:
Since macOS 12.1 is due out in several weeks what are the chances that Vectorworks 2022 SP2 or 3 will function with 12.1. Should we update to OS 12 now and hope VW2022 SP 3 catches OS 12 or wait.
The problem is that on new MBP you can't install Big Sur
- 1
-
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.
I had the same issue. Try to remove and reinsert the doors and windows, let me know if it works
-
3 hours ago, trashcan said:
@JuanP can you update your article with the latest compatibility info? Wondering if I should upgrade and it's not really clear.
Yes please
Mac Studio & M1 Ultra
in Hardware
Posted · Edited by zeno
Take this! 118 GB!!!