F16 - Please, start the fixing and stop to implement new issues.

[Pillowcat]

31 minutes ago, LeopardLenin said:

To me it sounds like

Spoiler

kekekeke

 

[slughead]

IMHO, you can no longer say that the Viper is Early Access. Wasn't it first released in 2019? Five years ago? It's probably best to stop using "early access" in combination with the F-16.

[ghostskills82]

Some people probably shouldn’t mess with early access modules... Apparently, not everyone realizes that early access is tied to development, and during development, errors and bugs may happen.

Early access = may contain bugs and errors during development  
Full release = optimized, basically complete, almost free of issues

Seriously, does this have any real impact on your life, Nedum? If yes, maybe it's time to reflect a bit... Someone doesn't like the state of the DCS F-16? Then just fly BMS in the meantime or swap to another module instead!

Edited October 7, 2024 by ghostskills82

[Q3ark]

You’re wasting your time with this thread, in the context of DCS an early access module doesn’t only mean that it’s not finished and parts are still being added but also that it will be full of bugs as they add the new features because they don’t test properly. They think that early access is a free pass for bugs. If you check their complete modules you’ll find bugs and problems that just get left because reasons. ED have always been this way and always will be until they go under anyway.

[nessuno0505]

ED have always been this way, you're right. But what we are asking here is to change this behaviour: you have a stable version of the game, keep it as bug free as possible. Do not push half cooked upgrades full of bugs in the stable: keep them in the closed beta, test there as you want, and then push to stable when it's all bug free. Early access = incomplete with bugs. I can accept incomplete, and I can accept also some bugs (we have bugs in released modules too), but I can't accept tons of bugs just because you are testing. Release version is for gaming, we want to play not to be your beta testers. Is this clear enough?!?

[jubuttib]

On 10/5/2024 at 8:30 PM, NineLine said:

This is a common issue in Early Access products and in fact, shows more so that it's being worked on. As new systems and features are added, it can affect older systems either unintentionally or by design in order for new things to be added. We do our best to mitigate these issues, but it's not always possible. Also, rarely do these issues make it past our Q&A team or Tester team (and are known before anyone), and just because they are marked reported on the forums does not mean we missed them, we are only acknowledging that these are reported. We do not enjoy or look at adding new issues, but it can be the downside of active development on a very complex aircraft. Most early-access aircraft see very similar problems.

I have worked in the game industry in a few companies, making some very complex games, mostly simulators, and talked shop with many colleagues, and operating like this, even on an early access product, would just not fly in any of them.

If a new update broke an existing feature in a major way, significantly affecting the usability of a given vehicle or somesuch, AND it was caught by our testers, that part of the update would not be allowed to go out, even if other updates did, until the issues were solved. A couple of those kinds of slip ups and you'd seriously risk getting fired.

This is specifically new stuff breaking old stuff AND being caught before release. If no-one caught it before release, fine, mistakes happen, and quite often those issues aren't 100% pervasive through the userbase. If you introduce a new feature that's partially broken, and issues with it were caught, also not that bad, it's a new thing that's under development.

But pushing updates that knowingly (i.e. QA caught them, and they're known about before pushing the update) break old systems and majorly impact the functioning of those systems, that is just immensely poor form. It's always preferable to roll back and withhold those updates until they are actually working.

Mistakes happen, absolutely, and I'm very sympathetic to development woes. Making games is damn hard, but it sounds like you're making things even harder and more stressful for yourselves operating like this. 

Edited October 8, 2024 by jubuttib

[BIGNEWY]

Again thank you all for your feedback but we are going in circles now, the issues in the last patch were a result of waiting for the phase 3 radar work to be fully merge, we will have fixes coming in the next patch. 

Thank you