So we shouldn't import our input profiles from a10c/bs2 to DCS world?

[SackDestroyer]

I've read a couple of times that we shouldn't import our previous .lua files into DCS World. Will this cause harm to the game or will it just result in wonky controls?

 

Will the A-10C still auto-detect a Thrustmaster HOTAS Warthog (my device)?

 

Is there a place where we can go for updated profiles? I'm currently using GreyWo1f's Warthog profile for Ka-50.

 

Thanks!

[xxJohnxx]

Hi,

 

I set up DCS World with DCS A-10 yesterday, and it detected my HOTAS Warthog without problems. The only thing I changed was the TRIM POV hat, because it defaults to the "view controll". I have changed those 4 points and everything was set up again. ;)

But I am not sure what to do with DCS BS2. I think we will have to map the functions ourselfs, because it can cause problems with the radios, etc. if we import the old profiles.

Hope that helps!

John

[Tracer2k]

which folder contains the old .lua files?

[Panzertard]

Some controls & keywords have been changed. from BS2/A10C 1111

Keep an eye out for odd behavior / crash. If so, reset your input profiles to defaults.

I never copy the profile from one version to another myself as I'm aware of the changes in general - and want to avoid having problems 50 mins into my favorite mission. ;)

[hassata]

Anyone know what the new input commands are so we can cut and paste into our existing luau? I did this before when iirc.

[Corrigan]

Opening both files with Winmerge might be a convenient way of transferring the old commands to the new file.

[hassata]

:thumbup:

[bengo]

Hi,

would ED consider filling up the empty keyboard-inputs in A10-C, because each update/install I have to generate a number of keyboard-inputs to be able to use my Touchbuddy-profile. I reckon it's the same for Helios and Hawgtouch-users ?

 

B

[Wolf Rider]

The DCS World: A-10C auto detects the TH Warthog HOTAS just great, and with far less double (the same switch/ button/ axis assignment for stick, rudder and throttle) assignments that all previous DCS releases have done.

 

:thumbup:

[Smoky]

My Warthog did not work properly after the update. Or rather, as always (beta or not) the command profile was butchered so it prob is detected but there is no way to know this.

 

Why do all DCS games like to rewrite the command config during updates? And why does it do things like assign a pitch axis to every device connected to my machine? Same for roll, rudder, throttle, etc. So I have to go clean all that garbage out each time or nothing works.

 

Guys, you are genius at making sims. So I don't understand why this issue persists. Our key/joystick command setups are PRECIOUS. More so in a DCS sim, of course!! So please try to accommodate that in future builds! This makes updating very PAINFUL otherwise!

 

The worst part is that I can't even revert now and restore my commands back because the DCS 1.1.2.1 patch butchered the OLD input files, to make sure I had no chance of saving my pain-stakingly configured control setup!!

 

Here is how you fix it DCS:

 

-During setup of a patch or update, add a wizard step to "import control mappings from previous version". This way the user turns over the import process to DCS, who are the experts in making this happen correctly. Now the end-user can't choose the wrong thing, or accidentally lose the new features etc.

 

and/or

 

-Warn users to back up their input files since the DCS update might very well erase everything! Ideally, give the user the option to back up their files WITHOUT having to exit the patch/update wizard.

 

The objective should be: "All user config settings are retained across all updates."

 

 

I'm wishing I could turn back time now. It'll be more hours of config setup all over again before I can play. When you have kids and family obligations and small windows of time to actually play, this kind of thing is the equivalent of shelving the sim for at least a month before you get to play it again.

 

DCS is king. Just needs a little more bedside manner during the updates (even the beta's...because how can we evaluate the beta if our controls do not work!)

 

Thanks and I look forward to future updates.

Edited May 20, 2012 by Smoky

[Wolf Rider]

its sort of a good play for keeping the HOTAS as a hotas instead of a button bay... less to reconfigure on any Beta release which alters command settings.

 

The way to properly evaluate a Beta is to run each new version as just that, as a fresh clean install.