ilias.tselios

You are doing nothing wrong. There are some dataref changes regarding GPU, that make it not to work. We will fix this with the 2.0.4 update, in the next weeks.

When will be released, you will download the new version installer, and that one will take care of everything.

I have fixed the issue I had, and already tested in 12.1.0b2. Needs a bit of clean up, testing for any unforeseen bugs, and then getting into release procedure. Here some late captures.

Currently, we are at the final stage before releasing the XP12 full compatible version. We will make sure that will be VR compatible, when will be released.

Show tablet, and go into Avanti menu and make sure that the Condition Lever Mode is set to HW AXES and not VR/MOUSE.

I don't have any good solution to offer, but I'll try myself to find what's possible to be done with that kind of setup. If nothing good turns out, I'll see if I can add some kind of option, in the next update, to help you.

See

We are planning, for a future update, to add support for controlling the mixture levers via axis. For pitch trim you must assign the mechanical commands. https://airfightergr.github.io/les_dc3_docs/commands/#pitch-trim. If flaps does not operate after take off, most probable cause is that you have exceeded flaps speed limits, and they have failed. Pay attention to the placarded limits on the panel. DC3 has fat, high lift wings, and if you're taking off without any passengers or cargo, and you are light on fuel, takes off very easily.

Wait... I was able to reproduce it and looking into this.

If you hide the Gizmo tool tray, does other plugins menus still flashing? I don't have to reproduce, so I have to ask you to do a few things to understand what's wrong.

Please try also the Modern aircraft to check if this happens to that one as well.

Is this happening only with DC-3? You can disable Gizmo tool tray if you want by the Plugins menu -> Gizmo.

I assume that you in windows right?

Good to know that. Had no idea of such thing.

There is a bug in my code, when the aircraft is not yet activated, crashes the sim. The walkaround is to load the default C172, enter your login details, and then load DC3. Then you can load DC3 directly. The bug will be fixed in the next update.

Looks to me that the aircraft is not yet activated, right? In that case, there is a bug in my code, when the aircraft is not activated, that might cause the crash. Please load a default aircraft (like C172), put in you logging information, and the load DC-3. This needs to happens only one time, and it will be fixed in the next update.

If you manhandle the engines, it is very possible to fail. Engine performance is degraded (power output is different in a just maintained aircraft vs one which maintenance is due) as you use the engine. There is a maintenance system, you must follow to keep the engine in good condition. There is an option to enable X-Plane failures, which MTBF depends on aircraft condition. For the discount, it is an X-Aviation matter, but I don't think that is possible now to get a discount as previous owner.

Yes it's 2.0.3, it's a typo. Does this happened once? Can you describe exactly the conditions to try to reproduce it? Like airport, weather conditions, and whatever else you can remember? Also there is something (plugin or setting in X-Plane) that have write almost 30,000 lines in the Log.txt, making it impossible to find the parts I'm interested in.

Not yet. The issue is that running, in my windows machine, X-Plane in debugging mode, is extremely slow. I hope to find the solution as soon as possible, and go for release.

Without describing with details what your issue is, how we can point to the solution? There are a ton of customers that happily fly our DC3 daily, without such issue. So the case that "something is wrong with the aircraft", does not hold water. Specially for the engines start, there is a dedicated section in our online manual, you can find it here: https://airfightergr.github.io/les_dc3_docs/docs/common/engines_start/ If that does not solve your issue, please describe with details what's wrong, according to the support guidelines: https://forums.x-pilot.com/forums/topic/27109-douglas-dc-3-v2-support-guidelines/.

I'm seeing a .DS_Store in the livery list. If such folder exists (might be hidden), remove it. Also check the liveries_index.les file if has any record with that name. I should add an exception for that.

https://github.com/mSparks43/XTLua

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.

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