![]() |
Control sensitivity
Hello everyone, first post for me on these forums but I have been using the IL-2 sims on and off since inception. I have some issues with the control set up in CoD and was hoping to get some feedback about what can be done and what will be done in the future to fix them. I am using a saitek x-52 standard.
1. Small adjustments towards the middle of the aileron, rudder and elevator axes are impossible since the movement is translated hugely to the control surfaces. This is making lining up good passes on bombers VERY difficult. I dont like to have to sit behind a bomber for five minutes trying to move the joystick .001 mm in any given direction to line up the crosshair. 2. Where is the old Il-2 system where we could adjust the curve of every axis on the controller? You know, 0,20,38,....and so on. This is the only thing that made my stick usable in IL-2 and it is DESPERATELY needed here. As it stands now combat flying in this sim is just far to stressful on the control side of things. I can not continue playing CoD without an axis curve adjustment. 3. If it isnt broken, dont fix it. See number 2 above. And yes the slider for the axis on my stick is moved all the way to 1.00 and its is still FAR TO SENSITIVE closer to center. If anyone can point me to a program that will let me adjust my axis curves outside of the sim please let me know, I can find nothing and the SST software seems useless for this. As far as I'm concerned all other bugs and things can wait, if I cant properly control the aircraft then all the eye candy in the world means nothing. Any thoughts are appreciated. |
I looked in all the config files and found nothing similar to the old 0,1,2,3,4,5 setup of the axes. There is some bit in there with decimal points but its only a few numbers and I have no idea what is what. Surely someone from 1C can chime in here and let us know what can be done. I have tried my hardest to use the sim with the controls how they are but it is just not possible. The more I play CoD the more I want to play 1946, at least the controls were configurable to the point where I was a serious threat in the air. Now I'm like some kinda invalid fumbling behind a bomber struggling to land even 10% of my shots... This really is the biggest issue I have at the moment. Further CoD use is suspended until I have a fix.
|
I am going to try a simple copy and paste from my 1946 config into the CoD config and see if the values are recognized at all. These entries in CoD will be placed under the same spot as the 1946 ones(rts_joystick).
The only thing under this in the CoD config is FF=0. I copied and pasted this from 1946: [rts_joystick] X=0 1 4 9 16 25 36 49 64 81 100 0 Y=0 1 4 9 16 25 36 49 64 81 100 0 Z=0 10 20 30 40 50 60 70 80 90 100 RZ=0 10 20 30 40 50 60 70 80 90 100 0 FF=0 U=0 10 20 30 40 50 60 70 80 90 100 0 V=0 10 20 30 40 50 60 70 80 90 100 0 I will test this now and report my results here. |
OK, even with the RZ (rudder) axis values set very low it is still very sensitive.
Little to no change with this I'm afraid. If anyone comes up with anything new let us know! |
Well, it seems possible that the above config edit did work, though not for all aircraft. The hurricane fells much more stable now but the spitfire feels twitchy as ever. I'm not sure exactly what is happening here, I hope someone with more knowledge of the games inner workings can fill me in.
|
I wish we had curves as we did in the previous game.
|
Mine is opposite, my axis are too slow! Can't figure it out..
|
Quote:
|
OK, I got it figured out! I was on the right track but what I failed to realize was that my 1946 was on a fresh install and I hadn't set up my controller for it yet. After I set up my controller in 1946 I went into its config file and sure enough the proper values were now in there. I simply copied and pasted from the 1946 config to the CoD one. Here is what it looks like:
[rts_joystick] X=0 1 4 9 16 25 36 49 64 81 100 0 Y=0 1 4 9 16 25 36 49 64 81 100 0 Z=0 10 20 30 40 50 60 70 80 90 100 RZ=0 10 20 30 40 50 60 70 80 90 100 0 FF=0 U=0 10 20 30 40 50 60 70 80 90 100 0 V=0 10 20 30 40 50 60 70 80 90 100 0 1X=0 1 6 10 15 22 33 44 58 72 100 0 1Y=0 1 6 10 16 23 31 43 56 73 100 0 1Z=0 100 100 100 100 100 100 100 100 100 100 0 1RX=0 100 100 100 100 100 100 100 100 100 100 0 1RY=0 100 100 100 100 100 100 100 100 100 100 0 1RZ=0 1 4 8 13 21 28 39 52 69 100 0 1U=0 100 100 100 100 100 100 100 100 100 100 0 1V=0 100 100 100 100 100 100 100 100 100 100 0 This, everyone, I have confirmed to work! You need the 1X values for it to work not the X values, the axes with the 1 infront are what windows uses to set the joystick sensitivity. Perhaps this should be stickied so everyone can benefiet from this. |
Doesn't make a difference for me. What is your stick listed as (i.e. Joystick or Joystick1) in the relevant control menu?
|
Doesn't the in game axis sensitivity slider work for you? Seems to work with my x52.
|
Quote:
|
Quote:
How it was my X-52 barely had to move to get huge input to the aircraft. The rudder was especially anoying since it was so sensitive, and you really need some good rudder control to make hitting small planes in dogfights feaseable. With this set up in the config it makes the movements near the center of the axis much less pronounced and therefore much easier to control. My hit % has gone from sub 10% to 25-45% just from this. |
Quote:
What stick are you using? Worked fine for my X-52. |
Quote:
|
Quote:
[BOB] [window] DepthBits =24 StencilBits=8 DrawIfNotFocused=0 SaveAspect=0 [NET] speed=100000 localPort=27015 serverName=My Server serverDescription=IL-2 Sturmovik: Cliffs of Dover serverInfo1= serverInfo2= serverInfo3= serverInfo4= VAC=1 maxPlayers=16 socksEnable=0 socksHost= socksPort=1080 socksUser= socksPwd= [Console] IP=20001 UseStartLog=1 WRAP=1 PAUSE=1 HISTORY=1024 HISTORYCMD=1024 PAGE=20 LOG=0 LOGTIME=0 LOAD=console.cmd SAVE=console.cmd LOGFILE=log.txt LOGKEEP=0 [rts] tickLen=30 ;ProcessAffinityMask=2 maxTimerTicksInRealTick=20 ; 0 - not use, 1 - show cursor and not capture, 2 - not show cursor, and capture mouseUse=2 ; 0 - not use, 1 - use if hardware exist joyUse=1 ; 0 - not use, 1 - use if hardware exist trackIRUse=1 DisableIME=0 culture=en-GB [rts_mouse] SensitivityX=1.0 SensitivityY=1.0 SensitivityZ=1.0 Invert=0 SwapButtons = 0 [rts_joystick] X=0 1 4 9 16 25 36 49 64 81 100 0 Y=0 1 4 9 16 25 36 49 64 81 100 0 Z=0 10 20 30 40 50 60 70 80 90 100 RZ=0 10 20 30 40 50 60 70 80 90 100 0 FF=0 U=0 10 20 30 40 50 60 70 80 90 100 0 V=0 10 20 30 40 50 60 70 80 90 100 0 1X=0 1 6 10 15 22 33 44 58 72 100 0 1Y=0 1 6 10 16 23 31 43 56 73 100 0 1Z=0 100 100 100 100 100 100 100 100 100 100 0 1RX=0 100 100 100 100 100 100 100 100 100 100 0 1RY=0 100 100 100 100 100 100 100 100 100 100 0 1RZ=0 1 4 8 13 21 28 39 52 69 100 0 1U=0 100 100 100 100 100 100 100 100 100 100 0 1V=0 100 100 100 100 100 100 100 100 100 100 0 [core] RandSeed = 0 TexQual=3 TexFlags.PolygonStipple=0 Shadows=1 SpecularLight=2 DiffuseLight=2 DynamicalLights=1 MeshDetail=1 LandShading=1 LandDetails=1 Sky=3 Forest=2 VisibilityDistance=3 LandGeom=2 DrawCollisions=1 Water=-1 Effects=1 EffFlags.Light=1 EffFlags.SpriteRender=0 Grass=3 CordEffect=1 UseFog=0 UseLandCube=1 UseLandConnectedObject=1 LinearObjectManager=1 Roads=1 Sun=1 Clouds=1 EffFlags.LightSpritesProj=1 ShadowMapSize=5 TexFlags.AsyncLoad=1 TexFlags.ShowTexture=0 SimpleMesh.SWTransform=0 SimpleMesh.QuadTreeClip=1 SimpleMesh.InstancingHW=1 EffFlags.LightContextSprites=1 CloudsFlags.Detailed=1 TexFlags.CreateHDR=1 Decals=1 EffFlags.SWLight=0 TexFlags.CockpitOnePass=0 MegaTexture=0 TexFlags.Reflection=0 RenderTargetQual=3 MSAA=4 MeshStatics=1 MeshStaticsDetail=2 SimpleMesh.QTNoCompose=0 MeshFirstLod=0 MeshShowLod=0 SpawnHumans=0 [sound] SoundUse=1 DebugSound=0 SoundEngine=1 Speakers=1 Placement=0 SoundFlags.reversestereo=0 RadioFlags.Enabled=1 RadioEngine=2 MusicVolume=14 ObjectVolume=7 MusState.takeoff=1 MusState.inflight=1 MusState.crash=1 MusFlags.play=1 MasterVolume=14 Attenuation=7 SoundMode=0 SamplingRate=0 NumChannels=2 SoundExt.occlusions=1 SoundFlags.hardware=1 SoundFlags.streams=1 SoundFlags.duplex=1 SoundExt.acoustics=1 SoundExt.volumefx=1 SoundFlags.voicemgr=1 SoundFlags.static=1 VoiceVolume=8 Channels=1 SoundFlags.bugscorrect=0 SoundExt.extrender=0 SoundSetupId=8 ActivationLevel=0.02 Preemphasis=0.8 RadioLatency=0.5 AGC=1 PTTMode=1 RadioFlags.PTTMode=0 RadioFlags.PlayClicks=1 ActLevel=9 MicLevel=10 SoundFlags.UseRadioChatter=0 SoundFlags.AutoActivation=0 SoundFlags.forceEAX1=1 speakers=1 |
Quote:
Controls are now far smoother. I was having real trouble with gunnery due to the rudder feeling way too twitchy, now it feels as smooth (maybe even smoother) as flying in IL21946. Thanks for finding this. Now we just need the devs to create an ingame interface so we can tweak it ingame. |
Good post . I to have suffered from oversensitive controls near the centre position. I would really like to try this.
However I like to play online and my question is will altering the values in this file fall foul of the "anticheat" features that I have heared about ? So far I have resisted the urge to mod this game in any way,purely because I dont want to find myself excluded from being able to play online. You only have to look at OFP and Arma2 to see how the mod comunity forces improvements and prolonges the life of a game |
which cong. one..
the one in the documents or the one on the steam common etc.. |
Quote:
This isn't modding it is merely changing your personal config or preferences or whatever you want to call it. Quote:
***\My Documents\1C SoftClub\il-2 sturmovik cliffs of dover\conf.ini It even works for me when I keep the Steamcloud enabled. |
thank you very much:-)
|
Quote:
|
Quote:
The leading and trailing zeros are kind of like stoppers, without these the config and controller wouldnt know where the axis begins and where it ends. All of the other axis are for various sliders on the stick so the number of these may vary depending on what model stick you have. |
I thought the zeros were deadzones (in IL-2 at least). Thanks for the effort, Formula88.
|
Finally had a chance to test this properly. Relevant section of my 1C Softclub conf.ini is:
[rts_joystick] FF=0 X=0 1 4 9 16 25 36 49 64 81 100 0 Y=0 1 4 9 16 25 36 49 64 81 100 0 Z=0 10 20 30 40 50 60 70 80 90 100 RZ=0 10 20 30 40 50 60 70 80 90 100 0 U=0 10 20 30 40 50 60 70 80 90 100 0 V=0 10 20 30 40 50 60 70 80 90 100 0 1X=0 1 6 10 15 22 33 44 58 72 100 0 1Y=0 1 6 10 16 23 31 43 56 73 100 0 1Z=0 100 100 100 100 100 100 100 100 100 100 0 1RX=0 100 100 100 100 100 100 100 100 100 100 0 1RY=0 100 100 100 100 100 100 100 100 100 100 0 1RZ=0 1 4 8 13 21 28 39 52 69 100 0 1U=0 100 100 100 100 100 100 100 100 100 100 0 1V=0 100 100 100 100 100 100 100 100 100 100 0 There is no difference in control sensitivity when I switch between everything at 1 and everything at 100 (or anything more sensible in-between) for both X, Y and 1X, 1Y. Not sure what's going on with my config since other users have reported this to be working. Any ideas? |
Not working for me either
Hi I have the x52 pro and find it way to sensitive as well the in game sensitivity sliders seem to have no effect cuting and pasting the config.ini seems to have no effect. In searching for an answer I came across a program that Oleg made IL2 Joy control.
http://www.mission4today.com/index.p...etails&id=1021 Will this work for COD? Thanks Gordo62 |
I have two questions for you guys:
First, do we have a consensus whether the old IL2 [Joystick_RTS] functions in CoD conf.ini? Second, as far as ALL the trim axes go, does the dead zone at 0% and at 100% refer to the center (50% of travel) of the axes or the way the are shown in the control panel ?(0% all the way to the left and 100% all the way to the right) I would ask the same thing about the rudders but those are usually self centered so I am assuming the center is 0% in rudders. |
Well, in my *.ini file there is only one entry under [rts_joystick] and that's FF=1.
Nothing else and I feel that my controls are hugely sensitive and there is no way of tuning them from a menu in game! Feels like something is amiss here ?! |
Quote:
|
Quote:
If this is in fact the case (correct me if I am wrong) then I recommend that those who find the lines they have edited have not had an effect attempt to try editing lines referring to another controller (ie if you have edited lines with "1" at the start, then try instead editing lines that have no number there). |
Well, I just copied my lines from good old IL2 and places 0 in all of the numbers for line 1x and 1y like Jimbo did and my Fighterstick is alive and kicking in game so I am leaning heavily in believing that this scenario is not working as we would like it to. :(
|
Quote:
full left is 1:1 and by sliding the slider to the right, the sensitvity reduces so that a lot of movement in the real world stick results in not much movement in the planes stick |
Quote:
|
Quote:
|
do you mean the "Bell Curve", where it becomes almost impossible to stall?
|
Quote:
Roll: 1 3 6 12 21 32 44 61 81 100 Pitch: 1 4 8 15 24 33 44 60 77 100 Yaw: 0 10 19 32 43 54 63 74 86 100 As you can see there is little response (i.e. 1, 3, 6) at the start of movement to allow for fine movements near the centre but large response at the extremity (i.e. 81, 100). Extreme movements still have bad effects... |
yes, I'm aware of that and I'm also aware of the bell curve too
|
Quote:
|
These settings wont work in CloD. I tried it with all 100's and even all 0's for all sticks#.
It is somewhere hardcoded because I can't find anything else related to it. |
All times are GMT. The time now is 12:41 AM. |
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 2007 Fulqrum Publishing. All rights reserved.