All Activity

Can you guys improve the look of the Iconic Table Mountain. On flightsim.to for 2020 it looks hundred times better.

I was doing a flight KBOS-EHAM, everything was going fine. While descending towards EHAM I decided to zoom in on the airport on the ND in order to set the BTV exit. First i get the "APT LOADING" on the ND, after a bit the sim freezes and stutters then it crashes and the flight is down the drain. Anyhow, any clues as to why?

I don't own the A220 yet, but I plan to buy it soon. I downloaded a bunch of liveries from iniManager in advance of my purchase. I now hear that there's a livery pack on the Marketplace that is only free for a week. I'm confused. Are these the same liveries or different ones? Should I get both, or just one or the other? Why only free for 1 week and does that also apply to the iniManager versions? If my intention is to transfer my order to the iniManager once it becomes available there, is it better to use the iniManager liveries from the get-go? I.e. if I only got the marketplace ones, would they even be able to transfer over? Some clarification about all this would be very helpful. Thanks.

Thank you!

I was not doing a turnaround. However, when running on GPU, and then turning on the beacon light, the GPU would get disconnected, causing my FO DEU's to go dark. Perhaps this triggers a turnaround state?

Apologies but I do not do discord, it's like searching for trees in a forest

Weirdly I was able to go back and edit and it worked, feel free to delete these messages regarding the photos!

Hi, I had the same issue and tried to reload the software as you said, but it didn't help for me. However in my first a220 flight I didn't have this issue.

Thank you for this, weirdly enough even when I follow the link it still comes up like this on the webpage

PS I don't know why two of the screenshots have just appeared as links rather than and embedded photos. I have always uploaded images in this exact way, and for some reason these two are just not showing but you should still be able to access them...

Hi all, Here are a few more bugs to add to my list of ones still present in 1.2.6 here: https://forum.inibuilds.com/topic/36783-bugs-that-still-are-not-fixed-in-v126/ Sound The sound during flap/slat extension from the cockpit can only be heard with the camera right at the front of the flight deck really close to the glareshield. You can see and hear on this video as I move the camera back and forth the sound is cutting in and out. https://youtu.be/q2BkI9-sLvM Systems From the F-PLN page, if you click on a speed prediction to take you to where you would enter a restriction, clicking on the RETURN button does not take you back to the F-PLN page. Obviously in this video you cannot tell if I am clicking, but when I am clicking the button (and you can see my mouse over it) but it is not returning to the F-PLN page. https://youtu.be/pEruRkfEk4M CMS (Constant Mach Segment) is not working. In this video you can see that I am entering a value for a CMS but nothing changes when it creates a temporary flight plan, and then nothing changes when inserting this. You can see I tried to enter a CMS by doing it directly from a waypoint and also from the CRZ PERF page. You should be able to enter a value here, and then it will use that speed for the rest of the waypoints until it reaches the end waypoint of the CMS (which I should select from a prompt after selecting the starting waypoint for the CMS). https://youtu.be/Pq30jzQf6Sk PERF Pages: The formatting of the speeds on the PERF pages is incorrect. Firstly on the CLB page, in the image below there should be no MACH value in the MANAGED line, the aircraft is just targeting 250KT(as under 10000ft) this will never be converted to MACH as at 10000ft the aircraft will accelerate to the ECON climb speed on 313KT, which it will then hold until that equals .84 MACH at which point it will target that. When it does this, the value for 313KT should not be shown on the CLB page as the aircraft is simply targeting .84. It should also state if this speed target is due to a SPD LIM or Constraint. (As shown on the DES page in reference photo below) On the DES page: The aircraft is now targeting a SPD (as shown on the FCU - although the logic for when the aircraft is showing SPD or MACH is bugged - see my previous reports), and this can also be seen on the PFD, the aircraft is targeting 325KT which is currently equal to .764M so clearly the aircraft has descended through the Mach to SPD transition. On the DES page therefore, the .84 should not appear and should be dashed out (as in the reference images at the bottom) The .84 is irrelevant as the aircraft will simply target 313KT until it decelerates for the 250@10000 SPD LIM. Whilst on this page, a reminder that the logic for SPD LIM shown on this page is bugged. At the moment the aircraft shows the final constraint rather than the next one. (In the case above it is correct by accident as the there were no further constraints and so the final one was also the next one if that makes sense.... Furthermore, whilst on speed restrictions, for some reason, as can be seen below, the aircraft decided to target 295KT, there is no reason for this, there is no constraint, as can be seen on the F-PLN page, and on the DES page it is still showing 325KT (and erroneously 0.84, as this should be dashed out as previously discussed. There is also a lack of a SPD LIM waypoint on the F-PLN page, the aircraft targeted this spurious 295KT until reaching exactly 10000ft when it changed to target 250KT. This is incorrect as it should begin the deceleration earlier. The point at which is does this should be shown by a SPDLIM pseudo waypoint on the F-PLN page, sequenced at, and indicating the altitude at which it will begin the deceleration. Here, once the aircraft is targeting 250KT (as below 10000ft), again the .84 should not be shown and it should simply show 250KT. And again, in the box where it says managed it should also show SPD LIM to indicate that this target is a SPD LIM not an ECON speed. Below is a reference image showing the MACH dashed out where not applicable, and the SPD LIM in the box with managed indicating that this speed is a SPD LIM rather than an ECON speed. Many thanks for your continued work!

