How can I make a zprj file that I created with Clo Version 6.0, compatible with an older version of Clo?
I am trying to open some zprj files in Clo Version 5.1.
I created these files in Clo Version 6.0. This problem only happens with some files.
How can I make a zprj, file compatible with an older version of Clo? I appreciate any help on this.
Thanks, Nati
-
I would think the need for this is maybe waning now that the upgrades are rolling with the software, however team users can get out of sync with their version for one reason or another, eg: independent users might be up-to-date whereas corporate and educational users may sit behind on software as deployment becomes a bigger issue to do with company policy, so inevitably groups whom may work across the cloud may simply get out of sync on what version they use. I expect in future this will become less of an issue as CLO3D have shifted to an easier technical update approach, however older v5 users might not yet have that rolling update benefit, so for the next 12-18 months I would expect some users across virtual teams may get caught in your similar predicament. In future I am sure that may simply disappear as the updates are rolling from an administrative level eg: outworkers in extended virtual teams and corporate users within integrated teams.
You might need to look at the features in CLO3D v6 and CLO3D v5 and only include details that are compatible between the two, for example shaders changed, so did edge pucker, so did UV maps now using UDIM, grading also changed subtley, etc. So it may stand to reason that if you use these more advanced details on your garment and trim project etc within a CLO3D v6 garment you might never get that flowing into an older format software, (logical) or that it simply rejects the file outright.
Might be an interesting project to see what works and what doesn't then list it so other also get that knowhow. I would imagine there would be many detail compatibility issues at the textural level, however the main garment and pattern might be okay - a matter of trying it out.
I can see where this may become a wider issue for some users whom cross over in this age of COVID-19 where adhoc teams form to work on projects across a number of users in the cloud, so maybe that is the area to look at > the CLO3D cloud based file and see if you load your project from CLO3D v6 will it download as a shared file for a CLO3D v5 user? If not then maybe there might be a compatibility spec produced by CLO3D as a simple A4 table of features users whom need this level of backward project compatibility to adhere too. eg: CLO3D might drive the potential problem by a simple specification based report table on what is compatible - backwards, so when users start out a v6 project they can be confident most of it can be passed back to a v5 user.
That is pretty common across the CAD industry - where many users cross over within a digital asset pipeline with various versions of software and the the integrity of the raw project asset needs to be maintained across a group of virtual users. Maybe time that was plonked on the technical teams desk as - urgent.
Give CLO3D support a tinkle and explain where and why this is crucial, who know how many users need backwards compatibility, 1 or 2 or most? Hard to gauge, I know it's been an issue for me many times, so I imagine many others also have come up against this. Time for CLO3D to nail this aspect down between major upgrades, perhaps? Yes.
0
Comments