Volk.

Don't have a trackfile for this specifically, but the Shkval seems to stutter or jump, especially if you tap the slewing hat. You can see it on this timestamp: It appears to be regardless of which slewing axis vs. ku-31 setting. It didn't happen before the 2.7 update. Laser nor inertial tracking have been engaged, and this is from a stable hover-mode with no wind/turbulence - it's purely moving the Shkval itself. I don't know if it's related but I've also seen quadrants of trees etc. pop into existence on the Shkval, which I don't recall seeing before, at least the first time you scan over things. I don't know if this is intentional to reduce frames from loading textures etc.

If you set the slewing to the Absolute Shkval Horizontal and Vertical axis (and clearing out the Ku-31 keybinds), then you can slide from e.g. diagonally up-right to down-right and back again with subtle movements. If you max out the hat's deflection, it push it as far as it would go diagonally and then try to change direction it stops moving in one axis. e.g. going diagonally up right then keeping the hat held right but transitioning to diagonally down-right, it stops moving right and just goes up-down until you release the hat. Track file attached. This timestamp also shows it in video if that helps: ps. this is post 2.7 update running OpenBeta. Slew Axis bug.trk

good spotting there.

Not that I've found. It's loaded at startup. All you can do is hide it by turning off tactical info, or use other 'marker' lines and such to cross off what you've confirmed is gone/dead. Think it's loaded by the ground crew/pre-flight by maybe a cartridge or something. If you want updated info, easiest is possibly to de-spawn and re-spawn in that role, which of course also resets your laser coolant.

There are controls behind the cyclic to the right of the landing gear lights to suppress Almaz messages. For normal startups though that shouldn't be be off or muted though - so somethings weird with your install/version maybe.

Go to the main menu > options > special settings tab > Ka-50. Change the trimmer mode from default to central position. It does exactly that. Just check your physical hardware doesn't have large deadzones - or you might have issues with it releasing your controls. The wingman AI has decayed some over the years. Currently they suck at attacking stuff. Generally I've found they do respond to commands (sort of) and do reply if able. Might be they're borked there. Did you change radio frequency and are the roughly in line-of-sight to get the radio commands?

Hydraulic loss, I think especially main hydraulics can lead to loss of the autopilot channels. Interesting mission if they start you in a storm with no/bleeding hydraulics - sounds fun.

Ok. I misread - you want that altitude p for rad-alt as 'r' or 'm' or such, and the lock TA/N/C stuff as I guess L and LA? Yeah those would be some kind of mod.

Actually it makes perfect sense. If you've lased up a new target and your Shkval is pointing at something, then selecting a data link type would be telling it you wish to designate whatever the Shkval is looking at. Again there are workarounds, but the base logic of it is sound.

Yeah, would be cool if we had the contrast lock coded. Number of times it 'should' lock with normal daylight visibility. That said, given it wasn't night capable, odds are in the low-light/visibility our IT-23 screen might just be a haze rather than showing that crystal-clear contrast we get at the moment. So no option for manual guidance anymore.

There's avionics language for the ABRIS, but under the main menu > options > special settings tab > Ka-50 there's options for an English cockpit.

Select that data link target so it flashed on the ABRIS - then press Clear on the PRTz panel. You can't select stuff on the PRTz if your Shvkal's in use and you locked/lazed something, so you typically need to reset it first. There are workaround for this I've covered in a vid on data link targets. Flicking the DL switch off-on or the wingman/commander knob to off of course resets all data link targets, like you mentioned.

Could be your INU switch (behind your right shoulder) is turned off, though if you started hot/midair, then might be you tried using Hover mode/auto hover while either your doppler wasn't warmed up yet or you then descended beneath 4m AGL, which would turn off all the channels, make them flicker until you either killed hover mode and manually re-engaged them or ascended high enough. Damage can also leave you without autopilot channels.

