Thanks, Stephan
A little slow in replying, but since your post I have added leap motion and notice that the operation (or not) of buttons seems to be the same with both so I conclude that the issues are with the Flyinside interface. Hoping, as you say, for some improvements with X Plane 11.
Is it helpful, if I provide someone with the details of issues (or post the detail here)? I could give some very specific feedback for development - even help with testing if that's useful.
In summary I have identified the following issues (can give more detail, if needed). They apply equally to Oculus Touch controllers and to LeapMotion:
1) MCDU: none of the buttons can be pressed with Touch or LM
My number one issue, because a flight plan and other settings have to be input for every flight and there is no work-around (flight plans can be loaded from text files, but the glide slope data is never correct and I use the excellent data from Navigraph).
Using the mouse with Oculus is a nightmare - several clicks often just to press one button 2) Flaps: can move to positions 2, 3 or 4 (eg "flaps 3" heard), but then always springs back to position 1 ("flaps 1" heard)
3) Altitude: moves nicely through the low thousands then jumps to 20,000 ft so always need a mouse to set something like 15,000 ft
4) Can't find a button on the overhead panel (power, lighting, other controls etc) that works
- also brake and brake fan buttons don't work
5) Thrust lever not grabable and moveable (for me not such a big issue)
6) On multi-function buttons like the pressure knob when using push-pull I sometimes end up "turning" the knob (eg changing the pressure setting, which once caused the aircraft to dive!) - maybe a way in Flyinside to make the knob less sensitive?
Just a start at documenting the issues; can do more, if helpful
(Ticked this time the "notify me when a reply is posted" box - so should react a little faster next time round, Stephan!)