Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by MHBrown

  1. Jim, asking us "did the frequency change..." leaves the impression that you have not isolated the problem and are sort of grabbing at straws.


    I do not understand why this cannot be tracked down and fixed. You need to STOP changing VW while you fix the horrible bugs that are rendering the application unusable. The digital world does not contain "frequencies." It will do the same thing every time when the same conditions are met. Outside of tunneling electron microscopes, quantum forces do not greatly affect us in the macro world where classical physics rules. Determine the exact conditions where this does not work first and go from there. Very frustrating...and time consuming...that this problem has existed since 2016 and it is almost 2019.

  2. When I render a camera viewport in "fast interior renderworks" style it renders solid black. The camera is not inside a wall because it renders fine in OpenGL. This was a problem over three years ago. Has it still not been fixed? I'm using VW2018, the latest SP whatever. I tried closing and re-opening VW. Nothing. A different file will render "fast interior" just fine. Any idea as to what I can do? I will not upgrade to 2019 until this works the way it is supposed to.

    Thanks for any help.


  3. I don't know what you mean by "add textures in viewport annotations." Textures are mapped in 3D views, but it is presently impossible to do this because OpenGL does not work in edit windows. If you go to Edit 3D for a symbol to put a texture on it, you can only view it in wireframe. If you go to Map Attribute tool, it only works about 20 percent of the time. When it does work, it can't be used because as soon as you render in OpenGL the model disappears. That's right. It disappears. It goes off to some other place. This is not only true with Interior Elevations, but with all views. OpenGL is unstable in any project that was NOT originally a VW2018 file. I am confident--especially with the purposeless yearly "upgrades"--that everyone has most of his files bridging across different year versions of VW. It is a stupefying miscalculation by VW to have a bug of this type. It greatly increases the time it takes to do color textures to the point where it is unusable. This must be fixed now.

  4. 2018SP4

    Interior Elevations evaluation:

    You cannot place the view plane

    You cannot adjust the view plane

    The elevation is not accurate to where you place the arrows in the floor plan...the only thing that resembles an adjustment tool for what will be seen in the elevation.


    It is unusable. I'm having to do section viewports or create symbols from all the materials that would have been in the interior elevation, put them on a separate design layer, and then fight with all the problems with texture maps, OpenGL not working, etc.

    This version of VW is, I'm sad to say, is completely useless for any color rendering uses. I'm going to have to recreate the entire model in Strata3D for rendering. Is this fixed for 2019? I've been asked if I want to upgrade, but not sure if I should.

  5. And I mean really blank (see attached screen shot.) It is usually chock full of stuff. What is up with this once stable program I used to brag about? This has happened twice this morning using VW2018SP4. I'm not building a skyscraper; it's a small museum exhibition. Why is this happening? I have to quit VW and then reopen, but I'm afraid that this will become more frequent as problems don't usually fix themselves (except for the "universal fix" of winning the lottery). Any ideas? As I said, only a quit and re-open works. Please don't ask me to close and reopen the RM or any other usual717414084_ScreenShot2018-10-24at2_52_14PM.thumb.png.69e43861656b0d3a86e4b65ce15696d3.png fixes. Thanks for any help.


  6. The problem seems to be with working in 2018 with files created in a previous version. This is an unforgivable oversight. I would wager that--especially with the accelerated, yearly upgrades--that nearly 100 percent of VectorWorks users start in one version and complete in another. My work around is to have an Untitled 2018 file open next to my real file. I copy and past anything I need to work on into that file and then copy and paste back. OpenGL works great in the Untitled file. This, however, is not an acceptable workflow step. Is this fixed in version 2019?

    • Like 1

  7. In VW2018 SP3, I create an interior elevation viewport. I want to edit the section line, so I click the "Edit Section Line" in the Object Info palette after high-lighting the elevation arrow symbol in the drawing. I get a window showing the section line, but the drawing is missing. What? I see a solid line, which is the section line, I assume, and a dotted line box, which I assume is the depth of view. But there is nothing else. How am I supposed to adjust the section line if I can't see the floor plan? Is this a joke? Really. What is going on here? I watched the YouTube video and it was not this way in THAT drawing.


  8. Mark, I'm glad it works for you in those windows, but it does not work for me. Regardless, OpenGL should work when editing from a sheet layer. It should always work everywhere. Anything less is unacceptable. Right not, some combination of VW, my video card, or something is causing OpenGL to fail. It is NOT my individual file. It happens everywhere. It may have to do with files created in VW2016 or VW2017, but it is very, very, very, very, very common to start a job in one version of VW and finish it in another. This minimal compatibility should be top of the list for future versions, but apparently it is not. I think that is the problem and it needs to be fixed if VW is going to continue its absurd release frequency of once a year---twice what it should be, in my opinion, to ensure a stable product.

  9. Why has this OpenGL problem not been solved? Because OpenGL does not work inside groups and other editing windows (like Symbols) you cannot do texture mapping in VW. The Attributes tool does not work because the OpenGL image disappears. You can work with Fast Renderworks, but that is, ironically, slow. I usually use Strata3D for my rendering and it used to be the buggy software. Now it's VW that is a problem. It is NOT a rendering program if you can't see what you are doing. Furthermore, you cannot select objects when they are rendered...assuming you get OpenGL to work in the handful of situations where it does work.

    This must be fixed before I continue the subscription. This has been happening for a couple of years now. When will it be fixed?


    • Like 1

  10. This may be one of those "bugs" that is presented as a feature, but it's a stretch to me. In previous versions of VW, if you realized you wanted to edit a symbol you would double-click on any instance and you'd get the question of 2D or 3D editing. After choosing, 3D you'd be inside the edit window. The symbol would be oriented in the way it was created--exactly what one would need for editing. At some point, VW stopped doing this and an extra step was added where you'd have to select Top/Plan and watch the symbol instance slowly rotate into its created position. OK, an added step, but no big deal except for one small problem: None of the other orthographic projections work. Go to Front view, for example, and you get the front view of the instance you selected at random. What? The same is true for the other views. Symbols can be placed everywhere and at all sorts of different angles. There is almost never a time where you would want to edit it at some skewed, random angle. More importantly, the fact that the orthographic projections do not "line up" flies in the face of drawing standards. This is really a problem. I don't want to have to hunt through the resource manager to find a symbol so I can edit it as it was created. I've already found it and double clicked on it. Anyway, if this is a "feature" that won't be fixed, please let me know. If it is a bug--which it is, in my opinion--I'll add it to the list. If I'm doing something wrong, that would be the best result. Something I can fix right away.



    VW2018 SP3

  11. I'm on an iMac. See the attached screen shot. The problems I am having are not related to the file with the exception of some of the speed issues. I usually create a symbol by taking the 3D object in Top view and doing a convert to polygons so it matches exactly in Top/Plan. VW apparently handles this in a very crude way. Rather than taking the original geometry from extrudes when available and creating circles from a series of concentric points or some other efficient interpretation of the plan curved geometry, it ham-handedly just converts everything to tiny or large polygons. I had over 200,000 polygons in one 2D symbol, so naturally it struggled to draw each instance. As I recall this is exactly what MiniCAD 5 did. I expected a bit more advancement in two decades of fine tuning. Perhaps instead of thinking up new protractor icons for the Rotate Tool, the programmers could investigate  more elegant ways to convert 3D orthographic views into 2D. Anyway, I redrew all the 2D symbols that had curves using arcs, circles, etc. and it has speeded up a lot.

    Anyway, there is no reason to post the file since I discovered this on my own and fixed it. The other problems rest with something else and are not file-specific. Thanks for your help!

    Screen Shot 2018-10-16 at 8.29.15 AM.png

  12. Not just lines, but almost everything in VW2018 latest SP, whatever that is. I'm working in Screen Plane Only (though VW stubbornly refuses to stay there). I go into a group/symbol to edit. I look at the object in front view. I draw a line, a circle, an anything. It looks like it works, but it instantly disappears.


    This. Is. Un. Acceptable.


    Along with the dead slow performance, the inscrutable texture mapping, and the infuriatingly unmodifiable bloatware called the Resource Manager, I vote VW2018 a bust. Really. I apologize for the rant, but why can I not draw a 2D line in front view of a 3D object? Why can't I use OpenGL in symbol edits? Why do I have to wait for 10 seconds for the screen to redraw? I cannot work in 3D because in VW it is way, way too imprecise, so please no suggestions along that line. I create 3D models, but prefer to do it two dimensions at a time. What in the world am I doing that is causing VW to hide my work? Any help is appreciated. Thanks.

  13. Thanks for the tips, but it does not matter under what conditions I am editing a symbol, it does not behave. When the object is rendered in OpenGL it "jumps" away and cannot be selected. This is because the computer "thinks" it is in the original position. See the attached screen shots with the wireframe and then the OpenGL render to see how far it "jumps." Sometimes it disappears completely.

    Screen Shot 2018-10-11 at 10.02.40 AM.png

    Screen Shot 2018-10-11 at 10.03.06 AM.png

  14. Here is a DropBox link (see below). OpenGL works for a while, but eventually when rendered it jumps to another part of the page. It cannot be selected at all while rendered because although the OpenGL image is visible, the computer "thinks" the model geometry is in the original location. If you lasso the ostensibly empty space or do a Select All, all the little blue squares light up in the original spot. If you go back to Wireframe, it is shown in the original position. Eventually nothing works, not attribute mapping, nothing at all if OpenGL is involved. I'd caution jumping to OpenGL as the problem, however. The new Attribute Mapping tool is nothing short of awful even when it works properly. VW should return to the 2015 or 2016 version...and STOP with the yearly "upgrades." Go back to 18 month or even two-year product cycles. You clearly do not have the staff resources to be in constant fast-track mode. Do it right, even if it takes longer or you will lose customers. Pay no attention to what other companies do. Here is the link:

    https://www.dropbox.com/s/o6mogph456niffp/ Sensing Nature Redesign E1.vwx?dl=0

    Thanks for any help!


  15. Upgraded to 10.13.6 and restarted. The condition is unchanged. I created another much more simple file, two extruded rectangles with different texture maps. I made it into a symbol and it worked fine, meaning OpenGL worked in the Edit Symbol window. This is something of a problem that I recall. The file I'm having problems with is fairly complicated (it's a museum with interactives, graphics, and a dozen or so design layers and saved sheets. There are around 50 texture maps, lights, nothing unusual. At some point, however, the files begin to degrade...almost always when doing texture mapping, lighting, etc. I was pretty sure the simple file would behave fine, but the file I need is now slowly becoming slow and buggy. It could be the MacOS, the video card, VW, Maxon CD4 legacy issues or a combination.


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...