> This is obviously a lie without even testing it. STEP files do not have any sort of support for parametric features.

Yes, this is also confusing me to no end. How can they make such a claim? They even explicitly state that they generate a B-rep (boundary representation) output only, then in their roller example they say "as the output is parametric, dimensions can easily be adjusted." Erm, no? I'd rather model it again with the proper feature history tree and constraints instead of fiddling with a step file.

I think the point they are making us that the intermediate representation the model works with is parametric and then converted to step for use with other tooling, I could be wrong, but I understand the argument both ways of their solution enables editing of that parametric version before conversion out.