zeno

May 10

I suggest to create a hybrid symbol who you model auto hybrid object near parametric object. You can reference everything on the symbol x y z parameter. Then you can create a big symbol when you manage also the 2D hole. If there are part between wall and symbol who don't get well you can adjust them by continuingmodelng and autohybrid. I suggest to use material, so you can have the right representation on sections. Is not very smart but works

April 29

the time factor is crucial.

There are importan mac youtuber in Italy who in the absence of other software ready for apple silicon show Revit Benmchmark emulated on windows. The opportunity should be developed soon. The thing is simple to reproduce: it would be enough to duplicate objects on many design layers. Ore something needs high CPU/GPU processes But I recommend: do not put any structural elements, which could be a bad boomerang

I wouldn't just focus on rendering. I wouldn't call it an exclusive field.

thank you

April 15

On 3/26/2022 at 10:40 AM, GatRed said:

Hello, I'm sorry for what I'm about to write but it's quite unbearable to see how nothing is changing on the side of doors and windows tools despite the many comments made on this forum and to distributors (design express in my case).
I really do not understand.

Doors and windows are important elements in architecture and they are also industrialized elements. Because of their variable dimensions, parametric tools are necessary to avoid modeling them one by one.
Why is Vectorworks failing to make this tool?

I note that many distributors have created their specific tool and I have tested the following:
American, (former) French, German/Italian, Belgian/French/Dutch, Australian.
NONE allows to have both a correct use and a correct representation in advanced phase of study.
By arguing local specificities, energy was spent for nothing by developing several tools when only one would suffice.
Having worked in Great Britain, Germany and France, no local specificity justifies different tools.

Please stop this.

Would it be possible to concentrate development efforts on a single tool to have a tool that works?

From my point of view, but it is debatable, the express design tool (belgium, france) is the most advanced in terms of options and representation, but it is unusable because badly programmed (long time to draw each element ) and because it doesn't have a style option.
The American tool behaves well, but it does not offer enough representation and drawing options.

Vectorworks, for architects who design spaces and need windows to bring light into their buildings, when are you going to seriously upgrade these tools?

Hello. Believe me I can really understand you. I'm designing 13-story buildings with details down to the millimeter and everything has to match exactly what's going to happen in reality. I'm not telling you about the fact that I will probably be locked up in some strange hospital at the end of this job, but for the windows the only way I could go was this. I work with the Italian version. But I also spent several days figuring out which window to use. The Germans (from which the Italians derive) do important things, the USA other things. All together there is not. It's okay to get angry. But then you can understand that either you expect the tool that does everything to arrive, or you try to make a difference by trying to understand how to adapt the tools to your goal. From here a few weeks later, thanks to the German window, to many autohybrid objects, and to a lot of patience I was able to confirm that if they had ordered those windows they could throw them in the garbage because they simply did not fit in that building. Remember that the whole set can be saved as a symbol. Self-hybrid and parametric objects together. A symbol as sure as you know can go into the wall. I had prepared the base in 2021. Then in 2022 at the beginning there was a panic because for a period the holes of the old symbols did not work. Then they solved it luckily, because without the support for M1 and then M1max I don't know how I would have done it. So, in my opinion, you are right to get angry. But get angry to ask for improvements but study a method to get to the end anyway. I think it makes the difference between a user who knows how to use software and a user who takes that software, bangs it on the wall, and beats it until he does what he wants, exactly how he wants it. To do this, being angry can be helpful.

Don't give up. Using Vectorworks need passion.

April 8

Luis soi encantado de tanta meraviglia!

April 5

5 hours ago, line-weight said:

The files in which you have issues; were they created in VW2022 or in earlier versions?

One thing I have noticed in my own files with similar problems, is that it's worst when I try to view a sheet layer that would have been created in a previous version of VW, and one that I may not have looked at or edited since converting to VW2021 or 2022.

Work started on 2021 but 70% was done on 2022

April 5

Already reinstalled 3 times. Every vw component following istructions on https://forum.vectorworks.net/index.php?/articles.html/articles/how-to/uninstallation/uninstalling-vectorworks-r268/

the problem persist only on a big file. But several times when I was teaching other people it happened that to continue working with vectorworks it was necessary to restart everything after several section viewports. Imemory remains busy after a complex process i think. Having a M1 Ultra with 128 GB memory can only postponed this process if no way is found to clear memory when terminating a complex viewport computation process. i was very worried about not being able to finish a job with m1max and 64GB. I was able to find a method. the point is that I can work with it without stressing the machine as much as it works. but if I don't restart vectorworks, as I said, I go from 35-40 GB directly to 190 GB. maybe it is when I have an ultra m1 I can do two sections, certainly not three

April 1

On 3/30/2022 at 6:22 PM, Sky said:

I went back and found that my memory leak problems (exactly like yours) started in VW2017 SP4 and it seemed to continue through VW 2019. I actually don't know how it resolved itself because I didn't post a solution in that thread. But it was suggested to reset VW preferences.