Hi, I do not have this hardware so I wont be able to immediately confirm this however I will ask around. In the meantime I'd recommend also making a post on the Synaptic Discord Server to see if anyone else or developers have encountered this issue. Thank you

Thanks! I appreciate the suggestion. However, I'm not really looking for a workaround by changing my control settings. My pedals work perfectly fine with other aircraft, including the Fenix A320, using the same linear sensitivity. I'm mainly trying to find out whether this is the intended, realistic behavior of the A220, or if the rudder response and ground handling can be reviewed by the developers. I'd prefer to keep my controls at their default settings if that's how the real aircraft should be flown.

Hello, I had the same problem I used these settings and it works well this applies to other spreader bar as well. Screenshot attached. Happy flying

That would be why, the turnaround doesn't fully state clear currently unless the aircraft is fully powered down in the current iteration which will be fixed in v1.0.3 (v.1.0.2 will be skipped on PC due to how the MP Ingestion Process works; this in turn will resync version numbers between FS20 and FS24) Thank you for understanding. https://docs.synapticsim.com/changelog#known-issues

I'll pass this along to our team, thank you.

Hi, I would like to report what seems to be excessive rudder sensitivity. I'm using Thrustmaster rudder pedals with the default linear sensitivity settings in MSFS 2024. With the A220, even the smallest rudder input produces a very large yaw response. It feels like I barely have to apply any pressure to the pedals before the aircraft starts moving aggressively left or right. During the takeoff roll, it is very difficult to keep the aircraft on the runway centerline because of this. What feels unusual is that the aircraft doesn't just yaw left or right – it also seems to roll excessively, almost as if it wants to tip over. In some cases, a very small rudder input causes one of the main landing gear wheels to nearly lift off the runway. I don't experience this behavior with other airliners, such as the Fenix A320, using the exact same hardware and control settings. Is this the intended and realistic behavior of the A220, or could the rudder response and ground handling be reviewed? Thank you.

I had this issue just now as well. Resetting the CBs resolved the issue. This was during a turnaround and for me happened on the ground at the gate. It seems to not happen when the aircraft is initially loaded into its cold and dark state.

After GSX refueling leaves, the fuel panel just stays open on the right wing

So its registering hardware actions but not the actual input to traverse the nose gear?

Yes, it's binded correctly as its responding to my inputs in the MSFS settings page. It also works fine with the Fenix A320 and Ini A350. If I disconnect/connect the pedal via the WinCtrl tiller, it also registers.

I'll pass this along to our team, I would definitely make this post over in the Synaptic Discord as well as they would be the ones to action this change. Thank you.

Hi, Someone else has mentioned this for A220, I personally have this issue in every single aircraft in the simulator. Some have said it's an MSFS issues, others say they don't have it. I'll note this for our team. Thank you :)

I'll note this for the team, have you checked the Synaptic Discord to see if someone has logged this issue there or if anyone else is having it as well. If not I recommend making a post there as well. Thank you.

Known sim issue to the team that will be fixed in SU6, thank you.