X-Plane 12.4.3-R1

AW109: latest patch 2026-06-09

Cheers!

About what you get at:

KHLN APPCH I27-Y SWEDD RW27

Not only is the hold sideways, also the waypoints are not aligned to the path.

For reference, I am getting it right on my PC

can you try loading it again after a restart?

Was just running through the pages and it happened.

Is this a known bug?

Is it only me or autopilot does not capture/intercept flight plan. I've created flight plan then took off following skyway than pressed "nav" button and aircraft did'nt seem to follow route.

Then I've decided to test if it will work with ILS. After choosing right frequency and setting course and pressing "nav" button the same behaviour has appeared. Aircraft did not followed the needle. Funny is that "GS" worked.

Also heading mode is still mistery to me as it does not hold desired value.

I'm aware that problem might be on my end but it never hurts to ask other players 🤣

X-Plane12 was updated with the 12.4.2 patch, AW 109 SP was updated with the 12.3 patch. All controls work correctly except for the cyclic.

The cyclic pitch and roll inputs are recognized in the joystick menu and in other aircraft but not in the 109 suggesting that the issue is in the aircraft module.

I deleted the 109 files and reinstalled without the 12.3 patch--same issue.

Multiple joysticks were tested and none of them move the in-game cyclic. The cyclic will move with the mouse, however.

Any additional ideas that may fix this problem would be greatly appreciated.

Thanks,

Regards

I am using version 2 of the AW109 and I am experiencing serious issues with the autopilot.

Very often and without any clear reason, the heading function behaves erratically and it becomes impossible to change direction. In addition, the autopilot frequently makes the helicopter perform continuous 360-degree turns, and there is no way to stop or correct this behavior once it starts and often even the IAS become crazy!

It feels like something is not working correctly with this helicopter’s autopilot system. I am confident that X-Trident will be able to identify and solve the issue, so I wanted to report this behavior for your attention.

Thank you for your support and for the great work you do.

I also yesterday was trying to follow a YT tutorial on initiating a HOV, then Climb with a flightplan to the nearest airport and including a VFR approach (added via the ND). Again, I never saw the referenced Skyway on the PFD.

Obviously, I'm doing something incorrectly. I checked the Settings and the displays are set for Standard, and the Declutter have the Skyway selected. No issues with FPS, etc.

Thanks for the assistance!

Time code in the link.

I've already added 4-axis AFCS support for the Airbus H145 and H160 aircraft for the other sim (.. I don't know what the rules are in here  ) so I am conceptually familiar with how AFCS works, though I am not a helo pilot. 

The TelemFFB application has basic support for X-Plane, for generic force trim, but I'm hoping you can point me in the right direction if there is any documentation or details you can provide around the specific datarefs needed and how to interpret them.  It would be neat to extend the FFB AFCS implementation to include the AW-109.

Happy to discuss here or via DM.

Thanks

Do you have any idea, what this is??? It seems this is a landing light.

Honestly, I didn't know that there was a XTrident bug page so I am re-posting here.

Original post: Jan 5, 2025

Hello All,

Can I please get some advice on what is causing non-stop CTD?

The Error is only with a single aircraft, the X-Trident A109SP, the flight loads, but soon after take-off the Vulkan appears.

My latest logs are attached.

My specs:

Ryzen 7950X3d (no OC)

64mb Ram

AMD 7900XTX (version 25.12.1,again with no OC), I do have Adrenaline

Windows 11 is updated to 25H2

WinWing Orion 2 Joystick and Orion Throttle Base, LogiTech rudder pedals

Just an observation...

Yesterday, I made some adjustments to my Winwing Orion 2 joystick button mapping as per the recommendation from XTrident and I FEEL that sometimes joystick input is what causes the error, is this possible? (screenshot below of the XTrident info)

History:

I have been enjoying the A109SP (it is a great helicopter from XTrident) after purchase on 12/28/25 without issues.

Yesterday, I downloaded AviTab and that is when my problem started. The error still occurs even after I removed AviTab from plugins.

I also, removed and re-installed the A109SP... AND, rolled back XPlane to 12.3.3 from the Beta.

It makes no difference on the Graphics levels either, low or high have the same result.

Still have the Vulkan error.

I also purchased the DA-64 from AeroBask and the G650 from AKD at the same time, both of these aircraft and all default Xplane 12 aircraft work normally.

Does anyone see what could be causing this problem in any of the data?

Thanks in advance!

KvK

Log.txtLog.txt

Log.txtLog_ATC.txt

I wanted to make another flight in the afternoon, but then it said there was an update for X plane 12 which I installed 🤣

then Xplane 12 Beta kept crashing with this new update from Xplane

and the cause was the AW 109 with the update for the beta version installed

I couldn't solve it, all my helicopters were flying but the AW 109 crashed Xplane 12, only if i remove this helicopter from the planes folder then x plane doesn't crash anymore

Luckily I still had a version of X plane 12 from before the update and I can fly again

So it's not just a problem with the liveries

The crash reports have automatic been forwarded to laminar

ps: I don't know which crash reports to include here

when I popout the PFD (top or bottom), the popup shows [Control Knob] in the lower right corner. Scrolling the mouse wheel over that area in the popout used to emulate the action of turning the lower right button, e.g. zoom the map. Now it will do the action of the lower left button, adjust the brightness.

I am pretty sure that worked in that past, so not sure when it changed. Using v2 with latest XP12 patch 2025-11-29.

I think the behaviour started after the v2 update, but not 100% sure. Did a fresh install with v2.

