Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Key press not recognized

Featured Replies

OK I have reinstalled RC 4.3 a number of times due to this issue but it keeps comming back. RC 4.3 will work fine for awhile then all of a sudden it will stop responding to key presses. Then no matter what I do, change keys, update FSUICP, ect nothing short of a complete reinstall seems to help.

 

Nothing is stealing the keys they just don't make it to RC 4.

 

Thank you,

Make sure:

1. RC is started with a shortcut property set to run as admin.

2. Make sure RC is excluded (bypassed in) all of your security applications. If you alt-tab does a covered error message pop up? Read the error 75 pinned topic even if you do not see it..

3. Does this happen with a default aircraft with just RC and FS running?

4. If FSX and using lots of apps and specifically if RC is on WideFS client to an FSX host, the windows messaging paths can really get clogged in some instances.

  • Author

Make sure:

1. RC is started with a shortcut property set to run as admin.

2. Make sure RC is excluded (bypassed in) all of your security applications. If you alt-tab does a covered error message pop up? Read the error 75 pinned topic even if you do not see it..

3. Does this happen with a default aircraft with just RC and FS running?

4. If FSX and using lots of apps and specifically if RC is on WideFS client to an FSX host, the windows messaging paths can really get clogged in some instances.

 

1. I have had it that way since the begining.

2. Checked, no error 75 or hidden error messages

3. Yes

4. But, usually this delay's keystrokes.

 

I have searched various forums and google. RC will work just great then it will not accept key strokes. Today reinstalling FSUIPC brought it back to life, saving me yet another reinstall. I also removed FSRecorder as it has seemed to cause problems since installing.

 

Thank you,

  • Commercial Member

make sure fs is running, not at a menu, or a flight selection, or an aircraft selection screen. but at the gate, clock ticking on the panel, when you click the start rc button

 

the other possibility is, another program or add on is using the same key. disable other addons, use a stock ms plane, see if the key works

 

if all else fails, make a log, instructions pinned to the top of the forum

 

jd

Hi!

 

Are you using more then one monitor? If so it can be you have been doing something on the second monitor with the mouse and then the monitor where you have your RC window is "not active". If that is the case, just click with the mouse somewhere in the the monitor where you have your RC window and then the keystrokes should work fine again. I normaly run the VC panel (incl the RC window) on my main monitor and pop-ups like FMC, overhead etc on a second monitor and often got this problem if have been setting or changing something on the panels on my second monitor.

 

Reagards

Johnny Holmgren

Johnny Holmgren

 

Banner_FS2Crew_NGX_Driver.jpg

When you click in the window where the RC menu displays, be sure you do not click on the RC menu/status window it self. It is the FS window that needs to be active so keystrokes are passed to RC.

  • Author

Thank you,

 

I reinstalled FSUIPC and that seemed to fix it for now. I'll report back if/when it dumps keypresses again.

 

I only use one monitor, and I make sure that FSX window is active. It is like something is getting in the way of RC4 from getting the keystroke and it does not matter if it is an add-on or default aircraft.

When RC is not receiving keystrokes can you alt-tab to bring up the RC main window and quit out of it? That is just a test to see if it is still running. Also FS should be set not to pause on task switch.

 

In addition after this occurrence and you close FS go to your modules folder and look at fsuipc.log. It is set in its basic mode but see if there is something unusual in there where RC terminated unexpectedly (except for the forced shutdown) or anything unusual. Save by renaming a few of those fsuipc.logs for comparison with a normal and troublesome flight.

 

In that log you'll see two fs flights loaded for that session. The first is a default flight always loaded by FS to intialize it even before its menus appear. the second is your selected flight. That is normal.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.