Does your Shkval slew around uncontrollably? Report here. The “Crazy Shkval" Problem

[Hunden Ynk]

Yeah, since I started to only lase when ready to fire and turning it of otherwise, zero crazy-skhval. But I thought that had to do with the ranging becoming inaccurate as described by Karambiatos. Is that a limitation to be expected by the range finder system? I remember being able to range one target, move on to next and the range would be remembered. Very useful when engaging with the canon for example. Now, as soon as I slew off the point I lased, the range will drastically change.

[karambiatos]

Here are two more tracks, the distance jumps are incredible, every time you laze and then move the piper the distance jumps by 1-3 kilometers,

sometimes the distance jumps, right as the laser stops working even if you havent moved the shkval piper. This should definitely not be happening, at least it does not happen in BS1 and it wasnt happening to such an extreme degree until this newest patch.

 

This makes adjusting your shkval on the target or moving it to a target at the same distance without relasing impossible since the moment you move it will jump to a crazy distance.

Shkval Distance error moving.trk

Shkval Distance error hover.trk

[Katmandu]

Ok now that does look like a bug!

[Nate--IRL--]

Here are two more tracks, the distance jumps are incredible, every time you laze and then move the piper the distance jumps by 1-3 kilometers,

sometimes the distance jumps, right as the laser stops working even if you havent moved the shkval piper. This should definitely not be happening, at least it does not happen in BS1 and it wasnt happening to such an extreme degree until this newest patch.

 

This makes adjusting your shkval on the target or moving it to a target at the same distance without relasing impossible since the moment you move it will jump to a crazy distance.

 

This certainly isn't a new bug - it has been around for quite a while. Severity of it seems to alter on different parts of the map.

 

Nate

[Katmandu]

Here are two more tracks, the distance jumps are incredible, every time you laze and then move the piper the distance jumps by 1-3 kilometers,

sometimes the distance jumps, right as the laser stops working even if you havent moved the shkval piper. This should definitely not be happening, at least it does not happen in BS1 and it wasnt happening to such an extreme degree until this newest patch.

 

This makes adjusting your shkval on the target or moving it to a target at the same distance without relasing impossible since the moment you move it will jump to a crazy distance.

 

Chizh's answer: "Calculation of sloping distance that is at a very sharp angle (ie at low altitude) leads to very big errors. The main thing is that rangefinder gives the correct distance when you make the measuremnt. "

http://forums.eagle.ru/showpost.php?p=1872274&postcount=2

Edited September 13, 2013 by Katmandu

[karambiatos]

Chizh's answer: "Calculation of sloping distance that is at a very sharp angle (ie at low altitude) leads to very big errors. The main thing is that rangefinder gives the correct distance when you make the measuremnt. "

http://forums.eagle.ru/showpost.php?p=1872274&postcount=2

 

So if its calculation has much inaccuracies, why doesnt it just keep the last range that was lazed in, that would make more sense, well at least to me.

[Hunden Ynk]

Thanks Katmandu! This is all very interesting.

[Katmandu]

So if its calculation has much inaccuracies, why doesnt it just keep the last range that was lazed in, that would make more sense, well at least to me.

 

WHy - I do not know, I guess it has a predict function and this fucntion has its uses and limitations.

[gunterlund21]

I believe I ran into this issue yesterday. I locked on a target and fired a missle that destroyed the target. When I tried to go to the next target the Schval kept drifting off to the right and would not lock on the next selected target. The only way I could stop the drift was to reset the schval and reacquire the targets.

[Darkwolf]

Strange behavior yesterday.

 

Impossible to lock anything with the skwall. Then after some quite erratic shot, the reset button on the firing computer stopped working. the skwall was just stuck in the middle position, no way to move it around, no way to lock, distance showing strange stuff, getting the firing computer on and off wasn't helping.

 

Some moment, after turning the thing on and off, i could lock and barely shoot, but the problem was happening again.

 

I'm flying the shark for quite long time now, i was really stuned at the strange behavior.

[toby23]

With 1.2.6 this is happening a lot and I never had it before...

