Jump to content

SkateZilla

+MODDER
 View Profile  See their activity

  • Content count

    1,508

  • Joined

  • Last visited

  • Days Won

    3

Posts posted by SkateZilla

  4. Posted

    In one of the thread of comments on the post on FB there is a comment by Thirdwire to the effect that they are planning on porting the mobile games to PC.

     

    Wonder if we'll be able to access the data, and will it be compatible to move to an SF2 install?

     

    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

  8. Posted · Edited by SkateZilla

    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.

     

  11. Posted · Edited by SkateZilla

    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
     

  12. Posted · Edited by SkateZilla

    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.

    • Like 1

  16. Posted

    What ever happened to Skate's F-100 for DCS?

     

    Yep, the C-101 will be another pass for me. The strike trainer concept intrigues me, but I'd prefer something slightly broader.

     

     

    The required A-G avionics code will come with the FA-18C - it is mentioned in the new video from Froogle/Matt Wagner

     

    Building the DCS terrains appears to be a colossal job - and any pay ones would likely take years.

     

    It's good that effort to put infrastructure in for multiple years is being considered - dodging SA-18s in a P-51 is not my thing

     

    I'm sure I have seen a post from Skate stating he doesn't have the time to finish the F-100 - would need to find it.

     

    The guy that did the BMS flight model has offered to help do a DCS flight model - but didn't sound like that went well. This has been discussed on the BMS forums - the underpinning implementation is so vastly different its not a simple case of porting anything and they are committed to improving F4.

     

     

    The pay campaigns is a good idea - I would buy all for the A-10C - but yeah probably might not buy any trainers myself.

     

     

     

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

  18. Posted · Edited by SkateZilla

    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:

    8 June 2014 Update
     
    We have been reading the discussions here and we will try to answer your questions as soon as we have concrete answers for them. The exception will be the circumstances which led to this change in product management and development. Sorry, but that simply is not going to happen due to legal agreements.
     
    One item I can shed some light on is where the Kickstarter funds went. All of the funds have been spent and they helped develop the Bf-109, P-47, Me.262, Spitfire, and Normandy map. However, given the massive amount of work, those Kickstarter funds were only a drop in the bucket of what is needed to flesh out this project. The vast majority of funds needed to finance this project have and will continue to come from Eagle Dynamics (not Kickstarter). To give you a feel… just the Eagle Dynamics developed and funded flight model for the Bf-109K has already cost us about 120k USD (that does not include external model, cockpit model, cockpit systems, etc.). Developing such products is not cheap!
     
    As mentioned yesterday, this project will only have minimal impact on our other internal projects given that much of the former-RRG team is now working for Eagle Dynamics. As such, projects like the F/A-18C, Su-27 PFM, and new maps are still under active development. As a policy, we now do not discuss internal projects until they are nearing beta level (the exception being DCS WWII due to KS obligations). So, just because we are not talking about them, hardly means that they are not being worked on.
     
    Today, I have also included a VERY early copy of the DCS: Fw 190 D-9 flight manual. Please note that this is hardly final and is very much subject to change over the next couple of months.
     
    Thanks,
    Matt
     
     
    -----------------------------------------------------------------------
     
     
    7 June 2014 Update
     
    We would first like to apologize for the long delay in projects updates. Since the last update from Luthier, there have been some significant changes in how this project will be developed and managed. No longer will RRG be developing this project and Luthier has ceased his involvement in the project. Eagle Dynamics though will be continuing its development and honor all Kickstarter backer commitments. There is nothing more we can say about this change and it is not open for discussion.
     
    Because there are some shared resources between projects (like cockpit systems programming), there will be some impact to our other projects. However, because much of the former RRG team is now employed by Eagle Dynamics, the impact on other Eagle projects will be minimal.
     
    We will be restructuring the DCS WWII: Europe 1944 forums to reflect this.
     
    DCS WWII: Europe 1944 is still planned as a single-package option, or users can purchase individual components to integrate into DCS World.
     
    Myself and Groove plan to provide monthly updates.
     
    As a basic outline, here are our current development intentions:
     
    August 2014 – Fw 190 D-9 Dora 
    October 2014 - BF-109K 
    December 2014- Spitfire IX 
    March 2015 - P-47D-30 
    May 2015 - Normandy Map with period AI units
    Other features like the Me.262A-1 and AI-only B-17G are also in development we but do not have a delivery data estimate at this time until these other features are further along.
     
    In the meantime, Groove and our moderator SiThSpAwN are working to make sure that all backers, based on their level of backing, receive their entitlements. 
     
    We fully realize that you probably have many unanswered questions. We are in the process of answering those internally first, and once we do, we will update you.
     
    In this update, we can share some updated images of the Fw 190 D-9 and Bf-109K cockpits. In future updates, Yoyo and other members of the development team will provide greater details about the various features.
     
    Thanks,
    Matt

     

     

  25. Posted · Edited by SkateZilla

    Pilot's Body: Material Name: pilot_F18C_body, Texture name: pilot_fa-18c

     

    Pilot's Helmet: Material Name: pilot_F18C_helmet, Texture name: hgu55

     

    Pilot's Helmet Visor: Material Name: F18C_Helmet_Glass, Texture name hgu55

     

     

    AFAIK, They are Case Sensitive.

     

    I'll double check when I get home from office. Material names Might have changed with some of the recent updates.

×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..

  I accept