I have bought the JustFlight Arrow and Carenado Seneca and have major issues with both.
Issue 1 - offset clickspots in VR
Since buying a headset last December I fly exclusively in VR. It’s so much more immersive, there is no going back.
It works perfectly fine in the default airplanes. Even got the fps to be reasonable with 100% render scale.
But both in the Arrow and the Seneca the virtual cockpit is a mess. I can’t click half of the buttons. Either the mouse is off by a few inches or the clickspots are so small it’s impossible to use them. Spent literally 5 minutes yesterday trying to move the fuel cutoff in the Seneca and gave up. On flat screen it worked just fine.
Control binding issues
My honeycomb yoke and throttle work perfectly in the default aircraft but not in those 2 add-ons. Switches in the cockpit don’t move when I change something like lights or battery on the physical controller or some systems don’t work at all due to some conflicts.
How is this possible, what am I doing wrong here? Are there no standards? Don’t they test? Why do 3rd party planes not support basic sim features?
I would return both if it was possible. Right now I just wasted 60 $
I have a Honeycomb Alpha and both the products you mention and have absolutely no issue with them. Using the default profile all the buttons on the yoke refer exactly to their in-game counterparts which move as they should in relation to the physical switch.
I can’t comment on VR as I don’t use it, but there’s nothing wrong with either product and their usage with the Alpha yoke.
3 Likes
Another VR user here.
Can’t speak about the Seneca as I don’t have it, but I have no issues in the JF Arrow and I fly it quite a bit in VR - I use a WMR headset from the 1st gen (a Dell Visor).
I have the Carenado M20R Ovation and have the same double-pointers in VR. Close your right eye. The pointer shown in your left eye is the correct one. It makes selecting things easier but I agree some of those switches are virtually impossible to select properly.
It’s such a disappointment that we have to do this. I tried to return the Carenado purchase after I bought it for exactly this reason. It’s incredible that the stadard planes don’t have this issue and the specially purchased aircraft does. Unfortunately I had no luck getting a refund. They have a monopoly on this software and you’re just stuck with no recourse when your purchase is poor. It certainly doesn’t motivate the developers to fix these issues. I sent a ticket to Carenado about this months ago with no change. I won’t be buying any more from them.
1 Like
I will investigate when I get some spare time again to play. I’ll start with disconnecting all my controllers and work up from there.
It’s an odd one that they’re not working.
Have you changed any of the bindings from the out-of-the-box state? I haven’t FWIW.
Of course I customized it a bit, but then again it works perfectly fine on the default aircraft.
That will probably be it then.
FWIW If I alter the default mapping then I save it as an individual profile for a specific aircraft.
If you revert to default you should find it works just fine.
I’ve read about the left eye thing, the problem is I’m physically unable to close just my right eye 
I can only blink with my left one.
Have the Arrow III and never had any of the issues you described.
That’s too bad about your eyes. Try to place the leftmost arrow over your target then.
I don’t really see 2 cursors, although sometimes it gets a bit blurry. It’s more like the 3d model is wrong and the cursor doesn’t correctly snap to the geometry. It’s like on a different plane +the clickspots arm to be the size of almost a single pixel sometimes.
This would mean that everyone had the problem but this is not the case, otherwise you’d see hundreds of complaints. I personally have to problem too but in every aircraft. I have the Oculus Rift and I am pretty sure it’s a setting issue on the user side. I can’t tell you what to do though as I haven’t figured it out yet myself. Some aircrat are affected more than others but I believe this is a focus problem. Some panels are further away from the eyes (viewpoint) than others.
Regarding your issues with the lights: Strobes and Taxi lights? Well the Arrow doesn’t have taxi lights but it’s those lights I have issues with in the sim, also in default aircraft like the DA40 and 62. If yes then that’s an Asobo problem. Don’t assign the yoke’s switches to lights on and off but to set and off. Then it works.
On the VR pointer control and double cursor issue - I use Index for this sim and find that how much I’m affected by this is directly proportional to how far the lenses are from my eyes.
The closer I wind the lenses, the better. Further away = double cursor. Can’t do much adjusting with a Rift or Quest, though - but you can do some with interfaces and pads. You can test it though, by trying it with no pad or pulling the headset away from your face - just to see if that is your issue or not.
PS - I would also try adjusting the IPD to see if it changes anything.