JMR

We encountered this issue with 2018 SP0-5, on project sharing. After the PS-phase was completed, the walls have remained joined, at least so far. On VW2019 we haven'tried PS yet. The only thing I could pinpoint at the time was the save/commit/refresh process: Workstation 1 displayed nicely joined walls, but workstations 2 and 3 unjoined them at refresh. What is baffling, the unjoins were not the same on different machines. Additionally, no intentional user operations on walls or wall styles were necessary for the unjoin to happen - simply refreshing the PF after doing anything at all on one of the workstations. The workaround was to save the project as .vwx from workstation 1, then reshare-it.

I've wished for the space tool initiation to be faster. 2019 acts faster than 2018, but there still a lag of a couple of seconds, which is way too long.

I ran into this again. The space tool, for some reason, sometimes "remembers" the DL shown previously, including where the walls are on that particular DL. To remedy the situation,restart VW.

Indeed! Those situations are what we mostly struggle with. I don't know if it's technically feasible, but it would be great to be able to stretch components in sections and elevations as well. Currently one has to create a zillion of different wall styles to achieve that, as far as I'm aware. A stepped wall affects the whole wall structure, I think. If a wall could be a system where one could manually shape, cut and stretch every component in all directions...now that would be something. Then the user could simply select for plan presentation "show these joined" or "show these with a line in between" etc...okay, I admit I'm daydreaming. But still.

Hi all, The idea (don't think this is possible currently?): 1. Point at an object (eg. a space) to pick up the object type and properties 2. Inject on a "seed" object (eg. a rectangle) 3. A new space object is created from the seed object. This is similar to "create a similar object" and "create new object from shapes", but would kind of combine the two. Faster than going through the menus.

Hi all, In some situations, joining wall components is mighty difficult and even impossible. There are no good workarounds since using multiple separate walls generate their own issues and is not "BIM". Wall end caps are sometimes problematic as well and do not fit well into wall joining situations. Would it not be possible to be able to stretch wall components to where they should be? Simple end-of-component dragging. Please see the below, these kind of joins are very difficult to use and maintain by using the standard component join. Maybe component-join functionality could be improved in stead, currently they don't always "obey" what the user says. Sometimes it is crucial to be able to manually stop a wall component at some certain position, eg. the white wall component should stop before the green bearing strip. Currently the bearing strip is in front of the wall covering it up, howerer at dwg export this is revealed -> the engineer is confused. Component priorities have been suggested before, maybe those could work as well. The core issue is that we should have absolute, working control where any wall component ends/joins.

This problem has been with us from 2017....on all Windows workstations in the office. No issues with any other application.

That would work too. Quality is the key. Continuous updates would require a very robust rollback functionality though, since eventually something, for someone, will go wrong despite best efforts of the programmers.

We use PC's.

Hi all, I find that the space tool reads nonexistent geometry in an empty room. Please see attached. All classes are on and other DL's invisible. Anyone else?

No, you're not! I thought we were the only ones. We see this almost always. For us the cursor refuses to move until one fiddles with the alignment settings once, eg. changing the alignment to right and then back to left. After this operation the cursor can be walked to the correct location. It almost never goes to the clicked position directly. This is a small but really annoying issue. I think 2017 was ok regarding this.

There has been improvement as to the speed of the space tool in 2019, however it still takes too long a time for the tool to "boot".

True, but that would be a very rookie mistake, no?

Hi all, The clip tool is a very fast way to edit objects and one of the more powerful VW features. Why not allow the clip tool to clip walls in plan, at least orthogonally? Splitting using the split tool is not that fast IMHO.

IMHO this is what NNA should do (in order to avoid losing all architects as their customers): -Hire, or extensively consult, a couple of experienced (+15 years) architects that have RUN practices. Not just experienced guys per se. Being responsible for several people's work certainly gives you a wider perspective to quality issues. Preferably from different continents to enable the tools to accommodate different ways of representation etc. -Fix ALL known issues. There is a huge amount of information on these on this forum alone. -Switch to biannual or triannual version cycle. Look at what McNeel does with Rhino, major updates are few and far between and overall quality is great. -Implement ALL wishlist issues that have unanimous support from the users = no questions as how to implement. These include doors, windows, stairs, 2D representation of 3D graphics. For example, a single glazed window object...it's the end of 2018. -Go through ALL tools that users have reported that don't function, like 3D cut plane (totally useless as it is) and make them COMPLETE = reliable and predictable usable in professional practice. -Refrain from new tools until everything accumulated has been fixed. -TEST and let some customers EVALUTE new tools THOROUGHLY before releasing! Eg. the title block "apply revision to all sheets" by default is something NO architect would EVER want on by default. It has messed up hundreds of our sheets, I still keep finding "revisions" on wrong sheets, especially since the title blocks don't update as they should (2018 SP5 at least). The 2019 release was baffling. It was supposed to be about quality, but like someone said it's been a kick in the face. Testing ? Year 2019 will be the last VSS round for us. After that we'll contemplate what to do. More and more time is spent on debugging and inventing workarounds. The price difference to competitors is MEANINGLESS if one considers this. In my previous life I used another package and it NEVER had any reliability/quality issues like these. Sure, there were some clumsy tools and not that many fancy features, but things were RELIABLE and worked PREDICTABLY. This is of paramount importance to an architect's practice. To sum it up, don't mess it up NNA! You have a great product, IF...