You do it; you found it. I tripped over it. Well done!
In this case, I would walk over to the dev and put the bug # on a sticky on their monitor. It impacts anyone who has both Store and Steam, so it’s a biggie.
I started wondering if I could simply map a Standard aircraft (Store copy) FIRST, then the Aviator aircraft from Steam would Inherit the mappings, but I don’t think there’s a workaround for this one.
I think that’s a Virpil ‘feature’. Not had a similar issue with anything else.
As a counterpoint: I run a Virpil stick and throttle, I’ve updated firmware occasionally, and I’ve never had FS20 or FS24 lose my bindings after a firmware change.
That’s not true. I’ve been flying DCS for over 15 years with the TM Warthog set and almost no software update has deleted my control inputs in that time. (DCS does not release firmware updates for controllers, e.g. TM, software updates only)
However, it has happened that a major software update for an aircraft (basically a new aircraft type) has changed the control inputs. This disadvantage is offset by the advantage that a backup of all controller inputs can be made very easily.
Where are the controller inputs stored in FS 24? Answer: Somewhere in the cloudy sky.
As with every new or modified aircraft in DCS, there are at least default settings that can be changed on one - just one - data page. No obscure, incomprehensible categories or profiles that you created out of sheer desperation to save your settings.
I hear it’s not an issue. I have Virpil kit, and it happens every time.
Believe it or not they’re in your AppData folder, in xml formatted files. Mine are also backed up to my NAS in case anything happens to the cloud versions.
OK, you make backups on your PC, that seems clever. But, there is the cloud. It has happened to me several times that my changes were overwritten with cloud content or even deleted, without any apparent logic. A backup is of little help in this case.
By the way, DCS does not overwrite the settings for an existing aircraft during a general software update. Only when the aircraft itself receives an major update (e.g. Black Shark II to version III). Then the existing settings are overwritten with “default” settings. Then I use my backup.
My AppData folder is empty for both FS20 and FS24 - both are MS-Store versions.
C:\Users\paul3\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\AppData
Where else could they be hiding?
Same issue here, no resolution because I understand that the sim cannot identify the quadrants as different devices. My config also reverted to default logitech/saitek default on the second controller every time.
No solution that I am aware of so moved the saiteks out and pulled in my old ch multiquad … sigh.
I have the same problem and it’s not just because there are two throttle quadrants. I have one vjoy device (a Space Mouse) and it always goes back to a default profile called “Tobii” no matter how many times I try to make it stick to a new general profile. It happens whenever I change planes or restart the sim. I’ve deleted my cloud data and started from scratch, but the bug persists. It’s absolutely a bug and not a UI design issue.
So, I tried what I thought might work, which is to use HIDHide to essentially “hide” the two quadrants while allowing the vJoy version of the two of them mashed together. Works great. Now I can use the vJoy version and the sim never even sees the quadrants by themselves. Problem solved for me at least.
It seems that after SU1 today, I can now save a different profile for my Vjoy device, and it no longer defaults to “Tobii” every time I restart the sim or switch to a different plane. Maybe that particular bug is fixed.
Bugs with the control profiles are just so random. Today my key bind (keyboard slash) to toggle the drone camera, which has worked for weeks, now suddenly no longer works. I find it’s no longer bound, although all of my other custom keybinds are still intact.
So I remap it, but it still does nothing. I tried the default mapping (Ctrl-X IIRC) and it does nothing either. The only way I can toggle the drone camera is by using the camera icon in the toolbar.
I won’t be surprised to find that the next time I boot up, it’s suddenly working again. Things like this happen all the time. I don’t understand how issues come and go like this, unless it’s because changes are made and streamed out without us being aware of it.
My custom controls are now sticking with the c172 after resetting since launch, Beta SU1
Hi everyone. Seems like this thread has been running for a while, so I’m hoping someone can explain a couple of things to me so I can avoid reading through the whole thing.
- Does “set as default” mean set as default for the current plane? Or for the whole game?
- What can this system do that the 2020 system + a button for “set as default for current aircraft” couldn’t do?
I’ve been kind of limping by with the bindings over the short life of this sim so far, but the more I use it the more it confuses me. It seems to actually go in the opposite direction of what I think would have made sense, which is to have a set of bindings that you could duplicate and change and then apply to a specific plane so that each time you got in those were the bindings you got. The way it seems to work now seems overcomplicated, like I have to keep track of all my peripherals PLUS which category they fit into PLUS which one of the profiles in each category I need.
I’m just looking for a way to have a set of bindings for each plane that loads in each time I get in that plane. Is this possible under this regime?
Thanks!
Yes that is exactly how it works now.
The “Set as Default” is only really useful early on. It will make that profile the “used” profile for that category (airplanes, helicopters, lighter than air etc) for that device for any NEW planes you install (that fit in those categories) in future.
As far as I see it will NOT override any specific planes you have already configured (meaning any you’ve manually picked a different profile for) already.
Do you mean the system as a whole? The main improvements are that it will switch to the profiles you want and have assigned automatically when you change to another aircraft.
And that you can edit bindings in the cockpit without pausing which is actually really useful for testing and setting up a new plane especially if it has some unusual or complex controls that most of your other rides don’t.
Both those things are huge time savers.
Overall I much much prefer this new system now. Its reliability in not wiping out all your hard work and time is still to be proven though.
I think the main source of confusion is in them firstly splitting out the categories (airplanes, helicopters, lighter than air etc) and secondly splitting out the TYPE of controls (General, Aircraft, Plane Specific or whatever they call it).
Once you accept that and get your head around it, honestly the system is rather good and powerful.
-
General = sim commands like pause, camera stuff etc. not anything to do with functions in the aircraft.
-
Aircraft = all the actions and interactions to operate the vehicle.
-
Specific = I don’t think it’s even used yet. Not in any aircraft I’ve got anyway. It would be in future custom commands that are unique to ONE plane such as maybe… I dunno, deploy parachute. Basically things that do not appear in their list of “searchable” definitions already. I think!
As for why they split out the aircraft types, I’m really not clear about their thinking there because for example Helicopter Collective is STILL available in the Airplanes category and saves into that category if the developer has not assigned their product as a Helicopter.
But I think it’s mainly so you can assign the “default” for helicopters (or apply to all) and when you BUY a new helicopter (assuming the developer has declared it as such) it will automatically pick up your dedicated default helicopter profiles for all devices that you’ve already made. So you won’t even have to do anything.
Personally even though I do have a lot of Payware I still set them up manually first time I fly each as it only takes a few seconds and I know what I’m getting then.
The only defaults I have is for my pedals, 360 contrlller (for camera stuff) and keyboard, as they are always the same for every aircraft so I’ve set that as default and apply to all for each category.
Does that help? Ask more if you need
Thanks for taking the time to write that out!
So if I have it right: If I select a particular “general”, “airplane controls”, and “airplane specific” profile when I’m in a particular plane, each time I get into that plane that set of three binding profiles will be set, right? I don’t have to click “set as default” or “apply to all aircraft” for that to work?
In 2020, what I had were profiles for: Single engine piston, twin engine piston, single engine turboprop, and so on. Since it was easy to duplicate and “save as”, I was able to use those basic profiles and make specific profiles such as “Comanche” or “Kodiak”. The only thing the system was missing for me at least was an ability to tell the sim “use this profile when I’m in the Kodiak” or “use that one for the Comanche”. Now in 2024 it seems to work that way (the plane is the center of what profiles are set), but I’m still not understanding why it’s split into general/airplane/specific. Couldn’t you just have all of those things in one profile and just add or subtract things as you needed for each plane? I suppose it would be quicker if you had a bunch of planes that required the exact same configuration of general vs. airplane controls, but that seems like a long way to go to solve that little inconvenience. It’s this confusion that leads me to think I might be missing something about the 2024 system. If I’m overthinking or underthinking and it makes sense then I’ll merrily go on my way.
(One reason why this is difficult for me is, on some planes that I fly a lot, each time I go back in the keyboard has reset itself to the 2024 traversal one and I’m not sure if that’s a bug or a feature but it doesn’t happen on all planes)
No worries at all! Happy to help.
Yes, 100% correct. You don’t need to click Set as Default or anything else. Just go to the plane you want, cycle the 3 profiles (per device) and it will remember that next time you go into that aircraft.
Yes, that is exactly how I have done it here too. For throttle I have like you wrote. For yoke and joystick I have one that is called “None” (or Disabled) so for a yoke plane, I disable my stick and vice versa.
And yes, once you have your ‘core’ assignments saved to new named profiles, if you are in an aircraft you want to branch off a NEW profile with other stuff, you can pick one of those you already have (that is closest to what you need), press the button on the right of it and Duplicate it, give it a new name and edit that one with new bindings and that will then be available for any other aircraft (so name it sensibly, but you can RENAME them later if you want to tidy up).
You might want one for JUST the Comanche, so name it “Comanche Throttle” or whatever and job done.
The reason is that (just taking Throttle for example), if you had your twin engine, 4 engine, single engine, Comanche, Wilga etc etc set up THEN decided you want one button to bring up the VR Toolbar (that is a General control, not a Aircraft control), you would have to go into EACH ONE and add that. This way, you only need to add it in ONE PLACE (General Throttle) and as that one is assigned already in your sets of 3 on every aircraft, it’s done in one place and job done again. It’s good!
Yeah I have had a FEW times that it resets, but I figure it is either a bug (hence me saying the reliability is still to be proved long term) or (and I think this is also true) the profile sets are assigned PER VARIANT in the aircraft.
I have DEFINITELY set up a few planes and then next time I go back it is not what I set. But I have usually changed livery or gone from Trike to Tail-Dragger version or something like that. Might be something going on at that level but it’s not so clear.
Also I have a bug now that if I click Apply To All the game CTD’s. Never used to. But you could definitely try that if you made a profile that you know you want for ALL or MOST planes, then hit that and just manually change back the ones that you wanted a different profile for. That might kick it into behaving. Especially for Keyboard that should be safe as nobody has different profiles for keyboard per plane lol