If you guys could look into why FO cannot set altimeter correctly that would be great Fenix I haven't used other ac in a while, wonder if others are having the same problem.. as an example i tell him set altimeter to 30.00 he goes all over the place then leaves it a wrong (29.85 last time) setting and tells me to cross check LMAO 

Edited September 24, 20241 yr by AndyCYXU

6 hours ago, AndyCYXU said:

If you guys could look into why FO cannot set altimeter correctly that would be great Fenix I haven't used other ac in a while, wonder if others are having the same problem.. as an example i tell him set altimeter to 30.00 he goes all over the place then leaves it a wrong (29.85 last time) setting and tells me to cross check LMAO 

OK, will be looked at. 

There was a plane update very recently, so anything is possible.

 

4 hours ago, FS++ said:

OK, will be looked at. 

There was a plane update very recently, so anything is possible.

 

actually the recent fenix update made MCE and Google Maps Mod work together just fine, go figure but yeah the altimeter setting by my FO was not working for long time for me i just never bother posting about it not the end of the world just though I mention it.

any updates on this altimeter issue ?

18 hours ago, AndyCYXU said:

any updates on this altimeter issue ?

Sorry, couldn't replicate issue with latest Fenix version.

Just in case.. here are some of the commands you can use. Words between parenthesis optional

set qnh one zero two seven (millbars)

altimeter ten twenty seven.

barometer two nine nine seven (inches)

altimeter twenty nine decimal nine seven

set qnh twenty nine ninety seven

Although couldn't replicate, I'm not assuming the issue was fictive.

So, try the commands above, then confirm whether the issue is still there and tell me about your computer specs. 

For instance, with Fenix, those increments/decrements relative to current value have to be done with some delay between 2 rotations of the knob.

If you dial too fast, you could eventually overshoot. So it's a matter of finding the right balance between dialing speed and reliability.

