Hand editing controller profiles

Discussion Hub General Discussion
,
1

While setting up my TQ for twin turboprops I came across the old problem of very slight asymmetry when it comes to the idle point, and reverse thrust.

In 2020 I would adjust the Neutral point for an axis, ensuring the white dot rested on the centre line. This usually amounted to something like 58 on one, and 60 on the other.

However in 2024, you don’t have that granularity, and it jumps in increments of 5. And to make matters worse the white dot doesn’t actually move so you have to do this blind. So I set the left to 55, and the right 60, and it works well enough. But I wanted to make it more accurate, so what I would do is hand edit the file.

In 2024, these reside here:

%LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\SystemAppData\wgs\00090000025CC6EC_000000000000000000000000604CC91B

This folder structure has other folders, some of which will comprise your controllers. For example, my TQ files is this one:

%LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\SystemAppData\wgs\00090000025CC6EC_000000000000000000000000604CC91B\C3D34C555A664F728A6BD0C708C4A608\AD432F21DD4545F285E9C5ABEF2A2871

The structure is very similar to what we had before, certainly the top part, but to my surprise I don’t see the configured Neutral points:

<?xml version="1.0" encoding="UTF-8"?>
<Version Num="-1"/>
<FriendlyName PlatformAvailability="1">TQ6 with Reverse</FriendlyName>
<Device DeviceName="VirtualFly - TQ6+ " GUID="{8A818860-ABFA-11EA-8001-444553540000}" ProductID="3490" CompositeID="0" HWVer="1.0.0.0">
	<AircraftInfo CategoryName="AIRPLANE"/>
	<Axes>
		<Axis AxisName="X" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/>
		<Axis AxisName="Y" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/>
		<Axis AxisName="Z" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/>
		<Axis AxisName="rX" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/>
		<Axis AxisName="rY" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/>
		<Axis AxisName="rZ" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/>
	</Axes>

All values are set to 0!

Compare that to my “wgs” backups from 2020.

<?xml version="1.0" encoding="UTF-8"?>
<Version Num="2440"/>
<FriendlyName PlatformAvailability="31">VirtualFly - TQ6+ - CLONE</FriendlyName>
<Device DeviceName="VirtualFly - TQ6+ " GUID="{8A818860-ABFA-11EA-8001-444553540000}" ProductID="3490" CompositeID="0">
	<Axes>
		<Axis AxisName="X" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="58" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/>
		<Axis AxisName="Y" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="62" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/>
		<Axis AxisName="Z" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/>
		<Axis AxisName="rX" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/>
		<Axis AxisName="rY" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/>
		<Axis AxisName="rZ" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/>
	</Axes>

You can see there I had “58”, and “62” configured. I’ve checked all the files that I could find, and I can see that the profile name is correct, so I don’t know why the data I see in the GUI doesn’t show here.

Scratch that! The settings are there, just further down in the file, in a structure that does not exist in the 2020 version.

		<Action ActionName="KEY_THROTTLE1_SET" ValueEvent="0.000000" Delay="2.000000" Flag="4228">
			<Axis AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="55" AxisDeadZone="4" AxisOutDeadZone="0" AxisResponseRate="-1"/>
			<Primary>
				<KEY Information="Joystick L-Axis X ">1026</KEY>
			</Primary>
		</Action>
		
		<Action ActionName="KEY_THROTTLE2_SET" ValueEvent="0.000000" Delay="2.000000" Flag="4228">
			<Axis AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="60" AxisDeadZone="4" AxisOutDeadZone="0" AxisResponseRate="-1"/>
			<Primary>
				<KEY Information="Joystick L-Axis Y ">1042</KEY>
			</Primary>
		</Action>

After lunch I will try setting those to “58”, and “62” as before. If it behaves anything like 2020 those hand edited settings will persist until you edit them in the GUI.

2

Have you considered Spad.Next?

3

I do use SPAD actually, for everything except the TQ with one exception, which is for prop feathering.

4

Can you use SPAD with 2024? Asking for a friend :slight_smile:

5

Yes, it works just as well as with 2020. If it didn’t I would have stayed on 2020. :wink:

Just make sure you have the latest beta, and the latest V5 LVAR bridge installed in Community.

1 Like
6

Tested the hand editing of the files, and it works perfectly. You can set it to any value that the GUI doesn’t allow for. I’m sure that’s already logged as a bug, but where do you even start. There are so many, but I will search all the same.