I wish there would be. We have massive issues with VCL files and Earthworks. Since they keep all the dependencies the VCL files are much much bigger than exporting it the old way into the ProjectLibrary. You end up with lots of unnecessary data on the machine. If a surface was made from lots of triangles they will end up in the VCL. We have to manually break all dependencies by exporting/importing as TTM or using the offset macro (which has its drawbacks as well). Please consider a special VCL format for Worksmanager-Upload that is automatically breaking dependencies and is just sending the data to the machine that was selected on the design definition page. I just need the surface on the machine, I don't an additional 200000 line work triangles.
I've got i.e. a design that is 64 MB for Earthworks and 0.8 MB for GCS900.
Our Worksmanager folder for Earthworks machines is 470 MB, for GCS900 machines just 90 MB. The biggest EW designs are up to 64 MB. We'd have to do a lot of unnecessary manual data prep to keep the VCL overhead low. The new workflow should be easier than the old one, but right now it seems the opposite.
The latest EW 2.1.3 does not to seem to be able to cope with either the design size or the VCL format in general, I can't change to our project, EW is completely crashing. We've also got a CAT Next Gen with 2.1.0, its software doesn't crash but it takes 4 minutes to change the design.
Also, model Type "Road surface" won't show a cross section in Siteworks if using .VCL. The old way with a .pro file it does.
We have absolutely no issue with GCS900, the model size is normal and it usually looks as intended. Siteworks also shows a lot of unnecessary data but at least doesn’t crash or slow down.