by Greyman » Mon Jun 12, 2017 3:56 pm
My signature should cover the hardware bits of your questions and as my plugins currently stand, i currently have:-
Autogate - got black screen before i installed this one
DataRefEditor - don't really use, but it's in Resources\Plugins
FlyInsideXP - i'm not sure, but i'd guess this one might be involved
FlyWithLua - ageing memory could be flawed, but i am fairly sure i was getting black screen before installing this one
GndHandling - JAR Designs addon that comes with their A330 and was definitely getting BS before installing this
QPACTerrainData - i think this came with the FF 777, but either way, i was getting the BS before installing it
xmultithrottle - again, was getting BS before installing this one
XPLM.framework - absolutely no idea what this does, but might have something to do with xsquawkbox that i removed
XPWidgets.framework - as above
X-RAAS2 - was getting BS before installing this one
As for which planes i get the BS with, it is pretty much all of them from the Eclipse 550NG, Pipistrel Panthera, JD A320, JD A330, SSG 748-i, FF 767 and 777 Worldliner
As for addon scenery, i have 2 tiles of Ortho4XP, for the areas around Heathrow and East Midlands and freeware add-on scenery from MisterX6 for JFK, LAX, SFO and BOS. I have had BS well away from of all of these though, so i am fairly sure that it isn't these that are causing it.
You have probably thought of all of the following, but just in case, a seemingly crazy idea might actually help solve the problem.
Don't the work-arounds provide any clue as to the state that the graphics engine is getting into. For example, changing from HD to non-HD solves the problem, but if you change it back to HD again, the problem still persists. Also, if you move AA up whilst you have the headset off and then drop it to 0 again, where i generally have it, the problem appears to go away, albeit mainly temporarily. If Laminar could provide some clue as to what their code does when the user changes these settings, maybe it might explain why changing them gets it out of that state and hopefully how it might have got into that state in the first place.
For example, might there be an inadvertently changed/called directX flag/command that might cause the screen to be drawn in black, yet still allow you to see the various icons, pause, flight setup etc. in the top right of the Sim window?
Is it just Nvidia cards that suffer from BS, as it might just be their drivers that are flaky? It wouldn't be the first time. I have the latest drivers and have had this problem now for at least 3 iterations, so it wouldn't just be the latest version.
For me, at least, there don't appear to be any clues on my MSI afterburner screen, that i have running all the time, displaying GPU and CPU temps and fan speeds, GPU and CPU usage, GPU memory usage and system RAM usage.
Good Luck and let me know if you need any more detail.
ASUS Hero VIII Motherboard, I7-6700K, EVGA GTX1080FTW, 48GB RAM, Windows 10
Oculus Rift/Touch
Warthog HOTAS and MFG Crosswind pedals