Jump to content
The simFlight Network Forums

Issue with Key Assignment and Fenix A320 presets


ricky74

Recommended Posts

Hi,

I was trying ti assign HEADING INC and DEC to key combo CTRL+SHIFT+Q and CTRL+SHIFT+W via FSUIPC and Select for Preset function with Mobifly (see attached screen) but it doesn't work.

I remeber that last week I've assigne this command without no problem and worked perfectly. Then I deleted all Key assignment because I wanted to renew all command for my specific needs. So today I repeat the steps to assign Preset function but it doesn't work. Any solution?

 

Capture.PNG

Link to comment
Share on other sites

Can you please attach your files and not screenshots. I need yo see your FSUIPC7.ini and FSUIPC7.log files, the latter generated with logging for Buttons & Keys and Events activated: start MSFS and FSUIPC7, activate the logging (Log->Buttons & Keys, Log->Events), load your aircraft, test the assignment then exit FSUIPC7 and attach those files.

John

Link to comment
Share on other sites

Hi John, problem solved. I restart the sim and works perfectly.

But if you want I can attach or copy the FSUIPC.ini file, but the .log where is? Do you want I attach here or copy as text?

 

 

Link to comment
Share on other sites

No need to attach if it is now working.

However. you should not need to restart for this to work, If you find that key assignments are not working, exit FSUIPC7 and then attach the log file. The log file is in the same place as the ini, in your FSUIPC7 installation folder. If you can't see it, you have Windows Explorer set to hide the extension of known file types.

There does seem to be an ongoing issue where key presses are sometimes not being sent from MSFS to FSUIPC7. If this happens, you can try disconnecting and re-connecting to MSFS (using FSUIPC7's MSFS menu) or restarting FSUIPC7. This also seems to be due to the timing of when FSUIPC7 connects to MSFS when auto-started, so you can also try increasing the DetectToConnectDelayAuto ini parameter by 5 (seconds) or so.

Edited by John Dowson
ini parameter name corrected, keep = key
Link to comment
Share on other sites

  • 2 weeks later...
On 8/12/2024 at 6:36 PM, John Dowson said:

There does seem to be an ongoing issue where keep presses are sometimes not being sent from MSFS to FSUIPC7. If this happens, you can try disconnecting and re-connecting to MSFS (using FSUIPC7's MSFS menu) or restarting FSUIPC7. This also seems to be due to the timing of when FSUIPC7 connects to MSFS when auto-started, so you can also try increasing the DetectToConnectDelayAuto ini parameter by 5 (seconds) or so.

I presume you mean >key presses<?

For some reason I have this quite regularly (not always) since not long ago. Key presses don't trigger their assigned actions. After a restart of FSUIPC, everything is working as intended again. I will increase the delay as you suggest. The delay is 85 right now, and I guess the value comes from auto tuning, because I can't remember setting something up myself.

Link to comment
Share on other sites

13 hours ago, NovemberUniform said:

I presume you mean >key presses<?

Yes - corrected.

13 hours ago, NovemberUniform said:

For some reason I have this quite regularly (not always) since not long ago. Key presses don't trigger their assigned actions. After a restart of FSUIPC, everything is working as intended again. I will increase the delay as you suggest. The delay is 85 right now, and I guess the value comes from auto tuning, because I can't remember setting something up myself.

I have also delayed the request of keys from MSFS to prevent this issue (or to at least make it less likely to occur) in the next release. I have attached a beta with this update below if you would like to try it. With this version, you should be able to keep the delay at 85, although there should also be no issue increasing this slightly.

John

FSUIPC7.exe

Link to comment
Share on other sites

6 hours ago, John Dowson said:

I have attached a beta with this update below if you would like to try it. With this version, you should be able to keep the delay at 85, although there should also be no issue increasing this slightly.

Thanks, John!

I may be able to test the beta later in the week. I'm occupied with work, unfortunately.

Link to comment
Share on other sites

  • 2 weeks later...
On 8/27/2024 at 10:38 AM, John Dowson said:

Yes - corrected.

I have also delayed the request of keys from MSFS to prevent this issue (or to at least make it less likely to occur) in the next release. I have attached a beta with this update below if you would like to try it. With this version, you should be able to keep the delay at 85, although there should also be no issue increasing this slightly.

John

FSUIPC7.exe 664 kB · 2 downloads

Hi John, just to let you know,

in the meantime, I think I loaded four to five flights and on all flights the keys did work with your provided beta. This looks promising. Thank you!

Link to comment
Share on other sites

2 hours ago, NovemberUniform said:

in the meantime, I think I loaded four to five flights and on all flights the keys did work with your provided beta. This looks promising. Thank you!

Thanks for the update. Note that this fix has now been released in the latest version of FSUIPC7, v7,4,17.

John

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.