[BigOHenry]

Same here, in 1.2.6 its happening a lot + crazy laser (crazy range)...

[Devrim]

Many things happening to me in v1.2.6

 

I've never had crash issue before. Last night DCS crashed three times during missions, in an hour! :(

[Midnight]

Never had this issue, started now on 1.2.6

 

Have the X52 Pro Siatek

[tietze]

Now I've been noticing a special version of the crazy Shkval problem. Usually I've had luck with curing the crazy shkval problem by resetting the weapons system and/or by using the laser range finder when locking a target or ground.

 

Now none of these methods work. When designating target using HMS sometimes the Shkval designator moves down, you can counter it, but it keeps moving down. The following does not stop the behaviour:

• Locking target again
  
• Uncaging shkval
  
• Locking a target without laser
  
• Using laser range finder when locking a target
  
• Resetting the weapons system
  
• Turning the K-041 on and off
  
• Turning the weapon system power on and off
  
• Repair
  

 

Only going back to spectators and selecting aircraft again cures this problem :-/

[Suchacz]

I can confirm crazy shkval in 1.2.6, it is unplayable now :cry: If it was left alone without any input for a little while, it starts slewing left and down by itself. Pressing Enter(Lock + Fire laser) stops it.

Edited October 19, 2013 by Suchacz

[agentkgb]

Hi,

Confirmed here aswell, however I'm still able to get rid of it by resetting the weapon system.

 

- KGB -

[Unformer]

Hello all,

 

Using X box Controller in addition to Hotas Warthog works fine for me with the following Settings:

JOY_RY:

Deadzone: 0; Saturation X: 100; Saturation Y: 40; Curvature: 0

User Curve: 0/4/13/17/33/38/51/70/80/90/100

JOY_X:

Deadzone: 0; Saturation X: 100; Saturation Y: 40; Curvature: 0

User Curve: 0/4/13/17/33/39/53/70/80/90/100

 

I transfered the same Settings also to the ministick of the Warthog throttle and it is more precise, but not as precise as with the X Box Controller.

 

Regards

Unformer

[karambiatos]

i've noticed if you arent tracking and launch a vikhr, afterwards if you move the shkval the ranging will go to the exact same distance the vikhr is, effectively trying to lock it, its most noticable during night since you dont get tracking, ill try to get some tests in later.

[Devrim]

Tonight that happened:

 

Shkval started to slew up constantly again - you know. Nothing could stop it. Resetting targeting systems, autopilot off etc. I tried what I can, except shut down my PC!

 

Then... For no reason I pressed "Num8" and it stopped!

 

What's the story of my Num8? I use SST software of Saitek.

• POV1_UP is assigned to Num8. In same way;
  
• POV1_DW > Num5,
  
• POV1_LT > Num7 and
  
• POV1_RT > Num9.

I use this way to slew Shkval diagonal.

 

15 mins later, Shkval started to go right itself. I pressed Num9 (POV1_RGT), and it stopped.

 

Are the pilots who experiencing this problem using any software like this, or is this a new SST bug for me?

[Suchacz]

I have this faulty behavior with my G940 too while I'm using its analog hat(ministick) to slew the shkval. Newest update changed nothing.

Edited October 24, 2013 by Suchacz

[Dejjvid]

I have this with my Warthog and not using any software to control it.

 

This is to most annoying bug in DCS World, and it's a mystery the devs ignore it...

[Devrim]

May be they can't find the bug. :D

[acemark]

Hello, would like to report that I am experiancing this problem alot with 1.26. Ive had this problem for a long time and hoped that removing the last piece of Saitek hardware [X-52 pro throttle ] might help. Nothing seamed to change.Saitek software was never installed.

So now Im using home built cyclic and collective wired to Brydlings B256-A13 board for all axis, Hat switch is assigned to the boards hat function.

The problem is allways eliminated with weapons reset button , but its happening more offten now.

Thanks Mark.

[chardly38]

I have a Warthog also andf in the past it was rare. Now in 1.2.6.19532 when it starts it will not stop