I am running into a rather odd issue with Carbide Create 756 on MAC OSX 13.3
I create a file and all of its toolpaths and save the file. It shows saved and shows a file size in file explorer but when I go to open the file back up it opens and is blank. No toolpaths and no designs at all. If I go to close the file or open a new one it says something has changed with the file and do I want to save it. I click no and try to re-open it same results file is blank. If I try to open this same file in Windows it is also blank there. If I create the file on Windows I can re-open on Windows or a MAC no problems. I do not recall running into this issue before on my MAC this seems to be a new thing and I am not sure if its a carbide create upgrade or an OSX upgrade that has caused the issue.
Any ideas or any other information I can provide to help troubleshoot. Its driving me a little nuts because I tend to do my designs inside and then head to the shop to cut them.
I’ve been running create 756 on my m2 mac for awhile with no issues.
So I’m pretty confident it’s not a carbide issue. Still, I’ll update my OS tonight and report back if any issues crop up.
So problem solved. The new MAC OSX update enabled IPv6 on my ethernet adapter. While doing a network packet capture I could see the file trying to be saved to my NAS across an IPv6 address. After disabling IPv6 in OSX I can save and open files to the NAS again.
Interesting that I only seemed to have this issue in CC as I save and open files to that NAS almost all day long in other programs.
Some interesting notes:
1.) I could save the file locally and copy it across to the NAS (w/IPv6 enabled) and re-open it from the NAS successfully.
2.) I could save smaller files (i.e a square with a pocket which ended up being a 45kb file) directly to the NAS and re-open them without issue. (again with IPv6 enabled)
None the less I don’t need/rely on IPv6 internally so turning it off is no big deal for me.
Well, if we gave out a “Nerd of the Month” prize, that line would win it for sure.
CC uses a Sqlite database as the root file format, rather than a binary blob. It could be that the file is not being written linearly because there are a number of threads that generate all of the data that goes into the file.
I have no idea what that would matter to a NAS that’s working properly, but it would be different than a program like Word saving the data.