- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I have dilemma . . . I was told that putting the.rcp file on your hard drive is the most efficient way of using a point cloud. So when user "A" links in a point cloud to a workshared Revit file, they link it in from their hard drive. Then user "A" synchronizes the Revit file to the Central file. Then user "B" needs to work in the same Revit file. They open a new local copy, but the point cloud is no where to be seen. So user "B" repaths the point cloud from their hard drive, synchronizes with the central. Then user "A" needs to do some work within the Revit model. They get into the Revit file & yep . . . . you guessed it, no point cloud. So they repath the point cloud location. Seems like a big circle here . . . . . Obvious solution is to let the point cloud reside on a server somewhere . . . right. But with the point cloud on the server you run into (2) issues. 1. The point cloud eats up lots of valuable server space. 2. The latency from running the point cloud from the server is significant & really slows down the users.
So do I deal with the latency or have the users repath every time they need to view the point cloud. What happens when user "A" & "B" are working simultaneously & are synchronizes their indiviual hard drive pathing back & forth with each other?
Looking for a better workflow. . . . any ideas?
Solved! Go to Solution.