SnuggleFairy

Indeed, I have no problems. The BS3 module is in an adequate/good shape right now

uhm, why not?

Same. I was only able to change SELF COOR with a fix point, INT PNT doesn't seem to affect alignment

Fast alignment drifts with pitch and roll angles of more than 10 degrees. You need to do normal or precise alignment

Alignment works well for me after the last update. Are you on open beta and have the latest patch installed? Upload your track here, showcasing the problem, and I can take a look

There are mentions on the forum here and there, that it's dependant on the QFE setting on the altimeter, so that's how it knows your altitude. That's how it should work i guess, but that's not how it works in DCS. No matter where the QFE is set, the datalink saves and ingresses on targets at exactly the same point

I made my own mission as well. I noticed my old mission had the same setting on "no alignment". I set it up with fully realistic as well. Are you on open beta? Can you attach a track here?

All of the above are manual. Ka-50 slots that are set for hot start have alignment preset in the mission editor, and there's a way to disable the need for alignment as well. I think that's what they are referring to as "auto"

From my understanding, the DISS is part of the K-041 Rubicon system and it gets turned on by that K-041 switch near your engine startup panel. It takes about 150 seconds to initialize and when you see your HUD appear, DISS should be ready as well. I don't believe it needs to be warmed up beyond that, the manual says it's ready for use after 150 seconds. After you flick that K-041 switch a yellow warning light "РАНЕТ" / "HUD NOT READY" will come up on the warning panel above your head. That one just warns about the HUD, but it's the similar timer as the DISS. I'll extinguish once the HUD is ready and DISS should be ready as well at that point. From there, if something is wrong with DISS, EKRAN will tell you that.

Maybe that's how it's supposed to be? I don't know how real KA works. But in DCS if you roll or pitch more than 10 degrees it'll give a "AC-POS. CAL. DATA" warning light on the top lights panel (aka "Aircraft position is roughly calculated using air data systems information") and that results in a drift. After you level out, the light extinguishes and it continues without drift, but with already accumulated error from the maneuver. I'm guessing with quick alignment the accuracy is reliant on the DISS system, and the pitch and/or roll of more than 10 degrees prevents DISS from interpreting the received data correctly.

у меня тоже чуть правее и ниже. Причем выставка атмосферного давления на выход шквала никак не влияет. В экстремальных значениях давления шквал выходит и запоминает цели в одной и той же точке

The one in the manual with 3 different options for alignment. Precise alignment drifted 0.1 of a minute of a degree after 1 hour and 45 minute flight (aka no noticeable drift). Normal alignment drifted 0.3 of a minute of a degree after the same flight (no noticeable drift), and quick alignment drifted every time you pitch or roll more than 10 degrees (noticeable drift but you can still work with that)

Какие ограничения у ДИСС по высоте?

Looks like INS and auto turn have been fixed. Datalink is still a little off, but it's usable and possibly realistic

Yeah I hear what you're saying, and I see why people are disappointed with the BS3 release. ED definitely dropped the ball on this one. But, in my opinion, it's not as bad as people make it out to be. I, personally, haven't touched the Shark 3 since I discovered the INU bug, because i don't want to fly it in this state. But I have full confidence in ED to fix it. But getting angry on the forums doesn't help anybody. Doesn't help you, or me, or ED. So let's do some bug reports and ED will eventually go through them, that's the best we can do. We all want the module to be better - we paid for it

