NPC Animation in VR: Why Characters Slide Across the Floor
In VR, the player is inside the scene and notices what no one would see on a flat screen. A character gliding across the floor as if on skates breaks the sense of presence faster than weak graphics or simple textures. The player forgives the conventions of the world, but not physics that contradicts their own body.
This is not a rare bug but a systemic problem. The character's legs do not match the step, the feet "float" above the surface, and when the body turns, it continues moving by inertia — this is character sliding, or foot sliding.
The closer the player gets to the interlocutor, the more noticeable the desynchronization, and in VR the communication distance is always short.
Players do not stay silent about this. In reviews and on forums they write "the hero rides across the floor," "it is impossible to believe he is standing on the ground," lower their scores, and tell friends to wait for a discount.
One detail of NPC animation in VR turns into a loss of trust in the entire project: the audience begins to doubt the story and the controls too.
It is especially frustrating that player complaints surface on stairs, uneven floors, and when walking pace changes — where the least testing was done.
There is no universal "tweak one animation" here: a systemic approach is needed to how the character places a foot and how their step relates to the surface. That is exactly what we do — we restore credibility to movement and strength to the player's immersion.
What the Client Gets: A Scene Players Believe In
Natural character movement
When a character "floats" above the floor, the scene falls apart: the player notices the error before understanding its cause.
We shape NPC behavior so that the step matches the surface and the body responds to leans and turns — at any point in the location, movement remains natural.
Player trust and retention
The player forgives stylization but does not forgive falseness. When characters move vividly, trust in the world grows: visitors stay in the scene longer, more often reach the finale, and return for another playthrough.
This is a direct link between animation quality and audience retention, not an abstract "beautiful picture."
Fewer revisions after launch
Movement refinements are the most costly part of support: each one requires rechecking in a virtual reality headset and rebuilding the scenario.
We remove the cause at the preparation stage, so after project delivery you do not have to revisit the same characters because of a single frame.
Stronger impression from the scene
Players discuss what they feel, not what they see in a description. A scene they believe in turns into screenshots, streams, and reviews on Steam — and that means project recognition and an influx of new audience without additional investment in promotion.
Work Formats: How to Choose the Right Option
Different teams come with different tasks: some already have characters in the game and they "float" across the floor with every step, while others are only preparing for launch and want to remove a weak spot in advance.
That is why we work in several formats — from a one-time animation rework to ongoing support for the entire life of the project.
How we get involved
| Work format | For whom | What it gives the client |
|---|---|---|
| One-time animation rework | A game where characters already exist but movement looks unnatural | An updated movement set that is immediately put into the build and goes to launch |
| Ongoing support | A project is evolving: updates are released, scenes and characters are added | Revisions and new movements as needed, without searching for and onboarding a new contractor |
| Dedicated engineer in your team | You have your own team but not enough hands for animation | Work within your processes: your lead assigns tasks directly |
| Urgent fix | Little time remains before a demo, test, or launch | We rearrange the queue and close the task within an agreed short timeframe |
| Current animation review | You need to understand the scope of work and the real cause of the problem | A conclusion on the state of movement and a clear plan for what to do next |
If you are unsure which format fits best, describe the task and show what already exists in the project. We will review the materials and propose an option that resolves the issue without unnecessary work. You can start with one stage and expand the collaboration later, once you see the result.
Work Process: From Task to Finished VR Scene
A transparent process is no less important than the result: at any moment you know what stage the task is at and when you will be able to see it in the headset. We work in short cycles and after each one show a working fragment of the scene, not a report on what was done.
- Brief. We discuss the task: how many characters are in the scene, how they move, what the player sees and does. We fix the expected result and acceptance criteria — so that "done" is understood the same way by everyone.
- Work plan. We break the task into stages, specify timelines, team composition, and the points where your participation is needed.
- Approval. We show the plan and references before the start. You confirm the scope and priorities — revisions at this stage take hours, not weeks.
- Implementation. We build character animation, remove foot "sliding" on the floor, and configure movement and NPC reactions to the player.
- Test build. You launch it yourself: view the scene in the headset, check how the characters behave, whether there are jerks or drop-throughs. We collect comments in a single list.
- Revisions and project launch. We refine based on your comments and prepare the scene for a demo to the client, investors, or for release.
- Support. After delivery, we stay in touch: new characters, scene expansion, refinements for changed requirements.
This order removes the main risk of VR projects — when a scene is "almost ready" for months. You see progress at every step and can change priorities without losing what has already been done.
What Will Be Included in Delivery Based on Project Results
The project result is not a set of files but a finished character animation system that your team can develop without us. We fix the delivery scope before the start, so at acceptance you check against a clear list, not feelings.
- Working animation in your VR scene: characters move without foot slipping at different speeds, slopes, and surfaces.
- Configured gait variants for character types: you add a new hero in a matter of minutes, without rebuilding movement logic.
- A document set: system description, parameter setup instructions, and an acceptance checklist — in language your team understands.
- Employee training: practical sessions where your specialists themselves edit gaits and character behavior.
- Transfer of source materials and usage rights — you are not tied to us and can work with other contractors.
- Quality assurance: testing on target VR devices according to an agreed test list — movement smoothness and correct foot placement.
- Post-launch support: we answer questions and make revisions when character behavior is visible with live users.
If, based on testing results, something diverges from the plan, we bring it to the required state within the warranty.
Case Study: How We Removed Character Sliding in a Project
A studio, Northlight VR, came to us with a project that had already passed internal testing. Players put on the headset, took a step — and the character next to them "floated" across the floor: the legs moved, but there was no support beneath them.
At a public demo, such small things cost trust: a person stops believing in the world and leaves before we manage to show the mechanic.
We rebuilt character movement: steps were tied to the actual surface, and foot adjustment to the terrain was configured through Foot IK — once and for all surface types in the scene. The studio's engineers then added new zones themselves, without our help.
Results were measured by clear metrics. Complaints about sliding in test sessions went from 4 out of 10 to zero by acceptance.
At a demo for more than two hundred guests, more than three hundred game sessions took place — not a single comment that "the character rides across the floor." Animation revisions that previously took days are now closed the same day, and the client returned with a repeat order — an expansion to a second level.
The entire cycle took six weeks from the first meeting to delivery, and we spent half of that time on approvals, not on rework.
For a department lead, this means something simple: fewer returns for revision, predictable revision timelines, and a confident presentation of the project to partners and players.
What If I Have Non-Standard Character Requirements?
Non-standard requirements are the norm, not the exception. Every game has its own set of characters: unusual proportions, wings and tails, quadruped creatures, heavy robots, or heroes on wheels.
We do not propose "taking a standard model and repainting it" — movements are configured for your world and your logic.
Special movements are the second part of the task. A character should not slide across the floor, fall through steps, or "hang" above a slope: we adapt foot placement to the surface and correct body movement. We configure this for your locations — sand, stairs, ship deck, uneven ground.
Integration into the project is also part of the work, not a separate surprise. New characters obey the rules already accepted in the game: controls, camera, combat mechanics, story scenes, co-op.
First we look at what you already have implemented and select solutions that do not break what is already done.
We start with an analysis of the task: how many characters, which movements are critical, on which surfaces and in which scenarios they must work. Then we show the result on one or two heroes — you evaluate the quality before we scale the approach to the entire set.
Next comes the plan, timelines, and a clear sequence: from configuring key movements to final verification in the assembled project. If requirements are clarified along the way, we make revisions calmly: we work in short stages and stay in touch after delivery.
Common Client Concerns Before Starting
Concerns before starting are normal: the client invests time and the project's reputation, and ultimately they are responsible for the result. That is why we answer uncomfortable questions before signing the contract, not after launch. Here are the ones that come up most often in meetings.
What if something breaks after delivery?
This is the main fear, and it is justified: character movement in virtual reality is sensitive to new scenes, device updates, and load. That is why we build in a margin of safety and test character behavior in the most inconvenient situations in advance, not in front of players.
We fix support terms in the contract before the start: you know in advance who to contact and how quickly you will receive an answer, and you do not find out at the moment of a problem.
Which revisions are included in the work, and what can be refined after delivery?
Comments on the agreed scope are included in the project: we show intermediate versions so you can see the result and speak about revisions while they are still easy to make. Refinements after delivery are normal practice: a new location, another character, a more natural gait.
In one project for Questline, the client returned with an expansion several months later — the team already knew the product and did not waste time onboarding.
How do I know everything is going according to plan?
Progress is visible not in reports but in working versions: characters move, scenes come together, you can put on the headset and go through the player's route from start to finish.
This way doubts are resolved during the work, not at final acceptance, when changing something is expensive and slow.
Who will stay in touch after launch?
The same specialist who led the project is assigned to it — you will not have to explain the task again to new people. If the client's team changes, we transfer context and instructions so that the product continues to evolve without us.
Let's Discuss the Task and Come Back with a Work Plan
When a character in the headset "floats" across the floor, the player feels it within seconds — and decides the game is raw. That is how reviews, recommendations, and returns are lost, not a single small flaw in movement. We handle such tasks turnkey: from movement diagnostics to testing with live players.
After contacting us, you get a clear picture, not a stream of technical terms. What exactly is included:
- Analysis of the task in terms of results: where exactly the legs "float," in which scenes, and how the player feels it.
- Project estimate by timeline and scope — without hidden stages and surprises in the process.
- Step-by-step work plan: movement diagnostics, foot placement setup, coordination with the team, tests on real scenarios.
- A list of what will be included in the result: fixed characters, tested scenes, short recommendations for your team for the future.
- Points where you get involved: acceptance by clear criteria, not "by eye."
- Post-delivery support terms — so refinements do not turn into a new story from scratch.
The next step is simple: describe the task — how many characters, what game, what effect gets in the way. We will come back with a project estimate and work plan, and you can calmly decide whether it suits you. The request takes a few minutes, and after that the conversation is already down to business.