Jump to content

srcooke

Members
 View Profile  See their activity

  • Content Count

    463

  • Donations

    $0.00 

  • Joined

  • Last visited

Posts posted by srcooke

  2. Posted

    Currently PMDG does not accommodate runways with dual ILS frequencies, hopefully this will be resolved in the new database structure.

    At present the first entry in the wpNavAID.txt is used which in this case is the 'Z' approach IIZJ 110.75

    Tuning the nav radios for the 'Y' frequency will utilize the IBYW 110.90 approach.

    Re-sequence the wpNavAID.txt file should you require the 'Y' selection via FMC

  3. Posted

    Just now, w6kd said:

    The missing DME is easily enough added with ADE...the point is that it's missing, needs to be fixed by the dev (I'm sure it will be), and in the meantime, if you're flying to KORD, consider it NOTAMed out for the time being.  I don't much care for planning and flying a flight and discovering the navaids are missing when I'm trying to fly the approach.

    Regards

    The DME is not co-located with the ILS and on a separate freq for VOR CGO 108.25, the ILS for 04R 110.10.

    I'm not aware that the dual frequency entry can be achieved in the sim, hence the need to tune the VOR separately.

     

  9. Posted

    Whilst I do not get a crash to desktop on exit it is not a clean close that requires a reboot:

    Faulting application name: PREPAR3D.EXE, version: 4.5.12.30293, time stamp: 0x5cd47aad
    Faulting module name: FS2CrewAirbusLabs64.gau, version: 1.0.0.86, time stamp: 0x5d297907
    Exception code: 0xc0000409
    Fault offset: 0x00000000000968f4
    Faulting process id: 0x4ac
    Faulting application start time: 0x01d53b9f87684d41
    Faulting application path: E:\Prepar3D v4\PREPAR3D.EXE
    Faulting module path: E:\Prepar3D v4\Gauges\FS2CrewAirbusLabs64.gau
    Report Id: dd3bec9e-e161-4df6-ab29-5d6722b27634
    Faulting package full name:
    Faulting package-relative application ID:

     

    Disabling FS2Crew via the config panel leaves P3D to close normally.

  12. Posted

    Enroute third flight with the same issue.

    Nearing cruise level the '1000 to go' is triggered and acknowledged 'checked', the PM sets TCAS to below.

    At cruise however the 'Cruising Flight Level XXX' is not played and I suspect this leads to having no Descent Mode later in the flight.

     

  13. Posted

    Upon install I met a somewhat similar issue.

    The initial screen asked for the path to the panel.cfg, assuming this to be any panel I set an A320CFM panel path.

    Filled in the registration screen.

    Was then met with set your panel.cfg path again.

    This led to the configuration panel as displayed by the OP.

    Having restarted the configuration panel the options to enable/disable FS2Crew were then displayed and the product is functional.

  14. Posted

    16 hours ago, swissdani said:

    Hi Brian

    Coming back to you. I know was able to run Make Runways and all the files were generated as they should. Is there anything I still need to do, to activate the "new runways" in RAAS? I tested in LSGG, RAAS still calls out rwy23 instead of rwy22.

    Dani

    Use an AFCAD editor such as ADE or Herve Sors ( easier ) Airport Inspector & Editor and change the runway identifier. Re-run makerwys and voila.

    • Like 1

  21. Posted · Edited by srcooke

    PFPX generated and EuroControl validated route:

     

    (FPL-DAESE-IS
    -A320/M-SDE1FGHIJ1RWXYZ/LB1
    -EGNT1655
    -N0439F370 DCT ERKIT L602 OTR L90 DOLAS L603 LAMSO UL603 EVELI UL19 TULIP DCT REMBA DCT PITES DCT EDISA Y852 NATOR UN850 ODINA DCT ROBAS/N0414F290 L153 BEROK
    -LIRQ0217 LIRP
    -PBN/A1B1C1D1L1O1S1 NAV/RNVD1E2A1 DOF/190330 REG/DAESE
     EET/EGTT0011 EHAA0034 EBUR0047 EDUU0105 LSAC0126 LIMM0140
     LSAC0143 LIMM0143 RVR/75 OPR///
     PER/C
    -E/0327)

  22. Posted

    11 minutes ago, Christopher Low said:

    I already have (a modified version of) the South west winds option active. I think it is just an annoying quirk of the software that sometimes results in Landing/Take Off settings for various runways being ignored. After all, I have 22L open for landings and 22R closed for landings, but I still get instructed to land on 22R (as do some of the AI planes). That is something that should never happen, so LM need to sort it out.

    Check the AFCAD has both runway ends set to the same operation mode.

    IE 22L/04R landing and 22R/04L takeoff. Mixed modes or single entry will not work.

×
×
  • Create New...