SkateZilla

That was a joke, for the most part. I still havent gotten my SF2 to work on my new machine (windows 10, ryzen, 32gb ram, etc etc). But since SF2 doesnt support VR, I havent really dug into the issue.

Would look so pretty in DCS.. :-p

Yup..... Fresh from Turbo Squid.... :-)

Same Source Model from Turbo Squid, Withing DCS 2.0 w/ alot of revamped texture and geometry work.

it will be Windows 10 App, since Windows 10 will be able to Run Android Apps. so same thing, but running on PC w/ KB/Mouse emulating Gyro etc

One of the Ones that Eventually Became Fighters Anthology

No, Roads, Coastlines, etc etc are placed after terrain data is imported. That video is over a year old, I doubt the SDK even looks like that anymore.

I stated a good reason, Too many unlicensed users are ripping or using ripped models from other sims and attempting to bring them to DCS already. (At least for the Aircraft Mods). We dont need them trying to rip FSX landscape meshes etc to attempt importing to DCS. The Terrain Building is a different story altogether, they would like to make sure anyone given the SDK for terrain (and likely access to other things), has the ability to produce the terrain in full. Has nothing to do with licensing, and more to do w/ quality control and asset protection. There are Videos on YT of the Landscape SDK, it's a pretty spiffy and developed GUI.

Problem is Nobody that does terrains for other sims is even attempting to engage in dialog w/ ED to get an agreement for the tools. The Tools are not freely distributed, and w/ Good Reason, Especially now since People are Ripping Models from Other games in attempts to bring to DCS.

Lets Get it Done!, http://www.kickstarter.com/projects/683368164/f-35a-lightning-ii-by-kinney-interactive Author Website http://www.kinneyinteractive.com/#!dcs-f-35-lightning-ii/c1bom

Kinney had a history for FSX, I'll leave it at that.

FC2 -> FC3 Notable Changes, several others unlisted, but these are the Meat. 1. DX11 vs DX8 and 9c 2. MP Compatible w/ DCSW Modules vs MP Compatible with only FC2 3. New 6DoF 3D Cockpits for F-15C, A-10A, Su-33, Su-27, Su-25A, MiG-29s vs old LOM 3D Cockpits w/ Limited View/Modeling 4. PFMs for F-15C, Su-27, Su-25, A-10A, w/ Mig-29 and Su-33 PFM's On the Way vs Old SFM For All FC3 Except Su-25T 5. New 3d External models for F-15C, A-10A, Su-27, Su-33, Su-25, w/ MiG-29 on the Way vs Older Low Poly Models. 6. Extended map into Eastern Georgia / Southern RUS and NTTR vs Old Black Sea Map Only. 7. Several Updated AI 3D Models for Ships, Aircraft and Ground Objects 8. Improved Graphical Effects Over FC2, Even more so since the Move to DX11 9. Improved Mission Editor, Mission Triggers/Functions and Resource Management systems 10. New Campaigns for FC3 Aircraft (even more since move to 1.2.16+ and Campaign DLC System Integrated) 11. Improved Ocean Dynamics and Weather System vs FC2 (even more so w/ the move to 1.5/2.0 and DX11) 12. Improved Low level graphics detail on terrain vs DX8/9c of FC2, even more so w/ move to DX11 13. Improved AI 14. Integrated Fast Mission Editor 15. Expanded Radio Communications 16. Improved Avionics for Su-27, Su-33, MiG-29

Assuming you want to develop your own Aircraft and not Mod an existing one, even as an Unlicensed 3rd Party. 1. HUD Symbology is 100% Configurable, You can script anything you want with your own symbology in a TGA/DDS File. LUA Scripting Knowledge is a Must (See A-10C HUD Folder and LUAs), 2. Same can be said for MFDs 3. Cockpit systems complexity can be as simple as you want them (ie, Basic Electric, Hydrualic, Fuel Systems, Basic Radar, Basic SMS, Etc, Clickable or not, etc) (Again LUA Scripting Knowledge is a Must) 4. Flight Model, You can Use SFM or SFM+External FCS as a Cockpit System or EFM. - SFM All Aero and Engine Parameters are in the Base AIRCRAFT.LUA ( USED BY AI) - SFM + External FCS Would Use the above parameters, and augment them with FCS System Scripted in LUA to manage Control Surface Movements. ( USED BY SFM FC3 JETS + Some 3rd Party Mods) - EFM, Allows Custom Aerodynamics, Forces and Advanced Control Managements Etc ( Used By Licensed 3rd Party Developers ) 5. Radars, And Other Weapons Systems, Can be as detailed or simple as you like, most of the FC3 Aircraft use simplified Avionics, where as the DCS Aircraft Use More Detailed Systems. - You could, Simply Define a New Radar, Enter a bunch of Public/Generic Parameters, Define the Symbology, Create the Symbology Art easily if One knew how. 6. "Unofficial Mods" and Cockpit Linking, Is Common due to time and complexity of coding cockpit systems, and even building and animating the cockpits. Most unlicensed "Mini Teams", Animate and Export an External Model and Link it to use a Pre-Defined Cockpit and Avionics Set that resembles the aircraft the closest (Most A2A Aircraft are Linked to the F-15C, while A2G are linked to Su-25T or A-10A. 7. License Agreements w/ Manufacturers Are Significant, Many 3rd Party Mods were shelved or cancelled due to not being able to Secure an License Agreement with Manufacter of Said Aircraft. Some Important Notes: The Coding is Done in LUA and Microsoft Visual Studio Projects (DLL). If you're not proficient in those, then that's already a HUGE Barrier to overcome. As an Unlicensed 3rd Party, You will also not have access to the SDK, which would make things a bit harder. The Learning Curve Coming from Say Thirdwire 2nd Gen Aircraft Development, Is Tremendously Steep, Both in Coding and Art Assets. Which is likely why no SF2 Team has Even Tried to make a FC3 Level Aircraft.

The odd Part is, I've seen this screenshot in at least 4 articles about the USAF's new Bomber today...

F-15Es were likely put on hold due to no A2G support in the 1.x engine. I assume IRiS is on hiatus, havent heard diddly from them since their T-38 announcement

Both the Hawk and C-101 are fun lil planes to fly, With AFM.they'll get better PS Steam sale.started, and.DCS.items are up to 60% off

http://forums.eagle.ru/showpost.php?p=2219282&postcount=152

P-51D was developed with and for The Fighter Collection....

I was hesitant to reply at first, but since this link is being pasted repeatedly on ED Forums, I'll offer my $.02 A. As stated, this change will have minimal impact on anything, B. EDGE will be with 1.3.0, nothing has changed, it's already in closed testing C. Most of the Intellectual Property and Staff working on DCS WWII are now with ED. So it's not like everyone at ED is dropping what they were working on to move to the WWII Stuff. D. 2025?, Seriously? while humorous, it's a bit harsh dont ya think? Seriously, those Expecting a DCS Fidelity F/A-18C in a matter of 2 years are not seeing the actual time frame. Consumer version of DCS A-10C Suite 3 was announced in May/June 2008, and was released in April/May 2011, so about 3 Years and that's not even counting initial development time for 3D Assets and Systems. I wasnt expecting to see anything regarding a Hornet until 2015 at the earliest anyway. Everything is subject to change in the software world. Example?: IIRC ED was getting ready to assemble Test teams for DCS: AH-64A Block 49.A and DCS: A-10A Suite 2 in 2008... On a Site note..... Being a Navy Brat.... outside of any F-14, The F-18 is prolly my 2nd Favorite Aircraft..... Also: