Court manual / PC release · keyboard & mouse
Choose your camera, cursor and HUD settings
Start with Dynamic for ball tracking or Static for a fixed view from your side, then press C to compare all four cameras. Zoom with V or the wheel. In Profile settings, use Reach Marker for contact timing and Last Touch Outline to see who touched the ball.
Updated 2026-11-16 · PC release · keyboard & mouse
- CCompare the views
- V / wheelKeep the court visible
- ProfileAdjust HUD and assists
From input to contact
Compare the four cameras on the court
Open Practice → Tutorial and reach the Camera section, or compare the views in Free Play. Keep your player in the same part of the court while pressing C. Pick the view in which you can read your depth and keep the intended target visible.
Open full-size image ↗Static shows the court from your own side. C changes view; V or the wheel changes zoom. Community tutorial image from a beta build; release-day inputs are described in the text. Camera choices and the trade-off to check Camera What it shows Check before choosing Dynamic Tracks the ball Can you aim while the camera follows play? Static Looks down from your side Can you judge near and far landing points? Broadcast Side-on elevated view Can you distinguish court depth from this angle? Action Third-person perspective Can you still see the next contact and target? Keep the cursor on a court target
The cursor normally stays attached to a court location when the camera angle changes. A moving camera can still make aiming feel different: compare it while aiming at one teammate or court spot, rather than chasing a fixed screen pixel. Q returns the cursor to your own position. M enables free mouse mode and changes the normal court-fixed behaviour, so leave it off for the basic aiming check.
Open full-size image ↗Dynamic follows the ball; its framing changes with play. Compare how easily you can keep a chosen court target. Community tutorial image from a beta build; release-day inputs are described in the text. Choose the HUD aids that solve your problem
Open Profile settings → Gameplay for HUD and input options, and Accessibility for the assists. Start with Reach Marker and Last Touch Outline so contact timing and touch ownership are visible. Place the charge indicator at the character, cursor, or a mix according to where you can see it while aiming.
Settings with a specific job Setting What it changes Use it when Reach Marker Shows a contact-time marker You cannot tell when the ball is in reach Last Touch Outline Outlines the last player to touch in team colour A crowded rally hides touch ownership Charge indicator position Character, cursor or mixed placement The charge display is away from your attention Mouse sensitivity How far the cursor moves You keep overshooting or cannot reach a target Cursor assist Restricts the cursor’s range beyond the court You often aim too far outside the court Set assist Keeps the set cursor from crossing the net You send intended sets into the opponent’s half Use the Reach Marker as a timing cue
With Reach Marker enabled, watch for the sight-like marker as the ball becomes reachable. Try a timed grounded left-click receive, then check the outgoing ball reaches the cursor target. For sensitivity, begin with your current value, make one small change and repeat the same target movement; there is no single value that fits every mouse.
Open full-size image ↗nu’s HUD comparison: off on the left, on on the right. The added sight is the Reach Marker.
When it works
You can see the landing area, aim at a chosen court spot and recognize the contact cue without losing the target when the camera moves.
If it does not work
If C skips a camera you want, open Profile → Cameras and check its cycle option. If a set cannot aim across the net, check Set Assist. If camera motion makes cursor placement difficult, switch to Static and repeat the same receive before changing sensitivity again.
Sources & version
Inputs and conditions follow nu’s Japanese specification guide and tutorial, updated for the November 16, 2026 PC release (November 17 in Japan). Screenshots retain their beta-build context.