Fixing VariCAD Crashes and File Encoding Issues

Nightmare #1: The "Save-Of-Death" Crash During Large Assembly Work

I've seen this a hundred times a machinist builds a nice fixture, then hits Ctrl+S, and everything locks up for thirty seconds, then greys out. The crash is almost always due to VariCAD's memory management hitting a wall during the recursive constraint solver when writing the native .FCStd file. The software tries to snapshot the entire constraint graph, and if there's a cyclic dependency or a missing reference, the XOR-based solve engine chokes.

What actually happens under the hood

VariCAD's parametric core uses a DAG (directed acyclic graph) for dependencies. When you have complex sketches referencing other sketches that reference back (even accidentally through derived planes), you create a cycle. The solver tries to linearize it, but during save it does a full dependency walk. If there's even one loose reference like a sketch that references a face that got eaten by a fillet operation the solver goes into an infinite loop until the OS kills it. In my 20 years, I've had more saves fail than actual geometry errors.

Field fix the "Constraint Audit" workflow

1. Enable the dependency graph viewer. Go to View → Panels → Constraints Graph. Look for any red lines that indicate cyclic references. If you see a loop, delete the offending constraint. In my experience, 90% of the time it's a coincident point that was accidentally snapped to a midpoint of an edge that was later trimmed.
2. Force a rebuild before saving. Hit the "Recompute" button (the blue arrows). Wait until it finishes don't touch anything. If it freezes there, you have a constraint that cannot be resolved. I've had luck with turning off auto-recompute under Edit → Preferences → General → Allow recomputation and manually recalculating after every three operations. Sounds tedious, but it prevents the big crash.
3. Save as .step for backup. Before any major save, hit File → Export → STEP. The STEP exporter doesn't touch the constraint solver it just dumps the B-rep. If VariCAD crashes on the native save, at least you have the geometry. Rebuild constraints later from the step. Yeah, it's a hack, but it works.

Nightmare #2: The "Unicode Bomb" Corrupted Filenames and Cross-Version Blowups

This is not a crash it's a silent data corruption. VariCAD stores metadata like feature names, part names, and sketch labels as UTF-8 in the XML inside the .FCStd zip. But the internal C++ string handling in older versions (pre-2024) used locale-dependent encoding. So if your Windows system locale is set to Japanese, French, or even English with special characters (like "Tête de piston"), the 2023 version will mangle the string on save. When the 2024 version tries to read it, it sees an invalid multibyte sequence and throws an exception that aborts the part load. You're left with an empty tree.

Step-by-step salvage procedure

• First, never rename files with special characters. Stick to ASCII: letters, numbers, underscore, and hyphen. I know it's 2025, but the bloody database backend wasn't designed by people who speak any language other than ASCII. I learned this when a German colleague used "Übergangsstück" the model opened with a blank tree and a "Document XML error" message.
• Recovery method: If you have a broken .FCStd, open it with 7-Zip (it's a zip file). Extract Document.xml. Open in Notepad++. Look for lines like Label="T\xE8te de piston" the \xE8 is a corrupted byte. Replace it with plain ASCII (e.g., "Tete de piston"). Save the xml, replace back into the zip, close, reopen in VariCAD. Works 80% of the time. If it still fails, delete all the Label attributes the tree will show default names, but all features load.
• For team environments: Agree on a strict ASCII-only naming convention for files and internal feature names. Write a python post-processing script that scans all .FCStd files in a folder, extracts Document.xml, strips non-ASCII characters via regex, and repackages. I've got one that runs as a cron job every night. Stops the problem before it reaches the next CAD user.

Nightmare #3: The "Constraint Hell" Sketches That Won't Solve or Are Over-Constrained

This is the #1 complaint on every VariCAD forum, and it stems from a core design decision: VariCAD uses a sequential constraint solver, not a simultaneous one like Dassault's CATIA. That means the order in which you add constraints matters. If you add a horizontal distance constraint before a vertical distance, and then later add an angle, the solver might find multiple valid solutions and pick one that causes an inversion or a zero-length edge. The error message is cryptic because the solver just gives up with "invalid".

Why it fails in the real world

When you drag a line segment near another, VariCAD's auto-constraint system adds coincident and parallel constraints automatically. If you then manually add an angle constraint that would force the lines to be not parallel, you get over-constrainment. The solver doesn't say "Dude, you can't have both parallel and 30°". It just says "invalid" and deletes the auto-constraint silently, which often leaves you with an under-constrained sketch that still won't solve because a dangling reference exists.

Field workflow the "Constraint Surgery"

1. Turn off auto-constraints. Under Edit → Preferences → Sketcher → Autoconstraints, uncheck everything except "Grid snap". Yes, it means more manual work, but it pays off. I've trained every new person in my shop to do this. The time lost in fixing auto-constraints is always more than the time saved by auto-constraints.
2. Use the "Constraint Selector" panel. Click on the sketch, then go to Sketch → Constraints → Show Constraints. A list appears. Sort by "Reference Geometry". Delete any constraint that refers to an edge that is not part of the sketch these are usually accidental external references that break when the part face changes. I've seen a sketch with 40 constraints, 12 of which were dangling references to a deleted face.
3. Force a sequential solve by splitting the sketch. Large sketches with >30 lines are a recipe for failure. Break the part into multiple sketches, each with its own base plane. Use external geometry references sparingly only for critical alignments. Then use additive/subtractive operations to combine. It's more work, but the solver handles 10-line sketches reliably.
4. When all else fails, use the "Export as .dxf reimport" trick. Delete all constraints, export the geometry as DXF, clean it up in a 2D editor (I use LibreCAD), reimport into new sketch, and add constraints fresh. You lose parametric history, but you get a clean solve. For complex sheet metal parts, I do this twice a week.

Bonus: The Purgatory of Feature Reorder

You know the one: you have a pocket operation that cuts a hole, then a fillet, then another pocket. You want to reorder the first pocket after the second to change the interferences. VariCAD's tree allows drag-and-drop, but if the second pocket references a face that was created by the first pocket, the reorder breaks. The tree turns red, and you have to manually map each feature's dependencies to the new geometry IDs. It's a nightmare that costs hours. My solution: never use face references for feature operations. Use datum planes and sketches that reference global origin. Yes, it takes longer to set up, but it makes reordering possible. I have a macro that replaces all face-based references with plane-based ones on any new part saves me twice a month.

One last thing the infamous "Rollback to feature" bug. If you use the slider to roll back the history, then add a new feature, VariCAD sometimes forgets the features after the slider position. They disappear from the tree entirely. The only recovery is to close without saving and reopen the file. Save a copy before using the rollback slider. I do it as muscle memory now.

That's the meat of what 20 years of VariCAD in a machine shop have taught me. No theory just blood, sweat, and a lot of manual .xml fixes.