Ramstein Posted December 10, 2009 Posted December 10, 2009 Setting Saitek joystick sensitivity setting for Black Shark. This works great: In the Saitek profile utility, open your Black Shark profile: set it to 'Product View' move joystick, it will show a X Axis and sensitivity setting slider. Move it further to the right to make it more sensitive. Save the profile. This way, when you move the stick, it will require less travel to change direction in the helo :joystick: 1 ASUS Strix Z790-H, i9-13900, WartHog HOTAS and MFG Crosswind G.Skill 64 GB Ram, 2TB SSD EVGA Nvidia RTX 2080-TI (trying to hang on for a bit longer) 55" Sony OLED TV, Oculus VR
astrospud Posted December 15, 2009 Posted December 15, 2009 Thx, Ramstein! Will give it a go tonight after work :) Rectum non bustus
Ramstein Posted December 22, 2009 Author Posted December 22, 2009 (edited) Black Shark Saitek X52 Pro profile I had a few crashes that appears to have been caused by Saitek X52 Pro stick, and so I checked my profile, and am now using the rotary knob #2 (large knob) to use as zoom in-out view. It is much larger and is not as sensitive (as the smaller knob) when turning, and also decided (unfortunately) to chage the zone to 20%-60%-20% with the 60% being neutral. I think the smaller knob had some glitches (maybe from getting older..) and was causing some spikes that sent bogus signals to the computer causing crashes.. So now my latest profile (on Saitek forums) has those changes.. only gripe is the larger knob is way above the small knob and not as easy to move with thumb.. FYI :joystick: Edited December 22, 2009 by Ramstein ASUS Strix Z790-H, i9-13900, WartHog HOTAS and MFG Crosswind G.Skill 64 GB Ram, 2TB SSD EVGA Nvidia RTX 2080-TI (trying to hang on for a bit longer) 55" Sony OLED TV, Oculus VR
astrospud Posted December 23, 2009 Posted December 23, 2009 Cheers, Ram. I use a greatly slimmed down version of your profile, having had problems with Bad Pool error blue screens. Nothing to do with your profiles, just removing mapped inputs and using them in DCS alone, whilst leaving SST inputs for stuff for things you can't set up in DCS. These are TS PTT and a setup to have trigger to fire both gun and hardpoints using modes 1 and 2. 1 for guns and 2 for HP. I used to have the Shkval Slew function mapped to my mini stick, but that was giving me so much grief in terms on lagged input - after slewing around a bit, no other functions aside from cyclic axes would function until 5 to 10 seconds later, all in one hit. There must be a correllation between ministick, DirectInput.dll, flickering MFD and this input lag. I'm happy with the way things are ATM; Slew function in on cyclic POV hat. I have since killed the Directinput process and have had no issues. I use Vista 32bit. Rectum non bustus
rapid Posted December 23, 2009 Posted December 23, 2009 Thanks Ramstein, I can finally log inti the Saitek forums they authenticated my account. I will down load it today. Asus ROG Crosshair Hero VIII , Ryzen 3900X, Nzxt Kraken Z73, Vengence RBG Pro DDR4 3600mhz 32 GB, 2x Corsair MP 600 pcie4 M.2 2 TB , 2x Samsung Qvo SSD 2x TB, RTX 3090 FE, EVGA PSU 800watt, Steelseries Apex Pro. TM WartHog,TM TPR, Track IR, TM 2 x MFD, Asus VG289Q, Virpil Control Panel#2
Recommended Posts