I am trying to remake or persuade my company to abandon autodesk or bentley solutions due to their financially unsustainable licencing policy and opt for Rhinos (potentially some 100-200+ licences), which is far cheaper and gets the same job done.
For our specific or general workflow in civil engineering there are minor drawbacks when using Rhino but at the same time i find them really easy things to implement with huge benefits.
I am currently designing one object on a new railway line which is 30km long.
Surveying and other base stuff are separate models which are usually huge in file size or extent.
For the workflow purposes it is really important to be able to attach external files on the fly and clip their boundaries to managable extent so the model does not get too huge to work with.
Real life example:
I am attaching 60mb .dgn surveying file as underlayer for the design process.
Problem n.1: Importing takes lot of time in order of minutes - i dont know if it is matter of optimization or it can not be further improved due to some technical limits with dgn conversion
Problem n.2: There is no real way to clip attached file to some extent. Working on object which is within 500m but the attached file´s extent is 30km, its simply not possible (extreme lags and freezes).
There should be a way to efficiently clip the attached file:
We are on the cross road now. I would really love Rhino as the main instrument in our firm but these are limitations which would cause lot of trouble and headaches if not implemented or be a reason why not to go for Rhino all the way.
I am writing this post because i dont see it on WIP7 list. Would this be implementable even for R6 in some update?