compusam

I have been using VW 12.5 for about a month and this bug seems to have been fixed.

I started this thread and I am the 1st to complain about bugs, but this bug seems to have been fixed with version 12.5. In fact, I have been using version 12.5 for about a month and it seems to work very well.

Well, finally after 3 days, the 12.5 update performed and I now have a functioning VW 12.5 version installed. I do not know how anyone could do this with dial-up. The 300 mb updater alone took almost 2 hours to download with DSL (shorter time with cable-modem). I have not experienced anything longer than about 10 minutes download time with previous updates. I reiterate my request that VW 12.0.1 update be made available again for download in the event that the 12.5 update corrupts a functioning 12. 0.1 installation and/or if the VW 12.5 installation proves to be flawed for some unforeseen cdircumstances.

Katie, I stand by my comments. I have downloaded the VW 12.5 installer 5 times and attempted to upgrade 10 times on 2 different computers with DSL and cable modem broadband connections. The most recent attempt continued for 8 hours without results, one continued for 16 hours (overnight) without results. As I said, I have ordered the DVD, and I am optimistic, but concerned.

Here is the problem: Based on numerous posts, the internet updater for VW 12.5 does not work for A LOT OF PEOPLE (even with high speed internet), and it may destroy your 12.0.1 version on your hard drive (as it did mine) forcing you to reinstall VW 12.0.0 from your CD's, however, Nemetschek has pulled the 12.0.1 updater from their website so you are stuck with version 12.0.0. (The 12.0.1 installer is no longer available and the 12.0.1 installer which you may have saved when you downloaded it several months ago is no longer supported and will not function). In my case, I have work in progress with hidden line elevations which will not render correctly with VW 12.0 so I am stuck until my VW 12.5 DVD arrives, hopefully in a few days. So here is the bottom line: VW 12.5 update (internet installer) may ruin your fully functioning VW 12.0.1 installation and there is no way to get it back (this seems to be almost diabolical). The VW 12.5 DVD is not very expensive ($9.95 for VW 12 users), so order the DVD and be patient for a few more days. After all, we have been waiting for numerous bug fixes for many months, so what are a "few more days?" The scary thing is that a reasonably functioning version (12.0.1) can no longer be created on your computer and, what if version 12.5 is not a reasonably functioning version? Well, then we will have to go back to version 12.0 or 11.5! OK, I admit it, VW 12 is fantastic (buggy, but fantastic). I have created a work flow based on VW 12.0.1, but now, I have lost some of the capabilities of VW 12.0.1 which will cause loss of revenue, embarrassment, and missed schedules until VW 12.5 arrives (assuming it works at least as well). I think Nemetschek should put the 12.0.1 updater back on their website until users have had a chance to successfully upgrade to 12.5 and try it out.

I am also having the same install problem w/VW12.5. I get to the point where the installer says "finishing?" and the ball just spins away for hours. I have tried this on 2 different computers using DSL on one and cable modem on the other with the same results (or more correctly no results). PowerBook G4, OS 10.4.7 and G5 tower OS 10.4.7.

Thanks. That seems to work. Now, of course, I have to "re-set" all of the existing roof framing members to get them to display the proper nominal size? a minor inconvenience.

Why does the Roof Framer Tool create the wrong nominal lumber sizes. For example, a 1.5" x 9.25" rafter which should create a nominal 2x10 is shown as a nominal 4x10 in the info palette and in the Framing Member Report. I have checked the lumber size data file in the Plug-ins/VW_Arch folder which has the correct nominal sizes.

Regarding the discussions about the door PIO and issues with door swings on RCP's, you might consider the WinDoor plug-in from OzCad (http://www.ozcad.com.au). There are 14 classes available for doors and windows with this plug-in including a "ceiling" class which shows the ceiling view of a door opening location (no trim) plus a grey door swing. Considering the number of classes assigned to the PIO, it is likely that one can find a combination that works for plans and/or RCP's. This plug-in also renders correctly without the big border or the misaligned texture, and there are 4 panel sliding doors as well as corner windows. There is a free demo available for download so you can try before you buy. Considering one post regarding charging more for a fully tested VectorWorks, I agree, but in the meantime one option is to pay for work-arounds for the bugs and WinDoor seems to be one of those work-arounds. Until now, I have not been able to use VW12 because of the rendering bug, but now that I am using WinDoor, I am finding that VW12 is indeed incredible (bugs aside).

Ramon PG, I tried your suggestion regarding changing line weights for trim parts, however, this did not solve the texture rendering probelm. I have posted more detailed info in the RenderWorks forum, but essentially, this bug has been around since VW 11 and became worse in VW 12 due to more parts to control. In VW 11, extra lines and/or borders show up in all rendered modes when the window or door trim is wider on one side (interior/exterior) of the window/door from the other including Open GL, Final Shaded Polygons, Hidden Line, Final Quality RenderWorks, Artistic RenderWorks, etc. In RenderWorks, textures are rotated 90? from the rest of the wall in this same bordered area. In VW 12.0.1, there has been some improvement? the erroneous border does not occur in Hidden Line, but it still occurs in almost all other rendering modes.

