I was worried they just hadn't replied or something, so that's sorted.
Don't just tell me that the origin is the problem, fix it. I reiterate my above concern about origins.if you're asking us to change the way we do things, then please offer a best practice that accounts for all of the intricacies of the coordination issues we face. I am glad to hear that bugs have been filed and that maybe, just maybe, someday VW2019 might be stable enough to give it another try. Additionally, the multiple files represent over 5 gb of data. The one I currently am running in VW2018 seems much more stable.still slow, but stable. I have several in VW2019, but re-patching together all of the references will likely take me a half a day. I can still send you all of the files, but now I have a conundrum.which version do I send. When I converted everything back to VW2018 yesterday, it purged in 2 minutes. I was never able to purge the file on my system in VW2019. I attempted to Purge this file, and was met with the monstrous delay that I believe I saw you describe elsewhere, has a successful purge ever been possible with this file to remove unused resources? Or has it not been purged because of this hang/slowness for some time? It's usually, "broken as designed" or "user error". It is heavily marketed as such, but in application, it poses problem after problem, and often no adequate solutions are provided.
#TIDYMYMUSIC SUPER SLOW TROUBLESHOOT SOFTWARE#
The software isn't developed to be compatible with real-world, large project workflows. This represents one of the largest frustrations I have with VW. I have been told repeatedly that working this far away from 0,0 is a problem in VW however, I have to date, never been offered a best practice or adequate workflow that accounts for the need to correctly georeference files, work with consultants using real world coordinates, At the time, our best practice was to forget about setting up an independent user origin and just always align it with the internal origin. In the past we have had problems with origins aligning in different files across the project, essentially moving the project to dramatically different locations.
#TIDYMYMUSIC SUPER SLOW TROUBLESHOOT HOW TO#
Our problem has been with user origin control and how to manage that across a multiple reference file workflow. Unfortunately we have relied on this methodology to correctly coordinate with consultants who are using the X, Y coordinates (minus the georeferencing) for awhile now. Is the 0,0 point just being assumed as the origin relative to a point in one of the referenced files? I have a few questions about this file however, it seems to be a bit far (not exceedingly though) 0,0,0, however none of the layers are georeferenced.
0 kommentar(er)
