How to Create VR Concept Art for Characters: Complete Guide and Process

We know: concept art for VR is not the same as concept art for flat screens. An artist drawing a character for a regular game works within a single camera angle. In VR, the player literally walks around the character, looks up from below, leans into facial details. This changes everything: from silhouette proportions to the density of detail on different mesh zones. Our team has 10+ years of experience in game development and has delivered over 50 VR projects (over 100 characters total), so we guarantee a quality result.

A typical mistake is bringing a concept made to AAA action standards into VR. A character detailed for a distance of 3–5 meters and a fixed camera angle looks poor in VR: textures blurry up close, head proportions distorted (VR skews perception), and clothing details readable on a screenshot become a mess when rendered at 72 fps stereo.

Why VR concept art starts with platform technical limitations

Before the artist opens Photoshop or Procreate, the target platform must be defined. Meta Quest 3 and Quest Pro are one thing. PC VR (SteamVR, Index) is another. Mixed reality via passthrough is a third.

For mobile VR (Quest 3 standalone), the concept immediately sets a budget: the character must not exceed 15,000–20,000 polygons in the final mesh, dictating which details are worth drawing and which must be baked into normal maps. An artist unaware of this limitation will draw armor with 200 small rivets — and then everything must be simplified during modeling, losing shape.

For PC VR, the budget is higher (up to 100k polys), but another problem arises — presence. When the player sees the character a meter away, the uncanny valley hits much harder. The concept must either lean into a clear stylized art direction (no attempt at realism) or immediately provide a level of detail sufficient for SSS skin shaders and high-quality displacement.

Let's compare platforms:

Following the Oculus Asset Optimization Guide (https://developer.oculus.com/resources/performance-asset-optimization/) helps adhere to these limitations. A properly designed concept reduces modeling time by 30–40% compared to art created without VR constraints — that's 2x faster than traditional pipelines.

What is included in the concept set for a VR character

A standard concept package for a VR character includes several layers that go directly into production:

Orthographic views — front, side, 3/4. Unlike regular projects, special attention is given to the top-down view: in VR, the player often looks down at NPCs, and the top of the head must be detailed.

Breakdown by detail zones — a diagram indicating where high-poly bake, diffuse detail, or flat color will be used. This is a production pipeline artifact — without it, the modeler wastes time on details that will never be seen.

Color layout and material zones — annotated for the PBR pipeline: what is metallic, roughness, which zones are emissive. A concept artist who understands PBR saves the technical team several iterations.

Variations — at least 2–3 color skins if needed for NPC variety. These are done on the same base concept mesh.

On some projects, we also produce an expression sheet — a set of key emotions if the character will be used in dialogue scenes with close VR camera. Without this, the animator improvises facial expressions on their own.

What's included in the work (deliverables)

Our standard deliverable package includes:

• High-resolution concept art (4 views) with full PBR material breakdown
• Documentation: color codes, material references, style guide
• Orthographic templates for modeling
• Support during asset integration (2 rounds of revisions included)
• Training for your team on VR-specific art optimization if needed

How we create concept art for VR: step-by-step

1. Technical specification analysis — study the target platform, allowed polygon count, style, and character role.
2. Reference gathering and art direction — collect references specific to the game and existing visual style.
3. Sketch round — draw 3–5 silhouettes to choose a direction. Present to the client.
4. Final concept — refine details considering VR: check silhouette readability, proportions from below, detail density in zones.
5. Create breakdown and PBR maps — mark materials, prepare schema for the modeler.
6. Handoff to modeling — deliver package with iterations (two rounds of revisions included).

Process overview

First — technical specification and reference gathering. It is crucial to understand the style (realism, stylization, toon, sci-fi), target platform, character role (main hero, background NPC, boss). If existing art direction exists, it must be studied to ensure the character fits the world.

Next — sketch round: 3–5 loose silhouettes, direction selected. Then final concept with detail refinement and package handoff to modeling.

Iterations are explicitly built into the process: two rounds of revisions are included, a third round is negotiated. This is important because VR concepts often require adjustments after the first view in the headset — what looks great on a monitor may feel different in the headset.

The cost is determined after discussing the TOR and references; basic concept starts from $500.

If you need high-quality concept art for a VR character, contact us to discuss the details. Get a consultation on pipeline and budget optimization.

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.