Jump to content

Kaare Baekgaard

Member
  • Content Count

    690
  • Joined

  • Last visited

Community Reputation

30 Great

1 Follower

About Kaare Baekgaard

  • Rank
    500 Club

Personal Information

  • Occupation
    Designer
  • Homepage
    www.idesign.li
  • Hobbies
    Product design
  • Location
    Aarhus, Denmark

Recent Profile Visitors

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

  1. I use the boomerang a lot, when I fillet corners. I select accessible corners then press spacebar, then pan or select the flyover tool to make new corners selectable etcetera. Now with VW21 I often have to start over, because the boomerang mode fails to remain active when selecting the flyover tool. It is not a consistent error, and I am not sure why it sometimes works and other times it does not. If anyone else gets this error, please say so, perhaps it is a bug.
  2. When I move a 3D object in the screen plane, I often find that it makes unwanted jumps in the plane perpendicular to the screen plane as it snaps on to some geometry. For example: I move an object in the front view and snap it onto the edge of some other object. When I inspect it in top view, it has moved to a different position in the Y-direction. I did not want this to happen. Can I activate some constraint to stop this from happening? Can I use a different procedure without too much extra effort? Please advise, if you have a solution.
  3. There are days, where e v e r y single interaction with the OIP in VW21 releases the frontmost tab and makes a mess out of my desktop. I hardly think anyone requested this pestilent feature. I for one hate it with every fibre in my body. Please provide me with a lockdown mechanism, so that the OIP and navigation tabs remain where they are supposed to remain - and please do so before VW22. And for future reference: Please provide users with a choice, whenever you make 'smart' improvements to something so fundamental as the OIP.
  4. The tabs of my Object Info and Navigation palettes are jumping out of their sockets every second time I try to move the palette. This is very frustrating. It must have seemed like a good idea at the time to be able to move the tabs freely, but in real life, it is not. So hopefully I can lock the tabs down for good, but I cannot locate this function. Can someone point me in the right direction?
  5. Hallo again to my oldest nemesis. For years I have tried wishing, suggesting, begging, pleading, sarcasm and ranting in order to get a fix on this most annoying feature, but there it is again in VW2021. Who do I need to bribe? Otherwise good job on the update.
  6. Today at this very minute of this hour of this day, I finally received the attached pop-up message for the ten millionth time! I am so happy and grateful for the advice. A huge congratulations is in order to the programmer who wrote it, and the team that allowed it to remain in VW for all these years. I especially appreciate the amazing feature, that the application automatically deselects the heretic object, that caused the message. It is only fair, that I should have to reselect the bugger before converting it into a proper layer plane object. Some may argue, that a different dialogue would allow me to do this in an easier way, but then it just wouldn't be VectorWorks 🙂 Feel free to share any similar favorites of yours!
  7. On one of my iMacs with VW2020, object history has stopped working on objects, that are slightly complex, and the highlight and modify buttons on the OIP are dimmed. Have I accidentally changed some setting to get this phenomenon?
  8. Kaare Baekgaard

    Blank

    Blank - issue resolved itself
  9. You can use duplicate along path to place copies of an object at equal distances along the ellipse. If the duplicated object is a short line segment, you can use the lines to trim the ellipse into equal sizes (lengths).
  10. Unless my setup is somehow flawed, anyone should be able to replicate the issue. But I attach an example: Go to the sheet layer and render the FQR viewport in the center. Go to the design layer and disable 'Use Textures' in OpenGL Options Return to the sheet layer and render again – if the textures are gone, you have replicated the issue. If you can do the same on a file of your own, the issue may be universal. I use an iMac. OpenGL test.vwx OpenGL test.pdf
  11. I quess this is a rare problem: Suddenly all my final quality renderworks viewports failed to render properly – transparencies were missing, etc. When I entered the design layer, everything looked looked right and rendered perfectly. I battled with the issue for several hours, then remembered, that I had disabled textures in the OpenGL option menu. I switched it back on and yes, that fixed the issue. So: OpenGL settings are somehow linked to Final Quality Renderworks in viewports.
  12. I get the same thing on a texture by texture basis. I change the settings of a texture and i a random sort of way, that texture will crash and render black. There is no other fix than to delete the crashed texture and replace it with another. Dave, is this a registered bug?

 

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