AnkH

I use them, see no difference in the VC on my 4K screen. Also see no relevant gain in VRAM, so I could basically again switch to the regular resolution, but then, if I dont see any difference, why care. The performance of this bird is anyway abysimal compared to other addon planes, so...

Yeah, but at least we can print now...

Almost a month later, nothing...

But you have a printer now... /sarcasm off

The same answer you gave months ago already, so why not be honest and state that it is so low on the priority list it might never get fixed? Inbetween, PMDG released another plane with perfectly working three axle main gear bogie. So it CAN be done right for sure...

Just that you are aware of: MSFS2024 has a bug (potentially fixed with SU3, who knows) that prevents the ingame time from being accelerated accordingly, so even if you use 4x or 8x in your A350, ingame time will still only progress with 1x. Which results in annoying time mismatches on destination. But there is a small tool on flightsim.to that fixes this, drawback: another tool that needs to run alongside the sim...

Same here, shadows only look good using ray traced shadows. Again a bummer other addons do not show...

Could you try this once: before doing anything with GSX (except maybe a reposition), fire up the electric systems of the plane and ask for boarding using the default ATC command. Do the jetways then move? Because I have exactly this issue with GSX moving jetways (or rather not moving them) on the new YSSY update from FlyTampa and RKSI from PacSim. No solution so far...

Still nothing?

I just did as I have exactly the same issue...

Of course not. GSX will use the data from the plane and airport stop positions can be defined only on the basis of the info from the plane.

Thanks Eddie, I guess this is the same issue:

This is not a Inibuilds A350 bug, but a general MSFS2024 bug (see: https://forums.flightsimulator.com/t/global-time-not-progressing-at-the-increased-sim-rate/669206) With this little tool, you can workaround this issue: https://flightsim.to/file/86894/sim-time-rate-adjuster-for-msfs-2024 Just another example of how bad the state of MSFS2024 was on release, it is supposedly fixed in SU3... while not even SU2 is released yet...

Hi there, strange observations when using the A350 with GSX and addon airports. It happens again and again that when I use the option "reposition" aircraft, the aircraft is moved way to much to the front (in direction terminal). Sometimes. Sometimes it does not. And it gets placed initially pretty ok. What I think is linked to this strange bug/issue is the fact that when using FSHUD, FSHUD always thinks that the A350 is not positioned correctly at the gate and it also then needs to be moved by FSHUD but that results in chaos as well. Asking this specific problem, someone on the FSHUD discord channel told me that the position of the A350 is bugged. Is this a known issue? What could be the problem?

The "problem" is that one of yours wrote in the discord channel that it was a bug unintentionally slipped into the release version because it was not like this in internal testing. That is why the "easy" comes from. Obviously, this was not the whole truth then, cant be that complicated to get something working again when it was already working prior release. But hey, in the end it is just the landing gear, no? 😉