Jump to content

Fab10

Member
  • Posts

    76
  • Joined

  • Last visited

  • Days Won

    1

Fab10 last won the day on December 8 2021

Fab10 had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Fab10's Achievements

33

Reputation

  1. Fab10

    DME ARCs: Oh dear!

    Hi, I’ve not tried it with the latest build, maybe there were improvements in that area? I was well below weight limits (the flight was a short hop from MMCE). I will give it another go, and I really appreciate that a few have provided feedback on this by trying the route. Thanks!
  2. Fab10

    DME ARCs: Oh dear!

    I will try at 180kts and I saw the overshoots but still it turned out of sync with the procedure. That said, we should be cleaned up and going higher & faster. I'll give it a go though.
  3. Fab10

    DME ARCs: Oh dear!

    That’s interesting. I also used FLC and kept it slow but the arc was nowhere near the 10DME point, and it didn’t follow the correct lateral path. I will try again.
  4. Fab10

    DME ARCs: Oh dear!

    I know, I reported this a while ago, but cannot believe it’s still an outstanding issue.
  5. I flew a route containing two DME ARCs, one each in the SID & STAR, but the A300 had tremendous issues at both ends. it is as if it loses track of the sequencing. I let it meander through both procedures to see how it would pan out and yet I had to intervene on both. Here’s the route: MMCE/13 CONT2A CONTO DCT ROLMI UT30 CZM UG765 IMOLO UR506 NUDUG L212 VTICO DCT UNG DCT BENON BENON3 MUHA/I06 We are several iterations into the build, yet reading through the forum posts it is apparent that there are still serious flaws in this payware aircraft.
  6. The MU-2 is a nice looking aeroplane, and one I enjoyed in FSX/P3D and XP. Compared with the others, the MSFS INIBuilds MU-2 is not so good. Rotation comes too late and it’s hard to unstick. Like the notorious real world aircraft, the IB MU-2 handling is full of horrific vices but seemingly worse than any other simulated MU-2. The AP is hard to interact with; reading labels is impossible, and the master on/off impossible to click from the P1 view. Please duplicate some click-spots elsewhere on the panel. The cockpit textures are very poor. There is no IB forum section for this aircraft but nevertheless I hope IB will update it. Where to start? I’ll start by not starting it until it’s fixed…
  7. Hi, The A300 is fast approaching perfection, but there are still issues. Profile VNAV seems to not manage descent altitude constraints (speeds seem OK). The PAUL2K into MMUN has one between, one at or above, and two at constraints, and whilst according to the “banana” it would have made the 3000’ constraint before the RNAV (which it flew wonderfully), it was over ten thousand feet too high for the first few even though the descent profile said it was spot on profile. To manually catch up with constraints, I used V/S mode plus spoilers, but then V/S mode switches itself off periodically. The PERF takeoff trim is always zero, and clicking trim automatically sets this to zero. As always, thanks.
  8. Am I correct in thinking that the INI Builds A300 uses stock MSFS navdata as there isn't a dedicated Navigraph component for it? Could someone else please confirm whether they can see the right runway data and SID/STAR dataset for MDPP? That way i'll know to stand down whilst IB fix things, thanks.
  9. Hi, The newly implemented MDPP airport (part of the MSFS Caribbean World Update) doesn't display properly in the A300-600R MCDU. Instead of listing SIDs for RW08/26, it shows RW01/19 instead. I've not tried MDPP in the A310 but MDPP in the PMDG B737-900ER is fine. Thanks.
  10. Fab10

    LGKR: DME ARC RW34

    Thank you. INI Builds, have you anything to help us out, and is this a known and recognised issue, especially considering that the A310 does the same at LGKR? Thank you
  11. Fab10

    LGKR: DME ARC RW34

    Thank you, I appreciate the confirmation. Over to INI Builds?
  12. Fab10

    LGKR: DME ARC RW34

    For what it's worth, here's a very short video of the issue: Perhaps I have missed something with respect to flying this type of arrival/approach in the A300/A310 as the IB A310 also exhibits the same behaviour:? Thanks.
  13. Hi, I twice repeated the flight listed below in the A300 with exactly the same results, which leads me to believe that there may be an issue with DME ARCs The STAR TIGR2T is essentially a 20DME ARC from VOR GAR colocated on LGKR. The IB A300 descends on PROF just fine but then turns left at the 22.5DME GAR direct towards the airfield instead of turning right to establish on the ARC. For reference, I had the RNAV RW34 inserted, and the MCDU list the waypoint as an INTERCEPT just as it fails to establish. The Maddog behaves as expected and follows the DME right down to the approach. I thought I’d report this in case it is of use, but TBH I’ve not flown other DME/ARCs with this latest build. For now, I can fly a descending DME ARC manually with the RMI/DME. Thanks. LIMC/35R TELV8G.ROB5J ROBAS L153 OSBUL Y765 ANC M736 PES M872 DIVKU P92 KAPPO L995 TIGRA TIGR2T LGKR/DIREX.R34
  14. TACT mode is a temporary selection which remains active until the next phase of flight. PROFILE follows the cues as shown in the MCDU. PROFILE mode ALT & IAS/M can be changed by selecting the RLSK and entering new values (A300 & A310).
  15. Yes, thanks, I knew that one, but still a good reminder.
×
×
  • Create New...