This is why all dialing (including FCU HDG, SPD, ALT, VS with Fenix is slower than say with PMDG 737 or 777.

If anyone else having the issue, please chime in.

 

 

This is what is happening in Fenix when I ask him to set QNG, works fine with PMDG 738.

My PC is 13900KS + 4090 on Windows 11, DX11

 

On 10/6/2024 at 9:57 AM, AndyCYXU said:

This is what is happening in Fenix when I ask him to set QNG, works fine with PMDG 738.

My PC is 13900KS + 4090 on Windows 11, DX11

 

I notice saccadic increments/decrements as if they are held off, then bursting. I even see dialing happening before the switching from HPA to inHG which shouldn't happen as there is a delay of approximately 2 seconds before he starts dialing (to ensure Fenix gets the command to switch mode and get the latest value to increment/decrement relative to). It's not what I experience here (regular and spaced increment on a mid range PC.

Could you please leave Google map or whatever other add-on you mentioned earlier out of the picture to see if that is a factor?

Most add-ons usually assume they are the only ones there, will typically request MSFS to notify them every frame (when it's not always necessary), bombard FSUIPC with huge requests, possibly starving other add-ons of valuable CPU time or access to Simconnect or/and FSUIPC.

Just because it works doesn't mean it's running efficiently.

Again, if required adjustments will be made to MCE, but we don't want to change that until we get to the bottom of the issue. That's why other users input is desired in this case.

Others using Fenix + MCE, please confirm.

Thank you

On 10/7/2024 at 11:42 AM, FS++ said:

Again, if required adjustments will be made to MCE, but we don't want to change that until we get to the bottom of the issue. That's why other users input is desired in this case.

Others using Fenix + MCE, please confirm.

Thank you

Confirmed. I see the same behaviour as described and shown in the video (I always set the altimeter myself so I never bothered.).

good to know I am not the only one.. google maps was OFF just to limit the list of culprits, 

Just to clarify he only problems with altimeter, everything else he sets up correctly no issues, altitude heading radios etc.. all good ONLY ALTIMETER 

as i look at the video now seem he is going up in increments of 2 while when going down you can see it is dialing in decrements of 1

at the beginning of video starting QNH 1017  Target 1027   10 spins he went to 1037 20spins then he went down to 1035 ..

later in video when he is adjusting Hg he is going +2 every time then down -1..

well I will see if there is anything in my set up that could be causing it

no the end of the world but would be nice to see what is causing this and as FS++ says it is fine on his end.. so.. 🧐

Edited October 8, 20241 yr by AndyCYXU

20 hours ago, AndyCYXU said:

good to know I am not the only one.. google maps was OFF just to limit the list of culprits, 

Just to clarify he only problems with altimeter, everything else he sets up correctly no issues, altitude heading radios etc.. all good ONLY ALTIMETER 

as i look at the video now seem he is going up in increments of 2 while when going down you can see it is dialing in decrements of 1

at the beginning of video starting QNH 1017  Target 1027   10 spins he went to 1037 20spins then he went down to 1035 ..

later in video when he is adjusting Hg he is going +2 every time then down -1..

well I will see if there is anything in my set up that could be causing it

no the end of the world but would be nice to see what is causing this and as FS++ says it is fine on his end.. so.. 🧐

He's not incrementing twice.

Unlike other dials, with this one, he's handling both Captain AND Co-pilot Baro dialing simultaneously, with a delay between inc/dec for Captain and inc/dec for FO side.

Both you and Ralph are on very high-end machines and bug shows itself under specific conditions. On your PC, the command to rotate arrive too fast.

In any case this will need to be addresses as it's confirmed by at least 2 users.

We'll reduce the delay between inc/dec on Captain Side and FO side, then if necessary, we'll increase the delay between 2 consecutive inc/dec for Baro

We definitely noticed that without those delays you'll overshoot everything, including HDG, ALT, SPD. As said earlier, just a matter of finding the right balance between fast enough dialing and reliability.

There will be a patch tomorrow.

Edit: Maybe there is an option in Fenix plane where both dials are handled simultaneously (enabled on your side) which could cause the FO side dialing to be seen as a second click on left side.

 

Edited October 9, 20241 yr by FS++

4 hours ago, FS++ said:

...and Ralph are on very high-end machines 

 

Err... no... 8700K, 1080TI here.  Desperately waiting for hardware comparison tests with MSFS2024 to finally get a new PC...

 

@Andy and Ralph

Please checkout the new patch uploaded today (V3.1.0.4) and provide feedback. Thanks

Edited October 11, 20241 yr by FS++

ok, so the new version makes no difference, however the problem is SOLVED as per your suggestion in previous post 

Quote

Edit: Maybe there is an option in Fenix plane where both dials are handled simultaneously (enabled on your side) which could cause the FO side dialing to be seen as a second click on left side.

 

Fenix has 3 options for QNH settings in its EFB,   LINKED ; LINK L+R ; INDEP when set to INDEP it works OK, mine was set to LINKED so that is what caused it, changed it to INDEP now is OK.

 

Thanks

On 10/15/2024 at 2:17 AM, AndyCYXU said:

ok, so the new version makes no difference, however the problem is SOLVED as per your suggestion in previous post 

 

Fenix has 3 options for QNH settings in its EFB,   LINKED ; LINK L+R ; INDEP when set to INDEP it works OK, mine was set to LINKED so that is what caused it, changed it to INDEP now is OK.

 

Thanks

Thanks for the follow-up and glad to hear the root cause is now known.

Here is something that even users who have been using MCE for a decade aren't aware of.

With dials, with a few exceptions (some planes), on most planes, you can correct on the fly by simply saying "correction XXX"

Example:

You "set qnh ten fifteen"

Let's assume for some reason speech engine got "set qnh ten fifty".

You realize he's dialing the wrong one.

While he's still dialing, just say "correction ten fifteen" ,or "correction one zero one five".

He should pause right where he's at, then dial the correct value on the fly.

When he's done dialing you would need a new speech command.

This applies to FCU as well "set heading 350", "correction two fifty". SPD, HDG, ALT, you name it

The last thing you want is waiting for the FO to dial an incorrect value by mistake and then have to wait until he's done dialing before giving him the correct value.

If FO starts dialing something you didn't request, just say "cancel this" or "cancel that" and he should return the dial to its original value (assuming the command was given while he's still dialing).

Edited October 21, 20241 yr by FS++

The FCU commands don't work for me anymore with the current Fenix version (altitude commands, etc.).