Controller virtual cursor: PointerSelect positions offset by the window's desktop position

Summary

With TouchMapping added, a gamepad player’s virtual cursor reports PointerSelect viewport positions offset by about (+20.0, −4.13) cm, roughly (756, 156) px at 96 dpi, whenever the Fortnite client runs in a window that is not maximized. The offset is consistent with the window’s position on the desktop. The mouse reports correctly in the same window, and the gamepad reports correctly once the window is maximized.

Build: Fortnite 43.10 (++Fortnite+Release-43.10-CL-60458657), UEFN edit session, Windows PC client with a Scuf Envision Pro gamepad for PC.

Evidence

Verse log from a top-down camera test, pressing A on the screen middle, the four corners of a square board and the screen edges. Positions are viewport cm (Left, Up). The windowed run used a 1920 × 1080 window (viewport middle (25.40, −14.29)); the maximized run read the viewport middle as (35.31, −14.29).

Window Input Aimed at Projected position Reported position Difference
Windowed Gamepad Board center (25.40, −10.55) (45.51, −14.47) +20.1, −3.9
Windowed Gamepad Left corner (9.57, −10.55) (29.77, −14.71) +20.2, −4.2
Windowed Gamepad Bottom corner (25.40, −2.16) (45.32, −6.38) +19.9, −4.2
Windowed Gamepad Top corner (offset would leave viewport) (25.40, −26.42) (25.29, −26.17) none
Windowed Gamepad Right corner (offset would leave viewport) (41.23, −10.55) (41.12, −10.48) none
Windowed Mouse Board center (29.59, −12.64) (29.61, −12.44) none
Maximized Gamepad Board center (35.31, −10.55) (35.29, −10.53) none
Maximized Gamepad Left corner (19.48, −10.55) (19.56, −10.59) none
Maximized Gamepad Top corner (35.31, −26.42) (35.16, −26.23) none
Maximized Gamepad Right corner (51.14, −10.55) (51.03, −10.39) none

Holding A and moving the cursor right with the stick in the windowed run, the reported position rose smoothly by about 0.5 cm a report, then jumped with no change in input:

PointerSelect triggered at (50.747083, -18.573750)
PointerSelect triggered at (30.744583, -14.446250)

Each crossing logged the same jump, (−20.0025, +4.1275) one way and (+20.0025, −4.1275) back. The same held-A pans in the maximized window logged no jumps.

Impact and workaround

On a windowed PC, gamepad players can’t pick world positions with the virtual cursor: taps land elsewhere, and drags jump as the cursor crosses the line. Verse can’t undo the offset, because over most of the screen one reported position fits two true positions. A drag can be patched by ignoring single-report jumps larger than the cursor’s top speed, but a tap can’t.

Workaround: maximize the Fortnite window, or play fullscreen.

Not yet checked: whether the offset follows the window when it’s moved, and whether consoles show anything similar.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Other

Steps to Reproduce

Steps to reproduce

  1. In a Verse device, for a player, call GetPlayerInput[Player].AddInputMapping(TouchMapping) and subscribe to GetInputEvents(PointerSelect).BeginDetectEvent. Print the position it reports.
  2. In the same handler, print Player.ProjectWorldToViewport[P] for a visible world point P, such as a prop near the middle of the screen.
  3. Launch a session with the Fortnite client in a window that is not maximized, placed away from the desktop’s top-left corner.
  4. With a gamepad, move the virtual cursor onto P and press A.
  5. Repeat with the mouse, then again with the gamepad after maximizing the window.

Expected Result

Expected: the PointerSelect position equals the projected position of P, within a small margin, for every input device and window state.

Observed Result

Actual: in a window that is not maximized, the gamepad’s reported position is the true position plus a constant offset, (+20.0, −4.13) cm in our test. Where the offset position would fall outside the viewport, the true position is reported instead. So while A is held and the cursor crosses that line, the reported position jumps by the full offset with no change in input. The mouse reports correctly in the same window. With the window maximized, the gamepad also reports correctly.

Platform(s)

PC

Island Code

9999-9999-9999

Additional Notes

Game is not published yet. Full Verse session logs are available on request: the raw PointerSelect begin and triggered lines for the windowed and maximized runs, with the projected positions of the reference points logged beside each press. I can also share the small Verse probe device used to capture them. A held-A stick pan in a non-maximized window shows the jump within a few seconds, so that’s the quickest way to see it.