CC Different builds incompatible

Is there a way to open a .c2d file created on a computer running build 413 on another computer running build 312? I get a empty screen when opening the file? I create my files on one computer and run them on another computer with 2 different builds.

The file format changed — you can export your files as SVGs and then remake the toolpaths, but it’s best to use the same version everywhere.

2 Likes

While you could get away working in 312 file and opening up in 413, you could not open a 413 file in 312.

All my old files open up fine in latest version I first did using 316

Like say you can watch a dvd in a bluray player but not a bluray in a dvd player.

Like Will mentioned being on same build on all pc’s is the way to go.

2 Likes

Alternately you could export an SVG from 413, and import that into 312.

1 Like

I’m surprised that the ability to save in the old format was not built in CC4XX, understanding that the newer functionality would be lost. Most software (Word Processors, Spreadsheets, etc.) will do this.

From memory of asking about the file format a while back, it’s pretty much the in-memory representation of data serialised to disk.

So when the libraries used by the program change (eg major update, or different libraries used) the serialisation changes.

One day it might be done differently (eg XML, JSON, whatever) for greater compatibility. :smile:

2 Likes

The c2d file is in a json type format. If you do a convertfrom-json you can read the file. The version 4 c2d added some hex data at the end of the file. But the rest of the file is still the same as version 3.

It is my understanding that the file format has changed, esp. for curves.

Old format:

"RECT_OBJECTS":[
{"height":40,"id":"00000000-0000-4000-a000-000000000100",
"position":[63,24],
"rotation":0,
"width":70},

New format:
“height”: 40,
“id”: “{00000000-0000-4000-a000-000000000100}”,
“num_sides”: 6,
“point_type”: [
0,
1,
1,
1,
1,
4
],
“points”: [
[
35,
20
],
[
35,
-20
],
[
-35,
-20
],
[
-35,
20
],
[
35,
20
],
[
35,
20
]
],
“position”: [
63,
24
],
“radius”: 0,
“rotation”: 0,
“smooth”: [
0,
0,
0,
0,
0,
0
],
“width”: 70
},
{
“behavior”: 1,
“corner_type”: 0,
“cp1”: [
[
35,
20
],
[
35,
20
],
[
35,
-20
],
[
-35,
-20
],
[
-35,
20
],
[
35,
20
]
],
“cp2”: [
[
35,
20
],
[
35,
-20
],
[
-35,
-20
],
[
-35,
20
],
[
35,
20
],
[
35,
20
]
],
“group_id”: [
],

Yes that is different. But it still is in a json type of format. I was mostly looking at things like paths, tools, text, start stop depths etc.

Yeah, that sounds like serialisation format changes. :slight_smile:

1 Like