JMR

I get ok results with the actual stairs, but the railings are a constant headache. Where the railing goes around the landing, there is a strange vertical jump. This renders the railing unusable elsewhere than in plan.

What I like about VW is that it's like a large Swiss pocket knife. It can do so many different things. For us the ability to assign custom records to anything and use these with worksheets has been a huge asset. The level of freedom is what I like in VW. I installed a demo version of AC today and fiddled with it a bit. Seems that dormer windows have a generic wall structure there as well - only thickness. The roofs connect and trim, but not in a very smart way (not component aware). The Morph system seems a bit simplistic, however this might be due to my own lack of knowledge.

Back in 2009 we were working on a complex building in AC. The walls were slanted (not vertical) and on 90 degrees in plan either. We had pretty massive difficulties with doors etc...however, a long time has passed since, I'm not fully aware of the current situation.

I guess stepped walls would need to be done in separate segments. Currently the only way to control this is through wall styles, if I'm correct.

Something like the "planar buildup" you mentioned could be a good solution. Different priorities for "buildup" layers: similar components join automatically etc. One thing I've wondered is that why it is not possible to stretch wall components (or any components) in live section - creating details from the BIM model would be a breeze, were that possible. Currently one has to go through complicated settings to achieve this.

...to elaborate on this, the ability to draw walls at an angle? Do away with roofs and replace them with wall functionality? Just operating at an angle not vertical.

We've been struggling with a similar roof recently. Dead ends everywhere except for 2d-drafting. One of the issues was dormer window "walls" - in real life they have a wall not roof structure. Being able to give components to extrudes would be great. Not sure if it is possible to program though. Any deviation from simple geometry results in a swamp of bim/3D/2D with no clear solution. This is not to say VW is alone in this - all major software packages struggle with this. Some programming and mathemathical breakthrouh is clearly required.

My ten cents: A wall tag aware of the wall data. A dropdown menu configuration: You could choose which data to show eg. Wall ID, fire rating, acoustic rating. These selections could be saved as styles.

Thanks for the update, Our NAS systems are (and were) as follows (exact same issues on both systems) Old: 100Gbit Ethernet / Lacie Network Space Max 2.0 running RAID 1 configuration, 2 disks New: 1000Gbit Ethernet/ Synology DS1517+ running RAID 6 configarion, 5 disks Please note that we have not encountered any performance issues when it comes to speed, only reliability issues (please see above thread). File I/O is very fast as such.

I did the signature just yesterday - you can't have seen it before :-) As to the PS issues, I'm hugely sceptical about them occurring due to faulty Network setup at the users' end...

We run Windows machines on a Gigabit ethernet with PERFECT read/write functionality. If doing something else than VW project sharing, that is...

Indeed! Will have to try again.

Just to confirm: Custom leaves can scale with the door size? I did a custom leaf some time ago but it wouldn't scale at all.

Maybe also a key-activated floating bar showing the options/mode row next to the mouse cursor?

Time to service pack project sharing, NNA? It's beta as it is, there is no denying it. I'm getting false alarms about the project file containing information missing from the working file. Again. The working file is just fine.

Where are your files located? The recommendation here was that the working file should be stored locally, and the project file on the server. BTW if you (or anyone else) open the main project file, VW will always create a new working file for you from it. You should only open your working file when you work. Maybe there is some duplication happening that confuses the system? Accessing the project file under different credentials eg. on an office desktop computer or on a home laptop will create two working files, if the logins are different.

Don't know the reason for the error, but try saving the file as a regular .vwx file and then re-sharing it. That night solve the issue...temporarily at least.

The weirdest thing is that VW runs on Siemens Parasolid - proper windows and doors should be a technological non-issue, if someone would simply connect the dots, please! As an architect, I use walls, doors, windows, spaces. After these comes everything else. BTW we have that B-thing in the office for quick checking of engineers' dwg drawings, units and such. Not the BIM version though.

Exactly what I've been wishing for,too. Now there is very much unnecessary ocural and manual movement to the left corner.

For 2017, we noticed that using "close and release" instead of save and commit helped to remedy the situation with mysterious soft locks. Perhaps worth trying here as well? In other words, we started to use "close and release" in the middle of the working day, several times.

That's it! Thank you. I hadn't opened the "record" dropdown menu at all - therefore I didn't notice that another record was applied. How and why this "red" door record came to be, with the strange lower bound and upper bound criteria, is a complete mystery to me. Well, the important thing is that it now works as expected, thanks again.

Thank you, Attached is a sample. Stripped of everything non-relevant. File version is 2017, Architect. Data_visualization_test.vwx

Hi all, I encountered the following phenomenon: I've created a custom door record and I'm using viewport data visualization to check if I've remembered to put the right record info into the right doors. I've found that this is a practical way to check if the correct doors have been assigned, let's say, an electronic access control lock. However, using custom door geometry seems to break the visualization - please see the attached snip. The red doors should be blue. Doors that have custom geometry always show up red, independent of the data. There is no red assigned anywhere: in classes, objects, visualization, object attributes. In normal plan views and other views, these custom geometry doors look fine, no red. Has anyone else had this issue? Before someone asks, the reason for using custom door geometry is that one cannot make an unequal swing door so that the side leaf would have a glass pane just like the main leaf (VW please fix this, important and a very basic requirement !). Another thing I noticed is that the data visualization system doesn't allow umlauts (Ä's, Ö's etc.) in record names - it ignores them, in VW 2017. I haven't tried the 2018 yet. Removing the umlauts solves the issue (but then the worksheed data headers have to be corrected correspondingly). This was surprising since these records with umlauts work just fine with the worksheets.

Reset smart cursor settings? We've noticed that there is some accidentally pressed keyboard combination that messes with SC settings. Reset always heals the situation. For us at least.

@Tolu: I've been tracking the soft locking issues while we work. Here's what I've found: The soft locks frequently happen, accidentally. The program doesn't warn about these soft locks occurring. There is no way to spot the soft locks, other than going through the project sharing window and check if the "release" button becomes highlighted. The program does not always indicate the soft locks through the "release" button becoming highlighted, even when there are some! Perhaps most importantly, selecting "release" for the particular layer in the project sharing window does not always release the soft locks.' The only way to release the soft locks reliably is to use the "Close and release" option in the file menu. As conclusion, it would seem the soft lock release mechanism isn't perfect. Additionally, there should be a clear indicator when a soft lock occurs, and the right-click "release" option should release these soft locks as well. Since starting to use the "close and release" option to handle the persistent soft locks, we've been able to work better. However, still too many crashes. Thanks