in progress ITR and G-Onset update, release date ?

[irq11]

Hi ED,

in the last update for OB, you specified that you were always in WIP for ITR and G-Onset, so do you have may be a release date for that ?
thanks by advance

[Hummingbird]

Been wondering the same thing, but didn't want to ask in fear of being shut down. But yeah, it's been a while now without any updates on this.

[BIGNEWY]

1 hour ago, irq11 said:

Hi ED,

in the last update for OB, you specified that you were always in WIP for ITR and G-Onset, so do you have may be a release date for that ?
thanks by advance

I do not have a date to share with you all currently. As soon as we are ready it will be included in a future changelog. 

thanks

[mobua]

28 minutes ago, BIGNEWY said:

I do not have a date to share with you all currently. As soon as we are ready it will be included in a future changelog. 

thanks

I understand that you might be reluctant to share a date, could you however shed some light on the reasons for the revised/delayed timeline? Any particular bumps in the road you can share with the community?

I believe the original FM was slated for 2021 Q3 (October/November)?

Thanks!

Edited January 26, 2022 by mobua

[NineLine]

Sorry, we don't have any info to share at this time.

[darkman222]

No offence intended. I work as a freelance graphic designer. If I had a client who booked me for my work and paid for it in advance and instead of me adressing the clients feedback, I would just tell him, that I dont know when I will fix my work and instead keep getting the same feedback over and over again, while working on everything else, I am pretty sure that this client would never book me again.

I understand that a complex thing like a DCS universe, with many modules and systems that are interconnected and dependent on each other cant be compared to me as a freelancer working for a single client, but priorities in the F16 modules development seem off to me.

Like selling a sports car with three tires. Then installing a cruise control next.

[NineLine]

I'm sorry but none of those analogies make any sense what-so-ever in this case. The F-16 was released in Early Access as not complete and in development, everyone should have had an understanding what that meant, especially with the Hornet being active in the very same thing. We have been very clear on what is to come in Early Access, we have tried to update you on progress as things go along, so the silly comparisons are just that, silly. 

I'm sorry, I will keep this thread open for now, but if we are just going to do this, I am not sure I see the point.

Thanks.

[Versor]

Ok but we hope that you realize that this is a priority for Viper drivers?

[darkman222]

@NineLineYou are right we have already been there, it has been discussed and after this I wont reply any further.

People are asking for a FM fix which is something major for the enjoyment and competitveness of this module. Thats the difference between the Hornet being in early access compared to the Viper in early access.

Over and out.

[NineLine]

11 minutes ago, Versor said:

Ok but we hope that you realize that this is a priority for Viper drivers?

Because it is a priority doesn't make it easy or quick to do. 

[Versor]

You have really good SME, he will tell you how Viper should fly. Please don't put it back in time.

[NineLine]

2 minutes ago, Versor said:

You have really good SME, he will tell you how Viper should fly. Please don't put it back in time.

It is not that simple. Yes we have good SMEs working with the team, we also have the most complex flight model available. But that doesnt mean you just type in "do this and not that" and it happens. Once again, this is complex work and it takes time. Changing one aspect of the FM can mess up another, it has to be carefully researched, tested and retested. A pilot saying it should fly like this or that doesnt make the FM magically fly like this or that.

[Martinbulldog]

I to am very much looking forward to the F16's flight model being updated , at present it really feels bad. I want to be able to dogfight BFM in this jet but its so sluggish compared it other jets. Keep up the great work ED.   

Edited January 29, 2022 by Martinbulldog

[Hummingbird]

Yes, I think that for ours, as well as your (devs) own sake, it would nice if in the weekly updates you could write the status on it. That way people don't become paranoid as to wether or not you've forgotten about it, and you avoid threads about it popping up all the time. A win win for all of us, customers and devs a like. 

[Theodore42]

Never heard of a company announce that they didn't do a thing on their "promised" (tentative) timetable, let alone announce it every week.

ED said the FM change would be in late last year and it didn't happen. So someone posted a thread on their forums asking about it and NineLine ate **** and answered. That's an official comment from the ED Team that can be used by media and YouTubers. Can't really ask for much more communication than that.

I read they delayed the EA release of the Apache which is a much bigger deal than a delay to a FM update. It might just be that they have some unforeseen interferences on their other projects due to the Apache needing to be pushed out to Early Access.

[Hummingbird]

25 minutes ago, Theodore42 said:

Never heard of a company announce that they didn't do a thing on their "promised" (tentative) timetable, let alone announce it every week.

 

It's not about announcing they did nothing, it's about keeping uncertainty to a minimum by communicating that work is still ongoing on it. They did this with the Apache, and pretty much avoided any negative feedback as a consequence. Ongoing communication is key to avoid misunderstandings and worry amongst your customers/followers, as well as ensuring their understanding regarding any delays. 

