normanleto Posted June 6, 2018 Posted June 6, 2018 I find it hard to adjust my target diamond in Auto bombing mode. My TDC is too sensitive, it jumps about 50-100 meters at 10000 feet with each slightest poke with finger (using saitek x-52 throttle mini stick on the fwd of grip). There is no option for tuning it since it's not an axis. Tried with default coma, colon keys, but these are as sensitive as the hotas slew. It can't be so tricky, it makes any bombing in auto mode impossible. I remember slewing in a-10, it was accurate. Also, Waggs tutorial seems to have a slower slewing speed. And yes. I fly in 1.0 time rate :) What am I doing wrong? ...10 years with dcs...
razo+r Posted June 6, 2018 Posted June 6, 2018 You can assign the TDC to an axis so you can make it less sensitive.
normanleto Posted June 6, 2018 Author Posted June 6, 2018 You can assign the TDC to an axis so you can make it less sensitive. x-52 doesnt have any free 4-way axis on the throttle, nor on the stick. I wonder if other users of x-52 have the same problem. ...10 years with dcs...
Eaglewings Posted June 7, 2018 Posted June 7, 2018 x-52 doesnt have any free 4-way axis on the throttle, nor on the stick. I wonder if other users of x-52 have the same problem.How about using a modifier. Right now I have yet to upgrade to the recent update with TDC axis functionality but my TDC have since be mapped to the only 4-way hat switch on my X-52 throttle and using pinkie switch, it is equally set to do radio coms. Windows 10 Pro 64bit|Ryzen 5600 @3.8Ghz|EVGA RTX 3070 XC3 Ultra|Corair vengence 32G DDR4 @3200mhz|MSI B550|Thrustmaster Flightstick| Virpil CM3 Throttle| Thrustmaster TFRP Rudder Pedal /Samsung Odyssey Plus Headset
DDSSTT Posted June 7, 2018 Posted June 7, 2018 x-52 doesnt have any free 4-way axis on the throttle, nor on the stick. I wonder if other users of x-52 have the same problem. Assign the mouse nipple to a joystick, although the one on my old x-52 pro was not the most... sensitive... [sIGPIC][/sIGPIC] http://www.csg-2.net/
normanleto Posted June 7, 2018 Author Posted June 7, 2018 How about using a modifier. Right now I have yet to upgrade to the recent update with TDC axis functionality but my TDC have since be mapped to the only 4-way hat switch on my X-52 throttle and using pinkie switch, it is equally set to do radio coms. To avoid confusion: By 4-way hat switch, on throttle, you understand the switch with blue/rubberish tint under your left thumb? If so, I can't make it visible for DCS. It's just only switch that is not recognizable by DCS. I don't use any special drivers for x-52, just windows plug-n-play and it might be the case. Which (exactly) Saitek drivers do you use for x-52 that the blue hat switch is usable for you? ...10 years with dcs...
dAsReLiCT Posted June 7, 2018 Posted June 7, 2018 Try the same setting for the slew like the a10 dz 30 and suteration Y 15 Gesendet von iPhone mit Tapatalk Pro The underground is where I dwell at, It's where I find my heaven, and where you find your hell at :music_whistling:
Fri13 Posted June 7, 2018 Posted June 7, 2018 While I am totally against all curves and saturation adjustments for flight controls (throttle and stick and pedals) I accept it very well for the axis used for aiming and operating the avionics. Set slight deadzone for the mini-stick so it doesn't move by itself when released. And then set hard saturation adjustment based for your finger skill to adjust it carefully. Example I have in a KA-50, Su-25T for Shkval about 20-30 saturation and 5-10 deadzone but zero curves. For a Su-25A reticle I have IIRC 15 saturation. It just makes it easier to do the small nice adjustments and still quickly move them around. In KA-50 it is even more simpler as you use HMS to do the big aiming changes (like over 30 degree). The curves are bad for, actually for everything. As you do not get any muscle memory to do the slight adjustments as ratio of input:output is constantly changing. That is why a saturation adjustment is far better as while you are clipping your max output, you rarely come to situation where you would need it, and you gain more benefits from having accurate and smooth aiming etc elsewhere. i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S. i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.
normanleto Posted June 7, 2018 Author Posted June 7, 2018 Thanks for advices, but first I'll make ministick on throttle to be visible for DCS. Right now it's not, need different x-52 drivers for windows 10. Do you use DCS with windows 10? ...10 years with dcs...
crab Posted June 7, 2018 Posted June 7, 2018 I put it on one of the mini sticks set up as banded, smooth as can be.
Eaglewings Posted June 7, 2018 Posted June 7, 2018 Thanks for advices, but first I'll make ministick on throttle to be visible for DCS. Right now it's not, need different x-52 drivers for windows 10. Do you use DCS with windows 10?Currently I have yet to map the mini stick to control TDC. Was having problem with my cursor drifting to the right of my screen disabled it. But if you want to use the ministick, it would not be visible in dcs key control setup page. You would need to use the saitek program software to change make the ministick bands instead of the default configuration. Use the X axis and Y axis for your ministick. Remember, the saitek profile you make must be running at the background each the you play dcs for it to work. Windows 10 Pro 64bit|Ryzen 5600 @3.8Ghz|EVGA RTX 3070 XC3 Ultra|Corair vengence 32G DDR4 @3200mhz|MSI B550|Thrustmaster Flightstick| Virpil CM3 Throttle| Thrustmaster TFRP Rudder Pedal /Samsung Odyssey Plus Headset
unknwn Posted June 7, 2018 Posted June 7, 2018 (edited) Thanks for advices, but first I'll make ministick on throttle to be visible for DCS. Right now it's not, need different x-52 drivers for windows 10. Do you use DCS with windows 10? Attached registry key allows to map x-52 ministick as X/Y axis in DCS. Be aware that after merging this registry key a new X52 profile will be created in "C:\Users\<User>\Saved Games\DCS\Config\Input\<module>\joystick" with different name "Saitek X52 Flight Controller {xxx}" instead of "Saitek X52 Flight Control System {xxx}" which contains your previous keymapping setup. You can just copy content of old file to a new one or rename the file. You will have to do that for each module (plane). I suggest to backup Config\Input folder to avoid mixing up the files. x52_ministick.zip Edited June 7, 2018 by unknwn
Recommended Posts