On Xbox, there is no way to adjust game resolution. Regardless of what TV the consoles are connected to, Xbox Series S runs Flight Simulator in 1080p and Series X in 1440p. This is later upscaled to 4K if a 4K screen is connected, or downscaled to 1080p if one’s TV is 1080p, but the internal resolution and therefore performance remains the same. The console versions of MSFS, on the other hand, use dynamic graphics settings, which means the game constantly adjusts things like draw distance and texture resolution in order to keep the target framerate (30 fps) stable. Needless to say it’s often not enough, but still good enough to keep the game playable in most instances.
Unfortunately, there are add-ons like scenery or aircraft that are just too resource-hungry (either CPU, GPU or memory), and therefore tank performance on consoles, like the A220 currently.
Hm, that’s pretty crazy actually. I’m on a PC that is a lot more powerful than a Series X but I still keep my resolution at 1080p in order to keep the framerate up. I much prefer to have a higher LOD, draw distance etc. instead of a super high resolution. But I guess the ability to adjust and customize is the reason I sim on a PC to begin with.
Do you have ‘AT/AP Disconnect Protection’ set to YES in the EFB Settings page? If not, the A/T will disconnect every time it thinks you have moved the throttles. In my experience, you don’t even need to move the throttle to cause this, for example I had a Logitech wireless mouse , which would go into sleep mode after a bit of time, and as soon as it was moved after sleep mode, the sim would act as if a new peripheral was added, and as far as I can tell, MSFS polls all of the peripherals when a new one is added, if your hardware throttles are not in exactly the right position they will be moved in the AC to where it detects them on the hardware, thus cutting off autothrottle.
Yes the Perf/TO warning has to do with bleed settings, if you have set the takeoff page to use engine bleeds, and the APU is still on this message will come up. I assume it also comes up if you have set APU bleed in the takeoff page, and the engine bleeds are still on. Don’t know if it checks trim and flaps also, but it doesn’t seem to notice if RTO is selected or not.
There’s a bug reported by real A220 pilots where, just before touchdown, between 3-2 feet above the runway, the aircraft unexpectedly pitches up, leaving the user no time to react and causing the main gears to slam into the ground, ruining the landing. It’s as if the aircraft is flaring on its own, on top of the flare the user is already doing.
This is not how the real A220 behaves and may explain the difficulty in achieving a soft landing with Synaptic A220.
I will check but I think that’s a very likely possibility. I have the WinCtrl throttle quadrant which is the only hardware mapped to the throttles.
Nice one thanks
edit: Just checked and unfortunately I already have it set to yes. I have the side buttons on the throttles mapped to A/T disconnect, I’ll try unmapping those just in case they’re sending some spurious signal. Thanks anyway
On the Synaptic Discord, there are 3-4 threads where people are reporting this issue, and I saw comments from at least two users claiming to be A220 pilots who say this isn’t how the real aircraft behaves.
Still having flap issues on landing. They will visibly deploy to only 3, while the MFD indicates the full 5. Then after landing/rollout, they’ll finally visibly deploy to 5. However if I spawn on the runway, ready to go, and do a circuit or two, they deploy properly. Not a binding issue, therefore; I can only think I’m missing something but I’ve watched a couple of tutorials and am not doing anything differently.
Anyone else’s flaps constantly stuck at 2 on the partial HUD in exterior view?
I saw the flare up behavior live on Edward’s stream (their A220 test pilot) on the launch day (or day before) stream. He was really confused as to what happened.
The preliminary changelog for update 1.0.4, to be released next Tuesday, mentions the display texture size has been reduced by roughly 40% by removing wasted space.
This change alone is expected to bring a significant performance improvement, as less VRAM will be used by the displays and less time will be taken in the graphics queue thread.
To help us quickly diagnose and fix issues, we implemented Sentry on the Synaptic A220 to assist with development and testing. Sentry is a self-hosted software platform that provides telemetry and release health monitoring capabilities.
We integrated the Sentry SDK into the Synaptic A220 avionics code to help us capture diagnostic information when users experience issues such as:
WASM crashes
MFW soft crashes
Other runtime errors
When a crash occurs, Sentry allows us to see the exact line of code that triggered the issue. This is incredibly valuable for the programming team to quickly turnaround issues and push out patches quicker than conventional workflows where the developer will try and reproduce the issue to eventually fix it.
Without it, we are often left guessing at potential causes or relying on users to manually retrieve developer logs. Sentry also tracks session health (via “heartbeat” pings) so we can compare aircraft versions and measure stability improvements between releases.
We have changed how this works from initial release, and we’d like to detail how things will be going forward.
Can iniBuilds can use this to chase WASM crashes for their other aircraft ?
Can iniBuilds can use this to chase WASM crashes for their other aircraft