Question about DEKA support

[Tinchus2009]

Hello all. I would like to say some comments about a lot of problems regarding the jf17. Amny times a failure is reported and I see that the answer is : "report the issue to ED". I think DEKA should get involved a little more about issues o the systems of the jf17  and take a little more pro active position regarding reporting THEM to ed and not the users, wich at the end of the day are actuyally CLIENTS because we all paid for this module.

The module is great to my opinion, but is like all problems made because of ED, not always but sometines are left to be reported to ed by us and I think should be the contrary: we clients report bugs here, and DEKA should take this a little more serious and make a stand with ED regarding the solutions, because it is affecting their product right?

Just a comment that aims to be constructive. I have read many times the answer "report the issue to ED" and fell like "hey ... I bought the module, and the module developer is you, it is you who should take the report and take actions"

 

Best regards

[antiload]

I agree, the JF17 is a fantastic module, and has many unique features that other high def aircraft do not have. However, recently noticed the 'report to ED' replies. I would have hoped that if a bug or problem is reported that this would be taken forward by Deka, rather than the customer making the report.

Hopefully, this is just a mis-communication or temporary thing and that all bugs or issues are looked at and acted on by Deka or at least reported to ED for investigation and fixed. 

[Mike_Romeo]

7 hours ago, Tinchus2009 said:

Hello all. I would like to say some comments about a lot of problems regarding the jf17. Amny times a failure is reported and I see that the answer is : "report the issue to ED". I think DEKA should get involved a little more about issues o the systems of the jf17  and take a little more pro active position regarding reporting THEM to ed and not the users, wich at the end of the day are actuyally CLIENTS because we all paid for this module.

The module is great to my opinion, but is like all problems made because of ED, not always but sometines are left to be reported to ed by us and I think should be the contrary: we clients report bugs here, and DEKA should take this a little more serious and make a stand with ED regarding the solutions, because it is affecting their product right?

Just a comment that aims to be constructive. I have read many times the answer "report the issue to ED" and fell like "hey ... I bought the module, and the module developer is you, it is you who should take the report and take actions"

 

Best regards

Deka has always quickly fixed the bugs they were reported by the players and that they can fix. If the bug is up to ED, then its likely that Deka already their best to fix the problem but couldnt solve it. ED does encrypt a lot of files that third party developers dont have access too. Examples would be all kind of weapons to secure the same quality on all weapons so that no developer can create "OP weapons" as a selling argument.

[BigBorner]

vor 14 Stunden schrieb Mike_Romeo:

ED does encrypt a lot of files that third party developers dont have access too. Examples would be all kind of weapons to secure the same quality on all weapons so that no developer can create "OP weapons" as a selling argument.

Whilst i do agree, it is honestly still Dekas Job to communicate that issues to ED. Where is the issue to just move, for example, the bug report for the runway bombs to the ED weapons but section and create some visibility and pressure if they don’t get any help from ED side as stated. 

All of us here are beta testers that even paid to be that - only to discover bugs that should have been catched on even the simplest regression testing flow which obviously did not happen. Neither on ED nor on Deka side. You can’t explain everything with hardware combination on user side. 
 

I would get shouted at by my project or integration manager if I’d work that way. And they would be right. 

[whisky.actual]

In my opinion, ED should take responsibility for the maintenance of all modules after they are released. The 3rd party developers are forever responsible for fixing things when ED updates their core program. Each update brings their load of bugs and keeping on top of this is quite difficult since 3rd party devs don't own the whole code base. This constant pressure to make the two pieces work and not being able to develop new products is just not sustainable. This is the exact reason why I don't wish to be a 3rd party dev after making mods for this game for the past three years.

The transfer of maintenance to ED would definitely help 3rd party developers to focus their efforts on new products and alleviate some of these issues since ED would need to test all the products, not only the one with their name on it.  

I can understand why Deka gave that answer, but without raising this to the proper people this kind of issue will always happen. @BIGNEWY / @NineLine what do you guys think we can do to help out Deka?

 

[NineLine]

Dear all, 3rd Parties are responsible for the maintaining of their modules from release and beyond. If the issue is truly something only we can fix or they require our assistance they have access to our internal reporting system to get the help and answers they need. We do not have access to their source code and to think we could maintain the core, our own modules and add all 3rd Party modules to that aswell would be a very big plate to hold. 

[whisky.actual]

Thank you for the clarifications, I guess Deka can pass along the bugs that we post here then.

[uboats]

Hi,

Since JF-17 is almost feature complete and stable, we havent changed code for a long time.

When we find that issue coming along with dcs big update and cannot handle from our side, we recommend players to report these issues to ED as well.

Since this subforum has fewer visit, reporting it in DCS main bug forum would attract more attention from ED, testers and community.

Other players can provide/supplement more data/info/trk to help narrow down/pin-point or even find the root cause

[sorry that i'm in covid, and away from computer, so I would not reply quickly]

Thanks

Edited November 27, 2023 by uboats

[BigBorner]

vor 23 Minuten schrieb uboats:

we havent changed code for a long time.

Yes, we noticed that. Every time we use the targeting pod or try to bomb runways with runway bombs. Or if SPI is runnning wild because AG radar decides to set one on its own and you need to unlock it first to do anything with SPI. Sometimes even with radar switched off. 
 

 

vor 26 Minuten schrieb uboats:

Since this subforum has fewer visit, reporting it in DCS main bug forum would attract more attention from ED, testers and community.

With all due respect, the only important visit needed here is you as DEKA representative. It’s your responsibility to put the bug reports on the right tracks. We don’t have access to EDs JIRA, and we are testing a product from DEKA. So Deka gets the report.

 

vor 29 Minuten schrieb uboats:

sorry that i'm in covid, and away from computer, so I would not reply quickly]

Hope you get well soon and don’t have any hassles with it afterwards. All the best! 

[Pavlin_33]

Sooo... is ED working on a fix for this bug or Deka?

I am not sure, who took ownership.

Edited December 28, 2023 by Pavlin_33

[Tiger-II]

On 12/28/2023 at 5:11 PM, Pavlin_33 said:

Sooo... is ED working on a fix for this bug or Deka?

I am not sure, who took ownership.

 

Aircraft bugs are Deka. Weapon and sim bugs are ED.