Blender 5.0 and newer, in both Eevee and Cycles, on Windows, macOS, and Linux. Earlier versions are not supported.

Yes. Gear links, the Motor, nuts, the piston and the hydraulic run on Blender's own drivers and constraints, not scripts, so they work with auto-run switched off. Simulated cables and springs should be baked first: press Bake in the panel, and the bake is saved in the .blend file

Simulate parts one step at a time while the timeline plays. A render that jumps straight to a frame, or renders frames out of order needs a bake: press Bake in the part's settings before rendering. With Simulate off, a cable hangs as a still curve and needs no bake.

Yes. Select the gears, make the driving one active and press Link Gears. MechFlow reads each mesh for its axis, tooth count and centre, finds which gears mesh or share a shaft, and drives them. Spur, ring, bevel, worm, rack and planetary sets are recognised. If a tooth count is read wrong, correct mech_teeth in the gear's Custom Properties and link again.

Not by keyframing the rpm. For a speed that changes, set Motor to 0 and keyframe the part's rotation instead. Everything linked to it follows.

No. A cable drapes over any closed mesh you choose as its Collision Object, still or moving, but two cables, or two loops of the same cable, can pass through each other.

Yes. Every part renders the material in its object's own material slot. The Piston and Hydraulic rigs rebuild their own parts when you change a setting, but a mesh you swapped in yourself is never overwritten.

Yes. Each add-on uses its own names throughout, so they run in the same scene without clashes.

Yes. Anything you make with MechFlow (renders, animations, models) is yours to use commercially.

Yes. Updates are free for everyone who bought MechFlow. For help, bug reports or feature requests, message me on Superhive or through amirsharoleslam.com.