Jump to content

Mik

Member
  • Posts

    86
  • Joined

  • Last visited

Everything posted by Mik

  1. Please forgive if this is already part of VW or has been hashed out in the forums (I did not see anything in quick search) but.... Wouldn't it be great if we could tell VW to just snap our dimensions to the rough wall framing vs. finish materials? 1. Place all the dimensions to one or the other. 2. Then duplicate the sheet and flip a switch that says to snap the dimensions the other way. Dimensions that land on non-wall objects stay put. Done! Then we can have both vital and convenient dimensions for the different users. (Framers hate finish dimensions, inspectors/plan checkers get picky when actual dimensions that require code conformance are not clear, etc.) And we don't have to dimension the place twice manually - which inevitably leads to mistakes.
  2. Are you talking about the export window? There are no tabs for this window. I am on VW2021 - Windows.
  3. Attached is the screenshot. I always thought the engineers needed the design layers to get the 3d model and that sheets were represented enough in PDFs that I send. Because we have to get all the 2d sheets accurate for a legal description of the project for permits, I figure that's what they should always use to confirm what they are seeing. But they don't want to bother with that and just get right into designing in 3d. And they are so used to being able to do that w/Autocad.
  4. This is an old topic. I have read other threads and watched a few videos. The VW help that simply shows where to click for an export and "then choose the appropriate options" explains nothing about tailoring the export. My structural engineers don't want all the extra stuff from the VW 3d model (sheetrock, siding, etc.) - just framing. Is there a simple switch for that? That is only a partial solution as not everything is a wall but it might help. The other thing is that layers are all screwed up. My engineer was putting 2nd story things on 1st fl. etc. He asked for an IFC export but I don't think that helped. He did not think so either. We have slowly and manually through discussion worked out the differences but had not the time to figure out the export. And he's not too keen on another project with all the effort required to sort out the problems. There is plenty of work in the industry and structural engineers would rather work with someone who is already in Autocad and just sends them a good working file. The latest indication from them was that they would need to charge additional amounts to cover for the extra time involved with sorting out file discrepancies - if they took the job. This is a real problem if one wants to continue to use VW. Anyone with some short, succinct tips or is this really involved to get a more usable Autocad export? Success stories or whatever much appreciated.
  5. Look at the attached screen shot to find which "one of these things is not like the others ..." (Or at least the one in error.) Create a door with Gothic shape and add trim, any size. Look at how the trim does not follow the door frame/jamb at the top of the door. Trim on the other shaped doors appear to align properly. Gothic windows work fine too (seen at right.) Just Gothic doors seem to be the problem for me. Anyone else? These days with what I am calling "neo-English Tudor Revival" all the rage, it would seem like this should be high on the fix list. (Assuming this is not user-error to which I am no stranger.) VW2021 - SP4.
  6. I had this same problem with VW2019 in 2019. Vectorworks tech support had me download something that made it work. This was on an older PC. It happened again last year on my new computer and they just said I need to upgrade to 2020 to make it stop. So here I am with 2021 and it still happens. I have reboot, refreshed, tried starting the Updater directly after rebooting without running anything else, gave the Updater a hole in Windows firewall. Nothing works. It just says the Updater needs to be refreshed, progress bar, repeat. Anyone else having the problem in VW2021? (I am on WIndows 10 Pro)
  7. Anyone notice a mismatch between mapping a surface in OpenGL and hidden line renders? My case: horizontal siding. Use vertical offset to line up between floors for a seamless transition in OpenGL and it is in a completely different place when viewed in hidden line mode. And vice versa. These seems like a bug to me - and a very frustrating one at that. Everything must be realigned for output to building set or back again for client presentations. I have not compared to other renders but am suspicious the problem goes on.
  8. Just to follow up: I have started using the 3DConnexion space mouse and it is definitely helping. It takes a little practice but one big improvement is that you don't lose a bunch of time waiting for the mouse after each movement. When I use the mouse to move around a complex model, after each movement, VW takes a couple seconds to be available for the next move. With the space mouse, movement is immediately available at all times. Also, the origin does follow you with the space mouse. There may be settings to anchor the origin but I find it works very naturally as the space mouse origin stays with you wherever you move. This means that you can "walk" down a corridor, turn the corner, go up the stairs and turn another corner and then pan around the room without the origin stuck back downstairs somewhere creating havoc. Thanks again for the tip on this handy little device. Highly recommended for anyone doing complex 3d modelling.
  9. Aha! You found a bunch of them. I only saw width/height as those are the ones I will routinely just tab to and type. Thanks for checking further and submitting. Cheers!
  10. I would not know of a keyboard setting like that but to have it only occur on a couple particular fields only in Vectorworks would seem to rule that out. What are the particulars of the machine you used to test this? VW version/SP/build; is the Windows machine current with all Microsoft updates; I suppose we could look at graphics card details ... But honestly, a problem so isolated like this would tend to point to the application. I mean, there are several other fields in that window that do highlight but only one or two that don't. You have answered one question for me implicitly: it should not behave that way. Thank you for taking a look.
  11. Zoomer, many thanks. I should have thought of this before. I am going to order one today. Cheers!
  12. I have checked out the flyover tool options. The different modes behave as expected but the interactive origin mode (the one I need to use to choose my own origin) loses the specified origin if the origin is rotated or slid out of view. Then it begins in a new location not specified by the user. The way I see it, this is a bug as I cannot see any setting that keeps the origin at the last position set by the user as described in the interactive origin mode. The problem becomes acute when zoomed in close and trying to move into the ideal position for viewing a complex space. Practically speaking, I need to show the 3d modeled interior for a client who would like to see what things look like, for example: leaning over the railing of a 3-story staircase tower. To move into just the right spot they prefer, I could rotate and slide to get close to the edge of the floor opening and then need to rotate down or up like one would move one's head to look to the different floors. But once I have moved to the edge of the stairs, the origin is out of view and when I try to "move one's head" to look down, the flyover rotation origin is way off and makes it extremely difficult to get into proper position. What would be ideal is if they had a "human head" mode that let us drive the eyes of a virtual occupant through the model with joystick-like control. Short of that, I will settle for just having the flyover tool do what it claims to do in interactive origin mode.
  13. This is probably one of those "Duh" questions so please forgive: Basically, when rotating a model view using CTL + mouse scroller button one can set the rotation point where wanted. But move the view where that point is not within the display window and the next attempt to rotate finds the point relocated elsewhere. It will stay put when obscured by other objects in the model but moves when the view has moved it off the display window. Then it can go anywhere. Is there a setting that causes this rotation point to move only when moving it by using the CTL + mouse button or similar?
  14. Kevin, In that video, there was no file loaded other than the default "Untitled1" when you open VW. I did it that way to illustrate there is nothing in files that are introducing this. It comes purely from VW itself. I was running VW fresh - nothing else loaded. Its been happening for years and I just ignored it thinking it would be something obvious they would fix on a new update. Maybe the number of users of VW on Windows is really tiny so they don't care about us? Until someone says something? LOL I was hoping it was a small oversight that they could see and flip a field parameter to fix it. Maybe other Windows users could chime in.
  15. Kevin, I should have given my environment info: Windows 10, VW2021 SP 2 (current). I can restart the app, reboot the computer. It has always happened since a few versions back. Although sometimes it won't highlight both the width and height fields but always the height. Check out the screen capture and watch the fields highlight as I tab through them. V-VW2021-WindowTabFieldProblem.mp4
  16. Please forgive me if there is an obvious reason for this but in my small world, this is annoying. Click on Settings of a window in the OIP and change the dimensions. I start with the first field (width), then tab to the next (height) and the field will not highlight - the cursor just sits at the front of the field. This forces me to delete what is there and then type the new dimension. The elevation and all other fields properly highlight when you tab to them. Reverse tab to the width and it behaves like the height. Only width and height will not highlight when tabbing to them in the Settings of an existing window. I noticed this on VW2019 and still here on VW2021 (I skip updates). I don't think it was a problem in VW2017 but it showed up somewhere between VW2015 - VW2017 for me. I just upgraded to VW2021 and see it is still happening. Does not happen if you edit the dimension right in the OIP nor when first setting up window parameters before placement. If there is no special reason for this, it seems it would be a simple thing to remedy.
  17. Seems the default solid arrow on callouts does not appear when first placed. I have to go and change the leader attributes to another style and then back again to see the solid arrow. Bug?
  18. That only removes level types. VW propagates levels when you just want to edit one. For example, a default Ceiling level is set at 9'. I want it to be 10' so I edit it. Instead of changing the one in place, VW adds another one by the same name at 10'. Now I have an extraneous one at 9' I do not want. Trying a long way around: delete the level type altogether and then add it back in with the desired elevation. But that does not work logically either: the 9' level disappears from the story graphic but remains in the Edit Story dialog box as <None> in the Level Type column and in the list as 1-Ceiling at 9' just under 1-Ceiling at 10'. It's still there. I see no reference to removing these in the VW help. Is there a good reason why it adds levels rather than just edit them? As long as I have used VW, I still find some basics befuddling.
  19. Thanks michaelk. Has 2021 been stable or is it still a bit early? Anyone with a PC?
  20. I usually fly on last year's model to avoid bugs. In this post there was a lot of dissatisfaction with speed going to VW2020: In this older post, it indicated that graphics cards really only help OpenGL & wireframe modes: So what does everyone think? Is 2020 still slower than 2019? Did 2021 help? Is it stable yet? Still very dissatisfied with my Renderworks speeds. A single-family house with good detail but apparently a lot less than some things I have seen others post can take hours to process. I have given up on using Renderworks. My machine: NVIDIA® Quadro® P4000 (8 GB GDDR5, 4 x Displayport 1.4) Intel® Xeon® W-2133 Processor (3.6 GHz, up to 3.9 GHz w/Turbo Boost, 8.25 MB cache, 6 core) 32 GB (2x16 GB) DDR4-2666 ECC Memory
  21. I should have been more specific: OpenGL will render the curved joins more smoothly in higher resolution, yes, if you want to deal with the performance. But all the other fine rendering modes I have found to leave the jagged lines visible more or less.
  22. Lines in hidden line view and jagged mismatching them in rendering modes:
  23. The problem was with OpenGl on design layers for me. It doesn't matter what kind of texture it is and it is not selective about the nature of the texture content. I try clicking around on things, moving in/out, changing views, etc. These things sometimes get it to come back. Other times, delete and recreate, close and reopen, etc.
×
×
  • Create New...