Use this checklist to separate preview setup, projectile movement and rendering issues.
Common symptoms#
| Symptom | Check |
|---|---|
| No path appears | Enable visualization; check the source, camera view/layers, direction, speed and path material. |
| The path ends too soon | Check preview distance, duration, steps, buffer, projectile lifetime/range, contact limits and stopping surfaces. |
| A control is locked | Check its feature toggle, assigned source or active performance profile. Movement belongs to the projectile; preview style and length belong to the trajectory. |
| The wrong prefab fires | Check the loadout, zero-based active index, unique entry ID and prefab reference. Look for scripts that keep restoring the old selection. |
| The projectile fires by itself | Disable Launch on Play for launcher-controlled prefabs. Check automatic input versus your custom input adapter. |
| Contact or bounce differs from the preview | Check dimension, colliders, layers, triggers and movement authority. Rigidbody mode uses native physics materials; swept modes use toolkit responses. |
| A marker disappears into a surface | Adjust its surface offset. Contact rings are flat meshes and do not project over curved terrain. |
| Drag aim jumps to full stretch | Read CurrentDragOffset, check the drag threshold and max distance, and make sure only one input owner handles the gesture. |
Compatibility and verification scope#
The publisher's compatibility statement is Unity 6000.3.13 or newer. Earlier Unity versions have not been tested. The supplied guide and project note identify the inspected configuration as Unity 6000.3.13f1, URP 17.3.0, Windows Editor/DX12. This website update did not compile or run the Unity package.
The source guide does not establish Built-in, HDRP, URP 2D Renderer, Android or iOS support, and it gives no universal trajectory-accuracy guarantee. Validate the materials and device behavior in the pipeline and target platform used by your own project. Moving-target paths use a snapshot; Rigidbody previews are approximate.
The supplied project note also reports legacy Trajectory and Demo Solid shaders without explicit SRP subshaders, alongside SRP-named alternatives. Existing references are not automatically migrated. Check those materials if an SRP compatibility warning appears.
For package questions, use the Support & contact link in the package details panel.