Jump to content

Search the Community

Showing results for tags 'sp2'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
  • Customization
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design
    • Terms of Service and Community Guidelines

Categories

  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs

Categories

  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes
  • Marionette - Menu Commands

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Occupation


Homepage


Hobbies


Location


Skype

Found 13 results

  1. Hi, I'm encountering the following issue: Drawing elements (lines, polylines, text etc) won't stay in front of walls and stairs. They always eventually go behind them "automatically". Sending them to front remedies the situation for some time. After a week of working or so the lines are again behind the walls. Everything is drawn on layer plane on the same design layer. This is a nuisance since eg. my fire compartment markings will become hidden. It's especially annoying if one doesn't notice this when issuing drawings. Is there a control somewhere I'm not aware of that would remedy the situation?
  2. Hi, There is maddening default setting in the title block editing window : When adding revisions to a sheet, the default setting is add to "All active sheets"! WHY not "this sheet only" by default? I've ended up adding wrong revisions to dozens of sheets and then having to pick them off one by one. And, for some reason, the title block doesn't update until one double clicks it - meaning the accidentally added revision is not visible, if you don't edit the title block.
  3. Hi all, I'm encountering the following: The options for textures intermittently disappear from walls. Sometimes they are there, sometimes not. There have been no changes made to the wall style. As I mentioned in a previous post, there is an issue with the world z not affecting the surface hatch, as well. Any ideas?
  4. Hi, I'm encountering zoom issues with a floating viewport. Previously this worked fine. Please see attached. I can't see my grade objects unless I zoom way back.
  5. Hi, I wonder what I'm doing wrong: I have two walls on different design layers with different elevations/heights. Previously, surface hatches have aligned nicely if "use world z for origin" has been checked. Now, it doesn't have any effect on the hatch. What might be overriding the setting?
  6. Hi all, We have encountered a pdf zoom issue suddenly. On a file that previously worked fine, zooming in on an underlying, imported pdf shifts the pdf sideways, significantly. The pdf doesn't actually move, but the display is incorrect. Zooming out remedies the situation. Previously the file worked fine. This occurs on at least two different pc setups. One user reported this after a windows update today. We've updated the graphics card drivers, restarted etc. but no help there. A sample file attached. PDF_Zoom_issue_sample.vwx
  7. Hi all, I'll post this as a separate thread since this has nothing to do with Mac-related graphics card issues discussed in another thread. We're encountering pretty maddening issues with screen updates in VW 2018. Please see the attached images. In a nutshell: 1) A door is moved to another location in a wall. 2) You can't see that the door has moved to the new location. It still appears in the original place. 3) If you do a mouseover on the new location, you can see the outline of the door. You can still see the door in the old location, as well. 4) When you zoom in/out a bit, the screen is updated properly and the old door disappears and the new one appears. We've encountered this problem with walls, too - sometimes when you draw a wall, it's not visible before you zoom in/out. I've tried every possible setting in the graphics options - no difference. Sometimes the issue goes away for a while and sometimes it appears again, which makes it even harder to track. We can replicate this on all different pc setups, so it's not likely to be a graphics card problem. We use cards from Quadros to GF 1050Ti's to laptop cards. No difference. We've tried to update all drivers on all machines. No help there either. From here on, we will adopt a policy of updating to a newer VW version only after the 5th service pack has been published. It's simply not possible to update before since the initial releases are, politely put, betas. For 2019, please fix doors, windows, stairs, overall quality and stability. I'll send you flowers and chocolate to HQ if you do that.
  8. Hi all, When selecting walls with the select similar tool and using "current selection mode", the tool ignores the current selection and selects objects not included as well. We are running 2018 Designer/SP2 in a pc environment. Oddly, the same problem persists even if we save the file to 2017. However, the file has been created with 2018. The issue occurs across different computers as well. It can be replicated almost always. Included is a screenshot and a sample file. I've selected the walls of the top plan, but the SS tool picks also walls from the lowermost plan, even though "current selection mode" is enabled. Anyone else come across this? Does this replicate on other peoples' installations as well? We have never encountered this before in VW. Happy holidays btw! current_selection_error_sample_file.vwx
  9. We are a UK based small sized office of 12 architects. Our computers are all Apple Macs, most of them are 2-year old with OSX Yosemite. I attach a screen grab of a system report which roughly covers our hardware background. Vast majority of our projects are run under Project Sharing. After a few service packs we found VW 2016 quite smooth and stable to use but since we have upgraded to VW 2017 with SP2 we have been experiencing many crashes and general instability. Just in January at least five of our projects suffered from numerous crashes. My colleagues have been constantly reporting problems ever since. Some of this projects had started in VW 2016 and were updated later to 2017, some of them were started from scratch in VW 2017. This does not seem to matter. We also have further projects to be upgraded to 2017 but at this stage we decided to pull up the handbrake instead. We also got in contact with the local Vectorworks Support Service as usually. They helped us out a lot in previous cases but currently it seems like they have become too busy and are not able to respond on time. I afraid we cannot afford a week - or even more - delay in response, if we get any at all… Our last two requests have not been answered by the time of this post, although they were issued on the 25th and 30th January. Having look at the request ID numbers, they must have received about 60 (!) requests from others within three working days. The increasing number of these requests also concerns us although I must admit that I do not know how many of these they receive usually on a daily basis. As things stand we are not sure whether we are having local issues with the software or there are general problems. Besides, any problem with project sharing seems utterly complex to identify. I do not think that we are able to send over our files to the Support Service every time and wait until they come up with any working solution. Sometimes they just send us back a fixed file by their engineers without any explanation what went wrong. I am not sure in that how we could prevent further issues then. I’d had 10 years of work with ArchiCad before I started using Vectorworks about three and a half year ago. The methodology of project sharing is almost identical which at least made it easy to understand how it works. However the stability of this function since it has been introduced in VW is rather divisive. Every time a new service pack is being introduced we are quite tentative whether we should upgrade or not. Sometimes previous issues simply re-incarnates and the software becomes unstable again. You never know. I thought I would share our experience which might draw the attention of other users who might have similar issues or alternatively it can be confirmed that this must be a separate and local problem only within our office if no one else finds VW 2017 unstable. All comments are appreciated. (Is there a new service pack in the pipeline maybe?)
  10. Asemblance

    2017 SP2 Crash When Print

    Hi, I feel I'm spending a lot of time on here reporting problems at the moment! Latest issue, after installing SP2 my file seems to be crashing whenever I send to print. Its a pretty instantaneous crash, as opposed to a lock-up or similar. At least one other person in my office has had this problem with a different file too. Anybody else suffering from this? Edit: Trial and error shows this only happening on certain sheets, but happens consistently on those sheets. Also turning off 'Reset all plugin objects which need resetting prior to printing...' option appears to stop the crashing, so looks related to plugins (of which I don't have any additional non-vanilla installed).
  11. Installed SP 2 and it looks like the outdated libraries update problem got fixed. At first it seemed still broken as it stalled writing the catalogue around 27% but if you wait a bit then it will complete the procedure. No more need to start up with admin right in Windows for this. The list of fixes and implemented wishes can be found at: http://www.vectorworks.net/downloads/notes/2017SP2_Notes
  12. McLovin88

    Hoist Tool 2017 Sp2

    I am having really odd issues with the Hoist tool in 2017 SP2. The object info palette shows correct distance from drawing origin but the Hoist data displayed on the plot itself is not even close. Is this a Known issue?
  13. Will the new symbols be updated to reflect whip orientation again in the future? Or am I missing something here. Its a pretty important part of correct previz workflow. Thanks!
×