Jump to content

arwasairl

Moderator
  • Posts

    30
  • Joined

  • Last visited

Recent Profile Visitors

386 profile views

arwasairl's Achievements

Explorer

Explorer (5/12)

  • Reacting Well Rare
  • Week One Done
  • One Month Later
  • One Year In
  • First Post

Recent Badges

12

Reputation

4

Community Answers

  1. The low speed protection in the 717 comprises of a stick pusher and increasing throttles to prevent the aircraft from stalling. It activates when the aircraft is close to the "barber pole", in a yellow section of the speed tape. During stall, the aircraft pushes the stick downwards to recover from the stall. The same goes for high speed protection, when nearing overspeed the aircraft reduces throttle. To avoid a low speed protection situation, you just need to make sure your aircraft is fast enough so that there won't be any situation where the speed protection would be activated. There isn't any way to disable the protection.
  2. We are working on an update that adds more languages and voices to PACX. As far as the user interface goes, we might consider adding other languages as well, but at the moment we're focusing on the voices. The files are proprietary to protect the files from being copied and used in other programs, though we may consider adding the ability to create your own voice pack. It is currently too early in the development stage to tell however, as we are developing tools to aid us in developing the next update for PACX. Stay tuned for more updates, as they will come out!
  3. The 717 is EOL (end of life), we do not intend to update it at the moment. We will still provide technical support as well as sell the product, but it will not see any large updates. We are currently working on the MD-11, smartCARS 3, and a PACX update, but once these things start to roll out we will most definitely consider making a newer version of the 717.
  4. The .SWV files are proprietary, so there isn't a way to convert files into our format.
  5. Does it say "WX" on the bottom left of the ND? If it doesn't, then the weather radar isn't on. If it is on, make sure your gain isn't too low and your tilt is set appropriately.
  6. Use the paintkit provided in the downloads section, and use any tool that supports psd files, photoshop is one of them.
  7. You can install the 717 multiple times on the same computer on different platforms, it will not cause activation conflicts.
  8. I'm currently working on toning down the landing light effects, it will require a lot more tweaking than what I initially thought.
  9. Most of the SIDs you've chosen to fly are also quite erratic, and do note that P3Dv3 is quite different from its 64 bit counterpart. I've just flown that departure out of MMLP, runway 36 and the ONGEX 2B departure. Heres a video. Yes, there are issues with the ND making extraneous flightplan lines, however the autopilot reacted accordingly, and I did not get any of those autopilot oddities that you have. The only thing I can think of is either a software difference (TFDi 717 x64 vs TFDi 717 x86), or a platform difference (P3D v4 vs P3Dv3).
  10. I put in the SID KAUA4B, then go direct to LIDEK. I set the speeds to 287 and altitude to 5000, and I put my arrival airport as KSFO ILS 28L, random STAR. Though admittedly I did not finish the flight after LIDEK, as the approach was just a test.
  11. From watching your videos, the flight looked fine (I've done that flight many times, it's why I wanted you to do it to see if there was any abnormalities). The autopilot limits it's bank angle up to 25°. You can manually set the bank angle to be 25° all the time by switching the bank angle selector on the heading knob from AUTO to 25. Unfortunately, you can't change how much the autopilot turns > 25°, as that's by design. I will have to let someone see if their autopilot performs the same as yours with these SIDs. Edit: I just flew the MMCT SID myself (KAUA4B), with the same V-Speeds, departure, runway, and went direct to LIDEK after the SID. The aircraft had no problem tracking the route, and it was flying fine. It went through CZA0 and CZA VOR perfectly fine, without cutting randomly. All I can assume at this point, is either a weight difference, or a flightplan oddity. All I can recommend is to try to use a higher altitude restriction, plan your departure AND arrival in the FMC at the ground, then fly. Do not edit the flightplan while flying, as it may cause the aircraft to start a direct. The 717 will not see an update as of now, as the MD-11 is currently being worked on. If you still have problems with the autopilot, please contact TFDi through the support ticket system, and refer to this forum thread.
  12. The 1st video, the aircraft is trying to determine if left and right is a more optimal route, hence why it's bouncing like that. The 2nd video, the aircraft was for some reason tracking the waypoint and not the route, so it was waiting to overfly the waypoint; then it became too far out and had a much greater turning radius to overcome. The 3rd video, happens time to time, I've had it happen with other aircrafts like the 737 on the SUNOL1 departure, where the runway restriction and the waypoint SUNOL have abnormal speed restrictions, and VNAV is bouncing between routes. The 4th video, I'm honestly not sure what's going on with the autopilot. Last thing, can you try out this route with the 717? KSJC TECKY3 SAC TARVR1 KRNO Change the altitude restriction of MLPTS, SPTNS and TECKY to your cruise altitude. Ignore any messages that may say Unable Cruise ALT. Use the SPOON transition for the TARVR1 arrival. Please come back with any findings.
  13. Did you try to go direct to the next waypoint? (LIDEK in your case).
  14. The latest AIRAC cycle is of June (2106) but the cycle shouldn't make the autopilot perform any worse. Does this happen on every SID or just one specific SID? I recall you use P3Dv3, and I had an issue with the FSL ConcordeX's FD banking left indefinitely, and was relegated to that INS flightplan. I suggest you try to fly a different SID, maybe use different thrust configurations as well. Also try engaging the autopilot very early (400 ft AGL) to see if it behaves like what you described. Also make sure your route isn't filled with weird altitude/speed restrictions.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.