ilias.tselios

From the KAP-140 Pilot's Guide: We simulate the software versions 03/01 and later, so you have to push and hold the button for more than 0.25 seconds.

Bummer... has from the outside though! Will be fixed with the first update.

Yes, @Goran_Mis working on it.

Let me say a few things about the criticism towards our DC-3. First of all, any criticism is welcomed. Even harsh ones; we can skip the harshness and see if there is any value into them, that will help us to improve. We understand that not everything is perfect and complete. Personally, I can't recall any release that was so successful that the aircraft never needed an update or fixes. On the other hand, the aircraft is far from unusable. About price: There is some criticism to be too high. You'll decide about this, but keep in mind that you get 2 aircraft, not one. While there are a lot of common elements between the two, also there is big divergence, not only on the visual part, but also to how the systems operate from the base level. For example, more than 5,000 lines of (lua) code is only for the Modern variant. There are things that might not be visible on the first sight. For example, the radio stack on the Modern variant. Except the GPS which is based on X-Plane 530 (with also support for RXP 530, and option to use the 650 instead), all other units are simulated to 95+% compared with the real life units. Include all modes, and all operations, from how to set the baro pressure on the autopilot, to store and recall stored frequencies in the COM2 radio, to OBS function on the NAV2, timers for NAV2 and 2 ADFs, to how to change your transponder ID, which initially is set by the tail number of each airframe, and much more. We are working now, harder than ever, to bring to you the updates as soon as possible, and also add things to cover user specific needs. We are deeply appreciate the money you pay for DC3, and will continue to fix and improve DC3.

@Rhinozherouslooking into adding the option into Options tab. You'll have to enable it to work with commands. The only culprit for this update is that this option will not be saved, and must be enabled for each flight. My thinking is to save some options into a separate file, so they are the same across all aircraft and airframes (liveries), and not be different for each one. Working now on this to try squeeze it in the first update.

Thanks for the feedback. Need to check why this is happening.

Why not? How says than a user cannot have a good idea? Personally, I believe that I don't have the whole knowledge of the world, and I want to hear ideas. And I might be able to squeeze this into the first update.

Thank you!

Working to finish an quick update for a few things, and I will do that for the next one. Updates will in come very fast. If understand correctly, you would like something like up/down commands to move the lever through the 4 positions, cut off - auto lean - auto reach - emergency?

Left mixture: Pad toggle dataref: les/dc3/engine/controls/L_mix_pad Mixture lever axis dataref: les/dc3/engine/controls/L_mix_lever Right mixture: Pad toggle dataref: les/dc3/engine/controls/R_mix_pad Mixture lever axis dataref: les/dc3/engine/controls/R_mix_lever

https://forums.x-pilot.com/forums/topic/27106-activate-state-not-working-airplane-in-general-not-usable/?do=findComment&comment=194200

It's a problem that we are working with Laminar to solve as soon as possible. The issue is on their side.

We've tested everything with special debugging X-Plane versions, which throw some physics error, which make no sense (except Austin probably). Laminar has the aircraft to conduct their own tests, as well. We are looking into it, and the fix will come from Laminar's side. Can you try again, but without VR?

Yes, does not happen to all, and does not happen always. Usually affects machine on the mid-low spec spectrum, and I'm working with Laminar to solve it. It is a bug on their side.

The problem might be logged into Log.txt.

If you have any issue, please follow the steps below: Check if the issue you have is already reported. You might find the solution there. Open a new post and, please, describe your issue as detailed as possible. The more info we have, the faster we can resolve your issue! ALWAYS include your Log.txt file and the DC3.log file, you will find in the Douglas DC-3 v2/resources/data/ folder. Read the online manual: https://airfightergr.github.io/les_dc3_docs/ You can also find us on our Discord support channel: https://discord.gg/fdmJxHkcJ7

@Rhinozherousjust checked your files, and I see activation failure. May be @Cameroncan have a look.

Could you please post your Log.txt and DC3.log file, as indicated here: https://airfightergr.github.io/les_dc3_docs/support/ ? Just replied to you on the other thread.

We make sure for the initial release, mixture controls work as they should in the 3D cockpit. Because those controls are not supposed to used to much during flight, there is a luck of support for controls like Honeycomb Bravo, and supporting all the types of existing controls is in our TODO list. I will come back to you with some info in a bit, but also I would like to have a bit co-operation from you side, on this specific issue. I think is easy to understand that is impossible to test all existing control set ups and support them from the get go. Is it possible to assign to the levers a custom dataref?

Re: GTN750 The unit does not fit within the current layout, as @Pils pointed out, so we added support only for the 650. We might be able to add the 750 in a future update.

Paintkit will be available soon after release. But due the special livery/airframe concept, please read the online manual. https://airfightergr.github.io/les_dc3_docs/liveries/

What I can say at this point is that testing has been concluded and we are heading for the final preparations for release. So you'll not keep that money much longer!

On hold until DC3 release.

Finishing DC3 and immediately pushing C23 for XP12 for release.