Jump to content

Search the Community

Showing results for tags 'project sharing'.



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 / Issues Resolved
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • 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

Calendars

  • Community Calendar

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 31 results

  1. Got to work this morning and we're finding we can't do anything with any of our Project Sharing files. If we try to edit a Working File we're getting the attached message. Same message in v2019 or v2020, macOS 10.14 or 10.15, which makes me think it's a Dropbox issue. Is anybody else experiencing this? We've had to convert them to standard vwx files to continue working on them for now.
  2. We are a Mac based office using vectorworks woth project sharing across the majority of our architectural projects as we have multiple users on each, and it’s been working fine. we are now looking at setting up some teams with pc’s instead (so they can also run revit), and we were wondering how the project sharing works across pc and Mac, and if anyone have had any problems with this? in effect some teams might have to do crossover work between Mac saved and pc saved vectorworks files via project sharing. any thoughts and suggestions would be helpful. many thanks kind regards anton
  3. Hi all, Does anyone have an idea why referenced DWG viewport classes turn off after updating the file link? The classes in the linked file have not changed, only the contents have been revised. This happens with project sharing, at least. After updating the link the DWG disappears, there is only a small red rectangle at the insertion point (usually origin) representing the viewport. Selecting this reveals in the OIP that all classes have turned off by themselves. If I turn the classes on and update the project file, the classes will still be off for other users (of course, since class visibility is a user setting). However, this affects sheet layer viewports as well since the referenced dwg viewport class control occurs at the DL viewport, not on a sheet layer. Therefore, updating a DWG link will cause any dwg information to disappear in all related sheet layer viewports as well.
  4. Christiaan

    Project Sharing and Dropbox

    We're considering a move from our local Mac server to Dropbox but I want to test a project first. Is there anything I should know? Is it as simply as moving the Project File to Dropbox and off we go or is there some process I need to follow? One other thing I'm curious of, because I seem to remember somebody telling me it works this way: Does Save & Commit and Refresh data get transmitted over the LAN if the Project File and Working Files are on the same LAN? Or does it need to upload to Dropbox first and then download again? Can we expect any kind of delay if we're all on a LAN?
  5. I'm working on a project with somebody and we're letting VW dynamically check stuff out rather than checking out whole design layers (because we need to work on the same layers), but we keep having to save, commit and release because various things are connected in some way or another to the parts that the other user is trying to edit. And when your Working File is nearing 1GB in size and you also need to wait for changes to upload to Dropbox this can course long delays in productivity. Sometimes it will be a wall that the other user doesn't need but it's connected in some way via windows or slabs or something. Sometimes, infuriatingly, it's the Sheet Borders. But lately we've been seeing "Record" coming up in the message that tells you which resources are already checked out by someone else. Either it's new or I just haven't come across it yet. What could this be and how do we avoid it? There are some Record Formats in the file but they're not associated with any objects in the model we're working on. There are a few special Formats, such as Sheet Border etc. Perhaps it's these? Either way, how do we avoid this or minimise the number of things in a Project Sharing file that could be checked out, restricting other users ability to work in the file? @Jim Wilson could we have a list of such objects and/or perhaps some guidance on how to reduce them and avoid this kind of thing?
  6. Is anybody else having a problem with Keynote Legends disappearing when using Project Sharing? Have you been able to isolate when it happens?
  7. Can somebody clarify: are updated/re-rendered viewports meant to sync across Project Files/Working Files in all cases? Or are there exceptions?
  8. Documenting in 3D with VW will get you pages and pages of Sections/Elevations (good!). However, if the viewport caches are not properly saved, then you end up with pages upon pages of blank pages with empty red rectangle frames (no good!). The problem here is not that we do not render our viewports often enough, it is that updated viewports are not synced properly across the various machines in Project Sharing. The end result after a few rounds of 'save and comment' is that we end up with blank viewports again across all the terminals. So, if a staff was expecting to 'fix up' something in an elevation we printed out, he would finds himself having to re-render that section/elevation in his machine, because there is no viewport cache. Unfortunately rendering a hidden-line viewport is not a quick process (will post a separate feature request for fixing this). VW has to better log which VP is the most recently rendered, regardless of when a particular terminal performs the 'save and commit' function. As an office that needs to produce drawings for issuance. This fix can't come soon enough. This fix really needs to happen NOW. (and if you were going to ask whether 'save viewport cache' is checked across all terminals. Well, obviously, yes)
  9. Jim S.

    Disappearing Sheet Layers

    A project sharing file had all of the sheet layers disappear, yet in two existing working files the sheet layers were still there. When the project sharing file was opened by a different user to create a working file the sheet layers were missing. Has anyone come across this issue before? We were able to catch the issue early enough to create a new project file from one of the working files with minimal work needing to be redrawn.
  10. Hi, We have upgraded to Mojave and started to have big issues with project sharing, VW 2018 SP6 The workaround is to work with regular VW files instead of project sharing. This is time consuming and really annoying when you are on deadlines. Ida
  11. Project sharing walls randomly disappear, or shows up in one users Working file, and yet not in another users Working file (although both are refreshed and up-to-date). We have had a number of incidents where walls simply gone missing, randomly on different floors in our 10 stories bldg (currently being shared via project sharing and 4-5 users using it). For example it could show up in one users file, but not another, even though all refreshed and saved-committed etc. Other incidents have been where some symbols have updated fine to the latest updates someone made, but not other, i.e. some not being 'pushed through' to the project file even though saved and committed. Our workaround has been to save a new project sharing file from one of the users working files, but this delays/slow down the working process, and means spending a lot of time trying to find what / what hasn't updated / been pushed through. We are currently using VW 2017, is this something that has been corrected within the VW2018 sp3 ? kind regards anton
  12. Hi folks, is anyone working with referenced project files? We have the following setup: A normal .vwx-file for our drawings and a referenced .vwxp file for our project library. It has to be a project file, because multiple people are creating and updating resources there. The refrence type is viewports and not sheet layers. We have the checkmark set at save copy of resources and updating when opening the file. Our problem ist that Vectorworks seems not to update the referenced .vwxp on opening the .vwx file, and is not giving any indication of being out of date(shown red). Symbols are shown with a black fill and wrong rotation(see Screenshot). After manually updating the refrence, the problem is solved. But this problem now raised doubt amongst my colleagues about the trustworthiness of the file. We can never be sure if what we see is the accurat. Any help appreciated. elepp
  13. In project sharing, you should have to check out entire symbols to reduce editing conflicts between users.
  14. We are having issues with disappearing windows in a project sharing file. It is the same windows repeatedly disappearing. We have gone in and replaced the windows in question several times, and they continue to disappear. Most recently, we saved the project file as a regular .VWX file, replaced the windows outside of project sharing mode, and then entered project sharing mode again, hoping this would solve the issue. This morning some of the windows have disappeared again. The window type is used repeatedly throughout the project, and is only disappearing from a few select locations. Any tips on the cause of/resolving this issue? Occasionally the disappearing windows will appear on *some* users files and not others. Kindly, Mark Zupan iMac 3.4GHz Intel Core i5 8 GB 2400 MHz DDR4 | Radeon Pro 570 4096 MB macOS high Sierra v10.13.6 VW 2016 Architect
  15. Since the introduction of Project Sharing in VW2016 and many other features in VW, it seems like the company has made a decision of steering users to single file workflows. With that said, we haven't found a way yet to consolidate our complex and memory intensive referenced file workflow into a single file system...at least not practically. I'm curious to what credit VW gives to differing workflows when developing tools or looking at the big picture. While I love the idea of doing everything in one file, we face two large hurdles to practically implement this practice on some of our larger sites. These roadblocks are: File Size - Our work is often broken out into 3 different segments (layout/grading, planting, and irrigation); thus, we have created a separate file for each. We have created a referenced file workflow that combines each of the various files together to generate our documents (schematic, design development, construction document). On large projects it is not uncommon for any one file to top out at 1+ GB, and individually, this already puts a strain on our machines. I cannot imagine combining our files together will result in smaller or more manageable file sizes, so we really haven't even considered it. Layer Management - With our multiple files, each with their respective design and sheet layers, it is also equally hard to imagine combining all of this organization into one file without a better way to organize it. Take our irrigation files alone. Our practice is to put each individual irrigation design zone/station into its own respective design layer. We do this for a myriad of reasons, but mainly, it is just easier to track and document complex systems. That said, it isn't unheard of that some of our irrigation files will contain almost 100 design layers! Similarly, we have worked on projects that have 20 irrigation sheets, 20 hardscape/grading sheets, 20 detail sheets, and 20 planting sheets. If I put all of that information together in one file, there is no way to organize it. I imagine a simple hierarchical or folder system similar to how classes currently sort would help this exponentially. The main reason I bring this topic up is that I have noticed that many of the new features VW has pushed in the past few years are solely intended to function in a single file workflow, but immediately run into difficulties when using a referenced file approach that we currently employ. Take the new Titleblocks for example, or even the old Sheet Borders...how do I use the same titleblock in 3-4 different files while keeping the Project specific data constant and maintaining individual control of the Sheet specific data? Referenced symbol? Referenced Titleblock Style? This works great in theory, but you quickly realize that the Project based data, when changed in one referenced file, does not transfer to other referenced files. I would love to hear more about peoples experiences/struggles with their single file or referenced file workflows. How is it working for you? Cumbersome? Have it all worked out? What else needs to be done to make this practical?
  16. Hi all, While this is not a completely new issue, it seems that (using project sharing/2018 designer SP4) DWG file import is extremely slow. Importing a simple 200k DWG might take several minutes. The procedurally following project file update from the working file will extremely slow, as well. The DWG files really are small and simple, HVAC line drawings etc. Is there any setting that might cause this?
  17. We have been experimenting with Project Sharing and are having some difficulties. On this particular project, a team member with Admin access to the file made changes to the Plant Definition and 2D symbol for a few of the plant resources in the file. He also moved them around and and added a few here and there...save and commit... When I open the file and refresh (I'm also an Admin), I can see that the Plants have been added and moved around, but the Definition does not change...the plants still appear at the same size, spacing, etc. as I had them prior to his changes, and the 2D symbol changes don't appear either? This is odd and only one of several abnormalities experienced with Project Sharing. We are in some desperate need of education regarding Best Practices for Project Sharing and would welcome any input. Thanks.
  18. Jeremiah Russell

    VW Crashes

    VW2018, latest SP I am trying to open a shared project file and VW crashes every time. It will not create a working file. It simply crashes. Anyone else run into this issue? Any thoughts?
  19. We are having difficulties Referencing Symbols from Project Sharing file to Elevations / Sections sheet files, mainly the Level symbols, and grid lines symbol. Things that we use in both Elevations, plans and sections at all scales. We have a project sharing file, with multiple users for one bldg only (10 stories, 256 apartments), which is working fine. we than have separate vectorworks sheet files for plans / elevations / sections, which generate all the sheets as above. Referencing in the main Working file. but we can't get in the grid line symbols nor the level symbols, as we get an error message saying that the Working file cannot be referenced in (only the Project file), which we know... but the symbol is inside the project file, and not reachable from within the resource browser. is there a way around this somehow? kind regards anton
  20. peterlukejenkins

    Project Sharing

    Hi all, our architects practice currently has up to 8 users working on projects, all running VW 2017 Architect (Fundamentals, Architect, Renderworks licensed) on Macs with a Mac pro server, using SMB. Recently we've landed some larger projects requiring multiple users working on the same scheme, which to date we have managed using split files and laborious processes of recombining information every day or so. So, surely Vectorworks has a better way of handling this... of course it does, Project Sharing. So I've started reading the various tutorials to get us up and running, but have tripped at the very first hurdle; creating a Project Sharing file. All the guides say to say the file on a shared drive; OK, all our files are on a shared drive already. Then they say to choose File: Project Sharing to begin setting up shared access permissions etc. Problem - I go to File:... and there is no "Project Sharing" option in the menu. It's not greyed out, it's just simply not there. Am I missing something simple here?
  21. James Scope

    Disabling Project Sharing

    In curiosity I enabled project sharing on a site map I am generating. Its not necessary for me to be using this feature with this document and its changing the way my classes and layers show up, along with me also now having two files (master and working). Id like to "Un Share" this document if thats possible. Any tips?
  22. Quick request related to Administrator 'powers' in project sharing files. Quite often we are suffering issues where a user may have a tiny bit of geometry checked out on a layer, stopping one of us from working effectively on the file. Of course as an admin, I could go in and force 'release' that entire layer, and sometimes this is a useful tool. It would be extremely useful though, if I could also select a single 'user' and release all information associated to that particular user. There are many situations this would have come in handy in. For instance, assume someone is out of the office but for whatever reason have accidentally got some small pieces of geometry checked out, all over the place. I want to release everything that that particular user has - but I may not want to release an entire layer, which other people are currently working on! (Please somebody do correct me if this is already possible and I have just not found the appropriate command :S)
  23. Hi Everyone, We are having difficulties with sometimes work is not being saved even after saving and committing in a project sharing file since we updated to 2018. We tried making a new project file after making previous project file into normal Vectorworks file. I am wondering if someone is having the same issue or know anything about it. Thank you!
  24. I am having trouble with a project sharing file. It automatically checkout layers and more importantly it shows me as person who checkout the layer. I can not release or checkout again. Please see an image showing the message I get, in this case I am the owner (hassan Raza) it won't let me do anything. Thanks
  25. Hi, We are constantly getting the following error message when working on a shared project. This appears when updating or committing the file. Accepting or discarding the "Format named "Space"" doesn't seem to have any effect on anything. Does anyone have an idea where this could originate? What does the "Formad named "Space"" refer to? We also quite often get the warning "The project file contains information not included in the working file....all modifications may be lost" etc., even though working file is up to date and seems to work fine. Thanks

 

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.

×