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.

Double entries for your display adapter in fsx.cfg

Featured Replies

Maybe this is old news but I didn't know about this and it had me a bit confused before I understood what was happening.

 

It started with I was going through my fsx.cfg file to check a couple of things and I then discovered 2 entries for my display adapter instead of the usual single entry. I had these

 

[DISPLAY.Device.NVIDIA GeForce GTX TITAN.0]
Mode=1920x1080x32
Anisotropic=1
AntiAlias=1
 
[DISPLAY.Device.NVIDIA GeForce GTX TITAN.0.0]
Mode=1920x1080x32
Anisotropic=1
AntiAlias=1
 
To me the second one called 0.0 felt like a double entry for the exact same graphics card so I decided to remove it. Next time I started FSX it looked like crap and I had lost all my AA and there was lots of shimmering. I then checked the Graphics tab in FSX and found the display adapter in fact had the same name as the entry I just removed from fsx.cfg and the AA and filtering settings were reset to default values. After I checked AA and chose a correct filtering mode everything was back to normal...puh...
 
I still couldn't let go of this wanted to know why I had two entries and after some testing I found that the first one is used when running FSX in DX9 mode and the second one is used running FSX in DX10 mode.
 
Mystery solved and thought I would share this finding if anyone else run into the same situation wondering what's happening. 
 

 

Hi Richard!

 

When you first ran DX10 - you used a brand new fg - you let FSX create it , then changed whichever settings, per the guides... right? At this point you would have only one display device entry - the "TITAN.0.0".  These two "0".s do indicate DX10, as you surmised. At some point, you switched back to DX9 for a test, perhaps - and at that time FSX found a new graphics driver api, and so that demanded a new pointer - hence "TITAN.0".

 

Wait till you hit 60, man... every day is a new day! <_<

 

All the Best,

 

pj


i7 [email protected] | 32GB RAM | EVGA RTX 3080Ti | Maximus Hero VII | 512GB 860 Pro | 512GB 850 Pro | 256GB 840 Pro | 2TB 860 QVO | 1TB 870 EVO | Seagate 3TB Cloud | EVGA 1000 GQ | Win10 Pro | EK Custom water cooling.

  • Author

:smile:

 

Ok, thanks for the further explanation behind these entries.

 

I decided to leave it like it is with both entries since I don't think that would do any harm.

Of course! It's not going to be used when running DX10, and vice-versa - that's why we have cfg files - right!

 

All the Best Richard,

 

pj


i7 [email protected] | 32GB RAM | EVGA RTX 3080Ti | Maximus Hero VII | 512GB 860 Pro | 512GB 850 Pro | 256GB 840 Pro | 2TB 860 QVO | 1TB 870 EVO | Seagate 3TB Cloud | EVGA 1000 GQ | Win10 Pro | EK Custom water cooling.

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.