All Activity

Can you show your graphics settings? Also, what's your VRAM amount installed in your PC machine?

Hi, This is a great suggestion! I’ve made note of it and will pass it along to the team for future consideration and evaluation. Thank you!

Hi, Thank you for the feedback and for attaching a video demonstrating the issue. I personally haven’t encountered this myself, but I’ll make sure to pass it along to the team for further evaluation. Thank you!

You are correct. It's some weird limitation issue within GSX itself. I'll keep this thread updated when/if we get a response from the GSX team. Thanks!

Hi, While I understand your frustration, as another user mentioned, this is a “default” aircraft. This may be better suited for the MSFS forums, as ultimately, the decision to release a paint kit to the community would be up to Microsoft/Asobo. Thanks for your understanding!

Hi, I’m sorry to hear that your experience so far has been less than ideal. While Synaptic continues to update and improve the aircraft, we’re hopeful that the upcoming updates will bring significant performance improvements. Thank you for your patience and understanding!

Hi, I just tested this myself and had no issues. Looking back at your video, it appears that you had the incorrect LOC frequency set. Thanks!

As if update 1.4 performance has got better but as soon as i start to taxi or fly it just stutters to the point where i cant do anything i feel like i wasted $70 i have just about every high fidelity aircraft in 2020and never have issues with any of them fenix inibuild pmdg all of it is great i have amd all amd systems i have tried lowering graphics and traffic cut out gsx everything possible and its just horrible it just feels like it will never be flyable for me unfortunately

@mstlc03 Not really, if you read my deep dive linked above it appears that as older sceneries made in the 2020 SDK are ported over into 2024...which has a much more evolved SDK, misnamed and duplicative texture files conflict with each other, especially if they are stored in a universal library to be used across multiple sceneries. This criss-crossing of texture files across two different SDKs does not translate well in the 2024 engine and that's why you see PINK or mismatched objects like you see in my linked post above. The only solution is a meticulous culling and updating of older texture files in the 2024 SDK or the removal of the older ones ported over from 2020 to eliminate the criss-crossing errors. At this stage, this is no easy feat and would likely be someone's full-time assignment for some time given the amount of iniSceneries that are out there and how many textures were brought over from 2020-built sceneries...KLAX, KJFK, KDTW just to name a few... --Nick N. DAL KRDU

Lack of paintkit as is the way with all default aircraft. Truly pitiful decision somewhere (likely MS/Asobo) that really doesn't help to sell the aircraft like it could

One issue I found is that if GSX places the plane where it wants it. All the way forward on the stop yellow taxi stop line. Which is fine except the Multi Jetway tool wont be able to reach, says door 1L is too close. But if it worked then I am pretty sure the bus wont arrive as it wont be called by GSX. Because pretty sure GSX calls the bus as a backup command when plane is not parked properly all the way forward. Only way I managed to get the two jetways to hook up to the plane as shown on screenshots above is to slew plane tiny bit back. Then Multi jetway tool via EFB is happy and connects. But then bus arrives when I decide to board via GSX and go up the back door 4L again. Only thing I can to have no bus and jetway is to let GSX park where it wants the plane then do boarding via only one jetway. But then the whole point with dual jetway kind of falls apart. Again, looking forward to the solution to this issue. I flew the flight anyway but with empty cabin back to Madrid :)

Thanks for the update, looking forward to when this is solved.

Hi Bert, It would appear that you may have the default Asobo Heathrow installed rather than the iniBuilds version. Please make sure to disable the default Heathrow through the Marketplace and ensure that the iniBuilds version is installed and enabled. I’ve attached screenshots showing what I’m seeing on my side for reference. Thanks!

Hi Del, This is the first time I’ve seen this issue reported. If you’re able to, I’d suggest joining the Synaptic Discord, where their team may be able to provide some additional troubleshooting tips. Thanks!

Hi, Thank you very much for the suggestion! We’re glad to hear you’re enjoying the aircraft. I’ll pass this along to the art team for further investigation and consideration. Thanks again!

Hi everyone, Thanks for providing your feedback. As we are the not the primary developer of the Synaptic A220, I would kindly ask you all to contact Synaptic on their discord if you continue to have issues. Thanks so much!

Hi, Thank you for the suggestions! I’ll pass them along to the team for future consideration and evaluation. Thanks again!

Hi, Thank you for taking the time to provide your feedback; we really appreciate your support! I’ll forward this to the team for further investigation and consideration. Thanks again!

Hi, Unfortunately, this appears to be a limitation/issue with GSX. We have reached out to Umberto for further clarification on why and how this is occurring, as we have done everything possible with the tools currently available to us. Thank you for your understanding. Please know that we are actively working to improve the jetway tool and provide the best experience possible.

Hello, I've noted your issues and have forwarded them to the team for further investigation. Thanks for your patience.

Hello all here! While beta testing an upcomming innovative moving map solution I saw that some parking positions at EGLL for MSFS 2024 are missing or showing wrong numbers: 213: 213L is missing as sign at the yellow taxi line. 218: 217L should read 218R. 303: The 303 sign is showing 301. Thanks for an update - cheers! Bert FS Reviews

Hello all. During my last flight, I've made a slight mistake that cost me my ILS approach. The issue isn't the error I made but how the plane reacted when I tried to correct it. On my approach to Athens (LGAV) the briefed approach was to runway 03R and that's what I programmed in my FMS. However, ATC had other ideas and I noticed on ATIS that the active arrival runway was actually runway 03L. In my rush to change everything, I messed up the approach selection in the FMS and given I was flying solo (of course), I didn't have corroboration and was overwhelmed with the procedures. This was my error, I kept the ILS-Z to runway 03R on the FMS, but I did tune in the correct frequency and runway course for the ILS-Z 03L on the physical ILS radio. When I noticed the wrong orientation while still on FMS navigation, I understood my error, but thought I could save the approach by doing a side step to 03L and activate the ILS in LAND mode, because I knew for sure (and confirmed) the frequency was correct. To my disbelief, even though I confirmed again the frequency and course, the LOC or GS didn't capture, in fact the ND remained in V/DEV mode, forcing me to a pure visual approach. Watch here (timestamped to the moment). Please apologize for the unintentional plug: https://www.youtube.com/live/Qslc0LIGhXw?si=vtSM241bhdZMPMOj&t=7353 I've done this several times, especially with non direct approaches to ILS in aircraft that have separate ILS/VLOC modes from the FMS, like the Fokker 70/100, for example. For me, this sounds like a bug, where the airplane is only reading from FMS data, "expecting" the same ILS frequencies and course of the pre-briefed approach. That or this is just how the real airplane works. Please clarify if you can.

Good afternoon. I've just started using this aircraft and I'm finding the DU's are pretty dim. I've tried using the various controls for each one to no avail. Does anybody else have this problem or just me (not being dim!)? Del

iniBuilds A350 Engine Fan Blur Please see this ,its v1.11 A350 engine start, and see the v1.26 A350 engine start, I can make sure it has issue https://youtu.be/cCNYytHT1_M