Mesh Retopology for Mobile Games: Meeting Polygon Limits

Mesh retopology for mobile games is essential to meet polygon limits. When we receive a sculpt from ZBrush or Nomad, it has 2–5 million polygons. A mobile game needs 3–8 thousand. Simply decimating via Decimate Modifier in Blender or ZRemesher is not an option: automatic tools don't think about animation, UV unwrapping, or how the mesh will deform under skinning. Manual retopology with proper edge loops for animation is superior to low-poly modeling tools. We provide game-ready assets including normal map baking for character retopology using advanced retopology tools. In one mobile RPG project on Unity (Android build), we received a character sculpt with 3.2 million polygons. After manual retopology, it weighed 7,800 triangles, and all 32 blend shapes worked without artifacts. Animation iterations were reduced by 40%, and rework costs during the rig stage decreased by 30% of the project budget. Character retopology is a key 3D model optimization step for mobile games, meeting the polygon limit mobile games require, making assets game-ready and saving team resources. With over 5 years of experience, we have completed 200+ retopology projects for major studios, delivering cost savings of $1,500–$5,000 per project on rigging. Typical pricing: $200 for a head, $800 for a full character, saving teams $1,500–$5,000 on rigging.

Shortcomings of Automatic Retopology for Animation

ZRemesher and Instant Meshes produce a quad mesh but do not create proper edge loops. On a character, loops must wrap around the mouth, eye sockets, joints—following anatomy, not a uniform grid. If an edge loop intersects the corner of the mouth incorrectly, animation causes creases or tearing.

For mobile VR on Quest, joints are especially critical: shoulder, elbow, knee, wrist. Loops must be parallel to the bone's rotation axis to distribute deformation correctly during weight painting. A typical mistake after ZRemesher is diagonal loops on the elbow, which when the arm bends produce triangular artifacts even with good skinning. Manual retopology is 3–5 times better than any automatic method for animation zones.

Decimation Master in ZBrush preserves shape better but produces a triangular mesh. A triangular mesh cannot be properly textured via UV seams without artifacts and is difficult to work with during further edits. It's only suitable as an intermediate step for baking, not as a final game-ready asset.

How We Distribute the Polygon Budget Across Zones

The process begins by defining the polygon budget per zone. A typical distribution for a VR character on Quest:

• Head + neck: 2000–3000 triangles (about 30%)
• Torso: 1500–2500 (20%)
• Arms (hands are most resource-intensive): 1500–2000 (20%)
• Legs: 1000–2000 (15%)
• Secondary details (clothing, accessories): remaining budget (15%)

Tools: RetopoFlow for Blender (best for manual retopology with surface snapping), Maya Quad Draw for those in a Maya pipeline. In ZBrush—ZSphere retopology as an alternative, but slower. RetopoFlow is 2x faster than Maya Quad Draw for complex characters.

Key principles that are most often violated:

• No triangles or N-gons in deformation zones. Only quads. Triangles are allowed in static areas: soles, back of neck, non-moving elements.
• Edge loops on the mouth slit and eyelids are not a stylistic choice—they are a requirement: without them, blend shapes for facial expressions won't work correctly.
• Mesh density is adaptive: higher on the face, lower on the back. A uniform mesh is a sign of automation.

After retopology, we bake a normal map from high-poly to low-poly in Marmoset Toolbag or Substance Painter. This restores the original's visual detail without polygon cost.

Typical Retopology Mistakes

• Using triangles in deformation zones (joints, face)—leads to animation artifacts.
• Uniform mesh density across the model—waste of polygons on non-animated areas and shortage on animated ones.
• Edge loops not following anatomy—incorrect deformation distribution.

What's Included in the Work: Stages and Deliverables

We perform retopology in several stages:

1. Sculpt analysis—identify animation zones, budget, and complexity.
2. Retopology—build a low-poly mesh with correct edge loops for animation readiness.
3. Baking—create normal maps, ambient occlusion, and other maps.
4. Verification—test deformation in Unity/Unreal, fix artifacts (we check blend shapes and skin weights in both engines).
5. Delivery—provide the final asset in FBX/glTF with UV layout and textures.

We guarantee no triangles in movable areas and correct blend shape functionality. Our engineers have extensive experience in mobile game development and VR. Investing in retopology pays off by reducing animation debugging time—on average, teams save 30% of the budget during the rig stage. The cost of the service is calculated individually after analyzing the sculpt, with typical pricing starting at $200 for a character head and $800 for a full character.