But if they're fine with threads popping up about it all the time, then keeping silent is fine I guess.

Edited February 2, 2022 by Hummingbird

[WHOGX5]

13 minutes ago, Hummingbird said:

 

It's not about announcing they did nothing, it's about keeping uncertainty to a minimum by communicating that work is still ongoing on it. They did this with the Apache, and pretty much avoided any negative feedback as a consequence. Ongoing communication is key to avoid misunderstandings and worry amongst your customers/followers, as well as ensuring their understanding regarding any delays. 

But if they're fine with threads popping up about it all the time, then keeping silent is fine I guess.

 

I wish I could mention other companies who do customer interaction 100% correctly but I don't want to get slapped with a warning. Suffice to say, there's an absolutely exemplary game company that is completely transparent with their progress in different areas of the development of their product and they can delay stuff for years without riling up the community at all. The reason for this is the clear communication and transparency. "This feature will not arrive as soon as we'd hoped because of our team running into issue X and Y and now we have to do A and B to try and solve this issue". It doesn't have to be harder than that. "Team E is still working on X and Y while Team F is just finishing up A and B". Then you give regular updates on the progress of different systems so the customers actually know why some system hasn't arrived for 24 months, but they can at least see what the reason is, whether it's difficult to implement, low priority, on the shelf, etc.

The reason people are loosing their excreta in this subforum is because someone starts a thread wondering when some system will arrive after 24+ months of early access. That thread is going to be ignored by ED until it turns into an absolute flame war and then the mods show up and simply say "Yes, it's coming later in development, it's early access" and that's all you get. Two weeks or two more years; who knows? Who knows if anyone's even working on it? It's not good customer interaction and I'd say it's the main reason this subforum is so volatile.

[NineLine]

2 hours ago, Hummingbird said:

Yes, I think that for ours, as well as your (devs) own sake, it would nice if in the weekly updates you could write the status on it. That way people don't become paranoid as to wether or not you've forgotten about it, and you avoid threads about it popping up all the time. A win win for all of us, customers and devs a like. 

Where does it stop? I mean we give an update weekly on one feature then every feature wanted by users will be expected to give weekly updates? Or one week we don't get anything done on it, or a whole host of other things...

How about you give us just a little bit of credit and trust we won't "forget" something important like finishing the FM. That could work as well 

[BuzzU]

Will the Viper take as long to finish as the Hornet is taking?

That should answer some questions.

[NineLine]

5 minutes ago, BuzzU said:

Will the Viper take as long to finish as the Hornet is taking?

That should answer some questions.

That's a loaded question, it could be shorter, it could be longer, it could be the same to the day, there are not good forecasting tools to foresee what issues could arise or not.

[BuzzU]

5 minutes ago, NineLine said:

That's a loaded question, it could be shorter, it could be longer, it could be the same to the day, there are not good forecasting tools to foresee what issues could arise or not.

True, but your guess will be better than ours. However, some will hold you to your guess, so lets not go there.

Edited February 2, 2022 by BuzzU

[NineLine]

1 minute ago, BuzzU said:

True, but your guess will be better than ours.

I can guess right now, but when you type out a guess, it tends to be formed and sealed in cement very fast. 

[BuzzU]

Just now, NineLine said:

I can guess right now, but when you type out a guess, it tends to be formed and sealed in cement very fast. 

Yes, you missed my edit. We agree.

[TobiasA]

vor 1 Stunde schrieb NineLine:

Where does it stop? I mean we give an update weekly on one feature then every feature wanted by users will be expected to give weekly updates? Or one week we don't get anything done on it, or a whole host of other things...

How about you give us just a little bit of credit and trust we won't "forget" something important like finishing the FM. That could work as well 

I am very thankful for the promise to not forget the FM, because it has been very quiet recently about that topic.

Apart from that, the F-16 has finally seen some love, and I appreciate it. 

[Hummingbird]

3 hours ago, NineLine said:

How about you give us just a little bit of credit and trust we won't "forget" something important like finishing the FM. That could work as well 

 

It's not about giving credit or trust, in real life things can happen that can/will set back things, but how are we supposed to know if any such thing has happened or not when nothing is said? It's always best to be proactive and quel the very natural worries your customers will get if nothing happens for many months without any word. 

I mean there's a reason posts & threads about this subject keep popping up, it's not because people can't wait or want to annoy you guys for sport or something. The communication could simply be better. 

A brief heads up on any/or no progress regarding the FM in the F16 newletters and I'm sure everyone will be as patient and understanding as they've been with the Apache, where the communication was great(= credit)

Edited February 2, 2022 by Hummingbird