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.

The Mouse Ballet - An Encore

Featured Replies

I seem to have solved my mouse gyration problem, so if anyone in the tech team is looking at this, they can stop. I say seem because I've only had the chance of one flight with a new config. but it did work. Given that the issue only arose with the NG I did not look closely at my basic set up for some time. However, in desparation, I took a good look at my fs9.cfg file.As we know, when any changes are made to vid cards or drivers, a new entry is made in the .cfg file. I think this is supposed to be helpful and ease the process of rolling back drivers by 'remembering' settings etc. Not sure how helpful this is; I found that by editing some of the entries, I could make significant changes to the graphic images in the NG. Eventually I decided to completely rebuild the .cfg file on the basis of the nvidia 52.16 drivers. This I did and it worked.However this apparent solution presents a dilemma - well, two in fact. Firstly, why is it that only the NG was affected - I had no probs with any other plane, and one or two of them are fairly complex packages. Is it possible that the views of the NG are built in a manner which is significantly different from the normal run of MSFS planes?The second is another oddity. I should explain that my NG is the centre of a home cockpit. All of the switches, gauges etc are controlled by various pieces of hardware and interfaced using Key2Mouse. Taking the overhead as an example, all of the active clickspots are mapped, the appropriate x,y axis values being stored in a definition file. Prior to the mouse problem, all of the clickspots could be activated, with the exception of three. Whatever I tried, I could not get these three switches to work. Following my fs9.cfg changes, I expected that I would have to re-map the overhead. I did, grrrrrrhh. The oddity is that I did not have to re-map the three switches which previously did not work. These three now functioned perfectly - why???I realise that this probably doesn't make a lot of sense to anyone who hasn't played around with Key2Mouse, but this has got me stumped. I would appreciate an answer to the question posed above, tho' on the way the NG views are built.Bud

  • Commercial Member

Bud,Glad to hear you found the problem, Had me baffled :-lolThe FS.cfg file can be a very strange animal from what I have seen. RegardsPaul Gollnick :-coolTechnical Operations/Customer Operational SupportPrecision Manuals Development Groupwww.precisionmanuals.com

Paul Gollnick

Manager Customer/Technical Support

Precision Manuals Development Group

www.precisionmanuals.com

PMDG_NGX_Dev_Team.jpg

Paul,Thanks - is there any chance of getting an answer to the question I posed re building views. Bud

  • Commercial Member

Bud,Send me that request again to [email protected] Gollnick :-coolTechnical Operations/Customer Operational SupportPrecision Manuals Development Groupwww.precisionmanuals.com

Paul Gollnick

Manager Customer/Technical Support

Precision Manuals Development Group

www.precisionmanuals.com

PMDG_NGX_Dev_Team.jpg

Paul,Many thanks - on its way.Bud

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.