Geddy_2112
Members
-
Joined
-
Last visited
-
Ya that's where I was heading but since I use it in Full screen I use the ForceFullScreenVSync=1 Tag. Glad you got it cleared up.
-
Nvidia Inspector is free http://www.guru3d.com/files-details/nvidia-inspector-download.html DX10 Fixer is $28.99 US http://sites.fastspring.com/stevesfsxanalysis/product/dx10sceneryfixer 2 additions that will change the look of your FSX. Also do you Sim full screen or Windowed?
-
Are you using DX10 Fixer & Nvidia Inspector as well?
-
Sounds like vsync, Knowing your specs will help of course. And also what your fsx.cfg looks like. Post those and I'm pretty sure we can get you fixed up.
-
Not to mention you also have two Display Device lines [DISPLAY.Device.NVIDIA GeForce GTX 560 Ti .0.0] AntiAlias=1 Mode=1920x1080x32 [DISPLAY.Device.NVIDIA GeForce GTX 560 Ti .0] Mode=1920x1080x32 TriLinear=1 Also, No way your 560 Ti will cope with TEXTURE_BANDWIDTH_MULT=120
-
Disable Collisions! Pretty much the safest way!
-
To each their own, Personally the dumbed down versions of Wilco drives me crazy. C'mon they're even using the default planner to import into the FMC? I like the BAe, I tolerate the 757. Far to simple. But then again, I'm a bass player and change my strings once a month!
-
From the looks of it this was close to today's routing, Seemed to use the NAT C ODN1B.ODN L975 VES L983 PETIL UL983 CUTEL UP16 NATEB UL602 TLA UN552 CBL MALOT NATC PORTI N112C ALLEX Q822 AJJAY.OOSHN3 https://www.flightradar24.com/SAS927/9a5e5c6
-
It's surreal to say the least, I'm also in Edmonton (and on the approach path for YEG, RWY20 actually) Glad everyone made it out. No reports of any casualties, which if you've been following the video footage is amazing in itself.
-
Alright fair enough, But still why only the one display seems to be doing it when the others don't ? Clarke Kruger
-
Sorry to Hijack this thread, but it's the closest thing to what I have a problem with. With my lights all set to control through the master and with all of them centered. The ND is always brightest and seems to be the only gauge that doesn't react to DX10 shadows, it's always bright! Any ideas or solutions? Current build is: 1.10.7025. Clarke Kruger
-
Check your Aircraft.cfg file.
-
Depends a lot on which addon you're referring to. PMDG! Expensive yes, Worth it, Absolutely!
-
Have you enabled VHF simulation? Have you configured your sound settings properly? not over modulated? I have troubles with a very few amount controllers not having there mics set at a proper distance (why does everyone think you need to swallow the mic?) But not to the extent you seem to be having, Maybe 1 in a 100.
-
AES is not compatible with FSX-SE!
