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
    • ConnectCAD
    • 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

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


About Me


Occupation


Homepage


Hobbies


Location


Skype

Found 38 results

  1. Hi folks, We're working on a file that's setup with Project Sharing and our Master File has corrupted a number of times and we're looking into it but in the mean time, I've been using our backups to create new Master Files and keep working. I've kind of cobbled together a workflow that I think works but I'm wondering what other folks do? There's probably a better way of getting everyone back up and running again with as little re-doing of work as possible. Here's what I do. 1 - Figure out which file is the most recent between the Master File backups and the local Working Files. I do this so that we have as little work to re-do as possible. 2 - Save a Copy of the most up-to date file, usually one of the working files as they'll always have the most recent work in them. 3 - Re-name the most recent file and append with todays date (ie Master-20-09-13_userid.vwx to Master-20-10-14.vwx) 4 - Move all existing Working Files to an "Archive" folder stored locally. Move the corrupted Master File to an "Corrupted" folder on our server (where the Master File is stored) 4 - Re-make a Master File from the new vwx file on the server. 5 - Have everyone create local Working Files from the new Master File. 6 - Re-do the work that was lost. It's not overly complicated but it could use some improvement. Ideally we could re-connect our local Working Files with the new Master without loosing the work we have done individually. Or if one user with a complete local Working file could Save and Commit to replace the information in the Master File with their copy and we could all keep working that would be grand. At one point I tried creating a new Master File as described above but I didn't re-name it with the current date. My hope was that just replacing the file with an uncorrupted version would allow everyone to continue to working without disruption. Well, that didn't work. Knowing that it might not work, everything was manually backed up and I followed the steps above and it worked. Any other recovery systems out there? Not just with Project Sharing either, vwx files corrupt as well. Is there a VW prescribed workflow that I haven't found in my searches? Cheers for the input and have a great day everyone. -Dylan
  2. Hello everyone, Our office just started using Project Sharing for one of our jobs and for the most part it works great. We have been running into some issues and I'm wondering if anyone is running into the same ones. Firstly, approximately every two weeks our Master file corrupts and we have to replace it from its backup file. While this isn't too much trouble, I get the feeling that it shouldn't be happening. Secondly, from time to time, walls/door/other symbols will delete. Its just two of us working on the file and we're not doing the deleting. Has anyone else had elements of their buildings disappear? The last issue might not be project sharing related (but maybe it is?). We've started using data tags for doors and windows. The door tags work fine but most of the window tags will empty (become blank) on plan and elevation views. The windows are there and haven't been modified at all. There's no rhyme or reason as to which window tags go blank or when it happens. Here's the info about our system We are all working on Mac computers but our server is communicating with SMB (I've reached out to our IT folks to ask why it doesn't run AFP). The master file is located on our office server. VW 2020 SO% (Build 562257) (64 Bit) Mac OS 10.14.6 2.6 GHz i7 16 GB memory Radeon Pro 460 4 GB It looks like we will be working with Project Sharing more often and it would be great to have these issues sorted out. Cheers, Dylan
  3. Is anyone using Sharepoint and Project Sharing successfully? We are experimenting with Project Sharing, which looks fantastic - but trying to do this remotely with master files saved on Sharepoint for multiple access. We seem to be having issues with syncing - and I'm not sure if this is due to Project Sharing, or Sharepoint, or a general incompatibility between the two. (Working on a master file, committing changes and releasing, but then the master on sharepoint not updating.) Any insight or experience would be much appreciated.
  4. When we save and commit on a project sharing file, many of us are experiencing a visual thing where multiple viewports ghost in. It seems to be a memory issue but it is strange that it seems to be tied to project sharing and saving and committing.
  5. We're running into a nasty problem with the callouts and keynotes in that the 'relative path' setting for the database doesn't seem to be working. Couple this with Dropbox and Project Sharing and you have a recipe for disaster. Every time somebody opens their working file or tries to manipulate the notes they all go haywire and the user needs redefine where the database is again for every single note. The problem appears to be that it's effectively looking for the database in Users/Dropbox/Database.xml Instead of: Users/[username]/Dropbox/Database.xml Anyone else experiencing this? Any thoughts on how to workaround? I wondered about moving the Dropbox folder to the Users folder but I'd have to mess around in the Terminal to change the permissions on the Users folder to achieve that.
  6. I'd like the option to have a window pop-up when a Refresh of the Project File is available, with choices to Cancel or Refresh.
  7. 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.
  8. 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
  9. 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?
  10. 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)
  11. 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.
  12. 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
  13. 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
  14. Despite the advent of Project Sharing we still find ourselves (reluctantly) splitting files up in order to minimise memory usage when working in the main model file (and, to a lesser extent, save and commit time). If we weren't slowed down by large numbers of Sheet Layers and Viewports we'd almost certainly keep everything in one file. So in order to split files up we have to use Workgroup Referencing. But Workgroup Referencing is cumbersome, because the process of editing the model file, then doing a save and commit, then waiting for Dropbox to sync, then updating the workgroup reference is a long one. But the main culprit is the last step, updating the workgroup reference. Because it fetches the entire file every time you do it. So until Vectorworks can handle a large number of Sheet Layers and Viewports without getting bogged down, it would be great if we had a new form of referencing that worked more like Project Sharing: It would support delta updates rather than having to fetch the entire file It would have a refresh button like Working Files do But it would behave differently to a Working File in the that you could create Sheet Layers that aren't pushed back to the Project File Any thoughts?
  15. 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
  16. In project sharing, you should have to check out entire symbols to reduce editing conflicts between users.
  17. 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?
  18. 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.
  19. 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
  20. 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.
  21. 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?
  22. 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?
  23. Can somebody clarify: are updated/re-rendered viewports meant to sync across Project Files/Working Files in all cases? Or are there exceptions?
  24. 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
  25. 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?

 

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