STEP files for CAD about gasherbrum-k3

[whattheflukz]

Skill issue, Onshape can import X_T

[Trails5000]

flukz closed this but im going to expand on it, because you probably dont have a design background where your daily into and out of CAD.

STEP is considered to be a lossy format, it tends to randomly lose surfaces and require alot of repair upon import. This is something that fusion ignores. It also doesnt help that most of the CAD companies cant seem to agree on standards for step, what is exported out of solidworks is not the same as what is exported out of fusion. Ive wasted more hours of my personal time repairing steps than most of our dev team has spent working on printers. STEP files suck and are the bane of most engineers existences. IGES falls into the same standard, its just older and shittier in different ways.

Therefore, we share "native engine cad" only. Most of the dev team works in solidworks, which is powered by the parasolid engine. X_T files are basically native files with the file tree and all personally identifying data stripped out.

TLDR: step sucks, move onto a better format.

[johonan]

Hi. I understand and appreciate the concerns about the STEP format. But I'd still appreciate if a step was available, even despite the negatives. I don't mean that a step should be supported in any way, just available for convenience.

I've been building a k3 using cad as a reference, and I don't have any commercial cad programs installed, basically only freecad. I tried converting x_t to step using onshape, as flukz suggests, but I gave up after onshape has been "processing" the x_t file for a couple of days. I guess that maybe the k3 assembly is just too big..

Luckily, I found a friend who converted x_t to step for me, and it has been very very helpful