I´m dissapointed from BS3 .....

[Schlomo1933]

For me its looking like , EDs 1st priority was releasing the shark before christmas , without testing his biggest new feature (the new Inu system).

The whole INU is completely bugged.... it starts with the alligment thats not working.

-the heading is wrong,- inu fix works only sometimes , and when it works the heading is also incorrect.

And this will make that the auto turn to target is also messed up.... 

For a module in 2022/23 it is sad, that not all buttons and knob´s are possible to map as 2 or 3 position bindings ar as axes. 

So many people use/build their own homecockpits or some important parts of a cockpit. why u dont support them ? 

Also shkval is tracking moving targets, even no "moving ground target" is selected. The shkval have not changed since BS1 ... it dont track/lock with contrast. It is still cheating in a bad way ....  all the contrast modes are useless.

The possibility to open all the hatches is a nice Eye Candy, but its eats frames (espacially in VR) even the hatches are clothed. because all whats         inside is still rendered.  

The Igla ... hmmm ... you know the discussion about it. I like them but dont realy need them.The MWS is realy nice and saved me now a lot of times. 

The look of the ouside model is amazing , but also shows some mistakes... like the broken cockpit glass after a hit what is only visible from outside view.

I´m pretty shure u ED will fix the Bugs fast as possible...

but for an update that is needed to pay for it,its just not enough. Especially what makes me really sad is the fact, that the Shark was your first high fidelity module (and also my first love in 2009) .

Sorry ED, but i´m disapointed .... 

 

(Pls. Could a moderator send this please directly to ED ?)

Edited December 29, 2022 by Schlomo1933

[ADHS]

Hello.

I agree with your point. The only that i can add
is that in lately years, updates have fixed many
of the problems that for years were stood unresolved.
If this was a KA-52, glady to wait so this to comes
out of the "Early Access" status, even for a decade.
But for this one, i do believe that is an extension
of BS2 just for AH-64D to have a more equal opponent.

Thank you.

Edited December 29, 2022 by ADHS

[Dangerzone]

FWIW - it's difficult to read the first post due to some formatting. @Schlomo1933 you may want to correct this (remove whatever formatting you have applied) if you're looking for some more responses.

[ADHS]

1 hour ago, Dangerzone said:

due to some formatting

I can read it. Check if you have special view formating. Or else hover the mouse over the thread and you will ba able to read the text.

Thank you.

[Dangerzone]

I'm just running dark mode in the forum settings. Just letting the OP realise that whatever format they're using is showing up as per my screenshot for users using darkmode. Whether he chooses to do anything about it or not is up to him, just that others running dark mode may skip over his post due to the formatting, that's all. 

Edited December 29, 2022 by Dangerzone

[Schlomo1933]

I have no idea what’s wrong … color is automatic. Text is standard. 
Have u an idea? 

Edited December 29, 2022 by Schlomo1933

[QuiGon]

4 hours ago, Schlomo1933 said:

I have no idea what’s wrong … color is automatic. Text is standard. 
Have u an idea?

Well, just change the color from automatic to black.

[Schlomo1933]

Thank you.

[Fastbreak]

On 12/28/2022 at 5:53 PM, Schlomo1933 said:

For me its looking like , EDs 1st priority was releasing the shark before christmas , without testing his biggest new feature (the new Inu system).

The whole INU is completely bugged.... it starts with the alligment thats not working.

-the heading is wrong,- inu fix works only sometimes , and when it works the heading is also incorrect.

And this will make that the auto turn to target is also messed up.... 

For a module in 2022/23 it is sad, that not all buttons and knob´s are possible to map as 2 or 3 position bindings ar as axes. 

So many people use/build their own homecockpits or some important parts of a cockpit. why u dont support them ? 

Also shkval is tracking moving targets, even no "moving ground target" is selected. The shkval have not changed since BS1 ... it dont track/lock with contrast. It is still cheating in a bad way ....  all the contrast modes are useless.

The possibility to open all the hatches is a nice Eye Candy, but its eats frames (espacially in VR) even the hatches are clothed. because all whats         inside is still rendered.  

The Igla ... hmmm ... you know the discussion about it. I like them but dont realy need them.The MWS is realy nice and saved me now a lot of times. 

The look of the ouside model is amazing , but also shows some mistakes... like the broken cockpit glass after a hit what is only visible from outside view.

I´m pretty shure u ED will fix the Bugs fast as possible...

but for an update that is needed to pay for it,its just not enough. Especially what makes me really sad is the fact, that the Shark was your first high fidelity module (and also my first love in 2009) .

Sorry ED, but i´m disapointed .... 

 

(Pls. Could a moderator send this please directly to ED ?)

 

 

Yes, yes and yes again. Every and every time the same procedure...!

[mtd2811]

How ED managed to release this untested?

The INS was the big change over the 50 and they didnt test it?Autoturn to target messed up and a simple flight would have shown the issues

Are there no internal QA procedures?

Edited: 52 to 50 ofc

Sent from my iPhone using Tapatalk

[LastRifleRound]

I have to say I am continually mystified at what practices an entity could follow that would continually lead to releases like this.

When I bought BS1 back in 2009, I noticed that the advertised "Highly accurately modeled GPS/INS system" never drifted like one would assume from the advertising. The manual said the update feature was performative only. I came right on this here forum to ask about it, and was told essentially maybe they'll add it later.

13 frickin years later, after paying for this module once more at full price and another $9.99, with the latest time the feature being 25% of the advertised feature set in explicit terms, it still doesn't work right and they don't even seem to know how or why or who or what or when it happened and somehow it got out of testing without anyone noticing. How can you not notice this? Someone had to know it, or it wasn't tested. When you fly more than 10 minutes and try to correct it literally dances back across the ring skip fakes and superman punches you directly in the face. It is literally impossible to miss.