Uhm, not sure where you got that idea from. I don't see that in any of the manuals. It's designed for 5 series of 16 cycles in each series, with a 5 second cooldown between cycles and 30 minutes between series (source: https://forum.dcs.world/topic/168736-bag-s-vihrjami/?do=findComment&comment=3359770 ). Except it doesn't work like that. There's a temperature/durability value that constantly go up with each use, and in my testing it burns out consistently after 24-30 Vikhrs plus some cannon work, no matter what pauses you take. And the "coolant" never used to get refilled with the rearm. It gets fixed with repair, but you could only trigger the repair if something else was broken in addition to the laser. They fixed that recently - you can trigger repair with burnt laser

I've read some of your bug reports. Some of them are valid, but none of them are major game breaking bugs. To my knowledge, Shark 3 has a couple major bugs (like INS) and a few minor bugs (like english cockpit translation issues, fixpoints 3 and 4 being mixed up etc). Devs promised to fix the major bugs as well as a bunch of minor ones already with the next patch. But a lot of other "bug reports" there are trash. What's your source?

It'll show the correct fuel level at mission start, but the gauge will not update with the switch set to off. Not sure how it is in real Ka, but possibly correct as is

sorry your track isn't playing properly for me. On my screen it looks like you're trying to save targets far in the water. I just made this yesterday:

@Taz1004 Point me at the issue, because i don't see it

Because if you fly the BS2 right now, DL and turn to target work perfectly. Jump into the BS2, make a short track of your issue and post here, and i'll take a closer look

Datalink isn't working right now due to INS alignment issue (the new bug i mentioned above), wingman refusing to fire due to AI code problems (not Ka-50 issue). Most of the "bugs" reported in both BS3 and BS2 aren't bugs at all and just people not knowing how to operate the airframe. Laser burning out is a bug, because the laser never cools when not operating. Eventually it just reaches critical temperature and burns out.

Bugs like what? The only one I remember is the laser burning out.

Well they keep putting man hours into an old module to try to improve it and bring it to modern standards and they don't charge for most of those improvements. I don't think you can call that "milking" this module since they continuously putting money into this module to try to improve it for us. I'm not sure how they missed the INS alignment bug - there could be a few scenarios. I think ED had this before with a different module - they did their internal testing and everything was working correctly, then they released the patch onto the live servers and bunch of things were broken for the customers. Everything was working on ED systems, but customers had bugs even though both versions were supposed to be the same. And that's just the nature of coding sometimes - a butterfly flaps its wings in Singapore and Ka-50 INS breaks. Also it could be that they were pushed to release the module before Christmas and didn't test it properly. Which is unfortunate, but that's sometimes the decision a business has to make. They promised a patch in January, so as long as they fix it, it's fine by me. In terms of "no statements on the bug reports". Bug reports are tricky to go through. 95 out of 100 people that post a "bug" on the forums don't know what they are doing in the airframe. They do X expecting Y, but get Z instead and they go on the forums and post a "bug". They say "I did X and i should have gotten Y, but got Z instead". And that's it - no additional information and no track file. It's like going to a doctor and saying "my stomach hurts" and then sitting there silently waiting for a diagnosis. Track files are hugely helpful, because you can see exactly what the person did and when you play someone else's track file it also applies their game settings to it. So with a track file you can eliminate a lot of variable trying to determine the reason for the issue. Without a track file it's too time consuming to try to diagnose a problem. And again, 9.5 times out of 10, it's the person doing something wrong with their startup or operation because they misunderstood the manual or something. So, they need a guy going through tens or hundreds of bug reports and try to determine which ones are actual bugs. And, I'm gonna go into the realm of speculation right now, they don't have enough staff for that to comb through everything and reply to everything, because I don't think they make enough money as a company to be able to afford that. They make a niche product with not a lot of customers. I bet their RnD costs are astronomical and they are barely making money as is. Ka-50 has 1 major bug right now and a couple small ones. The major one being incorrect INS drift during cold start. And there are a bunch of issues that stem from that - broken autoturn to target (it's not supposed to be tied to INS, but it is right now), broken datalink and navigation. 1 bug but there are like 15 threads here about it, that someone needs to look at and reply? Also don't forget there are Russian forums, and the Ka-50 is gonna be more popular with the Russian crowd. They have their own active bug report section and discussions. So just because you don't see a reply there, doesn't mean that an issue hasn't been acknowledged. Bottom line is - if we, as a community, need to make better bug reports. Maybe that way we'd get more responses from ED?

Спасибо! Я сюда вписал этот баг. Там у меня и видео есть, которое показывает и увод ИНС, и как АДВ работает и даталинк, и как оно всё ремонтируется с коррекцией координат