Jump to content

Recommended Posts

Posted

First of all, i like the late kick start DCS World has brought to the Combat Sim community. For me it's an old dream come true that is, having a common platform where different people flying different (properly modeled) AC Types flying a multilayer mission.

An here comes the million dollar question... Is every developer responsible for developing his own weapons for his AC, or are there interfaces for each weapons type (eg. interfaces for FOX3,Fox2,Fox1 missiles, JSAWS,LGB's etc).

If such thing exists, it could create a tremendous work offload,simply because the developer wouldn;t have to write something,just a driver for the current interface, for a weapon that already exists.

Posted (edited)

Every licenced 3rd party developer has access to ED's existing ordinance and related coding for their developmental programmes.

Edited by 159th_Viper
Spelling

Novice or Veteran looking for an alternative MP career?

Click me to commence your Journey of Pillage and Plunder!

[sIGPIC][/sIGPIC]

'....And when I get to Heaven, to St Peter I will tell....

One more Soldier reporting Sir, I've served my time in Hell......'

Posted

Thats good to know. To be honest, I didn't even think that they might have to "reinvent the wheel" as it relates to weapons already simulated by ED. :D

My Rig: EVGA GTX 1070 x 2 | EVGA x58 SLI classified | i7 X 990 CPU | 24 GB RAM | Windows 10 Home 64 bit| Track IR Pro | CH Fighter Stick | CH Throttle | CH Pro Pedals |

 

[sIGPIC][/sIGPIC]

Posted
Thats good to know. To be honest, I didn't even think that they might have to "reinvent the wheel" as it relates to weapons already simulated by ED. :D

 

 

Not only that. Imagine the same weapon modelled differently by different developers.... it would be a mess.

Posted

Hopefully the World will act as a framework for developers and be the guide that all plugins have to fit into.

 

I did notice that some of Beczl's Mig:21 weapons are new to the framework and when asked he did not know if they would be absorbed into World (at the time of asking).

 

It would be logical if there were a legal covering in 3rd party agreements where ED took these on for reuse or kept them individual to the module depending how each item might work.

 

I would have thought (but don't know) that this applies to everything that a 3rd party might develop including the basis for flight models, shared textures, complete systems and so on and i also expect (but don't know) that it's probably not something we need to worry about.

 

I have to admit to being slightly interested in if when a 3rd party develops something that plugs into a brand name, if they aren't just selling under license and that their work might not even be their own property once sold as such. Software and licensing are complicated beasts!

___________________________________________________________________________

SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *

Posted
Not only that. Imagine the same weapon modelled differently by different developers.... it would be a mess.

 

I asked this question the other day but not as eloquently... So here's a piggyback question. Let's say we're talking the Harm Targeting system... The F16's in sim can employ them so the system "Works". Does ED provide all aspects of the weapon system, including the cockpit interface or just the weapon modeling? (clear as mud?)

[sIGPIC][/sIGPIC]

Primary Computer

ASUS Z390-P, i7-9700K CPU @ 5.0Ghz, 32GB Patriot Viper Steel DDR4 @ 3200Mhz, ZOTAC GeForce 1070 Ti AMP Extreme, Samsung 970 EVO M.2 NVMe drives (1Tb & 500 Gb), Windows 10 Professional, Thrustmaster Warthog HOTAS, Thrustmaster Warthog Stick, Thrustmaster Cougar Throttle, Cougar MFDs x3, Saitek Combat Rudder Pedals and TrackIR 5.

 

-={TAC}=-DCS Server

Gigabyte GA-Z68XP-UD3, i7-3770K CPU @ 3.90GHz, 32GB G.SKILL Ripjaws DDR3 @ 1600Mhz, ZOTAC GeForce® GTX 970.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...