When this happens it means that the plugin is not installed properly. Make sure that the plugin’s folder structure is as required by X-Plane.
The expected folder structure is the following:
Yes, HeadShake works on X-Plane 10 (64 bit), X-Plane 11, and X-Plane 12.
Yes. HeadShake works on X-Plane 12 on M CPUs.
First of all, make sure that Headshake is shown in plugins admin. If it’s not, make sure you installed it correctly as shown in this FAQ: https://www.simcoders.com/faqs/headshake-is-not-shown-in-the-plugins-list/
Then, make sure that none of your devices (joysticks, yokes, etc.) repeatedly calls an X-Plane view command (“Glance Left”, “Glance Right”, etc). If this happens, Headshake temporarily stops its control over the X-Plane camera to let the view change properly. If a device repeatedly sends a view command then Headshake stays on hold forever. It does then not show any effect.
This problem occurs when using a multimonitor setup.
To avoid it, just enable the “Multimonitor Compatibility” in HeadShake’s settings.
At the moment, it seems that HeadShake must share the same datarefs with many other plugins. The same view dataref cannot be writed by more plugins at the same time.
We’re working to improve the compatibility but there isn’t a specific roadmap nor a release release date planned.
You may want to take a look at the X-Camera plugin that provides a compatibility interface for both HeadShake and the Track IR.
This plugin is not aimed to simulate the view of a handheld camera. It simulates the point of view of the pilot. Usually, while flying a plane your head does’t “roll” when you start turning the plane, even when you’re doing aerobatics.
This is hard to tell. It depends on many factors. Basically, if a new effect can be done without too much work, it may be included.
Just write to firstname.lastname@example.org.
Make sure you provide:
- A description of the bug you’re reporting. Possibly, provide a step by step guide.
- Your X-Plane version
- The plugin version
- A list of the plugins you’re using along the one which is afflicted by the bug
- The content of your Log.txt (as attachment)