ilias.tselios

The update postponed to include X-Plane's 12.2.0 important changes. Now it is matter of finding some time to finish it.

May be it is a set up issue? Can you check is the joystick settings, when you press the right pedal, you see movement on the yaw axis?

@hukes You should use Rosetta, but there is bug described here:

Flap extension is limited to 97 knots (plus a few knots margin). The speed limits above are for flaps stationary.

Please provide more information on what is happening. I will theorize, since you said about the GTN, you are trying to follow a GPS flight plan, but the aircraft does not turn "as it should". DC-3 HSI's course indicator is not driven by the GPS, so when you reach every waypoint, you must manually set the course is prompted by the GPS the last seconds before reaching the waypoint.

Regarding the engine start, I cannot replicate the issue. Please, when happen again, post your Log.txt file for debugging. Regarding spins, I am sure that the aircraft behaves correctly up to stalls. Normally should not spin, except you force the plane into stall. Can you please describe the procedure you use in the real aircraft to induce spin, so I can see what's going on?

You press the left key next to RONAG, and then the left key at the DISCONTINUITY line, and then might require to press EXEC.

Gizmo is a part of things that needed to be updated. So there is no meaning to continue write Lua code, and re-write the everything in a c/c++ plugin is not possible right now. There are also many changes in XP12, even in the latest 12.2.0 version, that must be changed in the existing code, planemaker, etc. Needs a lot of work, which I have no time at this point.

Does this happened before activate the aircraft? If so, load a default aircraft, activate, and then load DC3. Then should not happen again. It is a known bug, fixed for the next update.

There are changes in the 12.2.0 that I will include in the update. So expect release close to when the new X-Plane version become final.

The aircraft has its own states and does not follow X-Plane's. You can read more here: https://airfightergr.github.io/les_dc3_docs/gui/#panel-state-options

Any images to show the issue? Also attach the Log.txt. Btw the support forum for C23 are here: https://forums.x-pilot.com/forums/forum/235-beechcraft-sundowner-c23-v2/

It is written with red letters at the top of the description:

I can't put it mildly, but it is not possible at this time. With Gizmo development stopped, there is no simple way to achieve XP12 compatibility. Said that, there is a possibility in the future, to remake everything from scratch in a form of payware, with complete proline avionics and more.

https://airfightergr.github.io/les_dc3_docs/commands/#pitch-trim

Which model? Classic or Modern?

First of all, Avanti is only compatible with XP11. Won't work in XP12. And yes you need to own an X-Aviation product to be able to run her, in XP11.

TDSSim GTN Xi 650 Ready!

Yes will not be there.

I found the issue. G500 plugin has changed the signature (each plugin has one), so it cannot been found and that's why you see the above. I might release an update in the next weeks fixing this and a few other things. For now, download the linked image below, and drop it into LES C23 Sundowner/cockpit_3d/generic folder to overwrite the old image. It is an empty image. https://www.dropbox.com/scl/fi/yv88qjhc04tjpuvlutbsa/RSG500-1.png?rlkey=6uknf81e1o50ywo6tuvkye5n2&st=j162n420&dl=1

March '23 or '25? I haven't try it myself yet. Please post your Log.txt.

I couldn't start working before 12.1 went final. Beyond this, 1 person, me, working on 2 aircraft support and 2 aircraft under development. Moreover, I'm slowly moving the code from Lua to Cpp, which I'm learning as I'm doing things. Mostly, the update is almost done, needs final touches to be ready.

Good! Cause I'm thinking to add support for their 650 for both C23 and DC3.

I found in their documentation that the must have own log files stored in the Windows Documents folder.

If happened at 134 kts, either the flaps were not 100% fully retracted, or some random x-plane failure kicked in. If you look the flaps limits placard, there are values for each flap position (per 1/4). Those limits are for flaps being stationary. Also the bottom line says "EXTENSION 97kts", which means that you should not try to extend at all, even a tiny bit, if you speed is much higher than 97 kts. All limits have some leeway though. You might extend the flaps at, for example, at 102kts and nothing will happen, but do not push your luck too much. At the end, we left the option to be able to reset the failure, not to make you flight more challenging than anticipated.