After even more experimentation, I now realize (as others have found), that one cannot apply textures to the parts of "Simple" doors and windows in VW 11.5.1. One can apply a texture to the whole window (int jambs, ext jambs, sills, etc., but the individual parts cannot be controled with the "style?" textures. These are legacy PIO's and do not work properly with VW 11.5.1 and do not work at all with VW 12. So, window and door PIO's do not render properly with VW 11 or VW 12. The only option is to use the updated versions of these PIO's and keep the interior and exterior trims the same width, or to convert to symbols as some have suggested, although this has not worked for me, yet. This is very frustrating.

After further experimentation, I now find that the big border around rendered windows and doors occurs in VW 11.5.1 as well as VW 12.0.1 (2/21 update). I had not noticed this before because all of my interior and exterior window trims in earlier projects were the same width which disguises the problem. To work around this in VW 11.5, use the "Simple door 2" and "simple window 2" pio's in lieu of the updated version of these pio's which shipped with VW 11 (or possibly earlier). To see the problem very dramatically in VW 11.5, create a wall and insert a "Simple Window 2" in the wall and a newer type "Window" in the same wall. Give each window a 4" exterior trim and a 12" interior trim. Give the wall an exterior texture such as shingles or siding. Then render the exterior of the wall. The "simple window" will render correctly, however, the more up to date "window" will render with a 12" border (from the interior) or misaligned textures. Un fortunately, the "Simple" pio's do not work with VW 12 (the simple window works with error messages and the simple door crashes VectorWorks 12). This problem shows up in VW 11.5.1 in "Hidden Line," in "Final Quality RenderWorks," in "Artistic RenderWorks," in "Final Shaded Polygon," and "Open GL." This problem shows up in VW 12.0.1 in "Final Quality RenderWorks," in "Artistic RenderWorks," and in "Open GL," but not in "Hidden Line," or "Final Shaded Polygon," I am surprised not to have seen this in VW 11.5 or read about it previously.

I have already submitted a file to "bug submit" and it is an acknowledged "bug."

The windows PIO in VW 12.0.1 is flawed (and possibly the door PIO as well). I do not think that it is productive for VW users to suck on eggs apologizing for their complaints. I bought VW 12 which is TOTALLY USELESS because of this bug. I am continuing to "work" with VW 11.5, but my confidence in upgrading in the future has been unalterably flawed.

The windows PIO in VW 12.0.1 is flawed (and possibly the door PIO as well). I do not think that it is productive for VW users to suck on eggs apologizing for their complaints. I bought VW 12 which is TOTALLY USELESS because of this bug. I am continuing to "work" with VW 11.5, but my confidence in upgrading in the future has been unalterably flawed.

The windows PIO in VW 12.0.1 is flawed (and possibly the door PIO as well). I do not think that it is productive for VW users to suck on eggs apologizing for their complaints. I bought VW 12 which is TOTALLY USELESS because of this bug. I am continuing to "work" with VW 11.5, but my confidence in upgrading in the future has been unalterably flawed.

The windows PIO in VW 12.0.1 is flawed (and possibly the door PIO as well). I do not think that it is productive for VW users to suck on eggs apologizing for their complaints. I bought VW 12 which is TOTALLY USELESS because of this bug. I am continuing to "work" with VW 11.5, but my confidence in upgrading in the future has been unalterably flawed.

VW 12.0.1 update has not fixed the problem and Nemetschek is stonewalling. This is a serious issue regarding rendereing high quality images with "windows" or "doors." Maybe we should eliminate "doors" and "windows" in architecture. In any event, VW 12 is worthless for my purposes and I am "working" in VW 11.5 which is not flawed in this respect.

It does not matter when the wall is textured? and should not matter. THIS IS A BUG. The Window PIO is flawed (in RenderWorks) and possibly the door PIO as well. I am not investing any more of my time in trying to diagnose an acknowleged bug. The bug is there. I cannot solve the problem. That is YOUR problem, not mine (I have posted about 30 messages to this forum as well as BugSubmit). Fix it.

The trim does not have a texture so it appears as a wide white border the same width as the trim on the opposite side of the wall. If I give the trim a texture, the wide white border disappears, but misaligned texture appears on the wall the same width as the trim on the opposite side of the wall. The texture below the sill is totated 90?.

To test your theory that there is "something questionable" about my installation, I have loaded VectorWorks 12 on my laptop (Mac G4 800 Mhz) and updated to VectorWorks 12.0.1. The same problem appears, although the build number has changed to (53931). My laptop is running OS 10.3.9. So, with 2 different computers running different operating systems, I get the border around windows with RenderWorks. I do not think my installation is the problem.

My computer profile is: G5 dual processor 2Ghz, 2 gig ram Mac OS 10.4.4 (recently updated to 10.4.5) VW Application version 12.0.1(53930)

I have submitted a file to "bugSubmit" along with a description which you can review in the General Discussions forum. The test file I created is a new VW 12.0.1 file with a single wall with a single window. I made the window trim 4" wide on one side and 12" wide on the other side (to make the problem more obvious) with no sill trim. The big border renders on all 4 sides including the sill in Final Quality RenderWorks, but appears to render correctly in Hidden Line.

I have submitted a file to bugSubmit which illustrates the problem (Window Bug.mcd) which is a single wall with a single window rendered in Final Quality RenderWorks. As far as I can tell so far, the problem does not show up in Hidden Line, but I will keep you posted on this if I see it somewhere else. The text of the description which acompanies the file is as follows: "On my computer, this image is viewed in Final Quality RenderWorks mode and the width of trim on the opposite side of the wall is rendered as a border on all 4 sides of the window. I have exagerated the trim width on one side of the window to make this more obvious. When viewed in Hidden Line mode, you will notice that there is no sill trim (which is correct), but FinalQuality RenderWorks has the border at the sill. If you select the window and "flip" it in the info pallette, you will notice that the window will lose the big border on the wrong side of the wall, but the texture renders in the wrong orientation in some instances or it is shifted noticeably so that the coursing of the shingles around the window do not line up with the rest of the wall. You might have to zoom in around the window to see the texture shift."

VW 12.0.1 update is out, but this bug has not been fixed. I am still getting artifacts around windows when rendered, exterior trim textures appearing around interior views, texture shifts around windows, etc., etc., etc.