![]() The model would crash everytime we tried to open it. However in our case, there was some corruption in the model yesterday morning. Technically, none of this should really matter, you usually don't change the model much once it is georefferenced. On my end, I am left to suffer the consequence of the technical limitation, which has deep and severe implication for a collaborative model.įor a technical perspective, is it not possible to go back to the less efficient non-cached version of the model for the rare times that the model needs to be coordinated? Like switch back temporarily during the operation? The data cache is a bit complicated and not relevant to my user experience. Hi you for your pretty complete and timely response. Keep it up, even if you're not happy about it. I appreciate you taking the time to let us know how you feel about this topic. Ultimately the investment to process down path #2 above is what our development team sizes as a "Large" T Shirt size, and does battle with many other very valuable backlog items pertaining to service resiliency, scalability, performance, and workflow. I can tell you for certain, as part of the product leadership, that the IdeaStation is not where things go to die, nor is the sentiment on this topic disregarded. So the question here is whether we 1) continue to use the Acquire Coordinates workflow, accepting the performance benefits that cause the limitation or 2) evolve the local data architecture and/or enhance Revit to carry out the equivalent of a SWC to a Linked model, which would enable the Shared Coordinates workflows that need to push information to the Links. It's been documented since we released C4R (now BIM 360 Design). We knew full well the implications of the tradeoff, and deemed that ~20% improvement in the high frequency Model Open command, for all team members, was worth the lower efficiency of a the Acquire Coordinates workflow, which is much less frequent than Model Open. ![]() The converse of those workflows, Acquire Coordinates, does work as expected.
0 Comments
Leave a Reply. |