
-
Posts
6,084 -
Joined
-
Last visited
-
Donations
0.00 USD
Community Answers
-
Paul J's post in Single Monitor, No Vsync Fixer 2.0 was marked as the answer
Do you have "DisablePreload=1" in the [Main] section of the fsx.cfg, Joe? B)
All the Best,
pj
-
Paul J's post in Anyone know what this is or what caused it? was marked as the answer
You have your "Thermals" turned on. These are to help soaring pilots locate them.
Set it in your fsx.cfg [Panels] section: "0" means Off and a "1" means ..... what you are seeing - ok!
THERMAL_VISUALS=0
OR:-
Set it in your FSX -> Settings -> Weather -> Thermal Visualizations. Set it to "None"
All the Best,
pj
-
Paul J's post in D3D9.dll enb issue was marked as the answer
Duh! ... it's on the page right after the Copyright, Credits, Support & Beta Testers page. It doesn't have a number and I don't look at it unless asked!
There's an acronym for this somewhere.... something like R-T- er.. something - something... :lol:
-
Paul J's post in DX10 & FSX Instability was marked as the answer
Do we have the fix for you!!
This is a Microsoft issue, as a result of their constant barrage of "You should install this update" messages.
Open up your Windows Update history and look for KB2670838, and uninstall it. Done.
-
Paul J's post in PMDG737ngx Instument Panel Issue was marked as the answer
Ok, Paul. Can you switch the TV out of the picture, please and just use the 24" LG as the FSX monitor. Bear with me. If this is giving the same pic in DX9, then it's not the configs or DX10.
Let's see how it looks with a pukka monitor. Thanks for your patience.
pj
-
Paul J's post in PMDG 777 and DX10 was marked as the answer
Those blue textures look suspiciously as if the bkg.bmp is not in place. Can you check if it's installed (Bonus folder of the patch) - it goes in the FSX root folder.
I don't know why it would make any difference - or even be used by PMDG - but stranger things have happened.
-
Paul J's post in Word of caution for those getting the PMDG 777 was marked as the answer
Hey, Trey - go into your Shaders cache folder and delete the "Shaders10" folder, FSX will re-create this on the next startup.
It's located in your "C:\Users\[your username here}\AppData\Local\Microsoft\FSX\" folder.
This may or may not be the cause - but it can cause this symptom if there's been a change made in the ShadersHLSL folder without rebuilding the cache. OK?
pj