Axis tuning not being saved

[frostycab]

 After a break form flying I came back it at the weekend. As usual, I expected to need to reassign a few things, and for now it seems like assigning buttons and axes is working ok. However, tuning adjustments to those axes is being lost every time I exit DCS.

For example, I have a Virpil CM3 throttle, and have physical detents on it. In planes like the Hornet I use the lower one for idle thrust and the upper one for military power, pushing past it for afterburner. I go into the control settings, open the axis tune window and set up as a slider as opposed to axis, set deadzones and curves to match my HOTAS, and then go flying. When I'm done I close down DCS from the main menu.

On the next load ALL axis adjustments are gone. Every time. The axis is still assigned properly, but it loses reverts back from slider, has no deadzones and no curves.

Somebody on Discord suggested it could be a permissions issue with my Saved Games folder, but as far as I can see any other control changes are being saved just fine. I can remap keys, buttons and axes to other functions and they'll stay like that on subsequent reloads, which would suggest to me that the profile is being saved properly.

I have tried manually saving the profile after tuning too, but when I reload the save file the tuning is still missing. It's made flying an utter pointless chore for me at the moment, as I need to spend time setting up each aircraft before I fly it over and over again.

Any suggestions?

[MAXsenna]

Steam or Standalone. If Standalone, try to disable the launcher. If that does not work. Try to rename the DCS folder in the Saved Games folder, start DCS and make a test.
Cheers!

Sent from my SM-A536B using Tapatalk

[frostycab]

Thanks. I'm running the MT standalone version. build 59263 from 2 weeks ago. I've disabled the launcher and moved all DCS-related folders out of Saved Games, allowing the sim to create new ones. The problem still persists. I am able to change and make new assignments, and any modifications to the response curves or deadzones are fine during a session, even if I fly multiple scenarios. However, after exiting DCS and relaunching all user-defined curves and deadzones have reset to default values.

It's a real head-scratcher, and I genuinely can't see how it could be something on my end, though I'm happy if it can be fixed any which way.

[nexion]

Same issue here, user curves and other axis tune get completely lost after dcs restart, while general key and axis binding is fine.

Anyone else having this issue?

[frostycab]

Oh thank God!!!!!! It's not just me! I've been fiddling with things for nearly 2 weeks and it's driving me round the twist. It's not just the curves that are resetting, but sometimes it even forget if you've set an axis to be a slider or not.

[nexion]

Coincidently I also use a Virpil CM3 as throttle and tried to tune the afterburner gate on the Hornet.

The last weeks I flew exclusively helicopters, where I had to tune rudder and collective axis also. But I didn't noticed any problems there. Maybe I missed it, or it's a hornet or cm3 issue?

[frostycab]

1 hour ago, nexion said:

Coincidently I also use a Virpil CM3 as throttle and tried to tune the afterburner gate on the Hornet.

The last weeks I flew exclusively helicopters, where I had to tune rudder and collective axis also. But I didn't noticed any problems there. Maybe I missed it, or it's a hornet or cm3 issue?

It's in all the modules I've tried recently. Whenever I fly a helicopter I adjust the response curve to stay between my idle and mil-power detents since I don't want to use the finger-lifts to get full-range of collective, but even then in the Apache, Huey, Mi-8, and Mi-24 my curves are gone on each restart. After a bit of a break from DCS I was just in the mood to get back into it, but without a solution I can't be bothered to deal with this every time.

[nexion]

So I came up with some kind of solution here.

First I looked into those .lua files in the saved games dcs f-18 input folder. To my surprise in the cm3 throttle file there aren't even entries for the thrust axis, just zoom and TDC. In the stick file, the axis for pitch and roll are missing also. So the game must getting them elswhere. I then looked into the main dcs folder for input files for the F-18. And there are many preconfigured files for many controllers, also vpc cm3 throttle. Other modules like F-15E don't have them. So I deleted those default profile for the cm3 ( in fact copied it out to the desktop), fired dcs up, changed axis tune, exit dcs and looked in the saved games dcs f-18 profile for the throttle again. Still no entries for thrust axis and ingame all axis tune got lost again.

Now I looked into those default cm3 profile I moved out of the main dcs folder to the desktop. There are axis entries for thrust left and right. I copied those lines and pasted them in the saved games profile for the cm3.

Starting dcs and changed axis tune, exit dcs, look into saved games cm3 .lua again and voila, all changes are saved.

 

[frostycab]

50 minutes ago, nexion said:

So I came up with some kind of solution here.

First I looked into those .lua files in the saved games dcs f-18 input folder. To my surprise in the cm3 throttle file there aren't even entries for the thrust axis, just zoom and TDC. In the stick file, the axis for pitch and roll are missing also. So the game must getting them elswhere. I then looked into the main dcs folder for input files for the F-18. And there are many preconfigured files for many controllers, also vpc cm3 throttle. Other modules like F-15E don't have them. So I deleted those default profile for the cm3 ( in fact copied it out to the desktop), fired dcs up, changed axis tune, exit dcs and looked in the saved games dcs f-18 profile for the throttle again. Still no entries for thrust axis and ingame all axis tune got lost again.

Now I looked into those default cm3 profile I moved out of the main dcs folder to the desktop. There are axis entries for thrust left and right. I copied those lines and pasted them in the saved games profile for the cm3.

Starting dcs and changed axis tune, exit dcs, look into saved games cm3 .lua again and voila, all changes are saved.

 

I'm not at my computer so can't test at the moment, but I'll give this a try when I can. If MacGyver-ing it works then great, and hopefully I'll be able to get some flying done without wasting time on every load, but if it does work I still hope that someone will be able to explain what changed and why the "correct" way of doing it stopped working. 

I'll pop back and mark your post as solution once I've had a chance to confirm it.

[frostycab]

On 9/11/2024 at 8:45 PM, nexion said:

So I came up with some kind of solution here.

First I looked into those .lua files in the saved games dcs f-18 input folder. To my surprise in the cm3 throttle file there aren't even entries for the thrust axis, just zoom and TDC. In the stick file, the axis for pitch and roll are missing also. So the game must getting them elswhere. I then looked into the main dcs folder for input files for the F-18. And there are many preconfigured files for many controllers, also vpc cm3 throttle. Other modules like F-15E don't have them. So I deleted those default profile for the cm3 ( in fact copied it out to the desktop), fired dcs up, changed axis tune, exit dcs and looked in the saved games dcs f-18 profile for the throttle again. Still no entries for thrust axis and ingame all axis tune got lost again.

Now I looked into those default cm3 profile I moved out of the main dcs folder to the desktop. There are axis entries for thrust left and right. I copied those lines and pasted them in the saved games profile for the cm3.

Starting dcs and changed axis tune, exit dcs, look into saved games cm3 .lua again and voila, all changes are saved.

 

Yeah, I'm sorry to report that I'm not having any luck with that particular method, though I will (tentatively for the moment) say I've found another possible solution. Normally I tend not to update the firmware on my VPC devices as I remember someone saying that you always need to fix all your input luas due to the hardware ID changing when you do so. Since I was having to remap my controls for each new session anyway I thought I'd try it and it seems to have done the trick. I've only made a very quick test so far, and will need to confirm everything when I have more time. It's kind of the nuclear option, but also not .

[Andrew u.k.]

Did you find a fix for this? 

Cheers