Mapping control inputs

[badhorse]

I am having a continuing problems with mapping controls. Specifically I map the controls and save the profile. But when I return to it, everything has changed. Example: I mapped my X-56 Joystick, Throttle and Thrustmaster Rudder Pedals for the F-18. I set it up exactly how I wanted it. I flew it and everything worked fine. I quit the program. When I started it up again, I loaded the F-18 profile. But when I started a mission, nothing worked or it worked incorrectly. I mapped the thrust lever to my X-56 Throttle but when I move the throttle the thrust lever doesn't move but the cockpit joystick moves instead. Nothing works as it should. I went so far as to delete the entire program and re-downloaded and installed it again. But after mapping the controls, the same things happen again. No matter which switch, button, slider or dial I assign and save, it always is screwed up when I load it. I shouldn't have to map the controls every time I want to fly. I must be doing something wrong, but dang if I can figure out what it is.

[Flappie]

Hi badhorse. What are you calling "loading the F-18 profile"? Are you using an external Saitek/Logitech software to bind controls or do you only rely on DCS?

[badhorse]

I ran the Logitech software to test out the controls when I first got them. But I set them in DCS. I went through the different action items and assign the ones I wanted. Then I "saved the profile" under F-18. This created a file F-18.diff.lua  When I ran the program again the file was there and I selected it. But my problem is still there. Since I reloaded the game, this is the only profile file there so I don't understand what is causing the change. I was under the belief that you could create a separate file for each model of aircraft. But if I am having this much trouble with only one, I am not even going to try an map controls for any other airplanes. 

[Flappie]

Actually, you don't need to "load profiles". I've never used this button, and probably never will.

 

Here's how to do it: when you get to the controls menu, first select the aircraft you want to configure in the top-left combo box (ie. "F-18 Real" or "TF-51D Game"), then modify controls to your taste, hit "OK" and then you're done. It will work. Launch an instant action mission and see.

 

Then, when you restart the game, you don't have anything to do (no "load profile" or anything else): launch any mission and your controls will keep working.

 

If you need to make backups of your controls, simply copy your Save Games\DCS\Configu\Input folder and paste it into a backup drive.

[badhorse]

Okay, thanks Flappie. I'll give that a try. 

[badhorse]

Maybe I should go back to Aces High.  I deleted the input files so I could start fresh. I loaded the game and completely re-mapped my Throttle, Joystick and Rudder Pedals. I saved the profile. I quit the game. I then started the game, made a quick mission and started it. It opened with me sitting on the ramp with a cold F-18 as it should. So before I did anything else I moved my throttle forward. In the cockpit, the throttle did not move but the control stick did. Same old thing. I am at a complete loss as to what is causing the mapping to change. But DCS is unusable for me as it is.

[Sr.]

51 minutes ago, Flappie said:

Actually, you don't need to "load profiles". I've never used this button, and probably never will.

 

Here's how to do it: when you get to the controls menu, first select the aircraft you want to configure in the top-left combo box (ie. "F-18 Real" or "TF-51D Game"), then modify controls to your taste, hit "OK" and then you're done. It will work. Launch an instant action mission and see.

 

Then, when you restart the game, you don't have anything to do (no "load profile" or anything else): launch any mission and your controls will keep working.

 

If you need to make backups of your controls, simply copy your Save Games\DCS\Configu\Input folder and paste it into a backup drive.

This is how I "used" to do it as well. But lately I find that if I start the game and go straight to controls, select a plane, program (even save), then the next time I restart...poof, all gone.

 

What I do now is, start game, load a quick mission, ESC, THEN go map controls.

[Sr.]

9 minutes ago, badhorse said:

Maybe I should go back to Aces High.  I deleted the input files so I could start fresh. I loaded the game and completely re-mapped my Throttle, Joystick and Rudder Pedals. I saved the profile. I quit the game. I then started the game, made a quick mission and started it. It opened with me sitting on the ramp with a cold F-18 as it should. So before I did anything else I moved my throttle forward. In the cockpit, the throttle did not move but the control stick did. Same old thing. I am at a complete loss as to what is causing the mapping to change. But DCS is unusable for me as it is.

I feel for ya man... I also have an X56 and lately something is just "off".

 

I started a whole rant thread about it...(

Up until a week or so ago I had several custom binding, macros etc inside the X.56 HOTAS but primarily used the manual mapping via the DCS menu. All was fine...)

 

