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.

Minor bugs

Featured Replies

I believe I have found a couple of minor bugs in RC3 that you might be interested in knowing about. Both concern redefinition of keyboard shortcuts:1. On my Danish keyboard I have the character

  • Commercial Member

1) since i can't test every keyboard out there, maybe i should put in the documentation that US style keyboards only :-)2) ouch. i'll need to not allow spaces on keyboard re-definitions.

I don't mind too much if my keyboard acts like a US American one. Most American produced games behave like that. FS2002 is a brilliant exception to this trend, though.The real problem is that when I define my keys, my input is processed through the DA keyboard layout that I use, and so it is when the key to press is printed in AdvDisp. But when I press that key, the input appears to be passed through another table or based on hardware codes.Hmm, just had thought. If I enter the character placed unshifted on that key on a US keyboard, maybe it'll work. I believe there's an Accent Grave (`) to the left of the One (1) key, right?

Henrik,>Hmm, just had thought. If I enter the character placed unshifted on that key on a US keyboard, maybe it'll work. I believe there's an Accent Grave (`) to the left of the One (1) key, right?Correct, and definitely don't use the shifted key in the input field. Use the "Shift" checkbox. Rc does, as you point out, read the direct key codes.Keep us posted.

Okay, I've now tested my theory, but much to my surprise, it failed.Here's what I did:I opened RC3's key configuration window and entered an Accent Grave (`) for Acknowledge. I made sure the shift and ctrl check boxes were blank. The number next to the line was 192. I should mention that I went as far as changing my keyboard layout in the Control Panel to US English so I could hit the button I wanted, i.e. the one next to the One (1) key, rather than relying on me knowing which key to press on a Danish keyboard. (It didn't seem to make any difference, I got 192 with either method.)Then I exited RC and started FS2002. When I was in the cockpit, I started RC3 again and loaded a plan, etc. I made sure to untick Pilot Autoreply. Everything seemed normal, and when I came to the first incident where acknowledgment was required, I saw the (`) character next to the Acknowledge line as I expected. But to my disappointment, nothing happened when I pressed the key.I have checked that nothing is assigned to that key in FS2002.

Henrik,The best I can think of is that since the grave is what opens the ATC window, that it may be not getting to FSUIPC. Check your FS key assignments and see if there's something else confligting if it's not set to open the ATC window.

I already did check that. If I try in FS2002 to assign that key (which is (

Update:A quick test reveals that this is indeed a general problem. Two other keys (

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.