Then, when people dutifully reported the bug/s, they got the infamous "correct as is", presumably because whoever tagged the post followed whatever horrifically unreliable procedure leads to these sorts of things not getting caught in the first place (or just didn't check it at all but I repeat myself). Only after persistent lobbying was the tag dropped on 2 of the posts, with one now being confirmed (Datalink one just now doesn't say "correct as is", but remains unconfirmed).

Maybe if we buy it another 3 times and they mega-advertise it we can have INS? People around here are so obsessed with tiny hatches. I just don't get it.

[Eisprinzessin]

My answer is:
 

Bought the BS3, still playing BS2

First time (and i bought nearly everything) that i regret the buy.

[Sneethe]

I'm a bit disappointed with how bugged it is and really hoped for a polished release as well, Slewing the Shkval to Datalink targets is also broken now and slews way off target, also affects the black shark 2,[BS2 still works thankfully] did nobody bugtest the shark before sending it out?

Also why were none of the campaigns converted? I have to keep BS2 installed to play them.

Edited January 12, 2023 by Sneethe

[Schlomo1933]

And no statement on the bug reports from mods and devs…. 
I start feeling that the Shark is just a cow that gets milked till it’s dry from Ed… no love for this module…

which Module  deserves more  Love  than the shark ? It was ED‘s first real module… with it Ed’s glory started…

And no, Flanker an Lock-On don’t count as realistic for me.

 

the only mod (I’m not shure if he is really a moderator) is flappie who is looking at some bug reports…. Big Thank you to you @Flappie

Edited January 11, 2023 by Schlomo1933

[SnuggleFairy]

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?

 

[Taz1004]

Only reason I bought this the day it came out was because it isn't worth $20.

Majority of the bugs existed in BS2.  Just ignored for years.  What I understood in previous BS2 discussion is that INS worked until new Caucasus map was released.  And was never updated.  And it also affected Datalink and how AI wingmen behaved.  I am hoping that ED will finally fix them with BS3 but I think they're just realizing what a mess it's in.

Edited January 12, 2023 by Taz1004

[SnuggleFairy]

15 minutes ago, Taz1004 said:

Only reason I bought this the day it came out was because it isn't worth $20.

Majority of the bugs existed in BS2.  Just ignored for years.  I was hoping that ED will finally fix them with BS3 but I think they're just realizing what a mess it was in.

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

Edited January 12, 2023 by SnuggleFairy

[Taz1004]

8 minutes ago, SnuggleFairy said:

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

 

OP listed most of the major ones.  Datalink not working, Wingman refusing to fire... Most of the BS3 bugs reported, if you search, you'll find it in BS2 thread.

Laser burning out is not a bug actually.  Not being able to fix it was.

Edited January 12, 2023 by Taz1004

[SnuggleFairy]

24 minutes ago, Taz1004 said:

OP listed most of the major ones.  Datalink not working, Wingman refusing to fire... Most of the BS3 bugs reported, if you search, you'll find it in BS2 thread.

Laser burning out is not a bug actually.  Not being able to fix it was.

 

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.

[Taz1004]

40 minutes ago, SnuggleFairy said:

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.

You're saying Datalink issue is due to INS issue which is NEW bug.  Yet this 2015 thread describes same issue.  How is that possible if it's new?

 

[SnuggleFairy]

50 minutes ago, Taz1004 said:

You're saying Datalink issue is due to INS issue which is NEW bug.  Yet this 2015 thread describes same issue.  How is that possible if it's new?

 

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

Edited January 12, 2023 by SnuggleFairy

[Taz1004]

59 minutes ago, SnuggleFairy said:

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

 

Not talking about turn to target.  Looks like you didn't even read that thread.  There already is a thread about DL.  For both BS3 and BS2.  You just have to search.

You're basically saying BS2 has only one bug, and BS3 has just two bugs.  And everyone in bug section just don't know how to fly.  I'm not even gonna try to argue with you.

Edited January 12, 2023 by Taz1004

[SnuggleFairy]

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

 

 

[ak22]

I told myself I would not buy another ED module as they seem to be releasing a lot of them and taking very very long time to finish them. I went ahead and got this as I had some airmiles that were about to expire,  well another release that has not impressed me... at least it only cost me.

[Kappa-131st]

In my squadron, we are back on BS2 because BS3 is a joke...
Navigation, auto turn, datalink are bugged.

INU is totaly wrong. And if it is cool to have "realistic INU" in theory, in practice, KA-50 is a modern helicopter with glonass : On BS2, INU is recalibrated with glonass every 5 minutes. It is realictic on a modern helicopter... Manual realignment of the INU should only be necessary if satellite coverage is absent or the device is damaged (no more Glonass). Except with BS3, they simply removed the satellite registration. So, in the end, the device... Is less realistic than BS2!

The IGLAs... You have to remove the heat sinks and flares from the enemy helicopters, otherwise they are useless... Especially since even when they hit, the AI helicopters have such a life bar that it doesn't hurt them not much... We will continue to use Vikhr at long range (8-4 km), and gun at short range (0-4 km), it is more effective than the IGLAS.

Remains the MWS. It's the only really nice feature of BS3... And again, you shouldn't play in a squadron with 5 or 6 helicopters... Each time an ally fires, you get the alert. And if you don't deactivate the auto flares, these will quickly be exhausted by your allies' shots.

After 4 years of waiting, BS3 have only 3 new features, one is totally buggy, and an other one is practically unusable in combat.
And BS3 bring us a lot of new bugs..

Edited January 20, 2023 by Kappa-131st