Reading these considerations sincerely worries me a little. I thought it was a recent problem but I see that it is one of those problems that have been known for years. I have been running VB-183608 for months and it has been considered, but not fixed. It is clearly some major improvement that could be made. The biggest problem is that today it is not possible to update so many viewports during a period of user inactivity, such as overnight. Can you tell us on which files exactly this problem was happening to you? PS: I already reset user preferences hundred times.

Thank you

March 29

5 ore fa, Matt Overton ha detto:

Hai un supporto con ventole integrate per il raffreddamento?

O il calore non tende ad essere un problema.

Absolutely not a problem. I use the stand only to have a better visibility

March 26

28 minutes ago, Christiaan said:

43"!! Wow, which one is that? How far away do you sit? Can you post a photo of that setup with Vectorworks on screen @zeno?

Trust me, 43 is the right size, you'll not come back

March 26

27 minutes ago, Christiaan said:

43"!! Wow, which one is that? How far away do you sit? Can you post a photo of that setup with Vectorworks on screen @zeno?

MBP 16 on the left, 43 inch in the middle https://www.lg.com/it/monitor/lg-43un700-b, 27 on the right, iPad Pro 12 on bottom

March 26

18 minutes ago, Christiaan said:

If you were to go for this configuration, for another 900, I would seriously consider going with this instead. Add a Studio Display and you have the same setup + portability.

I got the same machine with a 43" lg display. It changes totally my workflow

March 25

140 for you guys 👀

March 25

2 minutes ago, Tom W. said:

I'm getting same thing - horrible

This has been going on since 2020-07-27? Hope it's sorted soon...

Did you try it on 2022 sp3 too?

March 25

Hi Jimmy

i have the m1max on MBP and everything going well. Could you please share a little video?

March 25

Good Morning

I'd like to share with you the first in-depth experience with this new system, which I consider light years ahead of before, but which certainly, having been a long time and the technologies being improved also in the whole market, in my opinion it needs some important points to be solved in very short time, while for other things you can wait even longer.

First let me exhale my enormous pleasure to see a model, even a large one, that can be shared with a link. In which you can turn the layers on and off, in which you can right click to point to a position and get there. It helps a lot, alone is a change that alone is worth a single thought: thank you for this work.

Now that we are here, however, I would like to be able to say the most important points.
- I had some problems with safari. No problem with chrome
- I had some problems using the clip cube
- The possibility of inserting borders must be added immediately. Even before ambient occlusion. In this way we risk losing much of the usefulness of this enormous work. The lines must be thin, no cartoon effect, and they must not show all the problems that vectorworks has with hidden lines rendering, where it always shows an intersection where in reality there isn't. This is a very important point because it makes the difference between understanding a project and not understanding it. I believe that here we first need to understand volumes, then calmly we can arrive at more realistic renderings. The rendering of the textures seems to me more than good for now. I only have problems with transparency.
- I believe that implementing visibility of classes and saved views is something that does not require a lot of work, but that would also radically change the experience here!
- It would be very useful to be able to add the visibility of 2D objects. For example, I would like to show how I developed a complex BIM model from 2D drawings of a structural project. If I could add it, it would be very clear to everyone. I add a screen to show what I mean.

These are the most important things, for the others as higher quality, leaps in time and space I would abandon any development for the moment.

I hope you will continue from this point of view, because what you have done is really beautiful, but in my opinion, as a user and designer and teacher, some very important elements are still missing.

Thank you thank you and thank you again @inikolova

March 24

12 hours ago, Sky said:

@line-weight I used to have to do that with VW2020 and maybe VW2021 but I don’t exactly recall when that problem went away for me.

I just looked at the Activity Monitor while rendering in VW2022 on my MacBook Pro M1 Max, and it looks like after each rendering is done, it releases the memory so I don’t run out.

I’m sorry I don’t have any advice for you, but I’m glad that problem went away for me.

on my experience, section viewport rendering takes max 30-35 gb and then they are correctly calculated. If I don’t turn off vw and reopen the file to do a second render, the memory going over 50. From 50 the memory request incres up to 190 GB but every time (trust me, there are months i’m trying to find a solution) without success. So: 35 GB after reopen vw, or 190 GB with s collaps

March 24

15 hours ago, line-weight said:

At the moment, I have to do them in batches. Do the maximum number that I can get away with without the memory collapsing. Wait for it to complete. Save the file. Quit Vectorworks. Re-open Vectorworks, re-open file. Do the next batch. Repeat.

welcome to the club. It’s the true. I suggest to work with more than one computer if you can.

March 21

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.

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!!!

March 21

Il 17/3/2022 alle 22:57, Kazemester ha detto:

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

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.

March 10

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?

March 10

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.

March 10

24 minutes ago, Anders Blomberg said:

@zeno I guess so. As I understood it from @SteveJ the publish command is one of those commands that doesn't benefit to much from more cores. But again, I'm far from an expert on this 🙂

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.

March 10

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?

March 10

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

February 18

The bug is resolved. I suggest waiting sp3

Profiles

Forums

Calendar

Articles

Marionette

Store

Posts posted by zeno