Random_Pilot Posted May 29, 2014 Posted May 29, 2014 With me the shkval slews extremely fast. I fixed it using the options panel then axis tune and finally Y axis saturation 104th_Junior
Flagrum Posted July 9, 2014 Posted July 9, 2014 I finally managed to recreate it, to some extent, its only when you are below 30m and your shooting, perhaps at a bit of an incline, after the vikhr's fired, you move the shkval to adjust aim, and it goes to 0 meters, then you shot is trashed, but the interesting is, that in BS1, i cannot recreate it, the shkval does go to 0 but immediately resets to the set distance, so that you can keep guiding your missile, and it happens only when you are below 10m or so. Another issue is, how can the system not know if its looking up or down? You could easily program so you know if your system is looking up or down, especially since the shkvals slant is already read by the system of the ka-50, for the distance calculations when the laser isn't working. In case for some reason you couldn't program that in, wouldn't you make it so that the distance calculation turns off after a vikhr is fired, so that pilots don't end up wasting missiles? Here's the track newest beta Although I am not sure if this is actually relevant, some of you might find it worth to be considered ...? From the manual: Vikhr ATGM Employment Parameters Minimum Safe Launch Altitude – Hover 10 m Minimum Safe Launch Altitude – Forward Flight 50 m Maximum Launch Altitude - Barometric 4,000 m Maximum Launch Altitude – Practical/All Speeds 3,000 m Minimum Range to Target 800 m Maximum Range to Target 8,000 m
Isegrim Posted July 9, 2014 Posted July 9, 2014 Just a Question....who all of you guys is using the X 52(Pro) Ministick(Mouse) for Shkval slew? And if so where does it mostly slew at ? (left up as example) "Blyat Naaaaa" - Izlom
FoReIgNeR Posted July 9, 2014 Posted July 9, 2014 With me the shkval slews extremely fast. I fixed it using the options panel then axis tune and finally Y axis saturation In the past I have tried a number of settings on the warthog hotas throttle slew control (saturation, gain etc.) axis to accurately control shkval aiming (not only KA-50, but also su-25T etc.). However, I never got it to work the way I wanted... The set-up which I use now is to also map the coolie hat to the shkval discrete slew (i.e., the ,./; key-bindings). Coarse aiming is done by either TrackIR HMS or warthog slew control, then refine by using the coolie hat. Works like a charm! [sIGPIC][/sIGPIC] Limitless Aerobatics Team Facebook
SAM77 Posted July 9, 2014 Posted July 9, 2014 I always thought the crazy slew was due to my chopper being unstable when trying to track a target. The reset does work but it also seems like once I get the chopper settled it never occurs. If I fly properly and patiently I rarely have a problem (5% of my flight time) If I don't then the chances of crazy slew increase a fair bit imo. Spoiler Intel i7 14700F | 64GB G.Skill Trident Z5 RGB | MSI RTX 4060 Gaming X 8G | WD Black SN770 2TB | Sound Blaster Audigy RX | MSI B760 Tomahawk WIFI | Thrustmaster T.16000M FCS Flight Pack | TrackIR 5 | Windows 11 Home |
Devrim Posted July 9, 2014 Posted July 9, 2014 (edited) Just a Question....who all of you guys is using the X 52(Pro) Ministick(Mouse) for Shkval slew? And if so where does it mostly slew at ? (left up as example) Hi. I think I've written about this before, in this thread, and I wanted to re-write. I use X52Pro and use silver hat to slew Shkval. If I encounter this problem Shkval goes left constantly. Additional I must give this info: I assigned Shkval slew commands to NumPad keys (cancelled cam commands, because I use FreeTrack). For example; Slew left: Num4 Slew right Num6 Slew up: Num8 Slew down: Num2 (By the way note that, I use this method to slew Shkval cam diagonally.) And silver hat assigned to these num keys via Saitek software. When Shkval starts to slew left uncontrollably I can't stop it, but hitting the Num4 key!!! When I hit the Num4 it stops. So, after this finding I thought Ka-50 module had no bug about this. The problem was in my SST software or something, and I stopped chasing this bug. But other friends insist on this bug, maybe I'm encountering same bug but in different ways. :D Edited July 9, 2014 by Devrim Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64) Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR >>MY MODS<< | Discord: Devrim#1068
Isegrim Posted July 9, 2014 Posted July 9, 2014 (edited) Yeah we have written about this Devrim. I for myself did find out that this is not the SST Software ..its the Stick. When Playing KSP (Yes thats Kerbal space Programm ^^) my mouse arrow sometimes began to slew into the upper left or left via the Ministick. But i only have the Drivers for my X52 Pro installed and no SST Software. Btw:ED should implement diagonal slew keys for the Shkval...can be usefull here and there. :) Edited July 9, 2014 by Isegrim "Blyat Naaaaa" - Izlom
dok_rp Posted August 12, 2014 Posted August 12, 2014 I also had this happen to me today. I'm trying to reproduce it. I was removing and adding helicopter groups for me to test. At a certain time, I added a Ka-50 to the US side, didn't save the changes in the mission and started it up. When I turned on the Shkval, it was slewing all over the place. Haven't been able to reproduce it since then. :(
Rogue Trooper Posted August 12, 2014 Posted August 12, 2014 (edited) Some times the crazy Shkval occurs to me, but as soon as I see it a reset of the targeting system usually cures it..... for a while.... Edited August 12, 2014 by Rogue Trooper HP G2 Reverb (Needs upgrading), Windows 10 VR settings: IPD is 64.5mm, High image quality, G2 reset to 60Hz refresh rate. set to OpenXR, but Open XR tool kit disabled. DCS: Pixel Density 1.0, Forced IPD at 55 (perceived world size), DLSS setting is quality at 1.0. VR Driver system: I9-9900KS 5Ghz CPU. XI Hero motherboard and RTX 3090 graphics card, 64 gigs Ram, No OC... Everything needs upgrading in this system!. Vaicom user and what a superb freebie it is! Virpil Mongoose T50M3 base & Mongoose CM2 Grip (not set for dead stick), Virpil TCS collective with counterbalance kit (woof woof). Virpil Apache Grip (OMG). MFG pedals with damper upgrade. Total controls Apache MPDs set to virtual Reality height. Simshaker Jet Pro vibration seat.. Uses data from DCS not sound... goodbye VRS.
BitMaster Posted August 13, 2014 Posted August 13, 2014 Some times the crazy Shkval occurs to me, but as soon as I see it a reset of the targeting system usually cures it..... for a while.... Same applies to me, it does happen from time to time, not really often but does occur. I dunno what I always do to stop it but I always managed to fix it in flight. And yes, as one poster said before, the softer and wiser you move the chopper the less chances you have to encounter the "Crazy Shkval" thing. If you slam that baby around and are also about to tilt the AP system, the Crazy Shkval is bound to happen somewhere down this road I guess. I have flown 2 full evenings, mostly Ka and Su-25T, both with Shkval usage, not a single glitch with 1.2.10. I don't run any Hotas, simple Logitech Freedom 2.4 Cordless Stick and Standard Keyboard Layout. Hold ALT-GR and Coolie Hat is what I use to control it. Bit Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Sapphire Nitro+ 7800XT - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus XG27ACG QHD 180Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X
rcjonessnp175 Posted August 13, 2014 Posted August 13, 2014 Same as Rogue Trooper, a reset of tgt system holds it out for a bit until the dreaded crayziness strikes again I7 4770k @ 4.6, sli 980 evga oc edition, ssdx2, Sony 55 inch edid hack nvidia 3dvision. Volair sim pit, DK2 Oculus Rift.
tflash Posted August 13, 2014 Posted August 13, 2014 I have the same issue, but only in crowded missions where there is a lot going on. I thought it was just my PC that was to slow. [sIGPIC][/sIGPIC]
SnowTiger Posted October 11, 2014 Posted October 11, 2014 WOW .. and all this time I thought it was just Me or more importantly my X52 (not pro). I am ready to purchase the X-55 Rhino TODAY (thinking that it is something to do with the Hat Switch I use on the Stick... after all, this is 15 yrs old but minimal use). BUT my biggest concern is that there is No Way to Lock the Twist Grip on the Stick ? AND No Way to Adjust for Small Hands ? Am I better off just getting an X52 Pro ? Should I just wait to see if DCS corrects this CRAZY Shkval Slewing Issue ? {... which I too correct by hitting Reset .. but that often gets me killed because of the wasted seconds}. Any Advice ? I am ready to purchase RIGHT NOW> SnowTiger AMD Ryzen 9 7950X - Zen 4 16-Core 4.5 GHz - Socket AM5 - 170W Desktop Processor ASUS ROG STRIX X670E-A GAMING WIFI 6E Socket AM5 (LGA 1718) Ryzen 7000 gaming motherboard Geforce RTX 4090 Gaming Trio X - 24GB GDDR6X + META Quest 3 + Controllers + Warthog Throttle, CH Pro Pedals, VKB Gunfighter MKII MCG Pro G.SKILL Trident Z5 Neo Series 64 GB RAM (2 x 32GB) 288-Pin PC RAM DDR5 6000 RAM
SnowTiger Posted October 11, 2014 Posted October 11, 2014 PS> With regards to Not being able to Lock the Twist Grip i.e. Rudder, can I Disable that axis so it doesn't fight my Saitek Rudder Pedals ? Sorry... I realize this is off topic .. but as mentioned the only reason I am even considering a new Hotas is because of the Wild Shkval Slewing issue which I thought was my current Hotas. SnowTiger AMD Ryzen 9 7950X - Zen 4 16-Core 4.5 GHz - Socket AM5 - 170W Desktop Processor ASUS ROG STRIX X670E-A GAMING WIFI 6E Socket AM5 (LGA 1718) Ryzen 7000 gaming motherboard Geforce RTX 4090 Gaming Trio X - 24GB GDDR6X + META Quest 3 + Controllers + Warthog Throttle, CH Pro Pedals, VKB Gunfighter MKII MCG Pro G.SKILL Trident Z5 Neo Series 64 GB RAM (2 x 32GB) 288-Pin PC RAM DDR5 6000 RAM
Isegrim Posted October 11, 2014 Posted October 11, 2014 PS> With regards to Not being able to Lock the Twist Grip i.e. Rudder, can I Disable that axis so it doesn't fight my Saitek Rudder Pedals ? Sorry... I realize this is off topic .. but as mentioned the only reason I am even considering a new Hotas is because of the Wild Shkval Slewing issue which I thought was my current Hotas. You can delete axes you dont need in Options. BTT "Blyat Naaaaa" - Izlom
SnowTiger Posted October 16, 2014 Posted October 16, 2014 I hope the X 55 Rhino I have coming will resolve this Slew Issue. I'm tired of getting killed because I have to keep resetting the Shkval every 2nd or 3rd shot. When vehicles are moving fast, it's hard enough to track them as it is without this bullony happening all the bloody time. Usually by the time I get back on target (assuming I even do), it's just on time to see missiles coming my way and BOOM .. game over. So if it's something to do with my X52 then fine ... my problem will be resolved in a week. However, if not .. I am going to be giantly ticked off to find I spent another $250 only to learn it was the Programming !! SnowTiger AMD Ryzen 9 7950X - Zen 4 16-Core 4.5 GHz - Socket AM5 - 170W Desktop Processor ASUS ROG STRIX X670E-A GAMING WIFI 6E Socket AM5 (LGA 1718) Ryzen 7000 gaming motherboard Geforce RTX 4090 Gaming Trio X - 24GB GDDR6X + META Quest 3 + Controllers + Warthog Throttle, CH Pro Pedals, VKB Gunfighter MKII MCG Pro G.SKILL Trident Z5 Neo Series 64 GB RAM (2 x 32GB) 288-Pin PC RAM DDR5 6000 RAM
Isegrim Posted October 16, 2014 Posted October 16, 2014 I hope the X 55 Rhino I have coming will resolve this Slew Issue. I'm tired of getting killed because I have to keep resetting the Shkval every 2nd or 3rd shot. When vehicles are moving fast, it's hard enough to track them as it is without this bullony happening all the bloody time. Usually by the time I get back on target (assuming I even do), it's just on time to see missiles coming my way and BOOM .. game over. So if it's something to do with my X52 then fine ... my problem will be resolved in a week. However, if not .. I am going to be giantly ticked off to find I spent another $250 only to learn it was the Programming !! Where do you have your Shkval slew mapped to? "Blyat Naaaaa" - Izlom
snuffles Posted October 16, 2014 Posted October 16, 2014 (edited) Did anyone ever try to isolate the cause of the problem by unbinding the slew controls from the joystick and HOTAS profile, and using the keyboard instead? Just a thought. It isn't your joystick doing this. It also happens when using Freetrack with mouse emulation, and cursor slew bound to the mouse axes. Edited October 16, 2014 by Tasselhoff I don't always openly list my things. But when I do, I put it in my signature.
Isegrim Posted October 17, 2014 Posted October 17, 2014 Its the Ministick in 95% of the situations. "Blyat Naaaaa" - Izlom
SnowTiger Posted October 17, 2014 Posted October 17, 2014 Hi Isegrim I use the POV Hat #1 on my X52 ... Up, Down, Left & Right (to move in those directions respectively). SnowTiger AMD Ryzen 9 7950X - Zen 4 16-Core 4.5 GHz - Socket AM5 - 170W Desktop Processor ASUS ROG STRIX X670E-A GAMING WIFI 6E Socket AM5 (LGA 1718) Ryzen 7000 gaming motherboard Geforce RTX 4090 Gaming Trio X - 24GB GDDR6X + META Quest 3 + Controllers + Warthog Throttle, CH Pro Pedals, VKB Gunfighter MKII MCG Pro G.SKILL Trident Z5 Neo Series 64 GB RAM (2 x 32GB) 288-Pin PC RAM DDR5 6000 RAM
Lascaille Posted November 1, 2014 Posted November 1, 2014 I don't believe this has anything to do with the joystick hats. I have a HOTAS Warthog and have the Shkval slew set to the trim hat on the joystick itself, if that trim hat was misbehaving it would cause problems in other models (i.e. a10 suddenly being trimmed hard over). The Shkval often does not ground stabilise, and when being slewed sometimes just decides to slew at full speed to one axis and stay hard over until re-centered with a 'boresight shkval' control. Also when rangefinding targets that are out of lock range (where the range is displayed below the target but the lock doesn't occur) the range will flip from the correct range (i.e. 14.0) to a random range (i.e. 5.4) a few seconds after the laser turns off, at which point the shkval will start to slew randomly off target. Pressing the 'uncage' button changes it from the crazy slewing to normal sweeping, if you press the hat to try and slew it back over the target the crazy slewing resumes the moment you release the hat. The solution is to re-range-find (the ground) to stabilise - if you are trying to lock an air target with no background, forget it, you're screwed. The BS50 is lovely to fly but frustrating as hell to fight with. These are not joystick issues, they are just terrible bugs that need fixing right now. The locking modes are also terribly programmed. I know that it 'cheats' by using game data (i.e. you can't lock a dead target, so it's not using real image-analysis target locking) so why can't we lock a helo that has a BIGGER ASPECT than a tank at a similar range?
Lascaille Posted November 1, 2014 Posted November 1, 2014 Yes this has nothing at all to do with the joystick or input selectors. OTHER issues may be being caused by misbehaving input devices but the Shkval slewing and mis-ranging is not it. I was just flying against some helicopter targets. I slewed the target box over the enemy helo and pressed the 'range/lock' button - the range appeared, about 14km, it didn't lock. I then experimented a bit and discovered: If you DO NOT slew more until the 2-second countdown on the HUD disappears then the range remains the same. You can then slew more without problems. The problem here is that if you have a moving target you tend to re-slew immediately once the lock fails to keep the target centered for another lock attempt, if you do that then...: If you slew more while the 2 second countdown is still on the HUD then the range will change the moment the laser stops firing (to what seems to be a bit random, I had it drop to 5 once and to 0.1 once. In both cases my helo target was against the sky so there was no 'background' range that could be obtained by the laser). The shkval will then slew madly, and the shorter the displayed range the higher the slew speed. The system is clearly trying to ground-stabilise the 'imaginary' target that's at the 'imaginary' range - and if that range is 0.1km obviously it will slew as fast as it possibly can. This is nothing to do with input devices, this is just a bug. ED, please resolve.
SnowTiger Posted November 9, 2014 Posted November 9, 2014 Oh man.. this is becoming EXTREMELY FRUSTRATING. I do seriously hope DCS gets wind of this issue and comes up with a solution because it's really pissing me off. I can't tell you how many times I will have been in mission for HOURS with only one single target left that the USELESS Wingman finds but won't shoot or takes days to line up on it !!.... So I try to take out that LAST TARGET only have this crap happen over and over and over again just as I am fine tuning and lining up on it. Then getting zeroed in on it and the Psycho Slew goes nuts AGAIN and AGAIN and AGAIN Only to get blown out of the sky because I can't get back on target. And I guarantee that it has NOTHING to do with ANYONE's Hotas. I have a brand new Hotas and this crap is Still Happening. This has to be dealt with ASAP because it makes BS almost untenable and definitely unplayable. SnowTiger AMD Ryzen 9 7950X - Zen 4 16-Core 4.5 GHz - Socket AM5 - 170W Desktop Processor ASUS ROG STRIX X670E-A GAMING WIFI 6E Socket AM5 (LGA 1718) Ryzen 7000 gaming motherboard Geforce RTX 4090 Gaming Trio X - 24GB GDDR6X + META Quest 3 + Controllers + Warthog Throttle, CH Pro Pedals, VKB Gunfighter MKII MCG Pro G.SKILL Trident Z5 Neo Series 64 GB RAM (2 x 32GB) 288-Pin PC RAM DDR5 6000 RAM
Nate--IRL-- Posted November 9, 2014 Posted November 9, 2014 Get me a short track - I'll get it looked at. Nate Ka-50 AutoPilot/stabilisation system description and operation by IvanK- Essential Reading
Isegrim Posted November 9, 2014 Posted November 9, 2014 You will find out that it slews around when you look their Track Nate. And if you fly later yourself the same track, it will not. This is what i find out everytime. ISE "Blyat Naaaaa" - Izlom
Recommended Posts