All Activity

Hi, This is great news, thanks for sharing your feedback. Hopefully others will have the same results. Thank you!

Hi, Thank you for the feedback. That's interesting to hear, as I regularly use GSX pushback with the aircraft and haven't experienced any issues myself. I'll make a note of your report and pass it along to the Synaptic team for review. Thank you!

Hi, I have seen a few reports of similar issues. As a troubleshooting step, I recommend adjusting some of the camera values within ChasePlane, as this may help resolve the issue. Thanks!

Hi, I haven't encountered this issue myself, nor have I seen other reports of it. I'll make a note of your report and pass it along to the Synaptic team for review. In the meantime, I recommend joining the Synaptic Discord, where the team and community may be able to provide additional support and troubleshooting. Thank you!

Hi Paul, I haven't encountered this issue myself, nor have I seen other reports of it. I'll make a note of your report and pass it along to the Synaptic team for review. In the meantime, I recommend joining the Synaptic Discord, where the team and community may be able to provide additional support and troubleshooting. Thank you!

Hi, Thank you very much for the detailed suggestions. We truly value community feedback like this, as it helps shape the future of our products. I'll make a note of your suggestions and pass them along to the team for future consideration. Thank you!

Hola: He tomado nota de los problemas con la flexión de las alas (*wingflex*). El A350 para consolas no incluye cabina de pasajeros debido a limitaciones de rendimiento. Espero que lo comprendas. Gracias!

Hi, This is a noted issue and the Synaptic team is working on a fix. Thanks!

Hi, I haven't encountered this issue in the simulator, and this is the first report I've received of it. I'll make a note of your report and pass it along to the Synaptic team for review. In the meantime, I recommend joining the Synaptic Discord, where the team and community may be able to provide additional support and troubleshooting assistance. Thanks!

I believe this might be a GSX config issue. Try deleting the synaptic_a220 folder from %AppData%\Virtuali\Airplanes and try reinstalling the profile. Thanks!

Is the issue with the forward right door opening when launching boarding or deboarding from your gsx profile ? Or is it something else ?

Hi, Thank you for your feedback and suggestions. I've taken note of them and will share them with the team for review. Thanks!

Hi, Jamir has logged the issues outlined above, and the team is aware of them. Thanks!

Few... Just a few. Scenery developers challenge, any chance to do the interiors of the jetways for at least 2 or 3 of them? I think it's time to raise the bar on current or upcoming sceneries. This is for the ones that are not glass.

dectenor2's feedbacks are always appreciated and show good values. Are the team taking them into account for further updates?

Thanks for the clear explanation. That makes sense—it's more of a limitation in how GSX places its simobjects than an issue with the airport itself. The suggestion about checking for other terrain or airport mods is also helpful, especially if the sinking is much worse than expected. Hopefully future simulator or GSX updates will provide better support for custom platforms.

Hello, I have an issue with EFB, no matter where i click on efb it doesn't react. I've reinstalled it and updated this addon and still nothing. EFB is just frozen. only current time shows up. Buttons are responding and i can use everything except EFB. Anyone has the same issue? Best regards.

Yes, I see the same here in New Zealand. It would be nice to know why. Perhaps I should RTFM in case the answer is there. Bruce R

Versión Xbox X. El avión está muy bien, hecho a faltar el movimiento y flexeo de las alas al despegar / aterrizar y en zonas de turbulencias, también en la versión XBox X, la cabina de pasajeros aparece sin asientos e incompleta, podrían modificar éstos punto en futuras actualizaciones, muchas gracias.

Recently I observed the gradual improvements of additional ECAMs especially for flaps and l/g, therefore showing potential into system depth with an already deep ECAM simulation. However, I think other failures might need attention here as behavior is different in real world documentation. For example: Bird strike situation should also affect outside TAT probes and windshield These probes such as AoA, airspeed, ice detection and static are located below the windshield and should have a random chance of failing due to bird strike to the cockpit since they could be located near the impact point. Interestingly, according to the virgin atlantic FCOM below, bird strike can affect the data that feeds to the ADRs and the current way of failing it other than turning those off is not available in the EFB, nor the bird strike situation. Another thing is window strike damage which will need the ABN COCKPIT WINDOW CRACKED checklist which is available in your ECAM but not in the bird strike simulation. Some engine systems such as engine relight simulation, EGT and vibration need work I am no engineer, but crosscheck this with other Airbus engineers. Bird strike doesnt necessarilly cause the engine to fail, but, when they do, its ingestion to the compressor might cause turbulent airflow into the compressor leading to a stall or surge. This should show the telltale signs such as high fluctuating egt, n1, fuel flow and abnormal vibration while the engine bangs occur. However, the eng page does not reflect to your external engine failure animation due to bird strike. It could be recoverable provided that the compressor returns to its normal airflow configuration ehich recovers the imbalance vs combustor. I also noticed that your engine failure in the efb induces it in such a way that it still windmills and has no abnormal vibration, which can consider a relight in flight. However, recovery cannot be done for some reason? Because, in that case, I would love an option for a recoverable (and unrecoverable) engine failure option in the efb, while showing the key differences between the two failures. In some FCOM documentation, unrecoverable ones could show a reason: The oil low pressure should gradually trigger high vibration and abnormal egt first before engine seizure, which should give off a more authentic engine simulation, as well as FADEC shaft failure trigger, any of these in order. You also forgot about the situation for lithium batteries too. This is also from real world operations: I look forward to the update of the a350v2, but please do a C check of your failure and system depth.

Thank you. I thought the flight simulator applied the GSX profile automatically

I am mystified by the message spoiler mismatch (in blue) which appears at seamingly random point in each flight. When it does, the spoilers stop responding (except for roll control and after landing) when the spoiler handle is actionned. Any suggestion on how to address this issue? Thanks Paul

Since the 1.0.3 update was released, I’ve been having this issue with the aircraft. It doesn’t matter whether I start from cold and dark or ready for takeoff—the aircraft immediately reports these system failures. I’ve already tried uninstalling and reinstalling it (which fixed the pink textures issue), but I still can’t figure out why the batteries are overheating, the hydraulic systems are failing, and the engines are losing so much power that it’s basically impossible to fly the aircraft.

Yes I am! Is this the issue?

coming back to report that.. nosewheel steering will not work with GSX pushback.... only works with default pushback through the efb. strange thing