Jump to content

srcooke

Members
  • Content Count

    463
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by srcooke

  1. 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.
  2. Having the same problem, I guess a network routing issue.
  3. PMDG system migration Check post #27 in the above link
  4. Fully agree with Ian, never had issues over the many years of FSDT product use through to P3Dv4 now.
  5. 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.
  6. That explains the confusion as the manual still has (FLASHING DM ON MAIN PANEL)
  7. 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
  8. 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.
  9. 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.
  10. Use an AFCAD editor such as ADE or Herve Sors ( easier ) Airport Inspector & Editor and change the runway identifier. Re-run makerwys and voila.
  11. 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.
  12. Are you using v1.0.0.52? in not check the forum post
  13. NEMBO6A starts at XENOL and not from the runway, you need to get there first via the initial climb eg XENOL7A
  14. The departure is in two parts, load the appropriate initial climb first for example XENOL7A, then the SID transition.
  15. I put the route created by PFPX through Simbrief, it should now be available to you.
  16. 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)
  17. 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.
  18. Not a false step climb/descent but related to the direction of flight on the airways and optimum cruise level. The despatcher can easily adjust this using the Speed/Altitude/Holding functions on the advanced planning screen to ensure an upward direction.
  19. Totally agree Peter and I use both.
  20. In a separate location your files will be fine.
  21. As long as the afcad has the SAME name it will not be automatically deleted, you are prompted as to whether to replace it. I have several modified in this way. Should you use your own file name then the file is deleted as it is not a recognized FSDT file.
  22. Which is why suggested disabling the crash detection and trying a wider mesh setting, known to cause issues at runways adjacent to water. 5m may not be enough as experience has shown.
×
×
  • Create New...