Jump to content

Recommended Posts

Posted (edited)
1 hour ago, some1 said:

So a serious question. Which 3rd party modules are actually protected from something like that happening again? Corsair - that thing was in development for a very long time, signed ages ago. Kiowa - Polychop has been around since the early days. Tomcat? Your guess is as good as mine. All confidential information of course, at least until another 3rd party goes belly up.

this is assuming, so take it with a grain of salt. I "assume" every module has a contractual agreement behind it rather than just the 3rd party (and Ill touch on that briefly), and if thats the case then yeah...every module contracted prior to VEAOs departure would be left out of the updated agreement, and those signed afterwards are enforced. If its the 3rd party that signed the contract and its for as long as they develop under the ED SDK, then every contract afterwards would be enforced regardless of when the module started.

 

ED never made this clear...personally I think they should, but it kind of doesnt really matter at this point.

Edited by Hammer1-1
  • Like 1

Intel 13900k @ 5.8ghz | 64gb GSkill Trident Z | MSI z790 Meg ACE | Zotac RTX4090 | Asus 1000w psu | Slaw RX Viper 2 pedals | VPForce Rhino/VKB MCE Ultimate + STECS Mk2  MAX / Virpil MongoosT50+ MongoosT50CM | Virpil TCS+/ AH64D grip/custom AH64D TEDAC | Samsung Odyssey G9 + Odyssey Ark | Next Level Racing Flight Seat Pro | WinWing F-18 MIPS | No more VR for this pilot.
 My wallpaper and skins

On today's episode of "Did You Know", Cessna Skyhawk crashes into cemetery; over 800 found dead as workers keep digging.

Posted
8 hours ago, Horns said:

There was nothing left out of that, 'new third-party agreements'

Ok, we agree on that,...

 

 

...so...

 

....remind us which new party or perhaps what modules are subjective to the post-Hawk agreements

 

Because currently it's like ED is advertising they took the poison out of their babyfood, but there is still 10 years of stock to sell before the non-poisoned babyfood will finally be in the stores

  • Like 4

Intel I5 13600k / AsRock Z790 Steel Legend / MSI  4080s 16G Gaming X Slim / Kingston Fury DDR5 5600 64Gb / Adata 960 Max / HP Reverb G2 v2

Rhino FFB / Virpil MT50 Mongoost T50 Throttle, T50cm Grip, VFX Grip, ACE Rudder / WinWing Orion2 Navy, UFC&HUD, PTO2, 2x MFD1, PFP7 / Logitech Flight Panel / VKB SEM V  / 2x DIY Bodnar Button Panels

DCS Juli 2025.jpg

Posted
2 hours ago, Nightdare said:

Ok, we agree on that,...

 

 

...so...

 

....remind us which new party or perhaps what modules are subjective to the post-Hawk agreements

 

Because currently it's like ED is advertising they took the poison out of their babyfood, but there is still 10 years of stock to sell before the non-poisoned babyfood will finally be in the stores

That's probably a fair analogy. Problem is I don't know which devs started their relationship with ED when so I can't give an answer to that, but it would not cover many of the third-party modules we have now, an extremely quick count leads me to a complete guesstimate of seven.

I could be totally wrong and it might be the majority released since 2018. We just don't know.

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F-15E] [F-16] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis]

[Afghanistan] [Cold War: Germany] [Iraq] [Kola] [NTTR] [PG] [SC]

Intel i9-14900KF, Nvidia GTX 4080, Gigabyte Z790 Aorus Master X 64GB DDR5 @ 6400 MHz, SteelSeries Apex Pro, Asus ROG Gladius 3, VKB Gunfighter 3 w/ F-14 grip, VKB STECS throttle, Thrustmaster MFD Cougars x2, MFG Crosswind, DSD Flight Series button controller, XK-24,

Meta Quest 3

Posted
6 hours ago, ruxtmp said:

This issue has brought the whole 3rd party developer risk to light. Anyone that thinks a third party will just hand over code to another party if they go belly up is deceiving themselves. If you believe any of the 3rd parties agreed to this supposed new contractual agreement I have a few bridges to sell you, or to the third party if they actually agreed to it. If a business goes belly up for any reason they are not going to just give up their work for free for another business entity to continue making profit off of their base work. All these 3rd party modules and maps are completely dependent on the original developer unless sold off. Razbam modules are going to either work and die a slow death or ED will just break them all in one version upgrade and be done with the issue and we won’t be able to do anything about it. The only way to prevent this is to have ED buy the rights to a developed module using the 3rd party as a sub contractor. The problem with this is ED can barely keep up with their own work let alone any extra modules being pushed out by other developers. 

Agreements like that do exist but with extremely specific triggers for when things get handed over. For instance a company I worked for provided a piece of software for day to day operations of a large client. If we went under or unilaterally withdrew from providing our services during however many years the contract ran for then they got access to the source code  and their data for the bit of software they were using.  If we had a mere contractual dispute they didn't get it. If they just wanted a look at it then they couldn't.

And yes, you're right. I've been saying this for ages but even if they get hold of the source/IP for the modules it still requires ED to be able to allocate the time and resources to then work with, build and package it.  And if they have to pay for it then that is additional cost on top of putting people onto working on it.

  • Thanks 1
×
×
  • Create New...