Jump to content

MHBrown

Member
  • Content Count

    193
  • Joined

  • Last visited

Community Reputation

8 Neutral

About MHBrown

  • Rank
    Journeyman

Personal Information

  • Location
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. MHBrown

    Publishing VW files broken

    Thanks. I'm mostly getting tired of having Vectorworks crash once or twice per day. I want to transfer to a new document, but VW has dropped the ball on that. There is no way to do this very fundamental action. Probably because it is "too hard" although "too hard" is not the same as "impossible." I want to do something analogous to an ID "package" where I could copy and paste an entire model and all the saved sheets, saved views, viewports, and elevation views would come with it. Alas, VW does not care about fundamentals, but would rather design little protractors for its rotate tool. At the height of its build, around VW12, I might go a year or more without a crash. Now it is at least once a day. I'd love to be able to downgrade back to that old version. I could not care less about the features added since then compared to the speed and reliability of the older version. VW has become as unstable as the old Strata3D of the mid 1990s--and that is saying a lot.
  2. MHBrown

    Viewports turn black in 2018

    No, I'm getting the problem in VW2018 with a file that was started in VW2017. I'm also getting what seem to be video card problems, which may be related to the OpenGL issues where the rendered image jumps around. Often, in wireframe, parts of the image will disappear to where a screen refresh does not bring it back. See attachment of system specs. Perhaps I don't have enough RAM or too small a video card? But my real question is this: is there a way to migrate an old file into a new document so that all the fixes work? This should be a major requirement that would have been discussed as part of the program of changing major updates from 18 months to 12. So, is there a way? I tried copy and paste but I could not use my elevations nor my viewports. Thanks, MHBrown
  3. MHBrown

    Viewports turn black in 2018

    The thread where I asked the original question was closed, but the problem has not been solved as far as I know. I'm sure that if one opens a pure VW2019 file that the black viewport rendering will not occur. But what about a file created in VW2018 or even VW2017? If VW insists on yearly major updates, the unintended consequence of letting the calendar (and not readiness) dictate major releases is the requirement that the update work with at least two older versions. This isn't because users are not updating---it's easy with a subscription--- but because sometimes projects will stretch across two years. There is no way that I know of to copy and paste the model, viewports, section views, elevation views, camera views, and more into a pristine file. Or is there? Thanks, MHBrown
  4. Good to hear. But does this also fix the problem with OpenGL renderings "jumping" out of view when trying to adjust texture maps or simply looking at a model? This makes it impossible to use texture maps. MHBrown
  5. 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.
  6. 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. MHBrown
  7. I'm still having this problem with 2018 SP4. Has it been fixed? I'm on a deadline and this is not funny. Don't tell me it's been fixed for 2019.
  8. MHBrown

    Interior Elevations do NOT work in VW2018

    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.
  9. That's a great tip! Thanks. That did the trick. Mike
  10. No, I have that unchecked so I can edit groups in isolation. I would not consider the plan view from which I am creating an interior elevation to fall into the category of "other." It is material to the process: namely placing an elevation line. Is this incorrect? thanks for the help! MHBrorwn
  11. 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.
  12. Does no one have an idea about this? How am I supposed to change where the section line goes for an interior elevation if I can't see the drawing??? 2018SP4 iMac
  13. MHBrown

    Resource Manager is blank

    No, I'm still on High Sierra. Thanks, I should have mentioned that.
  14. MHBrown

    Resource Manager is blank

    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 usual fixes. Thanks for any help. MHBrown
  15. 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?

 

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.

×