Jump to content

srcooke

Members
  • Content Count

    363
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

22 Neutral

About srcooke

  • Rank
    Member

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes

Recent Profile Visitors

3,049 profile views
  1. I believe a different offset requires monitoring for the altitude, but that would need confirming with the FSL developers.
  2. 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. 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.
  4. The 'Y' ILS is not included in the AFCAD, easily added uses Herve Sors Airport Inspector and Editor
  5. GCO can be tuned on a nav radio from the sim database to obtain the DME, at the least when updated with Herve Sors navaid updates.
  6. Having the same problem, I guess a network routing issue.
  7. PMDG system migration Check post #27 in the above link
  8. Fully agree with Ian, never had issues over the many years of FSDT product use through to P3Dv4 now.
  9. 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.
  10. That explains the confusion as the manual still has (FLASHING DM ON MAIN PANEL)
  11. That didn't appear to occur Bryan, at least with the descent briefing which was initiated just a few minutes before TOD. DM was not displayed and 'CABIN CREW PREPARE FOR ARRIVAL' not played descending through 20000ft
  12. 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. 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. Use an AFCAD editor such as ADE or Herve Sors ( easier ) Airport Inspector & Editor and change the runway identifier. Re-run makerwys and voila.
  15. Hello Stefan, For years I have used a speaker-out on the client to mic-in on the FS PC with vPilot on the client and FS2Crew on the sim.
×
×
  • Create New...