To clear a couple of things up:
1. FlyInside for Vive was originally in Beta due to driver issues, making Vive nearly unusable on a lot of hardware+resolution combinations. These days, FlyInside for Vive is really on par with FlyInside for CV1. I'm very close to taking Vive out of Beta, but want to fix bugs that exist when using Vive controllers to manipulate virtual windows. If you're waiting to purchase due to the "Beta" label, keep in mind it really is mostly a label at this point.
2. I'm actually no longer the only developer at FlyInside (not Tony's fault, forgot to tell him). Still too few people for too much code though
3. Don't worry, Vive isn't "on pause" nor has Vive support been abandoned to work on X-Plane. It's all under development, and you can expect future updates/improvements. It just takes time.
A suggestion for your particular issue. On certain computers/configurations, FlyInside is unable to load up certain modules it needs for interaction (usually related to anti-virus). Try loading the stock Cessna 172, then switching aircraft to your plane of choice. This should force your simulator to load the modules FlyInside needs, and they remain loaded when you switch to other aircraft
Please let me know if this fixes the inconsistently working aircraft for you.
Thanks,
Dan