All Activity

This stream auto-updates     

  1. Today
  2. Awesome news, Thank you.
  3. Yesterday
  4. You can add any aircraft to PACX by editing the C:\Program Files (x86)\TFDi Design\PACX\Assets\Airplanes.xml file.
  5. I agree! This will be something we'll make work in 3.
  6. I like it! Let me tag in @turbofandude to this
  7. This is normally just a communication time from our server to that of the VA. As we have now moved to entirely new servers, this issue should no longer present from our side.
  8. I would like to see the aircraft I have in my hangar. It makes no sence actually flying a LJ45 and this aircraft is not shown in the aircraft section. Either the program will enable this or the user can do this. The second point is the combined use with GSX. The boarding time should be synchronised the GSX and so on....
  9. After all these years I’m looking forward to flying the 717 again. Will the fix be pushed as an update or a clean install of the 717?
  10. The way it currently works is the same as the actual 717, if I recall correctly.
  11. Excellent. Really looking forward to taking her out of the hanger.
  12. great, time to get the 717 back in the air
  13. Could it be that the right transponder frequency knob inner and outer dials are reversed? Michael
  14. Last week
  15. @jangulo0626 It will prompt you to update when you open PACX.
  16. The folder is exactly at the location I put in the comment. Also, I apologize for the delayed response, it's been an unexpectedly hectic week!
  17. We have a fix. Lockheed Martin was able to confirm with us what it was (a texture format issue compounded by a bug in Prepar3D, it seems). We've done some internal testing over the last few weeks and it appears that it is solved. We are doing a final round of testing now, but we expect the fix to be public relatively soon.
  18. Hello, I use chaseplane for my viewing system. Flying the 717 I have had two CTD, any idea when this fix is coming? Cheers,
  19. Hi, I'd like to open a quick discussion about the FADEC here as I strongly believe the current response is incorrect (since V1.0 even) - this also explains why many people complained that taxiing was difficult. I want to make it clear that I am NOT talking about the response SPEED of the engines, as I see no issues with that. I did a lot of research into EPR FADEC systems and how engines with EPR as primary parameter respond. As you know, the EPR is not a linear function and you've modeled it correctly. However, where the mistake is, is that the throttle COMMAND is linear at the moment. Thus at lower N1s the response will be extremely sensitive due to EPR not changing that much, wheras at high N1 the response will be unresponsive due to EPR changing a lot - and indeed this is what happens in the TFDi 717. Now lets look at some information: in a classic airplane without FADEC, the response of the engine's N1 to the throttle command is fairly linear - this is good because it makes setting the power fairly easy to do, without thinking. The engine speed is fairly proportional to throttle lever. This can be observed in Flight simulator add-ons as well, I will name a few that I have experience with: - Leonardo FlyTheMaddog, all versions from FS9 to the latest FlyTheMaddog - Coolsky DC9/Super 80 series - Any stock FSX/P3D aircraft - Captain Sim 727/737/707 Now lets look at FADEC airplanes in the simulator. The throttle command "bug" does not move linearly with the throttles, but moves using the same response curve as EPR. Why? To preserve the correct throttle response, while still having the advantages of FADEC control on an engine with EPR as its primary control valve (such as these RR's). Thus, the N1 response stays linear, and the EPR throttle command moves only slightly at low positions, and more at high positions. Lets throw some examples here of again aircraft, that I have personal experience with. - PMDG MD-11, Pratt and Whitney engines - PMDG 747 QOTSII Pratt and Whitney or Rolls Royce engines - FSLabs A320 - IAE V2500 engines - Aerosoft A320 - IAE V2500 engines - Captain Sim 757 V3 - Both engine types In all these aircraft, FADEC is modelled, and the EPR bug/engine response moves how I describe. N1 response is linear, even though EPR is the primary control parameter. This allows fine control of engine power throughout all power levels. I've also asked a contact of mine who pilots A320 as captain aircraft a while back who confirmed this behavior is correct, to maintain control over the engines without difficulty. In conclusion, asumming you have correctly modelled the FADEC to have the engines followed the EPR command, I believe the FADEC's EPR command should be modified to be on the same curve as the EPR indication (as its custom coded, the default P3D one is totally wrong). I will probably making a video soon describing this behavior and demonstrating the issue exactly - I would also suggest asking your 717 pilots about this, as I would find it extremely odd if the 717 is the only airplane which had such a imprecise control system. Please let me know if you need any further info or clarifications. I really like the 717, and I'd love for this to be solved as its one of the very last gripes I have with the aircraft. Kind Regards, Josh
  20. Restricted, Prohibited and Dangerous Areas for flying What is the possibility that the PACX, software, represented in the crew or passengers the situations of danger, risk, tension, nervousness with reactions, alerts, warnings, announcements or signals when the aircraft approach or cross restricted, prohibited or dangerous areas to fly, previously included in the PACX, routes. I emphasize that the idea suggested is not to show the shoot down of planes, explosions or pursuit by fighters, but to reflect the possible reactions of a crew and their passengers. I apologize for insisting on this proposal, but I do so in the absence of an answer to it. It seems that it went unnoticed Translated with (free version)
  21. Proposal for PACX team: Hello: My proposal is that the PACX software, automatically includes the practical application of speeds V1, VR and V2, during the takeoff of the plane, and their corresponding sounds. That is PACX, should process these speeds according to the aircraft in use. In the event that this proposal is too complex because of the enormous diversity of existing aircraft, then it could be thought that PACX, offers the user the possibility to introduce the takeoff speeds for his aircraft that the software would collect and process. I will be very grateful for the attention you can give to this proposal A salute to the great PACX team. Good morning, good luck Translated with (free version)
  22. Thank You. It works. B.g. Steen Hoejengaard
  23. Eu deletei a msvcr100.dll e msvcp100.dll da pasta system32 e deu certo, tenta fazer isso, talvez resolva esse erro I deleted the msvcr100.dll and msvcp100.dll from the folder system32 and it worked, try to do that, maybe solve this error
  24. Hello, I'm still not sure how to set up the "time before takeoff" and the "flight time". I would assume the time before takeoff is from when I start PACX to wheels up on the takeoff (so includes taxi?). So if the flight time is wheels up to wheels down, how is the taxi time to the gate taken into account? If I am stuck on the tarmac for 20 minutes trying to get to my gate after landing does that mean I will be late or does it not matter as long as I landed when expected? And if I land a few minutes late, but get to the gate quickly, will I be forgiven or am I already late? Or if I take off late, but make up for it at cruise, will I be on time? I know that block timing is shown at the end, and I believe changes were made so that time can be made up after take-off, but would like to make sure I set up the time correctly at the start. Thanks so much!
  25. Hello,. I saw that many pilots in my V/A are experiencing a problem with delayed loading of the smartCARS. It is taking 15 to 30 seconds to open, keeping in mind that some v / a that I have participated in open from 2 to 5 seconds at most. What can be done, or what is wrong? Thanks
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up