Hello guys, it is my first flight in the new version of the fenix and unfortunately i am having some issues in VR. Once i enter VR (i am using a Pimax Crystal) the autopilot wont react to my input as well as the MCDU (or FMC). Is this a known issue? i am not sure if it has to do with the Pimax? or with Fenix? is there a workaround?
Thanks in advance for support!
I have the same exact issue and have been pulling my hair out trying to resolve it for 2 days now. All the inputs work in normal 2D view but once in VR none of the panel inputs to MCDU the transponder or any glare screen alt etc. inputs respond. If you switch back and forth between external view they do catch up but it is impossible to fly like that. It has to be a Fenix issue as all my other versions of airliners including the FlybyWire A320 Neo function just fine. I too am using the Pimax Crystal. I have even re-installed the Fenix bird and to no avail…
I just submitted a Tech Support Ticket with Fenix and will feedback on their response
It’s weird because I haven’t found any other post mentioning this issue… I am now wondering what are other VR users experiencing! I just opened a Ticket at Fenix, let’s see what they reply, because at the moment it is not possible to fly it in VR…
This is strange. I use the HP Reverb G2 and it works perfectly with the new version on the Fenix A320. I also use the mouse for input and have not had any unusual things happening with that either.
I have to believe that there is probably a reason that something isn’t communicating here. I use the Valve Index and I’ve never had an issue with the Fenix in VR. I always use my mouse to control everything in the cockpit. I’m not familiar with the Pimax, but I know loads of people are using it so I wouldn’t expect it to be linked to that.
How is everyone attempting to manipulate the panel or MCDU (controller, mouse, etc)? And what cockpit interaction system (Lock vs Legacy) in settings in MSFS? Not promising I can help but these details might give someone else the chance to step in and help.
Yes I would assume is something like that. All my settings are standard, I am on modern flight model. Not using controllers but only mouse. All other aircraft works fine. Only with the fenix I am seeing this issue.
Just to give you an update, I got feedback from the Fenix Customer support. They requested me to install the previous version 146 to test if the issues are related to the new version or also the previous one. I will be installing it soon as see what happens…
Interesting, as I had no issues prior to the latest update. As regards add-ons are you using GSX Pro?
Fenix have just asked me to test v146 as well.
Strangely I do seem to remember flying one trip after the update which was OK, but now I can’t fathom why it lags so terribly.
As I said if you switch between external and internal views it will trigger the displays to update.
I have the Crystal and the Fenix V2. I only fly in VR. Everything is woking fine.
So you are one of kind! 
so is indeed working with Pimax. May I ask you, do you have any special addons running?
Yes I have GSX, it has always work good all the time. I updated this week my pimax to a new version. Do you have yours to the lastest update?
Are you running the lastest Pimax Version? I updated my on Monday, I am not sure if it has to do with that update…
Yes I am running the latest firmware, but it was working fine with the previous versions.
I have lots of add-ons but just the usual stuff, nothing special that I am aware of.
Just updated to latest Fenix but no change. Another user popped up on VRFlightsimGuy’s discord Pimax channel. Said he had no issue then last night it happened to him too. Pimax was the latest thing to change but all other aircraft are fine. Will now do the retrograde 146 install and re-check
yeah! i just noticed that a new version of fenix is available. I just install it, removed any other addon from the community folder and the problem continues unfortunately.
You are correct, the input done in the cockpit do catch up only going to the external view and back into the cockpit. But it is impossible to fly it like that.
I am now in the process of installing the version 146. I report back soon…
Did I try a clean install?
Fenix ​​leaves folders everywhere.
I recommend revo uninstaller portable.
i guess you have the same result as mine? in Version 146 VR is working fine. I will write back to Fenix about this findings. But now i dont know how to proceed. I guess the option if to maintain Version 146 until there are more information or feedback from others that might be experiencing the problems in VR…
146 installed and all good again. Definitely looks like a Fenix issue. will feedback to support and await an update
If it is a Fenix issue then they will need to address it, not the community. I am waiting for feedback from Tech Support and will assist them in any way I can to source the cause of this problem.
yes! i appreciate if we can keep us informed here as soon as new information in available 