Not a huge deal, turning the in-cockpit knobs works just fine. Just the popout is affected, though I liked to make use of the popout a lot in earlier versions, which is pretty limited now without the lower right knob working.

Not sure if already reported, didn't find anything. Unlikely I am the only person using the popout. Possibily user error, don't want to exclude that. :-)

X-Plane 12.3 beta

Maybe this week-end as you work on the RNAP Approach, you might take a look too as you wish ?

Here are the reproducible steps !

First procedure [result NOT OK]

Start X-Plane

Log.txt for X-Plane 12.3.0-b4-267ef98d (build 123008 Intel 64-bit, Vulkan 318d37462270aec8b058eb92748ada6c6750d905)

Compiled on Sep 29 2025 19:24:53

Linux kernel version: Linux version 5.15.0-133-generic (buildd@lcy02-amd64-040) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #144-Ubuntu SMP Fri Feb 7 20:47:38 UTC 2025

Linux release info:

PRETTY_NAME: "Ubuntu 24.04.2 LTS"

NAME: "Ubuntu"

VERSION: "24.04.2 LTS (Noble Numbat)"

Desktop session type: x11

CPU type: : Intel Core i7-8700 CPU - Speed: 0.0-0.4 GHz - Cores: 12

MemTotal: 65547380 kB

Get the AW109SP 2.0 version. I still have OPEN/WXR.

Start the flight at YMNG Mangalore apron, Australia

Battery ... ON

GEN BUS 1 ... ON

GEN BUS 2 ... ON

RIGHT PFD ... Press any button to continue

RIGHT ND ... Press any button to continue

RIGHT ND ... Press set to display the Map mode

MASTER AVIONICS .... NORMAL

LEFT PFD ... Press any button to continue

LEFT ND ... Press any button to continue

LEFT ND ... Press set to display the Map mode

Stay on the left ND

INFO line select key .... Press

Observation : at that point, the displays show an empty information line at the bottom.

LEFT ND ... Press set

--=={This application has crashed because of the plugin: 109 1.0.0}==--

Second procedure (positive witness) [OK]

Battery ... ON

GEN BUS 1 ... ON

GEN BUS 2 ... ON

RIGHT PFD ... Press any button to continue

RIGHT ND ... Press any button to continue

RIGHT ND ... Press set to display the Map mode

Stay on the right hand side ND

INFO line select key .... Press

RIGHT ND ... Press set

Observation : at that point, the displays does not show an empty information line at the bottom. Pressing INFO has no effect if no airport, nor fix, nor anything is previously handled on the pilot side.

Third procedure [OK]

This third procedure is done with the pilot side and selecting the nearest airport.

Stay on the right hand side ND

INFO line select key .... Press

RIGHT ND ... Press set if you wish.

Observation : at that point, the displays shows some information about the nearest airport as expected.

Fourth procedure [OK]

This third procedure repeated but on the copilot side (left).

It displays the Mangalore information correctly without crash to desktop.

Conclusion : you need to prevent the information page to appear on the copilot side as you you already did it on the pilot side when no selection worth an information is previously available in the given copilot side.

sorry to report that -Plane freezes if I load the 109, load another helicopter , then reload the 109. In the console the output is :

[string "scripts/109.00.init/109.00.init.lua"]:142: Previously unresolved dataref is being written to but is an array or is still undefined.
stack traceback:
	[C]: at 0x7fe1f5f09d79
	[C]: in function 'error'
	[string "scripts/109.00.init/109.00.init.lua"]:142: in function '__set'
	[string "scripts/109.00.init/109.00.init.lua"]:378: in function '__newindex'
	[string "scripts/109.00.init/109.00.init.lua"]:72: in function <[string "scripts/109.00.init/109.00.init.lua"]:59>

I'm guessing this is the X-Trident 109 code.

Oh sorry that's only if the 109 battery is left to ON before changing from the AW109.

Best regards

When ever I try to use the X-Trident AW109 I sooner or later experience a Vulkan crash. I've tried different locations and different aircraft but the situation is only reliably reproducible with the X-T AW109 so I'll post here first.

Attached is the log and I hope someone more knowledgeable than me can give me some pointers.

Blue skies. 
Niels.

Log.txt

"--=={This application has crashed because of the plugin: 109 1.0.0}==--"

Log (2).txt

Edit:
I was able to replicate the crash--apparently it happens when selecting the NAV LOG page on the MFD.

Edit 2:
I still keep crashing from Vulkan error, similar to v1.

Log.txt

using the Version 2.0 I see a minor graphic issue when popping out the RTUs:

It seems the semi-transparent layers of the RTU display is not correctly placed/scaled in this case.

Happens with both RTUs and depending where you move the RTU on the screen the offset between the RTU and the semi-transparent layer is different.

If you switch the internal light to "Night" it becomes quite visible.

I checked with the Version 1+patches and did not notice this. Also did not notice it for the other displays.

Windows 11, latest XP12 beta.

Best regards

On the latest patch (downloaded yesterday) the LNAV button doesn't seem to have any effect. Not sure if something was changed or I forgot how to use it properly. User error not excluded. :-)

• Have flightplan, FMS active in OBS

• Be in Nav mode (PFD shows purple LNAV in bottom right)

• Turn HDG knob and press it. Will now turn to selected heading, PFD shows purple HDG in bottom right.

• Press LNAV button. Expect mode turns back into LNAV but does not

• Need to press "Nav" in autopilot panel to get back on track

Memory is blurry and I havn't flown the AW109 for a few months. But I think this had worked previously.