Compare ChasePlane vs EZdok for Prepar3D: setup, motion effects, profiles, compatibility and which camera add-on suits your flying.
For most Prepar3D users, ChasePlane is the better camera add-on because its interface, aircraft profiles and control assignments are easier to manage. EZdok remains a strong choice for simmers who want granular motion effects or already have tuned EZCA profiles. Before choosing either, confirm that its exact build supports your Prepar3D version.
ChasePlane vs EZdok at a glance
ChasePlane favours a streamlined, preset-oriented workflow, while EZdok Camera, usually called EZCA, rewards users prepared to spend more time configuring individual views and movement effects.
| Area | ChasePlane | EZdok |
|---|---|---|
| Best fit | New installations and users wanting quick per-aircraft camera setup | Existing EZCA users and those who prefer detailed manual tuning |
| Interface | More visual and generally easier to learn | More technical, with a steeper initial learning curve |
| Camera profiles | Convenient aircraft-specific profile workflow | Powerful profiles, but configuration takes more attention |
| Motion effects | Accessible controls for turbulence, vibration and ground movement | Detailed effect editing for users who want to tune each behaviour |
| Controls | Keyboard and controller assignments are straightforward to organise | Flexible assignments, though conflicts require careful checking |
| Migration | Cannot directly use EZCA profiles | Cannot directly use ChasePlane profiles |
Both can create cockpit, external and fixed viewpoints, and both can add motion that the standard Prepar3D camera system does not provide as conveniently. Neither improves frame rates; at unstable frame rates, strong movement effects can actually appear jerky.
Which camera add-on should you choose?
Choose ChasePlane for a fresh Prepar3D setup; choose EZdok when its established profiles or deeper effect-tuning workflow matter more to you.
- Choose ChasePlane if you fly several aircraft, frequently create new views or want to assign controls without spending much time learning the editor.
- Choose EZdok if you already have carefully tuned EZCA profiles, prefer its effects editor or depend on an existing control layout built around it.
- Choose neither if you only need a few fixed cockpit and exterior positions. Prepar3D can already save and organise useful viewpoints; our guide to built-in Prepar3D camera categories and saved views explains the simpler option.
Shared or imported profiles should be treated as starting points. Monitor aspect ratio, field of view, zoom and differences between aircraft variants can leave a downloaded cockpit view too high, too close to the panel or inside the seat geometry.
Will ChasePlane or EZdok work with Prepar3D v5 and v6?
Compatibility depends on the exact camera utility build and Prepar3D generation, not merely the Prepar3D name.
Do not assume that a build designed for Prepar3D v4 or v5 will work correctly in v6. Camera utilities interact closely with the simulator's view system, controls and internal interfaces, so an unsupported version may launch yet fail to save views, apply effects or recognise aircraft correctly. Our explanation of why P3D v5 add-ons do not automatically carry over to v6 covers the checks required before upgrading.
Before installing either utility, verify:
- the exact Prepar3D major version named by that release;
- whether the installer supports your Windows and simulator installation arrangement;
- whether an older edition of the same camera utility must be removed first;
- whether your existing profiles can be imported into that particular release.
If support information does not explicitly name your Prepar3D generation, treat the utility as unsupported rather than assuming backward compatibility.
Can ChasePlane and EZdok be used together?
No—do not run ChasePlane and EZdok as active camera controllers at the same time.
Both can intercept view commands, controller buttons and head movement. Running them together commonly produces double movement, views snapping back, duplicated vibration and controls that appear to ignore input. Their files may remain installed during a careful migration, but only one camera engine should start with Prepar3D.
- Back up your profiles. Use each utility's export or backup function where available; the two profile formats are not interchangeable.
- Disable the old utility. Remove its automatic start-up or simulator integration using its own configuration or uninstaller.
- Check assignments. Clear duplicate camera axes, hat-switch commands and view buttons from the inactive utility and Prepar3D.
- Configure one aircraft first. Test a default aircraft before building profiles for complex add-on aircraft.
- Add effects gradually. Establish reliable camera movement before enabling turbulence, engine vibration and ground-roll effects.
For safer removal, reinstalls and configuration changes, follow our Prepar3D utility installation and management checklist.
Why do camera controls snap, shake or stop responding?
Most ChasePlane and EZdok faults come from duplicate inputs, excessive effects or an old profile being applied to a changed aircraft.
The view moves twice or snaps back
Look for the same hat switch, keyboard command or analogue axis assigned in both Prepar3D and the camera utility. Native head tracking can also fight the add-on if both layers are trying to control the same view axis.
Movement is jerky during taxi or turbulence
Reduce ground-roll, turbulence and engine effects separately rather than lowering every effect at once. Check frame pacing as well: an aggressive shake profile exposes inconsistent frame delivery much more clearly than a stationary cockpit view.
A profile loads in the wrong position
Confirm that the profile belongs to the exact aircraft or variant being flown. Aircraft updates, renamed variants and different cockpit geometry can require a fresh profile or manual eyepoint adjustment.
The utility opens but does not control Prepar3D
Make sure the selected release supports that Prepar3D version, only one camera engine is active, and Prepar3D and the external utility run at the same Windows privilege level. If the fault remains, test with a default aircraft and a blank profile before reinstalling anything.
Our recommendation
We recommend ChasePlane for most users starting with a supported Prepar3D installation because it makes everyday camera creation and profile management easier. EZdok is the better fit for an established EZCA setup or a simmer who values detailed manual effect tuning. Version compatibility overrides every feature comparison: if the required build does not explicitly support your Prepar3D release, it is not the right choice.