[EARLY ACCESS IS A LONG PROCESS]F-16C Forgotten about again

[Tango3B]

Fact of the matter is that we weren't told that the F-16 would be put on hold for the F-18 to be finished. We were told there would be a parallel symbiotic development process for both the Viper and the Hornet. The issue isn't the slow rate at which new features are implemented at. The main issue is that most of the features that are already implemented are broken. This does not merely apply to newly added features, but features that were added +1 year ago are still broken and there's no signs of improvement. As a result of this a lot of the F-16 pilots in our community are leaving to fly other aircraft because it's simply not fun to fly a broken aircraft and ruin entire missions for ourselves and others because we fly an unpredictable, broken mess of an aircraft. I just hope it won't take too long for the Viper to start receiving serious bugfixes, but there's currently no improvement in sight.

 

Actually, the F-16C has not been put on hold. It does recieve regular updates. What makes you believe ED did stop working on the Viper? I mean, just take a look at the recent changelogs.

Also, you say that most features which are already implemented are broken and that the jet is an unpredictable, broken mess of an aircraft. Could you please explain that in more detail? Our experience seems to be completely different. Which systems do you mean exactly? I mean we can talk about missing or incomplete systems but currently there is no show stopper in Terms of broken stuff. Look, I do fly the Viper every couple of days in a very competitive PvP environment. It actually works really well and flying the Viper is a ton of fun. The FM is top notch. Most people I talk to online who also fly the Viper in that PvP environment completely share my point of view. What is it that makes you think the Viper is a unpredictable, broken mess of an aircraft? Can you please elaborate on that a little more?

[BIGNEWY]

Fact of the matter is that we weren't told that the F-16 would be put on hold for the F-18 to be finished. We were told there would be a parallel symbiotic development process for both the Viper and the Hornet. The issue isn't the slow rate at which new features are implemented at. The main issue is that most of the features that are already implemented are broken. This does not merely apply to newly added features, but features that were added +1 year ago are still broken and there's no signs of improvement. As a result of this a lot of the F-16 pilots in our community are leaving to fly other aircraft because it's simply not fun to fly a broken aircraft and ruin entire missions for ourselves and others because we fly an unpredictable, broken mess of an aircraft. I just hope it won't take too long for the Viper to start receiving serious bugfixes, but there's currently no improvement in sight.

 

Its not on hold, we just told you it has 2 new devs on it.

 

I get it, you are frustrated by the pace, but sorry there is no escaping it, early access is and always will be a long process.

 

 

Early access is a long process, there is no escaping it.

We currently have two engineers full time on the Viper; one is refactoring the entire SPI system for the Viper and the other is finishing up the Maverick and adding POS mode for the HARM. We also just recently re-did the ground handling model and adjust various drag values. Our primary goal is currently to get the Hornet out of early access by the end of the year, so the bulk of our resources must be first dedicated against this task.

 

Also to add, the viper was not "forgotten" in this patch

 

DCS F-16C Viper by ED

• Added pylons mass accounting to FM.
  
• Adjust payloads drag AIM-9.
  
• 3 Syria mission have snap views included creating problems for users - Fixed.
  
• Added CN localization for QS and Single missions.
  
• UFC Training mission static aircraft placement issue - Fixed
  

 

 

 

Edited November 21, 2020 by BIGNEWY

[Pikey]

People say that synchronous development of 2 or more seperate modules must make it longer to produce only one. Whilst that is true, it's so narrow minded as it considers only one module ever and not the larger picture of multiple, or indeed a continuous pipeline. Let's use some rough figures. 5 years to do the Hornet features mostly to release. You could say that doing any other similarly complex aircraft also takes 5 years. Then we have the copy-paste effect, which is actually not copy paste, but experience. Developers need to be familiar with the topic. Generally you forget things fairly fast. Does it make sense to do two similar-but-not-the-same radars at the same time or do one, wait 5 years, then do another? It does to me. Keep the skills current, od as much in parallel, even if it lengthens out the first module (which I dont actually think it really has, but whatever).

 

I would argue this is the vital part people completely miss in their undertanding of (software) development. At the core of it, there are humans, with memories and skill. 5 years is a long time in someone's life. 5 years ago, I was doing very different things with different skills.

 

You can see plain examples of how they release similar things together and move on to new topics. The A-10C II was a classic. Next you have the JHMCS for the Hornet. It's not a random occurence but part of a plan.

 

The only problem here in the way ED are doing it is that they didnt quite tell you how long it might take. You have to figure that out. You have to figure out, as a customer what early access means to ED, not what you think EA is because <insert company here> does/did. This takes a long time. It shoudl be obvious by now :) The Hornet is a good benchmark for everything to follow. I would rather they had the F-16 out and you can fly around and shoot things down, but its woefully gutted on it's features, than the alternative, which is "nothing". That is your choice. Nothing, or something. And the guys that choose "nothing", you can have that too! So really, no one loses at all and this entire discussion is a waste of time.

[BuzzU]

Sometimes "nothing" is the better choice.

[sobek]

It shoudl be obvious by now

 

It isn't, because it keeps changing, without notice. I've been following ED very closely since before the first BlackShark was released, i've been a translator and moderator with more insight into how they work than the average customer for quite a few years. I understand the hardships that cause these issues, since I've been a developer myself for well over 6 years now. Even putting all this into the mix, ED still manage to throw me the the occasional curve ball, to the point where i find it hard to still be excited about development and the product itself.

[Droning_On]

:( My God what have I started......should have kept my patience in check.. Sorry ED :(:joystick:

[Ziptie]

:( My God what have I started......should have kept my patience in check.. Sorry ED :(:joystick:

 

You can simply ask a moderator to close your thread, then this flame fest can cease to clutter people's forum list......

 

@BIGNEWY - seems like OP would be thrilled with it.

 

 

Cheers,

 

Ziptie

[BIGNEWY]

Thread closed,

 

I am sure it wont be the last thread on the subject however.

 

As mentioned we have two devs on the viper currently, work is in progress. Once the Hornet is out of early access more resources can be sent to the viper project.

 

Thank you for your support and patience.