NOW after several frustrating hours/days of seeing exactly what you're describing, I have cleared out all of the X56 software profiles I had, choose their default profile before starting DCS. Then start game, load a quick mission, ESC, THEN go map controls. Save to a separate folder with a unique name like MY X56 a10 throttle etc.  Haven't had the issue repeat since.

[badhorse]

It keeps getting curiouser and curiouser.  I tried what was suggested but the results were unchanged. Move the X-56 Throttle and the throttle in the cockpit did not move but the control stick did.  That was in a quick mission. I tried a couple of other switches and they didn't work either.  Just for giggles I went to training and tried it there. Everything I mapped worked as it should! I guess if I stick to training missions I will be okay.

[Sr.]

13 minutes ago, badhorse said:

It keeps getting curiouser and curiouser.  I tried what was suggested but the results were unchanged. Move the X-56 Throttle and the throttle in the cockpit did not move but the control stick did.  That was in a quick mission. I tried a couple of other switches and they didn't work either.  Just for giggles I went to training and tried it there. Everything I mapped worked as it should! I guess if I stick to training missions I will be okay.

 

 

While you're in training and it's working, click each X56 profile and save. Then try to load those profiles from another area where they aren't working.

 

Do you have any profiles active via the Logitech application?

[badhorse]

Okay, I'll give that a try.  No. I don't have any Logitech profiles loaded. thanks for the help. I do appreciate it.

[Lange_666]

6 hours ago, badhorse said:

I loaded the game and completely re-mapped my Throttle, Joystick and Rudder Pedals. I saved the profile.

I did read a few times that the X-56 does not always behave like other controllers do but you don't have the save the profile you made as Flappie already said.

If you change something in your setup and you click the OK button. This creates already an xxx.diff.lua file with the differences you made from the default controls.

Also, DCS tends to assign an axis to every axis that it can find when the game starts. If you have rudders attached, these can be assigned to stick or throttle. You have to set it up once and clear delete the ones you don't need or are set up wrong by default so you don't have a double input.

If still having problems, just assign one axis and try. Get into a mission, preferably a hot start so everything is powered up and working (cold start can leave some controls inoperable until they have power), hit esc, in that menu you then see, go into controls and change your axis input right there, click OK and try (no need to save, the OK button will do the job).

[badhorse]

I started DCS. When to controls and verified everything was like I set it. When to training and everything worked fine. Went to a Quick Start Mission and the once again things didn't work. I was so frustrated before I didn't notice that not only does the program not follow the mapping of my Joystick, Throttle and Rudder Pedals. But the TrackIR and the Keyboard commands also don't work.

I quit DCS for awhile. I restarted it a couple of hours later. Went to the controls and verified everything was like I set it. This time I went to the mission editor and made a small mission. Just me on the blue side and a few enemy helicopters. I did what Lange_666 suggested and started hot on the runway instead of cold on the ramp and started the mission. I spawned on the runway with the engine running. The only thing that worked was the mouse. The keyboard, joystick, throttle, rudder pedals and TrackIR did nothing. Since it didn't recognize even the keyboard I had to go to task manager to close the program. 

This is driving me nuts. Although I admit, in my case it's a short drive.

. 

[Flappie]

I'd like to guide you through the steps and check what's wrong with you. I've sent you my Discord user id in a private message.

[Art-J]

Two things to keep on mind when being a new DCS player:

 

a) profiles are not saved for aircraft as a whole, but also separately for every USB device / controller used with this aircraft (so when saving/loading profile you have to click on device column first and highlight it!);

 

b) there are separate Control configs for "game" flight and avionics mode vs. "Simulation" flight and avionics mode. I think training missions are hardcoded to run in simulation mode, but you might have game one set in your quick missions? You better double check that.

[Flappie]

34 minutes ago, Art-J said:

b) there are separate Control configs for "game" flight and avionics mode vs. "Simulation" flight and avionics mode. I think training missions are hardcoded to run in simulation mode, but you might have game one set in your quick missions? You better double check that.

Absolutely.

We've chatted a bit on Discord and it seems the issue was the "Game avionics mode" set to ON. Waiting for his feedback, now.

[badhorse]

Flappie sorry this feedback is late but I was overcome by life events for a while. 

It looks like you nailed it. I did have it in Game avionics mode  (which I obviously had no idea what it did) and unselecting that got rid of most of the issues. I still have a few minor glitches I will work out, but you did take care of the major issue. I was able to fly outside of the training area and my settings remained as mapped.  Thank you very much and also to everyone that helped.

[Flappie]

You're welcome. Thanks for your feedback.