Sell Async VTuber Rig Troubleshooting, No Live Call Needed

Riggers can sell paid async troubleshooting on an existing Live2D or VTuber rig — diagnosing a broken parameter, jittery physics, or a hinge that won't track — as a priced Creator Service where the VTuber uploads the.cmo3 project file and gets a written or recorded fix back, no live screen-share call required.

FanBell is free to start with no monthly fee and applies a 12% platform fee only when a fan pays (pricing).

Rig fixes are a recognized, separately-priced category of work, not a rare favour. Live2D rigger Lanora Nihil publishes a dedicated "Rig Fix Commission Form" — a separate intake channel from the new-rig commission form — for "rig adjustments and add-ons with work that is not my own" (Lanora Nihil commission page). A model that tracked fine yesterday can behave differently today after a settings or version change: Live2D's own manual warns that the physics Calculate FPS value alters results, and notes that the default was changed from 30 fps to 60 fps as of Cubism 5.0 beta1 (Live2D Cubism Editor Manual, "About Physics", updated 12/17/2024).

"Be sure to check the movement as changing the Calculate FPS setting will change the output result of the physics calculation." — Live2D Cubism Editor Manual, "About Physics", updated 12/17/2024

The audience creating those requests keeps growing: global VTuber livestream watch time hit a record 571.9 million hours in Q1 2026, up 4.7% quarter over quarter (Streams Charts, Q1 2026 VTuber report). Instead of absorbing the resulting "can you look at it real quick?" DMs as unpaid support, a rigger can point to a priced troubleshooting offer on their FanBell page — the same paid fan interaction model streamers and artists already use for other async requests (how it works).

What counts as rig troubleshooting versus a new commission?

Rig troubleshooting means diagnosing and repairing something in an existing Live2D file that used to work — a broken deform, a mistracked parameter, physics that overshoots. Building a new rig from an illustration is a full commission with its own scope and price (how much a VTuber model costs).

Published rate cards show how far apart the two jobs sit in price. Rigger Lanora Nihil lists a standard half-body rig at $200 and a full-body rig at $350, but prices small scoped edits separately at $15-$20 for an asset toggle and $25-$75 for a hair toggle. Rigger Jirai Ch lists half-body base rigging from $600 and full-body from $800, with single-parameter add-ons such as Mouth X and Cheek Puff at $40 each and part toggles at $10-$30 ("Prices adjusted as of 09/11/2023," Jirai Ch commission page). A troubleshooting fix belongs in the add-on price band, not the full-rig band.

If a fan sends a rig that needs a full re-rig rather than a repair, decline the troubleshooting-scoped order and redirect them to a commission listing instead of quietly doing the larger job at the smaller price.

Why offer this async instead of a live call?

Async troubleshooting works because the data a rigger needs to diagnose a bug lives inside the project file rather than in the live session. Live2D's manual states that ".cmo3" is the editable model data handled by the Model Workspace and that ".moc3" is the final export "used in the program," so the editable project file carries the parameters, deformers, and physics the rigger has to inspect (Live2D Cubism Editor Manual, "File Types and Extensions", updated 02/04/2025).

Treat the share of bugs that are file-diagnosable as practitioner guidance, not a measured statistic — Live2D publishes no dataset breaking VTuber rig faults down by type or by whether they need a live session. What is documented is that physics behaviour, parameter ranges, and deformer structure are all stored settings a rigger can open and read offline. A live call still earns its price for genuinely interactive debugging — watching the model move in real time while the VTuber tests tracking, or walking through the VTuber's own software setup together.

Should this be a Creator Service or a Paid Private Question?

Use a Creator Service, not a Paid Private Question, whenever the fan needs to send you the actual rig file or a video of the glitch. Paid Private Questions on FanBell are text-only in both directions, with no file or video upload supported in either direction; Creator Services support full media both ways.

A general question that needs no file — "does jaw-open usually cause double-chin clipping at high values?" — can stay a Paid Private Question. But "here's my file, the left arm jitters when I turn my head" needs the file attached, so it belongs in Creator Services.

What are the common Live2D rig issues worth pricing as a fix?

The recurring paid-fix requests riggers describe publicly are mistracked face parameters after a tracking-app or editor update, physics that overshoots or oscillates, ArtMesh deform errors after an art edit, and clipping at extreme parameter values. No public dataset ranks these by frequency, so treat the ordering as practitioner guidance rather than measured incidence.

One documented driver of demand is the free editor's hard ceilings. Live2D Cubism FREE caps a model at 100 ArtMesh, 30 motion parameters (including blend-shape parameters), 50 deformers, 30 parts, and 1 texture file up to 2048 px, and Live2D states plainly that "if you exceed the limit of the FREE version, you will not be able to save the file" (Live2D Cubism FREE vs PRO comparison). Hobbyist riggers working around those ceilings produce models that later need a professional fix, so a troubleshooting offer can explicitly welcome "I hit a limit in the free version and something broke" requests.

