For those folks experiencing more than usual black screens, please try again in the build just released and report back.
1 Like
Quick impressions of 1.37.4.0.
I havenāt had time to make long flights yet. Iāve tried the Cirrus SR22T and the screens work now, they turn on and stay turned on as well, at least for the last half hour. Havenāt had the chance to try airliners yet but Iām hopeful it will be ok now.
However: the glass cockpit screens update at an insanely low framerate now, even lower than before, itās like 5 fps. I mean, I could literally count 5 frames per second with a stopwatch. Itās a slideshow now on Xbox (Series X), which is extremely jarring even in normal flight, but during takeoff and landing itās just a terrible sight and makes it very hard to finely control the aircraft.
2 Likes
There will be more changes to that in a future update.
3 Likes
I tried the Boeing 787-10. Unfortunately, it still doesnāt seem usable.
I spawned ācold and darkā at a medium sized airport. At first it seemed OK, performance was relatively acceptable and the screens powered up as they should. However, while setting up the flight, the moment I turned the beacon light on, all screens turned black and came back immediately (after a big stutter), but everything from the FMC was deleted. After this, there were long stutters all the time and I just couldnāt continue preparing for the flight.
New build 1.37.4.0 on Xbox series X - NO rolling cache -
TL DR: Black screens still happens.
As always my testing place is Asobo PADERBORN custom airport on the A310. This combination is the biggest load on the sim that I can test.
Start cold & dark at gate 6, configure the plane for takeoff and landing at the same airport. Pushback and taxi.
I tried everything possible to make a black screen occur: switch to the outside camera, back inside, several times, pan on the outside camera to the airportā¦ no problem.
Line up and take off. Completely smooth, no problems, camera in and out, no black screens. I flew around the area, always trying to force overload (and black screens) by changing cameras and nothing.
Direct to the IAF for an ILS approach and decided to make a visual approach and landed. I was very happy with the results so far, until I started to notice some stuttering while taxiing to the gates.
The stutters became more noticeable but I was still able to align with the gate. APU running and turned off the engines, asked for gate connection, chokes and GPU.
At this moment switch to the outside camera and back to the inside, black screens.
1 Like
EDDK to EDFH (stock Asobo) in the ATR 72 600 this afternoon, using flight plan created in SimBrief. I had everything live (weather, traffic, etc.).
Jumped outside of the airplane plane at the gate before doing anything and panned around for a bit. Upon jumping back into the aircraft started to get slight stuttering.
Proceeded to set up aircraft, import flight plan and go through my usual flows. Once I was done and after requesting taxi clearance I opened the VFR map for taxing guidance and instantly got BS and had to restart flight. On restart EFB was BS and couldnāt proceed further.
Exited MSFS after deleting rolling cache and restarted Xbox S and then repeated the set up as above. This time I opened the VFR map before doing anything else then shut it down again and after setup flows I was able to taxi to the gate opening and shutting the VFR map with no issues.
No further BS incidents during the fight, some issues with tiles loading slower in external view but good flight all the way to the tarmac at EDFH.
My only complaint, albeit related to the ATR and not the Beta I think, is the transition from air to ground with the rudder being too sensitive and nearly impossible to transition without zig zagging when landing with a slight cross wind. I thought I had sorted this in the last version of the Beta by adjusting my rudder sensitivity but it looks like this update has thrown that out.
Same old problems for me on the new version of beta, black screens on startup with the PMDG and loads of stuttering that is not present in SU14. Had to go back once again to 14! I tried several restarts and cleared the rolling cache. I was using EGBB add on airport which is normally very smooth and stable for me.
Xbox X:
A310, BS after spawning on custom EPKK (Drzewiecki Desing).
Few second later everything is ok.
Then full cold and dark procedure, taxing and BS again. I need to take off blind.
Few miles later BS off and everything is ok.
I just tried to fly from LFPB airport in the Cirrus SR22T and the screens donāt even turn on. The simulator is just not playable on Xbox in the current state. If even light GA aircraft canāt be used, what do we expect of big airliners?
1 Like
My second attempt:
Alternate link if the first one doesnāt work:
Update: 1.37.5.0 doesnāt improve at all. All the above still apply.
1 Like
Did you try this dumping third party adds, particularly sim-wide scenery/textures/lights? And are you using live traffic? My MSFS is pretty darn smooth and itās 400gb on xbsx. Most of my issues were a few problem add ons. Mo rolling cache or live traffic though.
And if your tv supports it try 120hz vrr, seems to be better about bullying through ABOās and hella smoother. Other than the opening cinematics being borked if youāre in no hurry to push a button to start itās a big boost now.
We seeing really bad performance on Xbox S with SU15 vs SU14, lots of ABOs.
Xbox-X seems to be able to handle SU15 better.
R.
Do you have the same issue if you follow the OPās steps to reproduce it?
Just fly a 2 hour flight and screens go black during initial descent for IAP initiation.
Provide extra information to complete the original description of the issue:
Screens go black and I canāt reduce or increase thrust after screens go black
Are you using DX11 or DX12?
No
Are you using DLSS?
No
If relevant, provide additional screenshots/video:
On Xbox Series X (1.37.5.0): In āheavy load scenariosā (London TIN city, ORBX London City Airport extension, Citation Longitude with Garmin 5000) I experienced heavy stutters and also black glass cockpit screens with long recovery time. I suggest these problems are still related to memory issues on the console.