I think new flywithlua is addressing this matter. https://github.com/X-Friese/FlyWithLua/tree/master/FlyWithLua

Not at this time – we may look at it in the future. At this point I’m not sure Leap motion has everything it would need for critical mass:
– A lot of adoption within the VR adoption.
– A really solid technology.
– Being enough like other technology that it’s not just a big special case.

From our perspective, we can’t have every single input controller that gets invented mean a trip back to the drawing board for artists making planes with manipulators. So if it would take a lot more meta-data to have leap interaction than controller wand interaction, that’s a big problem..if we hang too much on the authors, 3rd parties are going to go “VR mouse only” – they get paid to make aircraft, not to add more free stuff to existing aircraft – that’s just the economics of the add-on market.

so for example, if the leap controller needs to know the knob radius but touch controllers don’t, that’s an example of the extra ‘art tax’ for what doesn’t have a lot of adoption.

What a wonderful and exciting time! Almost every week it’s christmas time.

Before anyone says, I will make a bug report as soon as I test a little further. Here I’m just asking if anyone else has experienced this and maybe found a solution.

Not sure if this could be related to a mod, since FlyWithLUA is throwing errors so my next step is going to be to try running without the mods but I thought I’d ask in the meantime if anyone else has had this problem.

Dazzy.

Please do!! A flawed AGP exporter is better than no AGP exporter. It could probably help us scenery designers a lot in some ways.

The advanced menu follows the same rules as the REAL menu bar: it disappears each time you pick one command.

Commands in the menu bar should be built around this principle, e.g. it’s a great place for “connect to VATSIM servers” and a terrible place for “move head up a tiny bit”.

The move commands are in there not because we think it’s a great place to pick them, but because it provides a very quick visual cue to users (when using 2-d menus) as to what the short-cut is for the view commands.

But…you’re totally doing this wrong. Bind something ELSE to the move commands – they’re keyboard, joystick, and controller accessible. Whatever else you have access to – use that.

(We’re not leaving the menus open because, for the vast majotiry of menu commands, pick once and hide the menu is the reasonable behavior; leaving the menu open for move commands is the tail wagging the dog.)

I am in VR using the Vive with two touch controllers.

If the advanced menu did not disappear until you pressed the menu button on the touch controller again this would work like in vr1.

Is there a reason this behavior changed from vr1?

Thanks Bill