JMR

It would be handy if there was a tick box for wall component "right pen" to follow the settings of the "left pen". Most of the time one uses same settings for both pens. At least I do.

Hi everyone. I wonder if the following is a bug. When working on a shared project, despite of diligent save and commit / close and release / refresh usage, we find the following: If someone duplicates a sheet layer, or changes the name of a sheet layer, the project management somehow cannot keep track of this - the sheet layer numbers and names don't match anymore. Please see the screenshot below. The highlighted area indicates where the numbers and names are wrong. It's not in English but one can see the difference. Trying to update, reopen etc. will not solve the issue. This particular project is not using automated title blocks/drawing coordination, but simple hand-written sheet numbers and names. The only thing that puts the project sharing sheet list back on track is temporarily saving the project as .vwx file and the re-sharing it.

Jim, Do you have any info about what is the status of this? We really need slab/component texture controls just like the walls have. Please... Please see this thread:

Thank you for the tip. I confirm that for us as well, the issue was solved by changing the display performance setting to the middle setting.

The fact that slab object doesn't accept editable texture mapping is quite surprising. Please see the attached image - this is perhaps a way to build jetties, not decks and terraces. Currently these vertical lines show up on elevations and must be hidden/covered by hand. We need control over slab texturing, please.

Hi, We have several projects in which DWG reference links seem to "break", even though nothing changes about the VW and DWG files, their names and locations, network setup etc. The navigator suddenly displays red "Broken link" text and the reference contents are not visible anymore. The situation can be fixed by manually locating the "broken" (not really broken) link and updating. We have a network drive for projects at \\192.168.1.199\, a setup that hasn't changed for years. We run Windows 7 and 10 64-bit PC's. Any ideas about a fix would be much appreciated.

In addition to the geometry issues, I would very much appreciate these: -a much more flexible door tag (custom tags are way too difficult) -tag showing door handedness automatically -tag displaying door size info, as is the default where I live. -tag displaying fire and acoustic rating, if desired. I know that in theory it is possible to achieve this via custom tag, but why not incorporate these into the standard tag(s)? The data is already there, the tag is already there, it's just a question of connecting these. An important option would be the ability to assing classes to different data fields in the tag. For instance, building permit documents require the display of fire and acoustic ratings, but not handedness and size info, with the exception of egress doors.

We have the exact same problem. Try turning off unified view, if you can work without it being turned on. This solved the problem for us.

I'm having the same problem. This has been asked before, but no answers. The override control simply doesn't work, it seems. Bug?

I'd like to underline one important aspect: If the software update is "continuous", there should be an option to postpone updates until they have been tested and tried for an extended period, and also skip an update or updates until later time. I know for a fact that many larger companies (10+ employees) using eg. Archicad often skip a version or two, since there is some known "dangerous" bug in the newer version, or simply because they know from experience that updating right away might be detrimental to their end product (=flawless building designs). Software reliability is of paramount importance in the architecture business. Even small two-person offices (like us) are responsible for buildings costing several million euros/dollars. It's a very different business from eg. graphic design if one thinks about the potential liabilities. A small error in a worksheet etc. can easily cost thousands for the architect. I'll give you an example: In one project, GetObjectSpaceNum for object returned space numbers of a different layer than that specified in the worksheet criteria. To this day I don't know why. In some other projects it seems to work fine, with the exact same setup. Of course we check manually but one doesn't always notice everything. Possible costs due to error like this could be huge. Now I don't dare to use that function at all. I personally love VW and it's versatility, however I'd like to suggest maybe a major version cycle of two years would also halve the number of initial bugs? Now it seems every year very fancy new features (I mean, which architect needs that recent 3D twisting tool...really) are added with the cost of simple quality control. Currently I'm waiting until summer 2017 to update to version 2017 even though I'm in VSS, to get all service packs that are coming before starting with the new version. Look at McNeel and their Rhinoceros: Versions can be several years apart, and the software is, as far as I can tell, extremely robust (however it's a different kind of software). Perhaps another thing particular to the architecture business is that projects are of very long duration. It's not at all unusual to start a project this year and still be working on it five years later. At the very least the projects must tranfer seamlessly to the new versions, or one has to run five generations of VW's in parallel (confusing). Still, I very much appreciate that Nemetschek takes user feedback into consideration so well. If you also up your quality control, you have a great product.

Any solution to this as yet? This is actually quite important, we need our own symbols to export text correctly. To elaborate further, I don't understand where this mirroring originates. In the original VW file, everything is at zero rotation, no mirroring. In the exported dwg, text in symbols flip seemingly by random.

I've been wondering this as well. Can't figure it out.

I'll rephrase my question: Am I really the only one having this problem? I still haven't figured it out. The product is VW Architect 2014 SP3. The section lines should export normally...or?

Hi all, I'm new to VW so this might be a dumb question, but for the life of me I can't figure this one out or find a solution online. I guess I must be overlooking something. The issue: When I export a (VW2014 SP3) file to a DWG, the section lines all vanish from the dwg. I do know about the "section line instances" thing and I've turned them on for the sheets, and they are fine. The layer the section lines are on is the same floor plan layer that exports just fine. This problem occurs when I export to dwg from the file menu. I've tried to turn all layers and classes on, to no effect. It's a Windows 7 64-bit machine with a Quadro FX2000 card. Thanks