Jump to content

ilias.tselios

Members
  • Posts

    896
  • Joined

  • Last visited

  • Days Won

    81

Everything posted by ilias.tselios

  1. Due to customizations needed to make systems work properly as in the real aircraft, some custom commands and datarefs are used... widely! It is recommended to create a separate controller profile for DC3, since you need to assign some custom commands. For example, for the tail lock you will find it here: https://airfightergr.github.io/les_dc3_docs/commands/#tail-wheel-lock. For pitch trim you need to assign not the "default", which refers the elecrtical trim, but the mechanical: sim/flight_controls/pitch_trim_up_mech Pitch trim up - Mechanical, not servo. sim/flight_controls/pitch_trim_down_mech Pitch trim down - Mechanical, not servo. Mixture levers' pads are designed to be operated in the 3D cockpit only. Mixture up/down commands circumvent the need to operate, so you don't need to be assigned.
  2. The "dark cockpits" issue, is a known Laminar's bug which will be fixed some time in the (near?) future. Some aircraft with small windows and dark textures suffer from that the most, like the DC3. I have created a FlyWithLua script, that hacks X-Plane to fight this, as a short-term solution. I'm attaching it here to give it a try. To install it, drop it into X-Plane12/Resources/plugins/FlyWithLua/Scripts folder. I'm waiting to get 12.1.0 in my hands to see what might will be changed, and see if I can include a more permanent solution into 2.0.4 update. bright_cockpit.lua
  3. Almost everything is ready, but I have a crashing bug(?) on windows that I'm investigating. As soon as I'll fix this, will be released.
  4. I'll try to find some time, to try the minimum to make her working in XP12, but no promises about when.
  5. If has Gizmo, I assume it is X-Avaition product. To amend functionality, where is possible, I will only go with c/c++/rust solution. Not because any issues using Gizmo/SASL/FWL in one acf, but because of performance. Having too many interpreters running at the same time, won't be nice.
  6. I don't know if someone here can help you. Better ask over FF official forums.
  7. As @Pilspointed out, get the right file and either contact X-Plane support (https://www.x-plane.com/support/), or file a bug report (https://www.x-plane.com/x-plane-bug-report-form/). Also make sure that you have installed the latest drivers for your graphics card.
  8. Every time X-Plane starts, creates a Log.txt file inside X-Plane's folder. Next time if hangs, please post your Log.txt file here, to see if gives any clue.
  9. You should probably contact Laminar's support: https://www.x-plane.com/support/
  10. Actually yes. Was on the back foot to release DC3, but now is getting ready. I'm implementing new UI, and as soon is ready, will go for release.
  11. Yes, looking so. Time for testing!
  12. With X-Plane 12.0.8.beta1 (and 2), a few system changes has been introduced, which affect DC-3. With that in mind, we have to clearly state that, Leading Edge Simulations DC-3 v2.0.3, officially supported version is X-Plane 12.07. We are gathering info at this point of what changes needs to be done to be compatible with 12.0.8 and beyond. We are started working on DC-3 v2.0.4 version, that will support X-Plane 12.0.8 (stable) and above. Will not be compatible with X-Plane 12.07. The release of 2.0.4 will happen, after 12.0.8 become the official X-Plane current version. As of now, the known issues are: GPU is not working. Fuel tanks selection does not work properly. If you tested DC-3 v2.0.3 against the beta versions of 12.0.8 and have any issues, please post them here, so we could gather them all, and fix them. You can also post them over our discord servers. Other issues not fixed with 2.0.3, will be included in 2.0.4. Thank you for your patient! Ilias Tselios
  13. I will make a 2.0.4 update to fix this, and a few more stuff in the next days. Seems libacfutils are not forgiving to such errors!
  14. Hm, yes... that's wrong, though it is called only if DRM has failed.
  15. G500 should not be installed in DC-3. I don't know if that's a installer bug, but please remove it. I will inform X-Aviation to check it though. Also, please post any issues at the dedicated support forums: https://forums.x-pilot.com/forums/forum/280-douglas-dc-3-v2/.
  16. There is a nice video from FlightChops, learning to fly the DC3 with "Mr. DC3", Dan Gryder. The take offs and landings are with crosswind, just check how much yoke to the left he puts during take off.
  17. Cool! Yes, FO's attitude indicator is rolling the wrong direction. Fixed for the upcoming, 2.0.3 update.
  18. Which sound package are you referring to?
  19. First of all the online manual about the KAP-140 autopilot, provides you a link to download the official manual, for how to operate it. The KAP-140 is coupled with the KI-525A HSI, but the GPS unit(s) does not provide steering commands directly to autopilot. In short, when the autopilot GPS hints you, before any turn, to set a new course, you have to set it manually, in the HSI. And then the autopilot will follow perfectly. If you don't do so, the autopilot will see the deviation, and will follow a heading (usually 30 degrees left or right of the current course on HSI) to try to capture the leg, but since does not have the correct course dialed in, this will never happen.
  20. @Erny_Modulewill be fixed, plus a few more things, but won't be available "next week". Also will require some livery tweaking as well.
  21. @Erny_Module, @Goran_M will have a look.
  22. No, but what's in you mind?
  23. Ah... haven't being enabled yet in the code. Working on this right now. Stopped in the middle of this testing Austin's builds. Should be ready for this release, probably around the end of the week.
  24. More updates are coming... stay tuned!
  25. I have created an "unofficial" one, with UV maps and AO layers. See if helps, until the official is ready. https://www.dropbox.com/scl/fi/cptz1ejcq2w8m8fbpo7w9/DC3_Paintkit.zip?rlkey=xof406hz2ax2amx066f1h0niz&dl=1
×
×
  • Create New...