Thanks. ps. I've been promising myself I'd get the next vid out on data link/target stuff for the past 2 weeks, but work has gotten in the way. Next one is incidentally on mission editor loading your ABRIS vs PVI etc, so I've was tweaking the scripts when you posted. I'm suspecting one of two things. Either maybe you're resuming a track file from a previous mission (rather than a clean .miz) and that somehow has these preloaded things - in which case unless that trackfile starts from 'spawn', it might be a bug. Or that it's just a bug. Reason being on your image there with the data link targets at mission start - you have TWO wingman ID "2" Sharks on your ABRIS - which is impossible. If you have conflicting IDs, then they go disco-light and flicker between them, but I think that flicker doesn't overlap - ie. you can at any one point in time only see one "2" on the ABRIS. So that's VERY weird. The waypoint info should stay, and I'm guessing that flight plan is correct. Also I don't think I've found a way to replicate Data Link icons. You can replicate what the ME does for target points with reference points etc, but for data link targets you'd need to go through painful line-drawing each icon - there's no built-in house-stamp like that Data Link Target:Ingress Point on the ABRIS - it has to come from the PRTz panel. Either way if it were conventional data link target and wingman circles, you'd be able to cull it with DL:Off or cycling the Wingman/Commander knob like Cheetah said, which should erase all that memory. So might be a case anyway of making a video/posting a track for ED ;-)

Tactical info comes purely from ground units that represent a threat in your mission, ie. from the mission editor. If those threats exist on your map, they'll exist on your ABRIS. It gets a little more complex, but that's the easy version. There should not be any ABRIS threats if you have no hostile enemy ground units in the map. You can't select these as targets via Data Link panel or Target Point. I'm not sure of a condition where you have Data Link Targets at time of spawning. Target Points, sure, but not Data Link Targets.

I'm not sure if this is a bug. I mean it could be if it doesn't work that way on the IRL Shark, but that might be exactly how it works. Tactical Information - those ABRIS threats can't be changed from in-mission - at best you can hide it. Data Link Targets can easily be removed by selecting them and clear (no 2nd row button selected). Anything PVI-800 can't be deleted in-flight - you can only change the points that are already there. Like Cheetah said - not sure these really need clearing unless you were running a multi-sortie thing and chose to repair lasers instead of respawning.

Weird. Some stuff to try: Check your system resources as you do it, including video ram - maybe rendering the screen tips it over the edge Lower the helmet mounted device. Then look around while holding Uncage Shkval - see if that also causes stutter. If it doesn't then it might not be a frames / cpu / resource issue Change your slewing keys from the defaults to something else - see if it still causes an issue. See if there was any specific key, like only slewing left, that causes it or all directions Bind slewing to Axis instead of K-031 keyboard inputs. Generally I don't recommend this, but maybe that solves it? Maybe test another mission? Could be the one you're on has a really large number of objects around to be rendered... Also worth checking if opentrack itself stutters on it's screen, or if it's only in DCS...

Moving the Shkval around would force DCS to use more frames to calculate both your normal cockpit view as well as what's rendered on the Shkval. So maybe doing so bleeds off too many resources that OpenTrack then struggles to track properly. Though I'd guess it would lag or slow down in general though instead of shaking like that. Do you maybe have any keybinds/shortcuts in Opentrack (default or otherwise)? Like maybe it's paysing the camera tracking or something on one or more of the slewing keys?

Sorry, under Misc. tab. Assuming it's not another setting/curve/saturation/double bind/actual hardware issue with the trimmer button, the below might help.

Alternately try another button for your Speedlink stick's trimming. Could be that's bust or that while it's depressed it messes with the stick's x & y inputs (ie in axis tuning screen, hold down trim and then move stick to see it behaves differently). There is also a Force-feedback tickbow in the general settings that you can turn off. Not sure what that does but heard it helps some folk.

I don't fully recall, and I don't think I have footage of that from an external view saved. I think weight on wheels it did stay down, but when it re-arms it levels off again (or at least angles as per uncaged shkval angle).

For what it's worth, I've played around a little in the Ka-50 and couldn't find a feasible way, including turning off Nav, INU, think even K-041, which of course isn't advisable, to 'reset' the PVI-800 waypoints like one can easily do with the Data Link, but no luck. So I think you're stuck with whatever has been pre-programmed from the mission or what you've coded yourself. All you can do is change the coordinates to something else.

@baldeagle611 you could try a different stick. Maybe it's best if you go on Discord or something and use that to livestream your screens so someone can diagnose what's wrong - assuming it is a setting and not maybe a bust button on your physical stick.

It was specifically designed to give enemies a false sense of hope, seeing the launchers pointing down so they'd assume the Shark is toothless and then lull them into coming out of cover so that the flanking Raptor wingman can take them out ;-) Whether it should point down after going winchester IRL I think is one of those really obscure facts one just won't get the answer to.

You didn't do anything wrong - once they're spent the launchers tip down. No need to deselect them or such specifically. Once you re-arm the launchers will point forwards again until the Shkval points it at another angle.