matteolosardo

I forgot to add, I'm talking about the MSFS version.

Hello, in the latest versions of the A300, it looks like the elevator pitch trim became too sensible, trimming too fast. this makes precise trimming very difficult... is there an option to go back to the older pitch trim of previous versions, which was slower and more precise? thanks

it can't be, because I tried reinstalling the aircraft and restarting the sim multiple times... it's a weird bug which is not easy to identify the cause of, but seems like a couple of other people are experiencing as well... it could be related to some SIDs with manual legs and discontinuity bugging the autopilot, either way I filed a support ticket so the devs can look into it a bit more

Bro what XD I'm literally saying that NOT EVEN hdg selection works in the autopilot, which is TOTALLY unrelated to any waypoint the RNAV system is actually having selected as the next one. My plane clearly has a bug, because if I select heading and change my dial, the plane should follow that heading if announced in the FMA. it should NOT randomly start a right spiral towards the ground which is what happens. I hate bragging online to people I don't even know, but telling me the plane is not broken but the pilot (me) is, is not a very smart thing to say... I have studied air navigation, hell I even have an EASA ATPL theory exams certificate... I'm a CPL student and have a minimum of experience of how an autopilot should operate (this doesn't make me a type rated A300 pilot, but saying I'm the issue? really?) just because not everyone are having this bug in the same context I'm having it, it does not mean necessarily that I'm doing something wrong or I'm a bad pilot. if I am in heading select and when I turn autopilot on, the plane randomly starts a spiral towards the ground, clearly something is wrong isn't it?

yeah I know why the vectored segments are here, I'm totally familiar with it, but it makes zero sense that if I delete them and DCT to the next SID waypoint, the autopilot should not randomly become useless, not even allowing me to use HDG SEL.

something new and quite important I noticed: I only have the issue IF I delete the "manual" waypoint from the SID, along with the discontinuity. If I leave the manual segment and the discontinuity, and takeoff with them still in the FMC, and after takeoff I just go direct to the first SID WPT, the autopilot and NAV mode works as it should. I hope this can help understand what the problem is... maybe it's related to "manual" segments during a departure.

I understand it has been tested and it's working fine for some people, but why is it not working for me though? why is my autopilot broken when I do it?

sorry here I tried to link some images in the wrong format... I'll send them again.

I wanted to add this happens both in passenger and cargo version... it never happened before the update.

IMG_6471.jpg.url IMG_6472.jpg.url

Hello, we've talked a lot about this in the discord server, and also on other reports in this forum. surely something is wrong here. What happened is: I started a KDFW - KPHX flight in the latest version A300, and as soon as I takeoff, the autopilots is completely broken. The NAV mode engaged shows the FD bar completely deviated to the right (even if the route should command a left turn) The HDG select mode correctly causes a change in FD bar, but the autopilot simply does not follow it… Whichever mode the autopilot is in, the plane does not actually follow it… sometimes it evens start a right roll that becomes a spiral towards the ground. I tried restarting the sim, totally uninstalling and reinstalling the A300, but it did not fix it… it even does the problem if I spawn directly on the runway, as I did many times when troubleshooting. To me this only happened in KDFW (default airport), but another user in the general chat reported the problem after taking off from a different airport. Can I please get help or have this issue acknowledged by a dev? I really want this plane to become stable and know that it won’t have such problems. Thanks in advance

Same thing for me, though it happens when taking off from KDFW. we've talked about it much in the discord server. hopefully any of the devs can look into this, it's basically unflyable, completely broken.

to me it does it even without changing to external view... what could be causing this? not even the new update fixed it

I wanted to add that this only seems to happen in the passenger version... the ET of the cargo version runs in real time.

hello, I'm using the latest A300 for MSFS (1.0.1) and I've noticed that the onboard clock ET runs faster than real time... this makes it totally useless because it shows at the end it will show a longer flight time than actual. I even tried this, I started the ET with a chronometer running in the meanwhile: as the real chronometer displayed 10 minutes, the plane's ET displayed 13 minutes and so on. How can I fix this? thanks

update: i tried deleting the airport addon I was using for LIMC: it was a freeware from flightsim.to... I tried again and looks like it did not do it. that's weird though, I only had this issue with the A300, not even with the A310 or other, even default, planes... I think it's still something that needs to get looked into for the sake of this addon's stability

well, the original route was (EGLL 27RDET2F DET L6 DVR UL9 KONAN UL607 KOK DCT IDOSA DCT SUTAL UN852 GTQ UZ343 BEGAR DCT BASGO Z424 RIXUV RIXU3E ILSZ35L LIMC, cruise FL330 and CI 37)... but that's what I tried today that surprised me... I loaded my A300 (happens on both pax and freighter) on EGLL 27R (so with the plane already on, directly on the runway), went to the FMC, and just selected departure and arrival airports EGLL/LIMC (this means I had no route waypoints, just DEP ARR), then I went directly to set the arrival (while still on the dep runway) and I did the same thing... I selected the ILS, the STAR, and then I went again to reselect a NO STAR approach... it froze totally, and the plane did not have anything else in the FMC other than dep and arr airports. I also discovered it's unrelated to both which STAR I select and also which airport I depart from... you just have to select LIMC as arrival and first select whatever star and approach, and then reselect that approach with no star, for the FMC to turn blank and freeze the whole avionics... if you need me to troubleshoot something else let me know, I really want to fix this as I want to feel the plane to be able to do whatever while setting approaches (say, I set an approach, then ATC clears me for another, I don't want the whole thing to freeze). Please help, let me know, thanks in advance

hopefully they fix this one soon... I anyway sent a support ticket to inibuilds support, hoping it's not anything deeper, maybe related to pc compatibility, causing my issue. thanks

honestly, I tried now doing the same thing on the asobo 747 and it didn't have the issue... are you sure its the exact same thing happening to me on the A300? I have the avionics freezing in position and FMC turning blank... do you have any link to people having the same issues on other planes?

oh okay, so I guess a fix is coming soon, or at least I hope... thanks for answering

update: it happened a third time, I literally spawned the plane on the runway, took off and tried setting the arrival in the same way as before... the avionics froze again... help please

Hello, I had this happening on the v1.0.1 A300-600. I was flying EGLL-LIMC, and during cruise, I was setting the arrival in the FMC... I selected the RIXU3E arrival ILS 35L, looked at my FPL in the MAP ND, and then decided to select a NO STAR approach ILS 35L... after doing so, the FMC completely turned blank, and all the avionics froze. The EFIS control panel also stopped working (for example, the ND Mode and Range knobs did turn, but producing no effect on the display) and the autopilot as well stopped responding. After this happened, I tried redoing the same exact flight all over again... After the climb out from Heathrow, I did the same exact process in the FMC, to see if the issue would've happened again, and surprisingly it did... Can this please get investigated? I believe the plane should be able to set and reset an approach in the FMC without freezing and becoming a flying brick. Thanks in advance :))

thanks :)) I'll be waiting for a fix

Hello, I have this issue with the A310, both in the previous and the new version of it... when I turn my APU or engine bleed on, the air sounds change too much when moving from the captain view to other positions in the cockpit... in the way that, in the first officer position they are completely unhearable and when looking at the EFB they're way too loud... this is especially noticable when on the ground with engines off and APU bleed on... can anyone help me or is a fix for this issue planned? thanks in advance :))