Video quality washout after clicking "Takeoff" in mission planner screen
-
Hi,
After clicking “takeoff” on the mission planner screen, the splash page with the parked jet appears very bright and washed out. Next, when I enter the 3D world, most of the video looks good above and below the horizon, but anywhere near the horizon is way too bright - totally white. This means I can’t see the HUD symbology no matter how bright I turn it up. Also, when exiting the cockpit, there is a screen that says “Exiting the Aircraft - Standby” that is also overly bright with the color washed out. Other screens like mission planner have NO COLOR PROBLEMS at all.
I suspect there is a different graphics “mode” (Direct X ?) that is used for the cockpit. The problem only happens when BMS is using that mode.
Can anyone clue me in here?
Many thanks for any help you can give me!
-
without knowing your setup or rig, it might be an idea to check in the Configuration editor that is in the boot menu and check the lighting is set to “Per Pixel” and not on “Per Vertex”, the later causes the darkest colour on the vertical strip to take over the brightness of the rest of the vertical strip and so on across the screen. Seeems funny how it only does it in the loading screen prior to take off. Give it a try and see what happens.
-
Thanks for your reply! I changed the lighting effects from per vertex to per pixel and it had no effect.
The problem happens in only 3 places -
1. Immediately before entering the cockpit - the image with the parked jet and the status bar on the bottom is very bright and washed out
2. Inside the cockpit - the horizon is a thick white stripe that washes out the HUD completely. I can’t see the HUD unless I nose up or down 20 degrees or so.
3. After exiting the cockpit - there is a screen that says “exiting the aircraft - standby” This is very bright and washed out also.Rig Specs - Asus Z-170A MoBo / Intel i5-7600K 3.8GHz CPU / 16G DDR4-3600 RAM / NVIDIA 1060 6GB Graphics / SSD storage / Thrustmaster T16 FCS HOTAS
-
Fixed!
Nvidia had me update my drivers and that of course corrected the problem. I assumed that my drivers were fresh because I had checked the box to allow auto update, but I guess that didn’t happen.
All’s well that ends well!