Sh4rk

There are so many possibilities, I don't know where to start. We'd need to look at your in-cockpit switches or keybinds. Can you post a video, or maybe a recorded track file?

TL;DR Short answer: Yes. Page 13-17 of the manual: 7 and 9 are the shutoff valves, 8 is the crossfeed.

Possibly the same fix, read above. I'd also recommend having a separate user folder (under Saved Games) for VR, not the same as when running in 2D. So the settings for each are separate. I run DCS.exe with the -w option e.g. DCS.exe --force_disable_VR -w DCS.novr or DCS.exe -w DCS.vr

Tunguska also does, but you have to keep the aiming circle on target. It helps you lead a bit, otherwise the missile will be in 'lag pursuit', losing kinetic energy and is more likely to miss. It does, and is the proper way. Or at least more like the real thing and any real gun or missile turret. Using the mouse to track a beaming target is next to impossible, as you run out of mouse pad / desk before the missile reaches the target.

Also had that issue and had to keep chasing for a cursor to be able to put the filter down. It could maybe be fixed by allowing you to click anywhere near that region since there isn't anything else there.

I understand what Hippo wants, but I think it's a bad idea. The helo would drift on its own - as trimmed - until you moved the stick back to center before releasing the trimmer button. I think this would make you need to correct (and overcorrect) as quickly as you could after moving the stick back to center, and releasing the button. It'd be akin to using the "central trimmer mode" in a Force Feedback joystick (which is what the default mode is meant for). I've done that before (when using a FFB stick) and wondered what the hell was going on with the stick going limp until recentered. The "center to regain control" mode is the best compromise for a spring-loaded, non-FFB stick. You just have to get used to remember where the stick is trimmed to, and quickly move it to that position, before pressing Trim Reset.

ABRIS does have a function for saving the ABRIS information to the "database", which is meant to save that inside the track / mission file. But as far as I've tried, that function was bugged (didn't work). I've even written my own mod to it so it'd save to a file instead (and I could load it manually in multiplayer). Maybe it now works in single player?

What if you reset your barometric altitude to QFE / radar alt?

BMP-3, even the upgraded versions, are rated for 12.7mm (.50) rounds, not 30 mm. They had become like they were made of paper in early 2.5.x, and were being killed by 7.62 mm gunfire even. Then they got "fixed" (buffed) but maybe a bit too much? Or maybe it's the Ka50's 30 mm gun that needs to be fixed.

Of course! Check again in 2 years The prototypes though, and specially #25 Yellow (the original BS1/2 reference) were seen flying with 6, or none, never less. Only the Ataka missiles are carried in racks of 2 or 4.

Here are some comments on that. TL;DR: the new features are fictional.

And where does this "KABRIS" thing come from? Kerbal Space Program? I've never seen it called that anywhere. Instead, here's a pamphlet describing the system. I don't think it includes a missile warning system...

To be honest I'm also a little disappointed with the fictional stuff. In a sim where realism has always been paramount, this breaks the spell a bit. And of course what it needs the most are fixes to the existing systems (Shkval). Say what you will about your skill, in 1.2.x or 1.5.x (before they refactored laser designation for the Harrier's and F18's pods), the Shkval used to work and lock a lot better, even if it already didn't really simulate contrast locking. As for the new features, as I posted earlier I think something much, much simpler (like a directional LED panel, similar to the LWS or Beryoza) would be much more credible. And the Iglas could be mounted on the existing hardpoints - no need to add two more? Just add them in the proper pylons, like in other helicopters. At the expense of carrying some or all Vikhrs or course, but 2 Iglas + 6 Vikhrs + rockets would look like a valid setup and could work in most missions where an airborne threat is expected.

You took that from a CGI video talking about the system, not from a cockpit or a picture of any real object or screen. As much as it's meant to portray the system, it's not a good (reliable) source. Care to share the other cited source (photograph)? Because the Ka50 is old, and if its other systems are anything to go by, a high accuracy, high resolution missile cue on a MFD doesn't fit with the rest.

Yes someone asked for this before. No word at all regarding payload in the BS3 except that it'll have Iglas.

As far as I believe the Ka50..52 to have MLWS and want it in BS3, that new display in the ABRIS does look game-y. I was kinda expecting the (real or fictional) system to be more like the existing LWS (4-directional) or, at most, similar to Beryoza.

Turn on the fuel pump, open the valve, and make sure throttle is IDLE and collective is fully lowered before cranking. You may have broken / bugged the engine by skipping one of those.

DIRCM apparently got left out, all the rest will probably reuse some of the Su-25T functions. MLWS will light up the same panel as the UV-26, and show information on the ABRIS somehow?

It's an old discussion. Refer to this old post Note that in the picture, it's a Ka-50 - the 52 has a different window configuration and snout, being more rounded, not square. Also the Ka50 being but a prototype and the testbed for the production Ka52s, it isn't totally untrue that it could carry Iglas. There are even cockpit switches for them in the old Ka-50! Finally, ED probably knows more than we can only find on the Internet and magazines about the Ka. If you want to know more about what we've been missing, just look for "no function" in the BS3 manual.

There's a keybind to turn the AB detent on/off - "Cycle Afterburner Detent - ON/OFF". But using the Finger Lifts to go past the AB detent once seems to disable it forever until you use that keybind to enable it again - seems bugged as of 2.7. Also using the Finger Lifts to move between IDLE/OFF isn't working - the dedicated Throttle Left/Right IDLE/OFF/IDLE keybinds are working fine, and I can see the throttle lifts being automatically lifted as the throttles move when I press those. The Finger Lifts animate in the cockpit, and I'm moving the throttle to cutoff and forward repeatedly, but the throttles don't go to IDLE / OFF as expected. In the picture, the lifts are up, but left throttle won't go to IDLE nor right will shut down when I zero the throttle.

Depending on your specs, yes, the smoke from the missile launch will lag your system down to hell, making you miss the shot. It's even worse in multiplayer (which is already taxing per se). I had that problem before...

Even without a proximity fuze, being optically guided, it'd have a radio fuse and be detonated by the operator at that point (a close miss). That said, on the topic at hand, the missile does have a bit of "lag" behind the operator's aim on a beaming target. That, I think, is normal and expected, as the missile has to constantly correct over the radio link to follow the operator's guidance. Much like the Vikhr lags a bit behind the Ka50's laser when lasing a crossing target.

I have the same issue, except if I alt+enter to fullscreen, the mouse in menus, rearm windows etc. (white bullet) is now "confined" to what the DCS window bounds (not in fullscreen) were. That is, I can't click anything past just a little to the left of center as the cursor won't move there, it stops by a vertical invisible window border (even though it's in fullscreen). Looking for a workaround.

On Oculus v28 and I get that white band sometimes. It's in the bottom of my view though, not at the middle.

You need this https://www.digitalcombatsimulator.com/en/shop/modules/dcs_black_shark_2_upgrade/ If you can't buy / acquire it through the store, maybe you can ask ED support.