8 hours ago, DANgerousFlyer said:

 

* I use VoiceAttack, and it works with more controls in the FBW than it does the Fenix. Perhaps most annoyingly, I can't control the altitude in the autopilot panel in the Fenix using VoiceAttack, but it works with FBW.

 

 

Weird because for me the push/pull functions with my Touch Controllers work fine with the default Asobo A320, but not with the FBW's knobs (still have to push/pull with mouse)

I can't get them to work with VR touch controllers to save my life....

Also are you using FENIX's CPU graphics resource assign option in VR?

If so do you see a major difference with the CPU graphics helping vs OFF?

Edited June 20, 20232 yr by blueshark747

12 hours ago, blueshark747 said:

Weird because for me the push/pull functions with my Touch Controllers work fine with the default Asobo A320, but not with the FBW's knobs (still have to push/pull with mouse)

I can't get them to work with VR touch controllers to save my life....

Also are you using FENIX's CPU graphics resource assign option in VR?

If so do you see a major difference with the CPU graphics helping vs OFF?

No comment on the controllers, as I only use the mouse and voice control for cockpit interaction. Longshot, but have you tried putting the control mode in "legacy" mode (I think it's in accessibility settings)? Once I did that I found it a lot easier to use the controls (with the mouse) in both planes. Whether that helps you with controllers or not I can't say but worth a look.

In the Fenix config I only get it to use the graphics card - I've got a 4090 which doesn't break a sweat no matter what, so I figured it was better than setting to CPU in the Fenix app. I was also hoping that my CPU wouldn't break a sweat as it's a 13900k... but no such luck! But I get very decent performance (relatively speaking) even with most of the details set on ultra.

A bit off topic, but I've found a sweet spot by using nVidia DLSS on quality mode in MSFS graphics settings, using OpenXR Tools to override the render scale much much higher than default, and setting sharpening to CAS 50% (no other settings changed). Using that combo, I get what I believe to be better visual fidelity and smoother performance than not using DLSS with temporal anti-aliasing. It took me a llloootttt of playing around to get to that point! I'm still CPU-bound though...

41 minutes ago, DANgerousFlyer said:

No comment on the controllers, as I only use the mouse and voice control for cockpit interaction. Longshot, but have you tried putting the control mode in "legacy" mode (I think it's in accessibility settings)? Once I did that I found it a lot easier to use the controls (with the mouse) in both planes. Whether that helps you with controllers or not I can't say but worth a look.

In the Fenix config I only get it to use the graphics card - I've got a 4090 which doesn't break a sweat no matter what, so I figured it was better than setting to CPU in the Fenix app. I was also hoping that my CPU wouldn't break a sweat as it's a 13900k... but no such luck! But I get very decent performance (relatively speaking) even with most of the details set on ultra.

A bit off topic, but I've found a sweet spot by using nVidia DLSS on quality mode in MSFS graphics settings, using OpenXR Tools to override the render scale much much higher than default, and setting sharpening to CAS 50% (no other settings changed). Using that combo, I get what I believe to be better visual fidelity and smoother performance than not using DLSS with temporal anti-aliasing. It took me a llloootttt of playing around to get to that point! I'm still CPU-bound though...

Wow! Your VR image must be stunning, as I'm still very impressed with this sim's visuals on my older 1080ti/8700k combo using mostly high settings in VR. I was hoping that 13900k allowed much more performance headroom, but yes OpenXR upscaling has worked wonders for me in VR. Gonna give legacy mode a try now and looks like I'll stick with the free FBW A320 over the FENIX.
Thanks!

 

Edited June 21, 20232 yr by blueshark747

It fun going down rabbit holes. One of the intersting comparisons between the FBW and Fenix is real world airlines that don't have the Neo, but do have the classic. Except in the case of jetBlue, whose a320s have IAE engines and not the CFMs on the Fenix. So, flying both a FBW and Fenix in the jetBlue livery is "wrong".

For now, am flying the FBW until v2 of the Fenix comes out. One other thing I like to fly are private jets, and the Airbus Business jets are Neos.

I catch V1 Sims streams. He's a real world Airbus captain. Somone brought up the differences in landings between the FBW and the Fenix. He mentioned that the FBW landing characteristics match what he sees on the real Neo.

There are things I generally like better about the NEOs, and some of that may change when v2 and the "IAE wen" are released. There are systems things in the Fenix I like more, though. It populates the missed approaches and I can set intersect waypoints from FIX.

It's really is a wash for me these days. I like both for different reasons.

On 2/17/2023 at 2:01 PM, Lucky38i said:

Yep, that’s entirely fair take. There’s a number of users just waiting for FINAL APP, it’s coming especially with advent of the monorepo move we’re getting close to cFMS v2

Just out of curiosity, how is this going? I saw there were a bunch of github commits. Are we still "close?"

On 6/26/2023 at 11:14 AM, BrammyH said:

It fun going down rabbit holes. One of the intersting comparisons between the FBW and Fenix is real world airlines that don't have the Neo, but do have the classic. Except in the case of jetBlue, whose a320s have IAE engines and not the CFMs on the Fenix. So, flying both a FBW and Fenix in the jetBlue livery is "wrong".

 

I am flying the Fenix A 320 in the Jet Blue livery in A Pilots LIfe V2.  It flies wonderfully.. Will I get sued?😉

2 minutes ago, Bobsk8 said:

I am flying the Fenix A 320 in the Jet Blue livery in A Pilots LIfe V2.  It flies wonderfully.. Will I get sued?

Only if the day ends in "y"

1 hour ago, BrammyH said:

Just out of curiosity, how is this going? I saw there were a bunch of github commits. Are we still "close?"

This kind of capability is live in the the A380 from a data/fms perspective but I can’t say about the 320.