Ala12Rv-watermanpc Posted December 9, 2015 Posted December 9, 2015 Hi guys, I have just get FC3 and runing in 1.5.1 I have a problem...all planes want to strongly turn to the right both in take-off and landing:mad:... I have checked my axis config and it looks good (Thrustmaster T.Flight Hotas X in rotation axis), even configured a smooth simetric curve to get more precision in slight movements but despite I orient the plane nicely with the runway, after some speed is reached, they all want to turn to right sharply:mad: to the point its extremely hard to make a straight and smooth landing/take-off...I dont think this is a matter of skill nor a question of realism as its REALLY strong movement and it doesnt happens when running slow so Im not sure if there is something im missing here...would apreciate some help here guys!! Thanks!! Take a look at my MODS here
Pikey Posted December 9, 2015 Posted December 9, 2015 Did you copy across your controller configs by any chance? ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *
BaconSarnie Posted December 9, 2015 Posted December 9, 2015 Ah so Im not going mad, this has been happening to me I completely removed all my joystick and throttle settings and then reassigned them all, seems a lot better but theres still some pull at times. This was in 2.0 at first but seems to be the same in 1.5 now. Its not my joystick, as I say I removed all controls, axis the works, tried with joystick disconnected just using keyboard and its the same. Even with control display (right ctrl and enter) showing zero movent from any controls its still been happening. And lo, Reverend Vegas did say "Take forth unto the infidel the mighty GAU 8 and expend its holy 30MM so that freedom will be brung upon them who knoweth not the joys of BBBBBBBRRRRRRRRRRRRRRRRRRRRTTTTTTTTTT" "Amen"
Cybermat47 Posted December 9, 2015 Posted December 9, 2015 I had this problem. Unplugging my stick and plugging it back in did the trick. [sIGPIC][/sIGPIC]
DrDetroit Posted December 10, 2015 Posted December 10, 2015 Unplugging my stick and plugging it back in did the trick. That's what she said. Sorry, just could not resist.
Ala12Rv-watermanpc Posted December 10, 2015 Author Posted December 10, 2015 Did you copy across your controller configs by any chance? You mean copy a previous configuration to the game??..No , I didnt, and its the first time I have the game installed in my PC... Ah so Im not going mad, this has been happening to me I completely removed all my joystick and throttle settings and then reassigned them all, seems a lot better but theres still some pull at times. This was in 2.0 at first but seems to be the same in 1.5 now. Its not my joystick, as I say I removed all controls, axis the works, tried with joystick disconnected just using keyboard and its the same. Even with control display (right ctrl and enter) showing zero movent from any controls its still been happening. Yes, man, you are not alone:(...I have done it also with no avail...also, I have checked my joy and its PERFECTLY centered, even in game and it works perfect once in the air for the rudder so... I had this problem. Unplugging my stick and plugging it back in did the trick. I have tried also...no success... Well, I surprised no more people is taliing about that because Im starting to think this is a bug. There is no reason for that to happen so it might be so. If anyone knows a solution for that it would be great as right now, taking-off and landing is a real pain in the neck...:cry: Take a look at my MODS here
Fakum Posted December 10, 2015 Posted December 10, 2015 I did copy over my input file from 1.5, I found that it copied over all my inputs for other modules except for the F-15, so I imported them from my 1.5 backup. I know your not supposed to do any of this, but I am testing myself, but I am NOT experiencing this particular problem mentioned above, I am experiencing another problem not the same though. Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle
Ala12Rv-watermanpc Posted December 11, 2015 Author Posted December 11, 2015 I did copy over my input file from 1.5, I found that it copied over all my inputs for other modules except for the F-15, so I imported them from my 1.5 backup. I know your not supposed to do any of this, but I am testing myself, but I am NOT experiencing this particular problem mentioned above, I am experiencing another problem not the same though. Really weird then :cry:...The problem is still present to me right now...dont know what else could I try...taking of and landing is a real pain :mad: Take a look at my MODS here
BaconSarnie Posted December 11, 2015 Posted December 11, 2015 Remove everything, controller wise. Go into controller settings and clear everything bound to your joystick/throttle/rudder. Make it so there is nothing asigned to them. Then re add each axis, testing each time to see how it behaves. Then buttons and so on until all are assigned. This has helped me, I appear to be flying fine now. But I have found out my twist axis on my X52 is out of alignement so needed to add deadzone, am saving up now for rudder pedals. And lo, Reverend Vegas did say "Take forth unto the infidel the mighty GAU 8 and expend its holy 30MM so that freedom will be brung upon them who knoweth not the joys of BBBBBBBRRRRRRRRRRRRRRRRRRRRTTTTTTTTTT" "Amen"
esb77 Posted December 11, 2015 Posted December 11, 2015 This sort of thing is almost always caused by a problem with input hardware configuration. Most often due to more than one input being assigned to an axis. Clear the axis controls for the aircraft module in question and then reassign, and it usually takes care of the problem if you remember to do it for all of your input devices: mouse, keyboard, stick, throttle, pedals, Track IR, etc. Rarely, it is a problem with the physical hardware. Worn or misaligned sensors in a stick, sticky key on a keyboard, that you can troubleshoot by plugging/unplugging one controller at a time to see if there's a correlation with the problem. You can also check the ground level wind speed and direction in the mission editor, or just test in different missions. Extremely unlikely to be the cause, but more likely than a bug. Of course, a bug is possible, but it's pretty much the explanation of last resort in this case. Callsign "Auger". It could mean to predict the future or a tool for boring large holes. I combine the two by predictably boring large holes in the ground with my plane.
Ala12Rv-watermanpc Posted December 11, 2015 Author Posted December 11, 2015 (edited) Ok guys!, looks like I have managed to solve it...in "general" I had the RZ axe assigned to rudder (which is good and should work) but seem like the game doesnt like to have asigned the comman in "general" and in a particular module /plane...so I erased the comman for general and let the assignation to every separate module...voila!!:)...now my f-15 goes almost perfectly straight!! The only thing is the su-25 wants to turn a little bit to the right yet, but I guess this is intended and normal from a simulation approach dont you think?? Thanks guys!! EDIT: Unfortunately it has broke again!!:mad:...after restarting computer again all planes turn hard to the right in the ground!!WTF!!!!!!!!!!!!!!:mad::mad::mad::mad::mad:...I have tried assinging again the RZ axis to de rudder but this time nothing works!!...I cant get it to work again. General section is erased as I leave it last time but everything is broken again...WTH?¿?¿?:mad::mad: EDIT2: Well, I think I finally got it...the problem seems to be Vjoy!!!...I have completely unistalled it as I dont think I need it, even for using FacetrackNOir (it seems to work fine without the vjoy, but correct me if Im wrong)...now after several starts of the game the rudder is working fine...will confirm after a while... Edited December 12, 2015 by watermanpc Take a look at my MODS here
azcoder Posted January 10, 2016 Posted January 10, 2016 I have been experiencing this with DCS 2.0, and only with the F-15 and the Su-27. I can't even take off in the F-15, it's incredibly sensitive to rudder input when on the runway, but fine if in the air. I can take off in the Su-27, but it's still trying to go right on the runway, fine in the air. The MiG-29 and A-10 don't have this issue at all.
TAW_Blaze Posted January 11, 2016 Posted January 11, 2016 Sounds like the infamous error where your throttle axis is also assigned to rudder. Due to some lunacy this happens to be default in some configs, like the Warthog profile for F-15C for example. LOL
NeilWillis Posted January 11, 2016 Posted January 11, 2016 The axis multiple assignment issue happens for all modules when they are first installed, so whenever you install one, you should delete all the duplicates as the very first step. Have the profiles been saved in your case watermanpc? It sounds like they are being re-set between sessions. It should be very easy to see if old settings have returned, because those multiple axis settings will be back. I'd also try re-installing the drivers for your joystick, and if all else fails, I'd then try starting over from scratch by backing up your entire saved games installation, and then restarting the game. It will then create a new saved games folder, and you can then re-save the input settings afresh. If it still happens, then it will probably mean an entire uninstall/reinstall of DCS World, and failing that, I'd start looking into the joystick as a possible cause. Borrow one that you know works, and try that if you can.
pandoraefretum Posted January 12, 2016 Posted January 12, 2016 This is probably wrong Are you sure there's no crosswind... I find even 10 kts of crosswind a nightmare!!
Weta43 Posted January 12, 2016 Posted January 12, 2016 When I installed my pedals, one foot brake was assigned to pitch, and one to roll... Cheers.
Recommended Posts