Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by arwasairl

  1. The .SWV files are proprietary, so there isn't a way to convert files into our format.
  2. 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.
  3. Use the paintkit provided in the downloads section, and use any tool that supports psd files, photoshop is one of them.
  4. You can install the 717 multiple times on the same computer on different platforms, it will not cause activation conflicts.
  5. I'm currently working on toning down the landing light effects, it will require a lot more tweaking than what I initially thought.
  6. 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).
  7. 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.
  8. 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.
  9. 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.
  10. Did you try to go direct to the next waypoint? (LIDEK in your case).
  11. 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.
  12. As said before in the Discord, TFDi are not planning on updating this aircraft at the moment until the MD-11 has been released and they assess newer flight simulators on the market.
  13. Open the effect file and go to any section that is labelled as [Particle.X] Change the X Scale to a set of numbers of your choosing, then save the file. Alternatively, use the FXTool provided in the P3D SDK to properly edit these effect files. See below:
  14. Please open a support ticket in the link on my signature.
  15. For reference, does PACX give any error when starting a flight? Or does PACX start a flight properly, and the HUD just reports as a PACX flight not being detected?
  16. Ensure that your parking brake is engaged and you are at the airport parked at a gate. I also advise you to try a starting airport like KSFO or KJFK, as some airports may be missing in PACX's database, which may detect your aircraft as being in the middle of a field when there actually is an airport. Also, make sure you have started a flight by clicking the Menu button, and "Start Flight".
  17. Hi Stephan, I'm assuming you've already done the basic troubleshooting steps? (uninstall, delete related files, reinstall, restart computer). Assuming you have already done that, could you try to update your FSUIPC to v7.1.0? Regarding the captcha issue, I'll let @Jishwaah know about the issues you have so that we can work things out.
  18. Hi Pr3dator, To ensure a more speedy response and elevated support, could you please submit a ticket through the link on my signature? We will get back to you once the weekday starts next week.
  19. Could you state the version of the 717 and addon manager you have installed? The addon manager version can be found by clicking the cogwheel at the top and clicking "about". The 717's version can be found in installation > and the version number will be stated under the simulator you have installed.
  20. Hi, it seems like that particular livery (N920ME) has no issues for me, however, i'm using P3Dv4. The only thing that I can speculate is that the UV maps of the P3Dv3 version is different than the P3Dv4 version. That livery may have been made with the P3Dv4 paintkit, and may not work properly in P3Dv3. @turbofandude Can you confirm this? The two extra files are not required for a livery to function properly, it's more of an optional texture map that repainters can use if they want, but is not required. Just to be clear, did you edit any of the texture maps? And does this happen with all custom liveries or just this one? I have P3D v3.4 installed, so I'll install the 717 and that livery to see if my suspicions are true. Edit: I just tried it in P3D v3.4, and I have no issues with the livery.
  21. Have you tried a reinstall of the aircraft? If that doesn't work, do you use FSUIPC to interface your hardware with the sim? Also, can you take a screenshot of your Configuration Synoptic page?
  22. Although I can't speak for the developers, since they are making the MD-11 for the ESP platform, I would assume that P3Dv5 would be supported, given that the 717 was updated to have compatibility with v5.
  23. Unfortunately, it doesn't do anything to the logo lights. Reason why it's appearing is due to the fact that the logo light is actually an emissive texture (an _lm texture), and the PBR maps is making them appear (when regular P3D materials would only make them appear at night). TFDi themselves would have to add a light attach point in their model file themselves in order for the light to be controlled via the logo light switch. I tried to make the logo light controlled by that switch, but unfortunately I don't have the source model file (and the .MDL is a compiled binary) so I don't know what the LVar is for the logo light switch (if there is any). However, although I can't make the logo light controlled, I can change the logo light to AdditiveNightOnly (which will make it appear only during night, but still not controllable). I completely forgot that I left it on additive, so I will update the model for the logo light to appear at night only.
  24. This is only compatible P3Dv4 or P3Dv5. FSX does not support PBR maps.
  • 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.