Quick answer: Screen Space Overlay canvases always have pressEventCamera = null. Camera-based or World Space canvases return their Event Camera. For drag-to-world conversion, fall back to Camera.main when pressEventCamera is null.

Here is how to fix Unity PointerEventData wrong camera. You implement drag-and-drop UI that projects to the world — click an inventory icon, drag over the world, get the world-space hit point under the cursor. You use eventData.pressEventCamera.ScreenPointToRay. NullReferenceException. Or the ray uses the wrong camera and your drop position is off by hundreds of meters.

The Symptom

UI event handlers that need a camera reference encounter one of:

What Causes This

Overlay canvases have no camera. Screen Space - Overlay is rendered directly to the screen without a camera. Unity sets pressEventCamera to null for these canvases. Any screen-to-world math fails.

Event Camera not assigned. For Screen Space - Camera canvases, the Event Camera field on Canvas must be set. If null, pointer events have no camera reference.

Multiple cameras competing. Scenes with several cameras (main, minimap, UI) can cause events to fire for the wrong camera if canvas Event Camera assignments are inconsistent.

Camera.main returns null. Camera.main finds the first enabled camera tagged MainCamera. If no camera has that tag, returns null. Your fallback breaks on scenes where you forgot to tag the camera.

The Fix

Step 1: Always null-check and fall back.

using UnityEngine;
using UnityEngine.EventSystems;

public class InventoryDrag : MonoBehaviour, IDragHandler
{
    public void OnDrag(PointerEventData eventData)
    {
        Camera cam = eventData.pressEventCamera;
        if (cam == null) cam = Camera.main;
        if (cam == null) return; // no viable camera

        Ray ray = cam.ScreenPointToRay(eventData.position);
        if (Physics.Raycast(ray, out RaycastHit hit))
        {
            UpdateDragPreview(hit.point);
        }
    }
}

Two-tier fallback handles both Overlay canvas users (no event camera) and camera-based canvas users (event camera set).

Step 2: Assign Event Camera consistently. For every non-Overlay canvas in your scene, assign the same camera to Event Camera — usually the main gameplay camera. This makes eventData.pressEventCamera predictable.

Step 3: Switch to Screen Space Camera mode. If your UI is screen-space but needs camera context, switch from Overlay to Camera mode:

  1. Canvas Render Mode: Screen Space - Camera
  2. Render Camera: main camera
  3. Plane Distance: 100 or so (distance in front of camera)

Now pressEventCamera is always your main camera, and screen-space UI still appears normal.

Step 4: Use RaycastResult.module.eventCamera for precise camera. PointerEventData includes RaycastResults from every raycaster that found the pointer. Each result’s module (the Raycaster component) has an eventCamera:

foreach (var hit in eventData.hovered)
{
    // Component hierarchy hit here
}

// Better: use the current raycast result's camera
Camera rayCam = eventData.pointerCurrentRaycast.module?.eventCamera;

For hit-testing within a specific canvas’s context, this is the most accurate camera to use.

Multi-Camera Tips

For a game with minimap and main views:

Each canvas stays associated with its intended camera. PointerEventData.pressEventCamera returns the correct one for each click location.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“pressEventCamera is only as smart as your canvas setup. Assign Event Camera explicitly; never rely on magic defaults.”

Related Issues

For World Space canvas issues, see World Space Canvas Not Following Camera. For raycaster blocking, UI Raycaster Blocking Clicks.

Null-check pressEventCamera. Fall back to Camera.main. Assign Event Camera consistently.