Fix ChasePlane WASM, mouse control and Smart View in MSFS by checking the Community package, WASM cache, bindings, focus and camera conflicts.
The ChasePlane WASM module, mouse control and Smart View usually fail in Microsoft Flight Simulator because the in-sim package is missing or stale, ChasePlane is connected to the wrong simulator installation, or another camera/input system owns the mouse. Verify the WASM connection first; Smart View depends on both that connection and a working binding.
This troubleshooting applies to the PC desktop-client and WASM setup. MSFS 2020 and MSFS 2024 have separate package locations and caches, so a ChasePlane installation working in one simulator does not prove that the other is configured correctly.
Which ChasePlane component is failing?
The symptom identifies whether the fault is in ChasePlane’s connection, its WASM package or the input and camera layer.
| Symptom | Most likely fault | Decisive test |
|---|---|---|
| ChasePlane does not detect MSFS | Desktop connection, launch or permission problem | Check whether it connects after both applications are restarted at the same privilege level |
| MSFS is detected but WASM remains unavailable | Wrong Community folder, disabled package or stale compiled cache | Load a normal flight with only ChasePlane in the Community folder |
| WASM connects but mouse control does nothing | Duplicate binding, window focus or another camera system | Assign the same action temporarily to an unused keyboard key |
| Smart View works by keyboard but not by mouse | Mouse assignment or input-capture conflict | Remove the same button from MSFS freelook and other camera commands |
| Smart View fails with one aircraft only | Aircraft profile, variant or custom camera conflict | Test a default aircraft with a fresh ChasePlane profile |
How do I restore the ChasePlane WASM connection?
A clean, correctly installed package must load before mouse control or Smart View can be diagnosed reliably.
- Close ChasePlane and MSFS completely. Confirm that neither application is still running before changing packages or caches. MSFS will not recognise a newly installed module reliably if its process remained open.
- Verify the selected simulator integration. Make sure the ChasePlane installer points to the active MSFS 2020 or MSFS 2024 installation, not an old Community folder left by another edition or installation method. Our ChasePlane installation and integration checks cover the setup choices without requiring a full simulator reinstall.
- Inspect the package structure. The ChasePlane package root should contain normal MSFS package files such as
manifest.jsonandlayout.json. If those files are inside an extra nested folder, MSFS will not scan the package. Do not move a bare.wasmfile into Community; retain the complete structure produced by the installer. - Start MSFS in Normal Mode and load a flight. Safe Mode deliberately suppresses third-party packages, so ChasePlane’s module being absent there is expected. Test with a default aircraft and wait for the cockpit to finish loading; the main menu alone is not a valid WASM test.
- Refresh both ChasePlane components. Use ChasePlane’s installer or updater so the desktop application and in-sim bridge come from the same release. Mixing a newer client with an older Community package is a common cause of a permanent disconnected-module status.
- Rebuild the compiled WASM cache. Do this only after confirming that the installed package is present. With MSFS closed, rename the relevant cache as a reversible test rather than deleting unidentified package files. For MSFS 2024, our guide to locating and safely refreshing the WASM cache explains the difference between compiled cache data and the installed Community package.
- Run a clean add-on test. Temporarily move every other Community package out, leaving only ChasePlane, then launch in Normal Mode. If the module connects, restore other camera utilities, aircraft systems and WASM add-ons in small groups until the conflict returns.
- Match Windows permissions. Run ChasePlane and MSFS under the same Windows account and privilege level, preferably with neither forced to run as administrator. Also check whether security software quarantined part of the client or module; allow the specific trusted component rather than disabling protection globally. If the desktop application itself will not connect or activate, follow our ChasePlane connection, permissions and launch-order checklist.
Why does ChasePlane connect but mouse control fail?
If ChasePlane and its WASM module are connected, a mouse-only failure is almost always an input assignment, focus or camera-ownership problem.
- Return focus to the 3D view. Close toolbar panels, pop-outs and text fields, then click the cockpit or external scene. A focused panel can consume the wheel and mouse buttons before ChasePlane sees them.
- Remove duplicate assignments. Inspect both ChasePlane’s input assignment and the MSFS mouse profile. A button assigned to ChasePlane and MSFS freelook can make the camera stick, move briefly or ignore the press entirely.
- Use a keyboard test binding. Assign the affected ChasePlane command temporarily to an unused keyboard key. If it works, leave the WASM installation alone and concentrate on the mouse profile or mouse utility software.
- Disable competing camera output. Pause head tracking, VR, drone-camera controls and any other camera utility for one test. Two systems writing the viewpoint can make ChasePlane appear unresponsive even though it is receiving the command.
- Test native MSFS panning. Exit ChasePlane and check whether the simulator’s own cockpit look works. If it does not, repair the underlying controls first; our MSFS 2024 mouse-look troubleshooting covers freelook bindings, input profiles, head tracking and focus conflicts.
Do not assume a particular mouse button must be the default. Imported profiles, mouse-driver software and previous camera assignments can all change what reaches ChasePlane.
Why is Smart View still not working?
Smart View will not recover until ChasePlane has a valid connection, receives its trigger and has an appropriate aircraft camera profile to use.
- Prove the trigger works. Bind Smart View to one unused keyboard key. If that works, the feature and profile are healthy; the fault is the mouse assignment.
- Select the correct aircraft profile. Confirm that ChasePlane loaded the profile for the exact aircraft or variant in use. Create a fresh test profile with one known camera if an imported or converted profile behaves unpredictably.
- Use a simple camera state. Test from a standard two-dimensional cockpit view without VR, head tracking, showcase controls or another camera application. Restore those systems one at a time after Smart View responds.
- Compare aircraft. If Smart View works in a default aircraft but not a complex add-on, the global WASM installation is sound. Rebuild or reassign that aircraft’s ChasePlane profile and check for custom camera logic supplied by the aircraft.
Do I need to reinstall Microsoft Flight Simulator?
No; reinstalling MSFS is rarely justified for a ChasePlane-only fault and does not necessarily remove a bad Community package, cache or control profile.
If ChasePlane still cannot establish its WASM connection with a clean package, refreshed cache, default aircraft and matched permissions, repair ChasePlane and its simulator integration. If that clean test works, restore add-ons and input devices one at a time—the item that makes the fault return is the component to remove, update or reconfigure.