Jump to content

Recommended Posts

Posted

Hi all,

 

I'm having a problem with my default controls not defaulting properly or mostly at all. Didn't have this problem on the same setup in Patch 2.

 

The "A-10C Game"profile seems to be fine. I notice that most of the settings are set by default and a lot of the actions available on the "A-10C Sim" profile are not there. Okay, makes sense... But if I switch to the "A-10C Sim" settings, all the actions are listed but 75% are missing key bindings.

 

I've attached my [basedir]\Config\Input\Aircrafts\A-10C\keyboard\default.lua (as default.lua.txt)

AND [basedir]\Config\Input\Aircrafts\default\keyboard\default.lua (as defaultdefault.lua.txt) in case it's any use. I don't think so since it's about 60kb smaller.

 

 

I have reinstalled 3 times. First time with "full" version of 2 and patch 3 and 4 (in order)...

Last two times I installed the "full" version of 4 in case of weird patching issues.

 

I've tried the 32 and 64 bit versions..

 

I've also installed to C:\games to avoid any UAC (which is off anyways :music_whistling:) issues..

 

OS is Windows 64 bit Pro

 

I do have (and it is detecting and assigning some stuff by default to) a Saitek X52 throttle/joystick) and TrackIR in case theres any known issues there.

 

I have tried defaulting the keys but it errors out when I hit the key and then default. See the defaulterror.txt attached for the error (it doesn't do this for the keys that are already there (obviously, but of note I suppose). I honestly could have spent more time searching the forum on the error but I'm mostly just kinda hoping someone will say "Yes, do that, you will fix your problem" since I'm losing motivation now on solving this in any way other than rebuilding my keys manually.

 

Any help is appreciated.

defaulterror.txt

default.lua.txt

defaultdefault.lua.txt

Posted

I should be sleeping already so i just quick read you post. But for now...

 

When you reinstalled, did you erase the DCS folder?

 

Second, don't re-use the settings files from older betas, they are not completely compatible, if thats what you trying to do. You will need to remap all controls.

AMD Athlon II X2 240 2.8@3360 MHz | MB Asus M4A78-EM | 4GB DDR2-800 Kingston | XFX HD 5770 @850-900/1200-1300 | 500G Samsung HD502HI | Case CM 335 | CM-EPP 460W | Windows 7 Ultimate (64bit) | Saitek X65F | Freetrack(Wii Remote) | LG 23' W2353V

Posted

I don't use arcade mode, but I would assume that it doesn't map keys to functions that aren't available in that mode.

It's a good thing that this is Early Access and we've all volunteered to help test and enhance this work in progress... despite the frustrations inherent in the task with even the simplest of software... otherwise people might not understand that this incredibly complex unfinished module is unfinished. /light-hearted sarcasm

Posted
I should be sleeping already so i just quick read you post. But for now...

 

When you reinstalled, did you erase the DCS folder?

 

Second, don't re-use the settings files from older betas, they are not completely compatible, if thats what you trying to do. You will need to remap all controls.

 

Yes, I did delete the DCS folder (I originally had it installed to Program Files) I also did some registry scrubbing with CCleaner just in case. Only one rogue entry was in there for DCS.

 

I did try the patch 2 default key file, but ty, good to know I can delete that versions installer and move on to just trying from 4.

 

With my current install, I did an uninstall, then manually deleted the folder and reinstalled. No copy pasting of older files, etc.

Posted
I don't use arcade mode, but I would assume that it doesn't map keys to functions that aren't available in that mode.

 

No, I'm not trying to use Arcade mode, I was just looking at the game profile to see if suffered the same problem, but it doesn't appear to. Active pause, and 90% of it is actually mapped as opposed to the sim profile which is 25% mapped.

Posted

Ok, i misunderstood your post, i through you wanted to re-use HOTAS key bindings between betas.

 

First you need to note that after either beta 1 or 2(can't remember which) they added lots of extra possible biddings like the MFCD OSB, CDU, UFC, etc... that are not available on previews betas, and most of these are empty by default.

 

 

Now about the errors, i did have some crashes too when assigning some buttons on the HOTAS, but they are inconsistent, and when i tried again they will work.

One way around for now on beta 4 to remove these errors is to switch to the old GUI.

Edit, with Notepad++, the "..\DCS A-10C Beta\MissionEditor\MissionEditor.lua" on the line "NEW_GUI = false" change from 'true' to 'false'. And try again.

AMD Athlon II X2 240 2.8@3360 MHz | MB Asus M4A78-EM | 4GB DDR2-800 Kingston | XFX HD 5770 @850-900/1200-1300 | 500G Samsung HD502HI | Case CM 335 | CM-EPP 460W | Windows 7 Ultimate (64bit) | Saitek X65F | Freetrack(Wii Remote) | LG 23' W2353V

Posted
Ok, i misunderstood your post, i through you wanted to re-use HOTAS key bindings between betas.

 

First you need to note that after either beta 1 or 2(can't remember which) they added lots of extra possible biddings like the MFCD OSB, CDU, UFC, etc... that are not available on previews betas, and most of these are empty by default.

 

 

Now about the errors, i did have some crashes too when assigning some buttons on the HOTAS, but they are inconsistent, and when i tried again they will work.

One way around for now on beta 4 to remove these errors is to switch to the old GUI.

Edit, with Notepad++, the "..\DCS A-10C Beta\MissionEditor\MissionEditor.lua" on the line "NEW_GUI = false" change from 'true' to 'false'. And try again.

 

I tried that, it errored out going to the controls right away. Defaulting also errors out. I copied the error that I got on its first attempt to go to the controls. It no longer errors out (since it removed just about every single binding that was left so now there are about 95% missing bindings)

 

I'm going to uninstall and reinstall and try (before loading the ui for the first time) changing it to false to see what happens.

 

Just to be sure - there aren't any appdata folders to be concerned about, right?

NEW_GUIerror.txt

Posted
I tried that, it errored out going to the controls right away. Defaulting also errors out. I copied the error that I got on its first attempt to go to the controls. It no longer errors out (since it removed just about every single binding that was left so now there are about 95% missing bindings)

 

I'm going to uninstall and reinstall and try (before loading the ui for the first time) changing it to false to see what happens.

 

Just to be sure - there aren't any appdata folders to be concerned about, right?

 

So I reinstalled and before running I both unplugged all peripherals (trackir/saitekx52) and changed the new gui to false and now the defaults seem to all be there (like right alt, home, etc.) that weren't there before. I'm not sure which of those solved the problem but setting new gui back to true still works. I have yet to replug back in the saitek/trackir. I'll report my findings tomorrow.

 

TY all for the help and suggestions. See you around (:

 

*Back to lurker status*

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...