I sent the same 300-frame character walk cycle to iRender, GarageFarm, RebusFarm, and Fox Renderfarm, once with a CAT rig and once with Biped. CAT: 100% success on all 4 farms.
Last Updated: May 2026
CAT rigs render perfectly on every cloud farm I’ve tested. Biped is a different story. I sent the same 300-frame character walk cycle to iRender, GarageFarm, RebusFarm, and Fox Renderfarm, once with a CAT rig and once with Biped. CAT: 100% success on all 4 farms. Biped on iRender: 100%. I verified the rig on the server myself. Biped on GarageFarm: 100%. Their pre-flight caught a footstep key issue. Biped on RebusFarm: 100%. Biped on Fox Renderfarm: 23 frames rendered in T-pose because the Biped motion file didn’t transfer correctly during their scene collection. If you use Biped for animation, test 10 frames on any SaaS farm before committing to the full sequence.
| Rig Type | iRender (IaaS) | GarageFarm | RebusFarm | Fox Renderfarm |
|---|---|---|---|---|
| CAT Rig | 100% | 100% | 100% | 100% |
| Biped (basic walk) | 100% | 100% | 100% | 92% (23 T-pose frames) |
| Biped + Layers | 100% | 100% | 98% (5 glitch frames) | 88% |
| Biped + Motion Flow | 100% | 95% | 93% | 78% (major failures) |
| Custom Bones + IK | 100% | 100% | 100% | 100% |
Why Do Biped Rigs Fail on Some Cloud Farms?
Biped stores animation data differently from CAT and custom bone rigs. Biped uses a proprietary motion system: footstep keys, motion flow graphs, and layer animations are stored as internal Biped data, not standard 3ds Max keyframes. When a SaaS farm’s scene collector packages your file, it grabs the .max file but sometimes misses the Biped motion (.bip) files that define the actual movement.
On frames where the motion data is missing, 3ds Max falls back to the Biped’s default pose – the T-pose. That’s exactly what happened on Fox Renderfarm: 23 frames between a motion clip transition came back with arms straight out. On iRender, this can’t happen because I open the scene on the server and verify the Biped moves correctly before rendering. That 2-minute viewport check has saved me from T-pose disasters at least four times.
Should I Convert Biped to CAT or Custom Bones Before Cloud Rendering?
If you’re sending to a SaaS farm, strongly consider it. Converting Biped animation to CAT or custom bones with standard keyframes eliminates the motion file dependency entirely. In 3ds Max, you can bake Biped animation to standard keys using the Motion Capture → Key Reduction workflow, then copy it to a CAT rig. It takes about 15-20 minutes per character but guarantees 100% compatibility on every farm.
If you’re using iRender, don’t bother converting, just verify the Biped plays correctly on the server before rendering. The 2 minutes you spend checking the viewport is way faster than the 15–20 minutes of rig conversion. GarageFarm also handles basic Biped well; their pre-flight checker flags missing .bip files before submission. The only scenario where conversion is essential: Biped + Motion Flow graphs on SaaS farms. My success rate dropped below 80% with that combination on Fox, and even GarageFarm hit 95%. Convert to standard keys or use IaaS.
This is how I render 3ds Max character animation without rig issues → Try iRender for 3ds Max rigs
FAQ
Do 3ds Max CAT rigs work on all cloud render farms?
Yes. In my testing, CAT rigs rendered with 100% success on all 4 farms: iRender, GarageFarm, RebusFarm, and Fox Renderfarm. CAT stores animation as standard keyframes, which transfers cleanly during scene packaging. No special preparation needed beyond the usual “Save Project with Assets” workflow. CAT is the safest built-in rig choice for cloud rendering, whether you’re using IaaS or SaaS farms.
Why did my 3ds Max Biped character render in T-pose on a cloud farm?
The farm’s scene collector likely missed your Biped motion files (.bip). Biped stores animation separately from standard 3ds Max keyframes, and some SaaS farm plugins don’t collect these proprietary files during packaging. The fix: either bake Biped animation to standard keys before submitting (15–20 min), use an IaaS farm like iRender where you verify the rig on the server, or test 10 frames on the SaaS farm before committing to the full sequence. GarageFarm’s pre-flight checker usually catches missing .bip files.
Is it better to use CAT or Biped for animation that will be cloud rendered?
For cloud rendering, CAT is significantly safer, 100% success rate on all farms I tested. Biped works on IaaS farms (100% with manual verification) and most SaaS submissions, but has failure risks with Motion Flow and complex layer setups (78-95% success on some SaaS farms). If you’re starting a new project that will be cloud rendered, choose CAT. If you have existing Biped animations, baking to standard keys before submission eliminates compatibility issues entirely.
You may want to read other articles of mine here.
Image source: bond1
COMMENTS