Jump to content

matteolosardo

Member
  • Posts

    24
  • Joined

  • Last visited

Posts posted by matteolosardo


  1. 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

  2. 1 hour ago, Skipper said:

    Hmmm I made three fully automated testflights with auto-land so far, with manual flight path programming, and the autopilot and also the ILS always worked flawless. Impressive how this old retro computer system cannot draw curves on the screen but the plane itself is cutting corners flying a smooth path. Love this plane, it is awesome!

    I was especially impressed that the internet said Bergen Lufthavn ILS frequency 109.90 with 27nm range, and somewhere below 30nm the A300 slowly begun to catch the ILS signal and started following the glide path down. I made it even more difficult for the MCDU when testing the systems by programming a flight path with vectors directly above the landing runway, but the machine left the pre-programmed MCDU waypoint course to catch the ILS, just like it should. Awesome.

    (I have not tested VNAV in the MCDU but manually went up to 10.000 and back to 3000 to catch the ILS. I rarely use pre-programmed MCDU-VNAV.)

    Everything seems to be fine with the autopilot. I never fly by hand and found no problem with the automatic systems so far. Maybe you encountered a glitch in the simulator or a simbrief problem.

    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 

  3. 26 minutes ago, Crabby said:

    He said why in a nice way and maybe you didn't pick up on it.  You are doing it wrong (procedures).  Don't say you followed the checklist.  A checklist does not help you fly a plane, procedures do.  Checklists only verify proper execution of flows (procedures).  Your autopilot is not broken.  Your pilot is broken.  For example, in the departure you referenced, taking off from 34L as in your simbrief.  The chart says "Climb on HEADING 353 to INTERCEPT COURSE 059 to DUGGS".  Where you in HDG mode when you took off?  Did you fly the HDG then use the directo button to put you aircraft on course to DUGGS?  Did you look at your FMC and try and erase the manual entries?  Manual does NOT mean the autopilot is OFF it means other than LNAV mode, spinning knobs and stuff.  Fix the pilot and the autopilot will work better. When I flew this SID, I took off in HDG and Profile mode, my FCU was set to a heading of 353 and my altitude was initially set to 10000.  Worked perfectly.

     

    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?

    • Like 2
  4. 34 minutes ago, Crabby said:

    Nothing to do with the possible issue but explains why I never see this behavior.  You were probably on an RNAV with a vectored first segment.  The manual waypoint and discontinuity are not a mistake.  On those SIDs, if you use live ATC, you will get vectors and should take off in HDG mode.  Once you are cleared "Direct To" hit the direct to button.  If you are not using ATC, you can simulate that at any time.  Basically, this will be the case any time you see a chart where the first waypoint is not drawn to the departure runway.  

    Are you using charts?

    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.

  5. 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.

    • Like 1
  6. 16 minutes ago, AthenaG said:

    INIBUILDS. FYI The reported issue departing KDFW 31L has already been tested by others as working fine. Whenever there’s a MANUAL leg in the SID there’s HDG or DIR to required. Just entering NAV isn’t going to work. Nor deleting a MANUAL leg. A irl pilot has also tested this SID and offered to share video is anyone is interested in the Ini Discord. In this case, the reported issue is procedures.

    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? 

  7. 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

     

    • Like 1
  8. 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.

  9. 4 hours ago, Mountainbuilder said:

    I would like to confirm this, it looks like a bug that is triggered by switching to external view. No anomaly while staring at the clock on the flightdeck, but after returning from external view you'll find that the timer was somehow faster. To reproduce:
    1) Get an external clock, start timer (ET) at 00 seconds
    2) After 10 sec, switch to any external view for exactly one minute
    3) When returning, ET should show 1:10, but actually shows 1:40

    Tested during cruise, high framrate, no time compression involved and speeds way too low for any relativity effects ;o)

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

  10. 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

  11. 5 hours ago, Nico - Gumby said:

    I dont know what @Aussiepilot is talking about.. But to me, this rather does sound like an iniBuilds issue. Thanks for the report @matteolosardo , could you please provide full route, flight level, cost index and the point when you entered the direct so we could look further into it? 🙂

    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

  12. 10 minutes ago, Aussiepilot said:

    Try the Asobo 747 & 787 & A320 and they are all experiencing this.

    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?

  13. 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 :))

  14. 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 :)) 

×
×
  • Create New...