Jump to content
Sign in to follow this  
tup61

Black screens... really... TIP!

Recommended Posts

The new update has introduced a nice new feature: FAILURES! Like black screens! "in rare occasions, Aircraft screens might not initialize correctly upon loading a flight. Please restart the flight to fix the issue." Well, I doubt they happen rarely because I've read about them already and the first flight I started in the TBM gave me black screens. Nice.

Tip: instead of restarting the flight (which takes ages) temporarily enable dev mode, switch planes, switch back again, disable dev mode and there you go. At least... it worked once for me so far.

Why does every update introduce new known issues, I wonder....

  • Like 1

Share this post


Link to post
Share on other sites

I believe only the NEO 320 developer version works? So that means I can't use my Thrustmaster Airbus throttle,because the detents only work with the fly by wire update, very frustrating.....

Edited by BIGSKY

Jim Driscoll, MSI Raider GE76 12UHS-607 17.3" Gaming Laptop Computer - Blue Intel Core i9 12th Gen 12900HK 1.8GHz Processor; NVIDIA GeForce RTX 3080 Ti 16GB GDDR6; 64GB DDR5-4800 RAM; Dual M2 2TB Solid State Drives.Driving a Sony KD-50X75, and KDL-48R470B @ 4k 3724x2094,MSFS 2020, 30 FPS on Ultra Settings.

Jorg/Asobo: “Weather is a core part of our simulator, and we will strive to make it as accurate as possible.”Also Jorg/Asobo: “We are going to limit the weather API to rain intensity only.”


 

Share this post


Link to post
Share on other sites
1 hour ago, tup61 said:

The new update has introduced a nice new feature: FAILURES! Like black screens! "in rare occasions, Aircraft screens might not initialize correctly upon loading a flight. Please restart the flight to fix the issue." Well, I doubt they happen rarely because I've read about them already and the first flight I started in the TBM gave me black screens. Nice.

Tip: instead of restarting the flight (which takes ages) temporarily enable dev mode, switch planes, switch back again, disable dev mode and there you go. At least... it worked once for me so far.

Why does every update introduce new known issues, I wonder....

If you have a conflicting mod, you can face black screens. In my case, copilot mod was conflicting and causing the black screens. Remove the mod.


Intel i7-9700K - Asus Nvidia RTX 2080 Super - 32 Gb Ram - SSD Drive - Win10 x64 - Samsung 43" 4K TV

Share this post


Link to post
Share on other sites

Thanks for reporting this and coming up with a tip for a work-around.  

Black Screens Matter. :biggrin:

  • Like 2

Call me Bob or Rob, I don't mind, but I prefer Rob.

I like to trick airline passengers into thinking I have my own swimming pool in my back yard by painting a large blue rectangle on my patio.

Intel 14900K in a Z790 motherboard with water cooling, RTX 4080, 32 GB 6000 CL30 DDR5 RAM, W11 and MSFS on Samsung 980 Pro NVME SSD's.  Core Isolation Off, Game Mode Off.

Share this post


Link to post
Share on other sites
2 hours ago, kt069 said:

If you have a conflicting mod, you can face black screens. In my case, copilot mod was conflicting and causing the black screens. Remove the mod.

No mods here. Never used any. Besides, I reinstalled Windows 10 and MSFS a week ago so... I have a very clean system. Never had black screen before and now twice in two flights.

Share this post


Link to post
Share on other sites

Hi All,
I have this "black screen" all the time in C172 Skyhawk.
In my case, restarting did not work.   Very frustrating.😢

KK


12700K@5.1Ghz, ASUS TUF GAMING Z690-PLUS WIFI D4, Noctua NH-U12S, G.SKILL 32GB Kit F4-3600C16D-32GTZNC Trident Z Neo RGB DDR4 3600MHz, SanDisk Extreme Pro SSD 1TB, Gigabyte RTX 1080 Ti, Cooler Master V750 Gold 750W PSU, Win10 Pro, Dell 24" 2408WFP 1920x1200 30 frames vSync to 60Hz, Fulcrum One Yoke,  MFG Crosswind V2 rudder pedal, Saitek Throttle Quadrant, Saitek Multi Panel, DIY Cessna 172 Radio stack (via Arduino/MobiFlight), Air manager V4 on 10" 1920x1080 monitor

Share this post


Link to post
Share on other sites

I had the same problem with the Daher930 and the Airbus Neo.

Then loaded the Baron58, where all panels worked without problems.

Afterwards i loaded the Daher930 again and the panels worked too.

That's a very strange behavior since the update

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...