ilias.tselios

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.

You may try to toggle reflections to low, to make instruments more readable. https://airfightergr.github.io/les_c23_docs/gui/. It is very well known across X-Plane's community that, currently, there is an issue with X-Plane's dark cockpits. Also it is very well known that Laminar is working to fix this, hopefully in the next update.

Please provide detailed feedback to be able to help you.

After installing the DC3, run X-Plane but load one of the default aircraft, like the Cessna C172. You must get a window to enter your X-Aviation login details. This will activate the DC3. The load the DC3 and should work. You Log file shows that has not been activated. 0:00:56.104 G64: debug: GK: Load license from disk.. 0:00:56.104 G64: debug: GK: 404: license database 0:00:56.104 G64: debug: GK: Empty license file. Defaulting to login page. 0:00:57.097 G64: debug: No license for: (Leading Edge Simulations)(Douglas DC-3 v2 Published by X-Aviation) 0:02:44.229 G64: debug: GK: Requesting license update.. 0:02:44.229 G64: debug: GK: update_license() 0:02:44.229 G64: debug: GK: No valid auth token, manual login required. Currently there is a bug in DC3 that crashes if you load the aircraft when has not been activated. Fixed for the next update.

Seems that DC3 has not been activated. Load a default aircraft and should get a window to enter your X-Aviation account login details. After the account is activated, load DC3 and should work.

https://www.x-plane.com/kb/using-x-plane-11-addons-with-x-plane-12-on-mac-systems/ Gizmo plugin, that used to code all DC3 systems, UI, etc., is no longer developed, so is not going to have an ARM compatible plugin. I've already started to create my own plugin that is ARM compatible, and moving the code from the Gizmo plugin, but this procedure will be long and won't happen overnight.

Because DC3 uses Gizmo plugin, you must run X-Plane under Rosetta to run.

Looking to find sometime to do a couple more fixes to cut a new release. Trying to do as fast as possible.

Depending on the lighting. If the instrument is backlit, will look brighter even in the day if you turn on instrument lighting. Here though, the instruments are not backlit, but each one has 1-2 lamps in front that cast light on the instrument. This light has no effect under day lighting, because of X-Plane.

Which plane?

In the Autopilot section, has a link for X-Plane's S-TEC 55 autopilot documentation, how's operation is identical. Here's the link: https://www.x-plane.com/manuals/S-TEC_Autopilot_Manual.pdf Also, there is a video tutorial for the Autopilot from Philipp, the guy who code it for X-Plane:

OK, it is a peculiarity of the Autopilot. You have to be below the glideslope and in ALT mode. Then press the APPR button and you should get both ALT and GS indications. When the glideslope needle is about 1/3 above the center, you must press the ALT button. The ALT indication will go away and only the GS will be visible (regarding the vertical navigation). Then the aircraft will follow the GS to the ground.

Do you mean does not?

You don't get glideslope deviation, or the autopilot does not follow the glideslope?

Sure she does! Check the online manual and if you have any questions, please ask! https://airfightergr.github.io/les_c23_docs/

@blondejfx there is an initialization issue, which will be fixed in the next update. Until then, there is a walkaround: Let the GTN650 to boot up normally. When you pass through the initial screens, you'll end up as your pic above. Let the unit to turn to COM mode. Press the small FMS knob to go into NAV mode. Turn the volume knob all the way down. Now turn the volume up. The NAV is now powered.

Thanks for reporting. I will look into this and let you know about a solution.

Open the file LES C23 Sundowner/objects/cockpit_objs/LES_Sundowner_cockpit.obj with a text editor (preferably something like Notepad++). 1. Search for "les/C23/avionics/gtn650/home" and change it to "RXP/GTN/HOME_1". 2. Search for "les/C23/avionics/gtn650/direct" and change it to "RXP/GTN/DTO_1". This will fix the issue. Of course will be fixed in the next update.

I added an option to control flaps via axis. I will try to release the update as soon as I can.

Very nice setup! I hope to enjoy it, with the Sundowner as well, to the fullest!

The tablet is stored behind copilot's yoke. See here in the online manual. https://airfightergr.github.io/les_c23_docs/all_acfs/lowrightpanel/. About the flaps, I will do some research and let you know. Probably you might need to setup axis with detents.

Correct. It's a bug that is to fix in the next update I'm working on.

I have started working (slowly) on the update and this is already done.