Contact us for a project assessment—we'll provide precise timelines and cost. Request retopology services and get advice on asset optimization.

Estimated Timelines for Retopology

Retopology Tool Comparison

Timelines depend on the complexity of the original sculpt, the number of animated zones, and UV requirements. Cost is calculated individually.

Source: Retopology — Wikipedia

VR and AR Development

When we first launch a project in a VR headset, most teams face the same thing: technically everything works, but in the headset either motion sickness occurs, or hands 'float' with a delay, or the scene looks jerky at the periphery. These are not bugs in the usual sense — they are a consequence of the fact that VR/AR development requires a different approach to render architecture, interaction, and UX from the very beginning of the project. Our experience: over 7 years in game dev, 15+ completed VR/AR projects for Meta Quest, SteamVR, PSVR2, HoloLens. We work with teams that need not just a prototype but a production‑ready application with a stable frame rate.

Platforms and SDKs

We work with all relevant stacks. We use OpenXR as the base layer wherever possible — it provides cross‑platform compatibility between Meta, Valve Index, HP Reverb and other PC VR devices. On top of OpenXR, we build on the XR Interaction Toolkit (Unity) or VR Expansion Plugin (Unreal). Contact us for a stack assessment tailored to your project.

How to minimize motion sickness in VR locomotion?

Locomotion — the main source of motion sickness for inexperienced VR users. According to research, about 70% of users experience discomfort with improper movement settings Oculus Developer Guidelines. Teleportation — standard navigation method when smooth movement is undesirable.

Components from XR Interaction Toolkit: TeleportationArea, TeleportationAnchor, TeleportationProvider. Basic implementation works out of the box, but for production we refine it in four steps:

1. Setting up XRRayInteractor with a curved ray (Bend Ray) — the teleportation arc looks more natural than a straight ray and is perceived better by users.
2. Adding a valid landing zone — a visual indicator changes color when hovering over an obstacle (red/green).
3. Implementing fade transition — smooth screen fade (black fade) before teleportation reduces disorientation.
4. Rotation snapping — after teleportation we offer snap rotation by 45° or 90° instead of smooth, reducing motion sickness risk.

For projects requiring smooth locomotion (action games, simulators), we use comfort settings: vignetting during movement, reducing FOV during acceleration. Settings are available to the user in the menu — different people have different sensitivity thresholds. The difference between kinematic and physics‑based movement: kinematic gives instant hand following but lets objects pass through walls; physics‑based via Joint provides realistic collisions but requires velocity damping and max joint force tuning. We choose based on the type of interaction.

How to make object grabbing in VR physically realistic?

This is the most underestimated part of VR development. Clients often perceive it as 'just hand animation', but in practice it is a complex system where physical correctness, responsiveness, and comfort conflict.

Grab (grabbing)

XR Interaction Toolkit provides three types of Interactable for grabbing:

• XRGrabInteractable — standard grab, object follows controller via physics joint or direct position/rotation
• XRSimpleInteractable — for objects without physical movement (buttons, levers)
• Custom Interactable by inheriting from XRBaseInteractable

Attach Transform — a frequently ignored detail. Each Interactable must have a properly configured Attach Transform (the point where the hand 'attaches'). Without it, the pistol grip will be at the center of the mesh, not where it is held.

For weapons and tools with two‑handed grab — a separate TwoHandGrab system: leading hand determines position, the second — orientation. XR Interaction Toolkit supports this via XRTwoHandGrabInteractable or custom logic with two Attach Points.

Throw (throwing)

Velocity smoothing is critical for realistic throwing because the Rigidbody.velocity at the moment of controller release reflects instantaneous speed, often incorrect due to tracking discretization. The user makes a quick wrist movement — but the object flies half as fast.

Solution: velocity smoothing over the last N frames (typically 5–10 frames, ~80–160 ms at 60 Hz) before release. XR Interaction Toolkit does this via VelocityEstimator. Additionally, we apply a velocity scaling multiplier — a small speed increase (1.2–1.5×) makes throws subjectively more satisfying. Angular velocity (for objects that should spin in flight) is also averaged similarly.

AR: Plane Tracking and Environment Interaction

AR adds a different class of problems — working with real, unpredictable environment. AR Foundation — a cross‑platform layer on top of ARKit and ARCore. Most basic features (plane detection, raycasting, image tracking, face tracking) are available through a unified API.

Plane Detection

ARPlaneManager detects horizontal and vertical planes. Practical nuances:

• Initialization takes time — the user must look around the room while the system builds a map. An explicit onboarding with instruction 'slowly move the camera across surfaces' is needed.
• Planes are unstable — their boundaries and position are updated as data accumulates. Objects placed on a plane need to be attached via parent to ARPlane, not to world coordinates.
• Plane merging — two detected floor segments may merge into one, moving the anchor. For critical anchors, use ARAnchor instead of direct attachment to the plane.

Image tracking (via ARTrackedImageManager) quality directly depends on the quality of reference images. Images with high detail frequency and contrasting edges (like a QR code but stylish) track more reliably than smooth logos. ARCore Geospatial API — for outdoor AR with real‑world coordinate binding (accuracy up to 10 cm in well‑mapped areas).

Optimization for VR: Frame Rate and Comfort

VR requires stable high frame rate. About 60% of development time in mobile VR goes to optimization, not functionality — retrofit costs twice as much as proper architecture from the first sprint.

Single Pass Instanced Rendering

The main render optimization in VR. Without it, the scene is rendered twice (once per eye), doubling draw calls. Single Pass Instanced renders both eyes in one pass via instancing: geometry is processed once, the shader gets two view/projection matrices through GPU instancing. Enabled in Unity via XR Plug-in Management > Rendering Mode: Single Pass Instanced. Important: custom shaders must support SPI — standard URP/HDRP shaders support it, custom HLSL requires modifications (UNITY_SETUP_STEREO_EYE_INDEX_POST_VERTEX and related macros). Applying this technique reduces draw calls by 40–50%, making it twice as efficient as naive double rendering.

Foveated Rendering

On Meta Quest, Fixed Foveated Rendering (FFR) is available — reducing resolution at the periphery where visual acuity is lower. Configured via OVRManager or Meta XR SDK:

OVRManager.fixedFoveatedRenderingLevel = OVRManager.FixedFoveatedRenderingLevel.High;
OVRManager.useDynamicFixedFoveatedRendering = true;

Dynamic FFR automatically increases the level when frame rate drops — more convenient than fixed in scenes with variable load.

IPD and Comfort Settings

IPD (Inter‑Pupillary Distance) — affects depth perception. At the programmable level on most devices, only reading IPD is available (OVRPlugin.GetSystemDisplayFrequency), physical adjustment is on the headset. For applications requiring precise positioning (medical simulators, training), we account for IPD in scene scale calculations.

Haptics

Haptic feedback — an underestimated tool. Even a simple vibration response when grabbing an object or hitting significantly increases the sense of presence. On average, integrating haptic patterns takes 30–80 hours per project.

XR Haptics via OpenXR:

var hapticImpulse = new UnityEngine.XR.HapticCapabilities();
InputDevice device = InputDevices.GetDeviceAtXRNode(XRNode.RightHand);
device.SendHapticImpulse(0, amplitude: 0.5f, duration: 0.1f);

For complex patterns (tactile 'texture' of a surface when touched, increasing vibration when drawing a bowstring) we use Meta Haptics Studio — allows designing haptic clips visually. This can reduce time spent on manual haptic tuning by about 30%.

What does VR/AR application development include?

When ordering a turnkey project, we provide the following deliverables:

• Architectural document with stack description, render logic, and interaction system
• Working prototype (MVP) for testing on target device
• Integration of necessary SDKs (Meta XR, OpenXR, AR Foundation, etc.)
• Optimization for target frequencies 72/90/120 Hz with draw call and FPS profiling
• Testing on physical hardware (Quest, SteamVR, HoloLens) with user involvement
• Full documentation for build, deployment, and support
• Training for the client's team (workshop on XR Toolkit)
• Warranty support for 1 month after delivery

What affects cost and timeline?

VR/AR projects are more expensive than regular games of similar scope. Iterations are slower — each fix must be tested in the headset, an emulator does not convey the real experience. Motion sickness forces reworking some conceptual decisions after the first playtest. Optimization takes a significant portion of time — for mobile VR (Quest) up to 60–70% of the cycle. For Quest projects, we start optimization from the first sprint. The cost of basic SDK integration (XR Interaction Toolkit) varies depending on the scope of custom Interactable. Typical budgets for a full Quest project range from $25,000 to $80,000 depending on complexity, number of custom interactions, and depth of optimization. Proper architectural planning from sprint one typically saves 40% on later rework compared to fixing performance bottlenecks retroactively.

Get a consultation on your project — we will assess the task, stack, and timelines. Order turnkey VR/AR application development with a guaranteed stable frame rate.