Version: SU15 XBOX
Frequency: Consistently
Severity: High
Context: Any aircraft
Bug description:
Due to the improved model matching of SU15, the result is now customers on XBOX are experiencing an increase number of avionics black outs, this is because obviously as more airplanes payware or advanced are around the user, the memory starvation increases.
It appears XBOX users don;t have any option to enable / disabling model matching, and therefore they are stuck with the issue where inevitably they will ran out of memory when LOD0 are loaded on many of these advance aircraft since full textures will be loaded.
Repro steps:
Use FSR500, Cub, SR22, etc. with full traffic enabled in XBOX in an area where a lot of users are present .
Remakrs
We need to improve this situation, I think we should allow XBOX users to enable / disable model matching on their settings, or alternatively allow 3rd party developers to exclude our airplanes from model matching.
For example, I might want to have a special low poly airplane for FSR500 which should be used for model matching excluding anything else I deliver with the product, this for sure would help to keep memory consumption lower when my customers are in group flights helping with the overall experience. Unfortunately there is no way for us as 3rd party developers to enforce this or even prevent our products from being used as model matching.
I think the very least that could be done in the short term is to help XBOX consoles by allowing users on this platform to decided if they want full model matching or not.
All the best,
Raul
3 Likes
I wonder if the AI traffic tags in the .cfg file could help in limiting the available models. For example, we make AI variants for our planes starting with LOD2 and going down from there, which are only available as AI.
Update
It appears is not only the model matching, all my internal team is experiencing Avionics Black Outs with Xbox-S much more frequently than without SU15 even with all traffic set to OFF.
Xbox-X is more resilient, but Xbox-S is just not able to handle SU15 at all for any of our aircraft (Sting S4, FSR500), which are resulting in ABOs in any default airport, the behaviour can also be replicated using Xbox-S with many default airplanes, A320, Xcub, SR22, etc.
Maybe the new memory management is too aggressive now in shutting down coherent in comparison with SU14?
Best,
Raul
Hello @SimbolFSReborn
This is a known issue and will be addressed in a future SU15 flighting build.
Regards,
Sylvain
3 Likes
Hello Sylvain (@FlyingRaccoon),
Thank you so much for your help in this regard, and thank you very, very much for your efforts addressing issues with the sim. About this ABO issue, an user of mine on Discord reported issues at first with my EMB-110 aircraft on an Xbox Series X, in similar circumstances as reported by Raul (@SimbolFSReborn).
Apparently, with the SU15 beta, this has been partially solved, according to feedback from that user of mine. Below, I attach the issue initially reported by that user, and its feedback after re-testing with the SU15 flighting build on Xbox, so that you can check a bit more in depth. That user also reports the model matching being the “common denominator” of the problem, so I guess it’s something like Alex (@SWS-AlexVletsas) and Raul describe. The Discord user’s tag is blurred on the screenshots, for privacy protection reasons.
Anyway, hoping this issue can be resolved, and once again I appreciate your efforts!
Regards,
Carlos Gonzalez
NextGen Simulations
