Jump to content

mcnobody

Member
  • Posts

    13
  • Joined

  • Last visited

mcnobody's Achievements

6

Reputation

  1. mcnobody

    TCAS 1.1.0

    Any other range than 6 or 12 is not possible.
  2. mcnobody

    TCAS 1.1.0

    All covered here:
  3. I am using the current data by Navigraph. It might cause the trouble but the problem doesn't exist with the FBW A32N nor with the ATR72. Both of them using the MSFS navdatabase as far as I am aware. I have already pointed out that the ILS frequencies are the ones being cutoff. My topic title is a bit misleading.
  4. Dear iniBuilds Team, when entering VOR / ILS names manually into the MCDU - i. e. the IKA VOR - certain frequencies are misaligned or cut on the duplicate names list. See the 1st, 3rd and 4th entry on the following screenshot: The named stations are all ILS frequencies and I guess the last zero (0) is cut. As usual: I don't have any real world documents. So I can say if this is actually a bug or a function of the MCDU. Christian
  5. Hello. I have got a dedicated tiller as well. It would be nice if the ini A300 could be set up for a separate use of rudders and tiller. For example the nose wheel tiller moves the nose wheel to its full extend while the rudder only to a few degrees. By the way: The PEDAL DISC button on the Airbus tiller is supposed to disconnect the rudder pedals from the nose wheel while performing the flight controls check. It doesn't have any other function - i. e. limiting movements etc. during take off. Do the A300/A310 even have that button or function? Christian
  6. Hello. When you enter a waypoint/airport on the PROGRESS page of the left MCDU (so that it shows beaering and distance), the right MCDU shows the same entry. I am not sure if this is the correct behaviour. Maybe different entries can be made on each MCDU or they are synced. Anyway - if you enter another waypoint/airport on the right MCDU it still shows the entry of the left MCDU while bearing and distance change to the new entry. The behavior seems to be a bit bugged there. Please check the attached image to prove my statement. Both MCDU show the waypoint IMPED. Bearing and distance are different. I tried to enter OMDB30L on the right MCDU. It still shows IMPED but the BRG / DIST have changed. Christian
  7. Nice shots Darryl. If you want to get closer to real ops you might consider parking at the west apron (terminal 1). The east apron (terminal 2) is primarily used by Lufthansa and its partner airlines. Is this the default Asobo A320neo?
  8. As far as I am aware it's common to set the frequencies on the PROG page. At least during departure and arrival. I am not sure when the receivers are set. Maybe in case of a failure or a manual VOR approach. These can only bet set if you move the flight director to VOR. This way you loose filgiht bar indications. Doesn't make much sense to me. It's quite useful to set the VORs on the PROG page as a backup or to get certain information at all. In EDDM you can tune in the DMN or DMS VOR. Both are DME only. You can use that information to verify the distance indications from the ILS. You don't get that information from your F-PLAN page since both VORs are not part of the lateral procedure. On the A320/A330/A340 you set the VOR (and ADF) frequencies on the RADNAV page basically. On the A300/A310 MCDU this feautre is located on the PROG page (exlcuding ADF).
  9. Hello iniBuilds team, could you consider changing the default pilot view slightly? In my opinion the head position could be a little higher and tilted downwards a few degrees. For example like this? ND and PFD are horizontally centered and fully visible. You can still see the engines indications of engine no. 1. All other important indicators are visible as well. While taxiing you get a slightly better view on the taxiway lines. Compared to other aircraft add-ons the default views on the A300 (as well as A310) feel a bit strange - for example the zoomed IAS indicator. A view on the MCDU, tablet etc. would be nice and more important during the busy phases of flight. Best regards, Christian
  10. Sorry, title was meant to be: Engine indications: needle dropping while AC takes over I can't change the title anymore. Can't any of the mods do this? Thanks!
  11. Hello iniBuilds team, this video was already posted in another thread: At minute 3:45 respectively N2 reaching 54% you can see the AC generator kicking in and all needles drop to zero. I think I saw this feature on the X-Plane version of the A300 (sorry, I don't own it). Since you have modeled the monitors switching over at this certain moment, can the drop of the needles be included as well? It's not essential but adds a lot to the immersion specific to the A300/A310. At the moment this is missing. Thanks and best regards, Christian
  12. Hello iniBuilds team, I have got two issues with radio navaids which are manually set on the PROG page of the MCDU. It seems like VORs which are DME-only can't be set manually but are automatically tuned by the MCDU. For example DMN, DMS (both at EDDM) or ALF (EDDH). If I enter these, the MCDU gives an error message: NAVAID NOT IN DATABASE. I had two occasions where a manually set VOR was overwritten by the MCDU i. e. while approaching KMEM (MEM VOR). I programmed MEM in quite early. Checking it later, suddenly another VOR/frequency was tuned in. I am not sure if both issues are replicating the aircraft's behaviour or can be regarded as errors. In my eyes these functions are quite essential for performing a proper flight management. Best regards, Christian
×
×
  • Create New...