Physics faults have a documented cause too: Cubism's physics is a pendulum simulation whose Calculate FPS can be set to 15, 30, 60, or 120, with 60 fps recommended when the target application is unknown (Live2D Cubism Editor Manual). A mismatch between that value and the app the VTuber streams in is a real, checkable cause of "it swings wrong now."

Non-Live2D 3D VTuber rigs belong in a separate offer — see the 3D model rig troubleshooting questions worth pricing separately. VRChat's own documentation requires at least "New User" Trust Rank in its Trust and Safety system before an account can upload content at all — a gate specific to VRChat's 3D avatar pipeline that has no equivalent in a Live2D project file.

How should an async rig-fix offer be priced?

Price by diagnostic complexity and turnaround using a simple formula: an hourly floor multiplied by the hours you estimate the tier takes, then sanity-checked against published rig-edit rates. FanBell Creator Services let the creator set the price and a delivery deadline of at most 120 hours from authorization.

For the hourly floor, the U.S. Bureau of Labor Statistics reports a median annual wage of $102,030 for special effects artists and animators as of May 2025, with the lowest 10 percent under $58,600. Spread across a 2,080-hour year that median is roughly $49 an hour for a salaried animator; a freelancer covering their own tools, taxes, and unbilled admin time typically sets a higher floor. The examples below use a $50/hour floor.

The sanity check comes from riggers' own published prices for scoped edits: $10-$30 per part toggle and $40 per single added parameter (Jirai Ch, prices adjusted 09/11/2023), and $15-$20 per asset toggle up to $80 for a VBridger mouth (Lanora Nihil). Scoped Live2D edits sit in roughly the $10-$100 band on public rate cards, well below the $200-$1,200+ band those same riggers charge for a full rig.

Illustrative tiers, built as $50/hour × estimated hours and cross-checked against those rate cards — these are examples, not FanBell-set prices or guaranteed earnings:

Every figure in that table is an illustrative starting framework, not an earnings guarantee. Your actual rates depend on your audience, positioning, and the complexity of the files you take on.

What should a rig-troubleshooting listing say before a fan pays?

A troubleshooting listing should state the accepted file format, what a "fix" includes, what is excluded, and your turnaround, so the fan knows before paying whether their request fits. Ask for the.cmo3 project file specifically: the.moc3 export is runtime data, not editable source (Live2D Cubism Editor Manual), and working riggers state the same requirement in their own terms.

"I will need the original.cmo3 file to edit the rig." — Lanora Nihil, Live2D Rig Terms of Service

At minimum, define: the accepted file type; whether you need a screen recording of the bug; how many issues are covered per purchase; whether the deliverable is a fixed file, a written diagnosis, or both; and your turnaround, kept inside FanBell's 120-hour maximum. Add a permissions line if you fix other riggers' work — Lanora Nihil requires that a client requesting a rig fix "MUST have permission from the original Live2D rigger" before the edit begins.

What if the fix turns out bigger than the file suggested?

If opening the file reveals a bigger job than the listing covered — a "quick fix" symptom that actually needs a partial re-rig — decline and refund the order rather than eating the extra hours, then point the fan to a larger tier or a full commission listing. FanBell lets a creator decline and refund any request.

Setting the expectation in the listing itself ("if the issue needs more than two hours of work, I'll refund and quote a custom price") keeps the async format sustainable instead of turning every order into unpaid overflow work.

Frequently asked questions

Do I need to see the VTuber live to diagnose a rig bug?

Usually not. Parameters, deformer structure, and physics settings are all stored in the.cmo3 project file, so a rigger can open and inspect them offline (Live2D Cubism Editor Manual). Bugs that only appear while the VTuber is actively testing tracking are the exception, and are better sold as a separate interactive service.

What file format should I ask for?

Ask for the Cubism project file (.cmo3). Live2D's manual defines.cmo3 as the model data handled by the Model Workspace editor and.moc3 as the final export "used in the program," so an exported.moc3 alone does not give you editable parameters or physics.

Should this be a Paid Private Question or a Creator Service?

Use a Creator Service whenever the fan needs to send a file or video — Paid Private Questions on FanBell are text-only in both directions, with no attachments supported. A general text question with no file can stay a Paid Private Question.

What does FanBell charge for this?

FanBell is free to start with no monthly fee and takes a 12% platform fee only when a fan pays. There's no follower minimum, and Stripe handles payouts; Stripe's published pricing puts typical US domestic online-card processing at 2.9% + $0.30, which is separate from FanBell's fee and varies by card type and country (Stripe pricing).

How long can I set my turnaround?

Up to 120 hours. FanBell caps Creator Service delivery at a maximum of 120 hours from authorization, and you set any shorter turnaround you want inside that limit.

Can I set how many revision rounds are included?

Yes — Creator Services let you define price, turnaround, and scope (including how many follow-up passes are included) in the listing itself, so state your revision policy up front rather than leaving it open-ended.

Create your free FanBell page and turn the next "can you fix my rig real quick?" DM into a priced, scoped async offer.