Jump to content

Mik

Member
  • Content Count

    78
  • Joined

  • Last visited

Community Reputation

12 Good

About Mik

  • Rank
    Apprentice

Personal Information

  • Location
    United States

Recent Profile Visitors

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

  1. 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.
  2. 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!
  3. 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.
  4. Zoomer, many thanks. I should have thought of this before. I am going to order one today. Cheers!
  5. 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.
  6. 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?
  7. 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.
  8. 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
  9. 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.
  10. 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?
  11. 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.
  12. Thanks michaelk. Has 2021 been stable or is it still a bit early? Anyone with a PC?
  13. 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

 

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...