The Livestream started. Jorg talks about the amount of updates over two years from release and what museums he visited. And now Q and A session starts. It appears helicopter questions have a priority over our issue.
Helicopter tutorials are coming.
The Livestream started. Jorg talks about the amount of updates over two years from release and what museums he visited. And now Q and A session starts. It appears helicopter questions have a priority over our issue.
Helicopter tutorials are coming.
Can u help me out . What am I supposed to look at exactly? What is so out of the ordinary here?
Thank you.
10 characters
Jorg: âYou know that we read the forumsâŠkeep the feedback on helicopters pleaseâ.
Seb says they are looking on Xbox downgrade. âConsoles have limited resources. The fix is going to come out in one of the future updatesâ. He doesnât sound positive on this issue.
Its not a bug folks, they cannot get frame rate under control. Maybe they will in the future.
Seb says that the problem stemmed from a protection on console that turns down LOD when framerate drops, but the frame rate detection was broken in a recent DirectX update. He says itâs âalready been fixedâ and will be pushed in some unknown update.
Most important: Sebastian just said IT WASNâT DELIBERATELY INTENTIONAL.
This is exactly opposite of what Seb said in the livestream. He said it was a non-intentional bug and it will be fixed in a future build as soon as possible.
Thanks,
MSFS Team
A system built into the engine is a bug?
And what about that frame rate protection?
Itâs gonna be a long long winterâŠâŠ
I think he said it was a bug within said system.
Fix mid January
The most interesting part of that answer (aside from it being surprisingly satisfying) to me is that the XBOX or the sim in general has an automatic LOD decrease when things get heavy. So our 500 post discussion about having a toggle was kind of moot because there already is something better than a toggle. Presumably if youâre in a complicated plane or airport the LOD will decrease by itself and was already doing it.
It was still a fun ride though I thoroughly enjoyed this thread.
Very odd decision to keep Xbox graphics this broken for months. Iâll be holding on all marketplace purchases over the holiday season as a result.
Iâve posted questions in the live Q&A which is on at the moment and they were answered! Itâs a bug and Mid Jan fix
Iâm amazed they saw my question but so glad we have an answer !
Itâs appear that an automatic setting on XBox was set to be too sensitive and is dialling down the detail - this is not an issue of XBox not being capable!
Is this since SU11?
Resolution of the issue planned for mid januaryâŠ
Thatâs just crazyâŠ![]()
![]()
![]()
Feel as a complete disrespect of Xbox usersâŠ
I think it existed before, it just got borked in recent work they did on DX12. Not sure though, just deducing based on what they said.
They didnât catch it during testing ? For what Reason we participate Beta and reporting issues and that they say we didnât catchend ? And on they other hand they say they reading the forum ?
Nevertheless they have a fix - which will be released not earlier mid of January 2023 if I get it correct,âŠâŠ
Thatâs disappointing. On one hand, Iâm glad they were able to identify the cause and implement a fix. But 2+ months to push down the patch? ![]()