Jump to content

mr.ocjr

Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by mr.ocjr

  1. I got back to planning my flights with PFPX after a bit of a hiatus and there are a few calculations that I am unclear about, specifically around costs (not cost index). So here is what I entered for a DFW-ICN flight with KE on the 747-400 and I am not totally clear on what is calculated or if it is reasonable. I am happy to crunch the numbers on a different aircraft/route if someone has more detailed information to compare. Flight #1: Fuel Price: $587.87/ton (https://www.iata.org/en/publications/economics/fuel-monitor/) Fixed/Flight Hour: $500.00 (round number to see how things are calculated) Var/Flight Hour: $3,151.00 (non-fuel costs for Delta 747-400 https://www.planestats.com/bhsw_2014sep) Result: 13:29 flight time Flight Cost: $50,008.00 Fuel Cost: $84,381.00 Total Cost: $134,389.00 Cost per Pax: $339 (This seems low considering the fare on a round trip DFW-ICN is $2000 for economy) I would love some better numbers but I am more curious about how the calculations are made for the fixed and variable flight costs and to a greater extent how it is used for the minimum cost flight plan option. Obviously this will never get quite as close to the real thing as overflight costs and landing fees aren't in this calculation but I am curious about making it a little better.
  2. Did we ever figure this out? I just installed PFPX on a new computer and I can't get it to run at all. Faulting application name: PFPX.exe, version: 2.0.4.0, time stamp: 0x5fdb05ce Faulting module name: ntdll.dll, version: 10.0.19041.804, time stamp: 0x039874b8 Exception code: 0xc0000005 Fault offset: 0x000621d3 Faulting process id: 0x3384 Faulting application start time: 0x01d70f10c64dcbf6 Faulting application path: C:\Program Files (x86)\Professional Flight Planner X\PFPX.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: e1cefbe2-3f50-41f9-a9fa-6c308f370fe3 Faulting package full name: Faulting package-relative application ID:
  3. Yeah I totally get that, I don't care that much about EA so as long as I can get it working some way So I think it has to do with loading the aircraft with EA on. When I would switch between the EA being on and off, the changes weren't apparent until I reloaded the aircraft. And even then it was inconsistent (mostly looking bad). The only way I could consistently get it to work right is with EA off. Now on to my next issue with DirectX
  4. So a little update. I went and downloaded the BA BEA A319 just to make sure I was comparing everything the same. And I was still getting the stripped paint look. I did a little more testing and it appears to only show up when I have Enhanced Atmospherics on. Perhaps I missed the post about how I should turn that off.
  5. So this striped paint effect is happening on all of my default liveries (on the A319/A318 only). On a fresh install. Just to confirm, this is an issue with P3D so I must wait until they fix it?
  6. So I thought I would post a reply in this thread that I had this same problem. Here is the timeline and how I fixed it, in case someone runs into the same issue. Installed the A320/A321 to P3D v5 Installed the Majestic Q400 to P3D v5 Installed the A319/A318 to P3D v5 This is when the errors started popping up. FYI, part of the Q400 install was an DirectX install. Doing a little digging on the two DLLs that were causing the issue (XAudio2_4.dll and D3D10Warp.dll) and everything pointed to a faulty DirectX install. I also read that with windows 10 there is no way to do a clean uninstall and reinstall of DirectX. However there are likely a few different versions of installer on your machine. Likely one that came with your install of windows and another with various games that have that installer. I did a search for DXSETUP.exe on my C: Drive and found the version in my NIVIDA folder. After running that installer, the issues appear to have abated. While this might not work for everyone, I thought I would share, in that a quick install of DXSETUP.exe is a lot easier to test than a complete reinstall of Windows.
  7. Yeah GSX never got past the tug hook up either, no "please release parking brakes". I just updated GSX so I will try again, but I do agree that this appears to be a GSX issue more than an A320 issue.
  8. So I followed your directions and after the doors were closed by GSX, the BeforeStart CL did not start and the INFOBAR went away. External Power didnt disconnect because the APU never started and so the pushback proceedure didn't finish. Everything just stopped. Wait! As I was preparing to close P3D i decided I would take the aircraft for a flight anyway, and as soon as I cancelled the GSX pushback the checklist got started again. So perhaps this is a GSX issue instead of a Aerosoft issue? Let me know your thoughts on what I could do next?
  9. I will give that a try! I do always try to follow the infobar, after I would close the doors the bar would disappear. I will let you know what I find.
  10. Departing from EBBR in both the 320 and 319 get stuck after I close the doors. I thought this was an issue with the version I was using so I ran the ASUpdater to get the most recent version and it still gets stuck. I tried it like 6 times this evening and I am stumped. On the 6th time the doors wouldn't stay closed, they just kept cycling, so could that have caused the checklist to get interrupted? Here are the steps to get going that I took: Load flight Sim Gate 353 at EBBR Set Turn around state Init Loadsheet Instant load Start GSX turn on checklist turn on copilot start cockpit prep checklist Set parking brake (when prompted by cockpit prep checklist) Enter flightplan and setup MCP set baro wait for GSX to finish boarding close the doors hear cabin secure checklist stops. I feel like this could be something simple but I keep racking my brain and I can't figure it out. This is how i start almost all of my Airbus flights and tonight is the first time this has happened. I have had checklists stop before, but a computer or P3D restart usually did the trick, not this time.
×
×
  • Create New...