Leaderboard

Greetings! Today I'd like to share our 2022 end of year development report on the A7 Corsair, which has been extracted from our full company report which is available here A7 Corsair II for DCS World Artwork The Corsair has had a tumultuous journey! 2022 saw the completion of our complete remake of the A7 3D model, which took a significant amount of time. With the aid of Iakov, our new artist, both the external and internal models of the A7 have been completely remade from scratch as we've previously discussed. The remake started work in 2021 and was completed around Q3 in 2022. The remake is significantly more detailed than our original model, with almost all elements of the aircraft accurately modelled, including maintenance areas. Having such a detailed model delivered by Iakov meant that lots of work was required in terms of optimizing the model to extract the maximum possible performance, without compromising much detail. This is still ongoing, however most of the exterior has now been optimized, as well as large chunks of the cockpit. Work is ongoing to optimize the remainder of the cockpit so it can then be textured. Work has begun on UV mapping the exterior model and to that end we have created a dedicated Paint-Kit team, who are providing value feedback during the UV mapping process to ensure that our paint-kit is as easy to use as possible for livery artists. Work is also well underway in animating the cockpit & exterior as well as setting up clickable areas, which has been very helpful in allowing us to start testing more systems in-flight using proper procedures. Flight Modelling The A7 Flight Model has undergone extensive work this year, especially in the first half of the year, with much of that work being 'behind the scenes' so to speak. This year we've been working closely with Research in Flight, an aerospace & hydrodynamics analysis company that creates tools for aerospace engineering applications. They are the developers of Flightstream, a sophisticated numerical flow solver and one of our primary tools that we use for CFD analysis & data collection for the A7. We have been working closely with them to enhance & improve our A7 Corsair model, to the point where we have been able to supply validation studies and case tests against the real wind-tunnel data we have gathered. The A7 model has also been used to test & assist in development of new control surface analysis techniques being integrated into Flightstream, in turn also enhancing our data collection capabilities for various control surface & damage configurations. CFD Collaboration & NASA Presentation As part of our collaboration, we spent some time this year developing some internal tools to aid in the collection of CFD data; not only for the A7 but also for any model we wish to analyze. One such tool that I developed personally was a utility that facilitated the conversion of an OpenVSP model into a solution-ready FlightStream model. Without going into too much detail, what this accomplished was an extremely fast & efficient method for simple OpenVSP geometry models to be analysed in great detail in FlightStream. For us, this allows us to gather CFD data in a fraction of the time required using traditional modelling techniques. Our work was shown off at the 2022 NASA OpenVSP workshop, and we have since made the tool publicly available, where it is now being used around the world in both academic & commercial design purposes. We have even been informed the utility is being used over at Boeing! It is our hope that this simple tool will make CFD modelling more accessible to all sim developers. For further reading, you can see the presentation slides that relate to the relevant Flightstream developments here. Of course, all this only matters if it helps us to develop the A7! Although it's taken some time, these developments have been a worthy time investment. By forging a new workflow, we're able to tweak & experiment with our models in a fraction of the time to get the best results possible when testing unusual aircraft configurations. If you've worked with CFD or know alittle about it, you'll know that it is an enormously time-intensive process using conventional techniques, and almost always requires constant model tuning & tweaking to collect valid results. As we are now developing the advanced aspects of the A7 Flight Model, this has been absolutely essential when testing non-standard configurations. For example, using our workflow we've been able to run tests and collect data on virtually every control surface interaction possible, in order to assess the relative significance of unusual interactions and determine how best to model them in-sim. Some examples include interactions between the flaps & elevator at various high Angle-of-Attack configs, forces in a spin and leading to a spin, spin recovery analysis and post-stall analysis. Furthermore, this new modelling workflow has provided us with a very efficient means to study the effects of airframe damage on flight dynamics, an aspect that is often modelled with only very simple approximations due to data limitations. Not so anymore! Design & Development of Control Augmentation System (CAS) and Automatic Flight Control Systems (AFCS) In terms of Flight modelling, the latter half of 2022 has been heavily focused on designing & developing the CAS for the A7 Corsair. This has been a huge undertaking and admittedly has required a large amount of time on my part devoted to studying advanced engineering control system design principles. Although we don't have the exact equations used in the real aircraft CAS, we do fortunately have enough information on the inputs & outputs of the system to be able to reverse engineer it. This has required us to approach the situation in much the same way as the original aircraft designers, attempting to carefully craft a control system that meets the requirements of the airframe and pilots. Although work is still ongoing, we are quite pleased with how things are shaping up and are confident that with the feedback from our SME's we will be able to fine-tune the CAS to operate almost exactly as the real system would. Flying with the CAS switched on is a completely different experience than flying with it off; the airframe is incredibly difficult to control without it. Therefore, it is absolutely critical that we get this right and we are dedicating an appropriate amount of time & resources to try and achieve this. The CAS is only one part of the A7's AFCS, which is used not only to enhance flight stability but also for Autopilot control of the aircraft. The AFCS is being developed in tandem with the CAS and has made significant progress in 2022. The primary Autopilot modes (HDG, ALT, ATT, Airspeed) have all been developed & implemented. We are currently in the process of refining the Yaw Stab system, which stabilizes and corrects for aircraft slip and assists in turn coordination. CAS & AFCS naturally have a strong interconnection with the control surfaces and thus required a complete rewrite of all of our control surface models. This was completed in 2022 and are controls are now working in harmony with the AFCS, respecting defined authority limits and behaviours. As a pilot you will need to be aware of & respect these limits to ensure that you are working with, and not against, the AFCS. The A7 Corsair is not a simple airframe to fly; it has extensive quirks that need to be understood and mastered for the aircraft to be flown effectively. The AFCS is a quintessential part of this; understanding & mastering it will be a key component of flying the A7 well. Other FM Developments On top of everything discussed above, this year we have been working to refine our mathematical classes & methods implemented in our codebase. Focusing on optimization, we have been spending time implementing new methods of data processing that require less computational resources to achieve the same result. An example of this is interpolation and look-up table (LUT) modelling, which is the foundation of data processing in a simulator and one of the primary methods used to implement CFD & aerodynamics data. These calculations happen thousands of times every second and have thus been a big priority for us in terms of code optimization. As discussed in the CFD section, we have developed a new workflow that has allowed us to quickly and efficiently analyze aircraft damage scenarios and the impact of damage on Flight dynamics. While still in-progress, we have been very pleased with the data we've been able to collect and are currently busy expanding the Flight Model to include damage modelling. Sound Design Although still only in the very early stages of development, work has begun on sound design for Corsair! Thanks to the collaboration from some amazing people in the community, we've been able to organise the recording of a real A7 during a maintenance engine run. This is of course an extremely rare opportunity, and we are so grateful to the good people at Tulsa Tech University for making this possible! Thanks to some collaborative efforts from 'Armorine' in our community discord (who has also been invaluable in helping us to secure certain documents. Thank you Armorine!), we were able to organise a professional field recording of the A7. The recording was carried out by Tulsa Tech's team of sound engineers & sound engineering students, with the entire engine run captured from various positions by professional grade equipment. The team even went so far as to produce an excellent master of the samples for us! In total we were given an amazing 29 high-quality aircraft samples from various mic positions, as well as 4 completed mixdown tracks. Below you can see some shots from the recording process Tulsa Tech sound engineering team, responsible for the excellent recordings provided. Images provided by Tulsa Tech & Armorine System & Weapons Development Alongside all of this, work has continued throughout the year to develop and flesh out the cockpit systems of the Corsair. Once again, we owe our thanks to 'Armorine' for assisting in helping us to acquire some missing documentation. Unfortunately, due to the nature of systems development, we don't have a wealth of flashy screenshots to show here, but I will do my best to explain the various systems under development and the state they are in. One of the biggest priorities this year has been developing the codebase & logic underlying the A7's targeting and weapon delivery systems. To this end, lots of time has been spent refining and further developing the armament control systems: developing correct pylon release cues & logic, release inhibition conditions, developing calculations for interval drops and developing the core logic that underpins the sophisticated weapons systems of the A7. The culmination of this has been the development and integration of CCIP & CCRP weapon release modes; both of which draw heavily from various sensors and targeting systems in the aircraft before making real-time calculations to determine an impact point. We are pleased to say our A7 can now accurately release unguided weapons on target, using both CCIP & CCRP methods that are unique to different weapon types. Work is ongoing to further develop both weapon release modes to include inhibition cues as well as to develop the navigational modes of weapon release, such as Bomb on Coordinates (BOC) and offset bombing modes. Navigation systems also received some development time in 2022, with the INS and tactical computer systems currently being expanded upon and developed. We have developed the aircrafts waypoint system, including storage, recall and editing of flight plan waypoints. We've also made progress integrating information from the navigation systems into other aircraft avionics; most importantly the HUD and PMDS. 2023 will see the detailing & expansion of the INS system; expanding on current modelling of the Inertial Measurement Unit (IMS) and the development of the Doppler Radar, both of which feed information to the INS. We will also be working to implement mark-points, target points and other in-flight navigational systems. As a pilot flying the A7 will require careful monitoring and management via positional updates and pilot corrections; the A7 requires navigational updates to correct for INS drift, in a similar fashion to the Viggen. As we've shown throughout the year, 2022 has seen the development of most of the A7's key avionic systems in various states of completion. The Projected Map Display (PMDS) is integrated and functioning, with current work focused on integrating navigational data from the Tactical Computer, as well as integrating some of the lesser used functionalities. The RWR has been on the backburner for some time due to some limitations in documentation, however we have now obtained the necessary documents and work is now ongoing in developing the RWR fully! The aircrafts multiple radio systems are also well in development, with the primary functionality of all radios already implemented and work ongoing to implement cockpit controls, presets and other functions. The A7 Radar systems are also well in-development as we've previously showcased, with current work focused on radar targeting functionalities as well as navigational cues. As well as all the above, our current codebase is being constantly refined, expanded upon and rewritten in order to be more realistic with its flow of information. To elaborate, we are aiming to mimic the flow of data as it occurs in the real A7 avionic systems, with many avionics being dependent on other systems and prone to certain failures and accuracy limitations. For example, the tactical computer relies upon information from the Air Data Computer (ADC) as well as IMS systems in order to complete navigational and targeting calculations; any inaccuracies in data supplied from either the ADC or IMS will result in flow on errors and inaccuracies further down the avionics chain. In practical terms, this means that simple things like damage or icing to your pitot tubes can result in inaccurate data being supplied to the ADC and thus the Tactical Computer, creating targeting & instrumentation inaccuracies. We want each system to be interacting with each other as organically and realistically as possible, allowing for the accurate simulation of failures, errors and inaccuracies as they can occur throughout the aircraft. To summarise the state of systems development in the A7 Corsair: most if not all systems have been developed and integrated to at least a basic extent, with work now being focused on expanding and developing the advanced functions of each system as well as the interconnections between each system. This will happen in-tandem with the art, as more & more cockpit controls and displays become available and ready to be tied to code work; we anticipate this will be ongoing for much of 2023. What's next? We've previously discussed our 4-phase development roadmap for the A7, which roughly translates to the following 4 phases: SFM Based model Basic EFM & flight systems Advanced EFM & advanced flight/weapon/avionic systems SME testing & tuning + damage modelling We are currently approaching the tail-end of phase 3, which as expected has been the longest development phase by quite a margin. Our goal is to complete phase 3 and move into phase 4 of development at some point in 2023. We know it's been a long wait and it seems to still be forever away, but we want to say thank you for your patience and hopefully this report can give you some insight into what's been happening behind the scenes. Thanks for reading! Sincerely, Dan K. FlyingIron Simulations

A7 CORSAIR II FOR DCS WORLD ARTWORK The Corsair has had a tumultuous journey! 2022 saw the completion of our complete remake of the A7 3D model, which took a significant amount of time. With the aid of Iakov, our new artist, both the external and internal models of the A7 have been completely remade from scratch as we've previously discussed. The remake started work in 2021 and was completed around Q3 in 2022. The remake is significantly more detailed than our original model, with almost all elements of the aircraft accurately modelled, including maintenance areas. Having such a detailed model delivered by Iakov meant that lots of work was required in terms of optimizing the model to extract the maximum possible performance, without compromising much detail. This is still ongoing, however most of the exterior has now been optimized, as well as large chunks of the cockpit. Work is ongoing to optimize the remainder of the cockpit so it can then be textured. Work has begun on UV mapping the exterior model and to that end we have created a dedicated Paint-Kit team, who are providing value feedback during the UV mapping process to ensure that our paint-kit is as easy to use as possible for livery artists. Work is also well underway in animating the cockpit & exterior as well as setting up clickable areas, which has been very helpful in allowing us to start testing more systems in-flight using proper procedures. FLIGHT MODELLING The A7 Flight Model has undergone extensive work this year, especially in the first half of the year, with much of that work being 'behind the scenes' so to speak. This year we've been working closely with Research in Flight, an aerospace & hydrodynamics analysis company that creates tools for aerospace engineering applications. They are the developers of Flightstream, a sophisticated numerical flow solver and one of our primary tools that we use for CFD analysis & data collection for the A7. We have been working closely with them to enhance & improve our A7 Corsair model, to the point where we have been able to supply validation studies and case tests against the real wind-tunnel data we have gathered. The A7 model has also been used to test & assist in development of new control surface analysis techniques being integrated into Flightstream, in turn also enhancing our data collection capabilities for various control surface & damage configurations. CFD COLLABORATION & NASA PRESENTATION As part of our collaboration, we spent some time this year developing some internal tools to aid in the collection of CFD data; not only for the A7 but also for any model we wish to analyze. One such tool that I developed personally was a utility that facilitated the conversion of an OpenVSP model into a solution-ready FlightStream model. Without going into too much detail, what this accomplished was an extremely fast & efficient method for simple OpenVSP geometry models to be analysed in great detail in FlightStream. For us, this allows us to gather CFD data in a fraction of the time required using traditional modelling techniques. Our work was shown off at the 2022 NASA OpenVSP workshop, and we have since made the tool publicly available, where it is now being used around the world in both academic & commercial design purposes. We have even been informed the utility is being used over at Boeing! It is our hope that this simple tool will make CFD modelling more accessible to all sim developers. For further reading, you can see the presentation slides that relate to the relevant Flightstream developments here. Of course, all this only matters if it helps us to develop the A7! Although it's taken some time, these developments have been a worthy time investment. By forging a new workflow, we're able to tweak & experiment with our models in a fraction of the time to get the best results possible when testing unusual aircraft configurations. If you've worked with CFD or know alittle about it, you'll know that it is an enormously time-intensive process using conventional techniques, and almost always requires constant model tuning & tweaking to collect valid results. As we are now developing the advanced aspects of the A7 Flight Model, this has been absolutely essential when testing non-standard configurations. For example, using our workflow we've been able to run tests and collect data on virtually every control surface interaction possible, in order to assess the relative significance of unusual interactions and determine how best to model them in-sim. Some examples include interactions between the flaps & elevator at various high Angle-of-Attack configs, forces in a spin and leading to a spin, spin recovery analysis and post-stall analysis. Furthermore, this new modelling workflow has provided us with a very efficient means to study the effects of airframe damage on flight dynamics, an aspect that is often modelled with only very simple approximations due to data limitations. Not so anymore! DESIGN & DEVELOPMENT OF CONTROL AUGMENTATION SYSTEM (CAS) AND AUTOMATIC FLIGHT CONTROL SYSTEMS (AFCS) In terms of Flight modelling, the latter half of 2022 has been heavily focused on designing & developing the CAS for the A7 Corsair. This has been a huge undertaking and admittedly has required a large amount of time on my part devoted to studying advanced engineering control system design principles. Although we don't have the exact equations used in the real aircraft CAS, we do fortunately have enough information on the inputs & outputs of the system to be able to reverse engineer it. This has required us to approach the situation in much the same way as the original aircraft designers, attempting to carefully craft a control system that meets the requirements of the airframe and pilots. Although work is still ongoing, we are quite pleased with how things are shaping up and are confident that with the feedback from our SME's we will be able to fine-tune the CAS to operate almost exactly as the real system would. Flying with the CAS switched on is a completely different experience than flying with it off; the airframe is incredibly difficult to control without it. Therefore, it is absolutely critical that we get this right and we are dedicating an appropriate amount of time & resources to try and achieve this. The CAS is only one part of the A7's AFCS, which is used not only to enhance flight stability but also for Autopilot control of the aircraft. The AFCS is being developed in tandem with the CAS and has made significant progress in 2022. The primary Autopilot modes (HDG, ALT, ATT, Airspeed) have all been developed & implemented. We are currently in the process of refining the Yaw Stab system, which stabilizes and corrects for aircraft slip and assists in turn coordination. CAS & AFCS naturally have a strong interconnection with the control surfaces and thus required a complete rewrite of all of our control surface models. This was completed in 2022 and are controls are now working in harmony with the AFCS, respecting defined authority limits and behaviours. As a pilot you will need to be aware of & respect these limits to ensure that you are working with, and not against, the AFCS. The A7 Corsair is not a simple airframe to fly; it has extensive quirks that need to be understood and mastered for the aircraft to be flown effectively. The AFCS is a quintessential part of this; understanding & mastering it will be a key component of flying the A7 well. OTHER FM DEVELOPMENTS On top of everything discussed above, this year we have been working to refine our mathematical classes & methods implemented in our codebase. Focusing on optimization, we have been spending time implementing new methods of data processing that require less computational resources to achieve the same result. An example of this is interpolation and look-up table (LUT) modelling, which is the foundation of data processing in a simulator and one of the primary methods used to implement CFD & aerodynamics data. These calculations happen thousands of times every second and have thus been a big priority for us in terms of code optimization. As discussed in the CFD section, we have developed a new workflow that has allowed us to quickly and efficiently analyze aircraft damage scenarios and the impact of damage on Flight dynamics. While still in-progress, we have been very pleased with the data we've been able to collect and are currently busy expanding the Flight Model to include damage modelling. SOUND DESIGN Although still only in the very early stages of development, work has begun on sound design for Corsair! Thanks to the collaboration from some amazing people in the community, we've been able to organise the recording of a real A7 during a maintenance engine run. This is of course an extremely rare opportunity, and we are so grateful to the good people at Tulsa Tech University for making this possible! Thanks to some collaborative efforts from 'Armorine' in our community discord (who has also been invaluable in helping us to secure certain documents. Thank you Armorine!), we were able to organise a professional field recording of the A7. The recording was carried out by Tulsa Tech's team of sound engineers & sound engineering students, with the entire engine run captured from various positions by professional grade equipment. The team even went so far as to produce an excellent master of the samples for us! In total we were given an amazing 29 high-quality aircraft samples from various mic positions, as well as 4 completed mixdown tracks. Below you can see some shots from the recording process Tulsa Tech sound engineering team, responsible for the excellent recordings provided. Images provided by Tulsa Tech & Armorine SYSTEM & WEAPONS DEVELOPMENT Alongside all of this, work has continued throughout the year to develop and flesh out the cockpit systems of the Corsair. Once again, we owe our thanks to 'Armorine' for assisting in helping us to acquire some missing documentation. Unfortunately, due to the nature of systems development, we don't have a wealth of flashy screenshots to show here, but I will do my best to explain the various systems under development and the state they are in. One of the biggest priorities this year has been developing the codebase & logic underlying the A7's targeting and weapon delivery systems. To this end, lots of time has been spent refining and further developing the armament control systems: developing correct pylon release cues & logic, release inhibition conditions, developing calculations for interval drops and developing the core logic that underpins the sophisticated weapons systems of the A7. The culmination of this has been the development and integration of CCIP & CCRP weapon release modes; both of which draw heavily from various sensors and targeting systems in the aircraft before making real-time calculations to determine an impact point. We are pleased to say our A7 can now accurately release unguided weapons on target, using both CCIP & CCRP methods that are unique to different weapon types. Work is ongoing to further develop both weapon release modes to include inhibition cues as well as to develop the navigational modes of weapon release, such as Bomb on Coordinates (BOC) and offset bombing modes. Navigation systems also received some development time in 2022, with the INS and tactical computer systems currently being expanded upon and developed. We have developed the aircrafts waypoint system, including storage, recall and editing of flight plan waypoints. We've also made progress integrating information from the navigation systems into other aircraft avionics; most importantly the HUD and PMDS. 2023 will see the detailing & expansion of the INS system; expanding on current modelling of the Inertial Measurement Unit (IMS) and the development of the Doppler Radar, both of which feed information to the INS. We will also be working to implement mark-points, target points and other in-flight navigational systems. As a pilot flying the A7 will require careful monitoring and management via positional updates and pilot corrections; the A7 requires navigational updates to correct for INS drift, in a similar fashion to the Viggen. As we've shown throughout the year, 2022 has seen the development of most of the A7's key avionic systems in various states of completion. The Projected Map Display (PMDS) is integrated and functioning, with current work focused on integrating navigational data from the Tactical Computer, as well as integrating some of the lesser used functionalities. The RWR has been on the backburner for some time due to some limitations in documentation, however we have now obtained the necessary documents and work is now ongoing in developing the RWR fully! The aircrafts multiple radio systems are also well in development, with the primary functionality of all radios already implemented and work ongoing to implement cockpit controls, presets and other functions. The A7 Radar systems are also well in-development as we've previously showcased, with current work focused on radar targeting functionalities as well as navigational cues. As well as all the above, our current codebase is being constantly refined, expanded upon and rewritten in order to be more realistic with its flow of information. To elaborate, we are aiming to mimic the flow of data as it occurs in the real A7 avionic systems, with many avionics being dependent on other systems and prone to certain failures and accuracy limitations. For example, the tactical computer relies upon information from the Air Data Computer (ADC) as well as IMS systems in order to complete navigational and targeting calculations; any inaccuracies in data supplied from either the ADC or IMS will result in flow on errors and inaccuracies further down the avionics chain. In practical terms, this means that simple things like damage or icing to your pitot tubes can result in inaccurate data being supplied to the ADC and thus the Tactical Computer, creating targeting & instrumentation inaccuracies. We want each system to be interacting with each other as organically and realistically as possible, allowing for the accurate simulation of failures, errors and inaccuracies as they can occur throughout the aircraft. To summarise the state of systems development in the A7 Corsair: most if not all systems have been developed and integrated to at least a basic extent, with work now being focused on expanding and developing the advanced functions of each system as well as the interconnections between each system. This will happen in-tandem with the art, as more & more cockpit controls and displays become available and ready to be tied to code work; we anticipate this will be ongoing for much of 2023. WHAT'S NEXT? We've previously discussed our 4-phase development roadmap for the A7, which roughly translates to the following 4 phases: SFM Based model Basic EFM & flight systems Advanced EFM & advanced flight/weapon/avionic systems SME testing & tuning + damage modelling We are currently approaching the tail-end of phase 3, which as expected has been the longest development phase by quite a margin. Our goal is to complete phase 3 and move into phase 4 of development at some point in 2023. We know it's been a long wait and it seems to still be forever away, but we want to say thank you for your patience and hopefully this report can give you some insight into what's been happening behind the scenes.

I meant animate a mesh, in Blender. I think the play animation function is for static object? ------------------ New generic bridge for the drivable ships

Denial ain't just a river in Egypt. And they say insanity is doing the same thing over and over again so I guess I'm insane because I'll try this one more time even though this has ALL been stated before in this thread and several others... With the exception of that video you've actually not backed up one claim with any numbers or reference to text. The Osprey series of books contain probably our best records of aircraft victories to date. They are not perfect and every researcher/author of each volume has disclaimed the possible errors in their books. Even if all but three or four of the ~115 claims these stock F-4E's got during the War of Attrition during their service from 1969-1973 and Yom Kippur War (Oct 1973) are unconfirmed, (stock means without modification because you ignored that twice already) it would still be more kills than the F-4J. Extensive modification (refuel probes, new weapons, etc.) of these F-4's happened after the Yom Kippur War. That said, the F-4J is not any less awesome than the F-4E just because it got fewer kills. This is a concept you do not understand, and one I'm sure you'll ignore for the fourth time. The stock slatted F-4E then saw combat with Iran as well in the 1980s during the Iran-Iraq War and was the back bone of their AF. We don't have reliable kill stats but we know they shot down at least a few MiG-21s and MiG-23s. We also know they undertook most of the bombing missions alongside F-5's and much later, modified F-14's. The tonnage dropped by just the F-4E when cross referenced with the other texts shows that it dropped more ordnance, and caused more collective damage than all other variants combined. Doesn't make it better, but it does make it far from non-negligible. Both the F-4E and F-4J got a similar number of kills in US service in Vietnam (~20) with the F-4J shooting down more MiG-17s and the F-4E shooting down more MiG-21s. In fact, according to [1] and [2] (see bottom of post), the F-4E got 23 kills and according to [3], [4], and [5], the F-4J got 20. So your whole argument based on air to air victories crumbles. I suppose you'll find a new goal post to invalidate this. I've already mentioned that the 24 Rivet Haste birds flew over 200 sorties logging over 600 combat hours between Nov 1972 and Jan 1973, but you've ignored the service of all those who took part in the program and anyone who flew the F-4E before them. Most of their combat was air to ground but you've ignored that as well. Even if you wanted to count that service as negligible, then your claims of the F-4S would hold no water because it saw no combat and was fewest in number between the F-4E or J. Then there's still that unaddressed claim you made that the slatted F-4E's maneuverability doesn't matter because it's not interesting or whatever you made up. But I'm sure you'll ignore this too and not address a single one, or maybe you'll focus on one claim and say the rest is wrong or you'll just say the opposite again for some reason. Frankly, this is a delusional statement. I've also tried to show empathy to your arguments on why the F-4J would best represent the Phantom first (my second favourite version) on three occassions and you have not reciprocated once... People are agreeing not because of popularity, but because most Phantom records are publicly verified and the replies to you contain logic that can only be dismissed by ignorance or denial (that, and you're not addressing rebuttals to your made-up claims, you're being unfriendly and unempathetic, to put it kindly). This is why I'm convinced you either have some unaddressed, unhealthy coping mechanism resulting in absolute denial of fact or you're doing this on purpose. Unless there are legitimate reasons to continue, I will stop talking to a wall. References: [1] Futrell, Frank (1976). United States Air Force in Southeast Asia 1965-1973: Aces and Aerial Victories. Air University, Headquarters USAF [2] Davies, Peter(2012). USAF F-4 Phantom II MiG Killers 1972–73 [3] Naval History and Heritage Command [4] Elward, Brad. US Navy F-4 Phantom II MiG Killers 1972-73. Osprey Publishing. [5] Stoffey, Robert (2008). Fighting to Leave: The Final Years of America's War in Vietnam, 1972-1973

2023 RAZBAM F-15E Enviado desde mi CPH2197 mediante Tapatalk

@RWC Thank you! Happy new year to you too! -------- Making progress with the lightbars. They are finally visible at a distance. Still a fair amount of tweaking to smoothen the transition between the LODs (right it's very obvious) but slowly getting there

You stated your opinion and no one cares, you can move on. Heatblur already decided to deliver two E variants regardless of what you think about it. If you don't like it, post in some other subforum, no one here cares.

https://discord.com/channels/1020277498363269120/1020303137145368627/1058724969674190878 We want to take this day and the end of the year to wish you all a Happy New Year. May the new year be filled with joy and peace, may all (or at least most) of your wishes come true in the new year. We as AviaStorm look back on an eventful year, we have accomplished a lot, also thanks to your great feedback and your great support we experienced throughout the year. It has been and will continue to be the biggest drive and motivation to deliver the best Tornado to you - the DCS community. Thank you also for your patience. We know that some things don't always go as fast as we all would like and that sometimes it just takes a little longer to get certain things up and running, for example the promised FAQ. But rest assured, we have not forgotten. But enough of the many words: THANK YOU, HAVE AN AMAZING 2023! We appreciate your support very much and will continue to work hard on our dream module.

Gentlemen, mission pack has been released and is ready to download: ■ I LOVE THIS JOB (LAST VERSION) ■ HUEY SHERIFF SKIN

My attempt to recreate a Christmastree with candles and balls "Oh Forrestal, oh Forrestal, how mighty is your air-wing With Tomcats, Hawkeyes and Vikings, but also Corsairs, Prowlers and Sea Kings Oh Forrestal, oh Forrestal, unleash your mighty air wing"

Happy New Year!!!

This thread has run its course so I will clarify the facts for you Open beta is a public test build and always will be. Stable version means just that, it is a stable as it can be. We use open beta to find as many of the show stopping issues or crashes as we can, but it can still contain bugs. Generally we aim for a Wednesday patch, but a patch can come anytime we deem it necessary, our development is constant and dynamic, we have to be flexible. While we appreciate your concerns about when we should patch and when we should not you do not have the full picture of the development cycle and tasks, the team do and they will always make the best choice for our development needs and product stability. thank you

I've only worked with F-16's IRL, but I believe it's mostly similar in the F-4, but when the jets are on QRA duy they "pre align" the jets, so when they scramble it only has to spin up and be confirmed. This of course has to be done again if it's moved or have been stationary for so and so long.

Dear Partners, fellow 3rd Party Devs, and Fans, May the New Year give everybody courage to triumph over vices and embrace the virtues! Happy New Year! - Mag3 Team

Best wishes and Happy New Year for 2023. and many many thanks for all your great work ED-Team !!! RWC.

I must agree. I am extremely dissappointed by stable moving to 2.81. It feels like mockery to me. Stable version has always been a bit of a meme, but at least it avoided the biggest issues. Now with stable on 2.81 it has become a complete farce.

Ist hier irgendwie nicht angekommen: An Heiligabend auf der FB Seite: Mit der S530F und dem neuen RWR der EE dürfte das Flugzeug in Air-Air deutlich tödlicher werden. DIe S530F sollte so um die 10-20NM Reichweite bringen. Inzwischen haben wir mit der Magic 2 auch eine zweite all-aspect Fox 2. Die S530F wird an allen Varianten verfügbar sein. Der neue RWR der EE wird vermutlich optional werden (anderes, kastenförmiges Fairing am Seitenleitwerk). Die AAR-Fähigkeit sorgt zusätzlich für mehr Missionsoptionen. Ebenso das INS, auch wenn das die meisten Casual-Player wohl eher nicht jucken dürfte. Für die Realisten: Die F1EE war in Gando (Gran Canaria) stationiert und ausschließlich für die Luftverteidigung zuständig. Das ganze kann man halbwegs augenzwinkernd auf der Marianenkarte nachstellen. Die Marianen waren mal im spanischen Besitz. Bevor sie deutsch, japanisch und schließlich amerikanisches Überseeterritorium wurden

I noticed an error in the Karakurt, the MG soldier doesn't seem to animate correctly. This will be fixed in the next release. This is how it should look.

Thank you have a good one. Best regards Bignewy and the Eagle Dynamics Team

Diese Form zu entwickeln ist angesichts des seit DCS World eingeführten modularisierten "Konzepts" sicher optimal, da sich wohl kaum jemand alle paar Jahre wg. einer "völlig neuen" Hauptversion die meisten Module neu kaufen würde - hab da selbst andernorts schon viel Lehrgeld gelassen und bin auch deshalb raus aus diesen. Das ist bei ED wirklich zu begrüßen, wie sie an sich recht gut diese kontinuierliche Entwicklung betreiben. Das bedeutet aber halt auch, dass man nicht nur die eigenen Module kontinuierlich weiter mit-entwickeln muss (ich sag nur F-5 *hust*), sondern dass auch die Drittentwickler damit am Ball bleiben (können) müssen. In einer Open Beta sehe ich dann auch noch ein, dass dies bisweilen zu "Brüchen" von einer Version zur nächsten führt und dass auch Mal bereits gefixtes plötzlich wieder "broken" ist. Das dann aber wie aktuell geschehen, eine Beta quasi 1:1 in die Stable übergeführt wird, damit deren Nutzer auch die neuesten Module nutzen (und vorher kaufen) können, führt das Konzept der 2 Versionen schon etwas ad absurdum. Denn die aktuelle OB (inkl. Hot Fixes) hat, wie ich selbst leider mit meinem System feststellen musste, durch einige neue Features, herbe Leistungseinbußen v.a. leider Mal wieder besonders in VR erfahren, deren Ursachen zumindest zum Teil wohl auch durch einige User heraus gefiltert wurden und die vermutlich nicht trivial oder schnell Mal eben zu beheben sind. Vllt. müsste hier gerade auch mit Blick auf das Dilemma, neue Module immer nur mit der aktuellsten Version nutzen zu können, auch an der Stelle konzeptionell gedreht werden, um diese Abhängigkeit etwas zu entkoppeln? - Und es betrifft halt nicht nur die neuesten Module, sondern beeinträchtigt halt teils auch längst erworbene und in die Jahre gekommene Assets nicht unwesentlich. Ich bin jetzt kein Software-Entwickler, habe aber schon einiges an Lebens- und Berufserfahrung im Projekt-Management und war bei ein paar Spiele-Entwicklungen auch sehr nah am Entwicklerteam in internen Closed Beta Test-Teams beteiligt, und meine mir deshalb schon einigermaßen bewusst zu sein, dass dies alles durchaus komplex ist und es multiple Abhängigkeiten auf und über viele Ebenen hinweg gibt. Wenn es einfach wäre, könnte es ja auch jeder . Und mit verteilten Ressourcen wird's nochmal aufwändiger. Um den Bogen zurück zum Thread-Thema zu schlagen: Insofern bin ich gespannt, ob auch hierzu künftig ggf. neue / verbesserte Ansätze seitens ED kommen und kommuniziert werden.

folks, stick to the topic and treat each other with respect and tolerance. thank you

Happy New Year! Yeah there's a lot to be excited for in 2023. The F-4E and F-15E are both really close to being ready for release as well as the Sinai map and possibly the F4U Corsair as well. Maybe there's more stuff that will come out as well, guess we'll just have to wait and see, won't we.

I mean seriously... Heatblur decides what Heatblur makes, not people on the internet. The history that's important here, is that sometime in 202X, Heatblur decided to begin the journey of bringing the F-4 Phantom into DCS. At some point, they made the decision to produce the E model first before a Navy model. Nobody here had any say in that, nor should they have.

It's 2023 here already... ...mudhen-times, I'd say! And a HAPPY NEW YEAR to the whole DCS-family!

30 декабря 2022 года Дорогие друзья, С глубокой благодарностью к Вам и всему нашему сообществу мы завершаем 2022 год и готовимся к предстоящему, насыщенному новыми событиями. Мы желаем Вам и вашей семье здоровья, любви и процветания! Благодарим вас за доверие к нашей компании и, конечно же, просим не пропустить наш традиционный новогодний видео-трейлер "2023 and Beyond", который выйдет 4 января. Наслаждайтесь! Если вы еще не посмотрели видеоролик, посвященный Новогодней распродаже Christmas Sale video и не посетили наш магазин, то предлагаем это сделать это сейчас, так как срок акции истекает в 23:59 8 января по Гринвичу. Это особая распродажа, в которой, наряду с традиционными скидками, вы впервые увидите 50% дисконт на DCS: Mosquito FB IV, DCS: Mi-24P Hind, DCS: F-16C Viper, DCS: F/A-18C Hornet, и DCS: Supercarrier. Спасибо! Ранее, мы уже сообщали о работах, идущих в рамках проекта создания динамических кампаний. Работы по созданию движка динамических кампаний идут вперед, хотя и не такими темпами, на которые мы рассчитывали. Размеры и сложность этой разработки оказались значительными и мы рады сообщить, что это станет весьма существенным дополнением к игре, способным изменить DCS. Сегодня мы расскажем о логике постановки задач игровым объектам, которая является фундаментом всего движка. Помимо сказанного, мы развили алгоритмы обработки больших объёмов данных, используемых при управлении большим количеством юнитов и объектов. Подробности ниже. Ещё раз благодарим вас за поддержку и тот вклад, который вы вносите. Вместе, мы сделаем наши мечты реальностью! Команда Игл Дайнемикс В Новый Год С Новыми скидками Желаем вам здоровья, счастья и радости в 2023 году! Спасибо вам, за ваше участие и энтузиазм! Всего самого наилучшего! Обратите внимание, что зимняя распродажа DCS 2022 продлится до 8 января в 23:59 по Гринвичу. Воспользуйтесь этой прекрасной возможностью получить эксклюзивную скидку на наши самые продаваемые модули, включая специальную скидку 50% на DCS: F-16C Viper, DCS: F/A-18C Hornet, и DCS: Supercarrier. Динамическая кампания Прогресс Движок динамических кампаний (EDDCE) представляет собой интегрированную в основной код надстройку над DCS, позволяющую создавать специальные кампании, где все юниты расставлены по карте и распределены по сторонам, но изначально не имеют предустановленных задач. Помимо юнитов в такую миссию добавляются различные объекты, включающие в себя заводы, склады и т.д. Также прописываются общие цели для каждой стороны. При старте такой миссии запускаются специальные алгоритмы, которые начинают создавать задачи для всех юнитов, призванные обеспечить выполнение основной цели для каждой из сторон. Задачей игрока при этом становится участие в созданных искусственным интеллектом (ИИ) задачах – операциях, управляя любым из существующих в игровом мире ЛА или другой техникой, а также управлять действиями ИИ, указывая на важные моменты при принятии решений, или создавая свои операции. Завершив работу над глобальными функциями движка, в 2022 году команда приступила в тонкой настройке его отдельных элементов. Так была построена общая схема работы авиации в современном конфликте, начиная от оборонительных операций патрулирования вдоль границ, через все этапы подавления ПВО противника, завоевания превосходства в воздухе и до уничтожения наземной техники и инфраструктуры. Получили толчок в развитии наземная техника и операции для нее. Помимо, собственно, перемещения подразделений для выполнения поставленных задач, был создан механизм корректного отображения техники в подразделении в зависимости от его типа и текущих действий: нахождения в атаке, обороне или на марше. Чтобы увеличить доступное число юнитов в кампании, но не перегружать компьютер расчетами, полноценно обсчитывается только техника, которая видна игроку или которая сама "видит" игрока. Для остальных юнитов используются упрощенные алгоритмы, основанные на множестве предпросчитанных данных. При подготовке таких данных используются отдельно написанные механизмы, позволяющие легко обрабатывать всю добавляемую в DCS технику и вооружение. Чтобы упрощенные алгоритмы не влияли негативно на ощущения игрока, реализованы бесшовные переходы между упрощенной и полноценной моделями расчетов. Это позволит игроку видеть все юниты на своих местах и выполняющими свои задачи при полете через всю карту, где бы игрок не оказался. При встрече же с игроком, все юниты будут использовать основные алгоритмы работы DCS, что и позволит игрокам получить знакомый игровой процесс при непосредственном управлении техникой. Еще один важный блок работ, получивший развитие в этом году – это система фронтов. Была реализована новая модель множественных фронтов, позволяющая получить более достоверную картину для организации прорывов, широких охватов и окружений. На данный момент можно сказать, что за этот год были настроены основные элементы движка, которые и делают управление кампаниями автоматизированным, основанным на развивающейся в кампании ситуации, т.е. динамическим. Следите за нашими новостями. С Новым Годом, друзья!

Dear all, Merry Christmas and all the best for 2023! As the team prepares for some well-earned time off, here is where we are with the Hornet: Highest priority is on bug fixing. This includes, but it not limited to issues with the Harpoon, SLAM, and SLAM-ER behaviors, ASE dot behavior, etc. We are performing a ground up review of and refactoring of the Hornet flight model and flight control system. This also includes a large update to the landing gear model. New and improved pilot model. Once this is complete, we’ll do the same for the Viper. Refactoring the radar for more accurate performance. Once this is complete, we’ll do the same for the Viper. We’ve updated the ALR-67 to include new functions and symbols. Following the next Open Beta, tasks include: IAM loft cues. New bomb fuzes like DSU-33 and JPF. MUMI page and DTC. This will follow the Viper DTE page and DTC. A review of MSI functions based on available data for the version we are modeling. Please note that the above are just the highlights is certainly not 100% inclusive of all planned work. Kind regards, Wags

That was 2 months ago on Reddit. The update since then was "the F-4 is nearing completion" a month later. The post on Reddit even specifies "sorry about the non-answer" showing they're explaining how things are going in the office, not how the timeline is. All I'm asking for is a timeline update. Obviously they missed their goal of 2022, but some communication would be nice.

I think no one really got a problem with you stating your opinion as long as you stay within topic of the thread. Every single thread you appeared in was transformed into something like "only -profanity- people like land based phantoms" which is your opinion but don't try forcing it upon us. That said there was a thread about why a naval phantom is objectively better, so maybe stay there? You wouldn't face so many opinions against yours and could freely discuss any shortcomings of landbased phantoms. I don't think you're necessarily wrong but like with most things people have subjective feelings about certain things and don't like it when you call them dumb. I think most of us get that most navy variants where objectively better than any landbased ones. But we still love the E or atleast we are fine with getting the E as long as we get any phantom. Maybe try understanding others? But that one goes in both directions. I really hope that it's possible to set our differences aside for atleast one thing. (Yeah I know wishful thinking but given the state of society in general hope is most we have I guess)

Neues Dev Diary: https://flyingironsimulations.com/blogs/news/flyingiron-2022-end-of-year-report (Mann muss etwas nach unten scrollen um zur A-7 zu kommen)

Moved this onto github for now https://github.com/shadowze/DCS_weather Updated with 2023 moon lit nights

Been having an absolute blast last few months with stable build 2.7 falling in love with the WWII birds while running at 3240x1920 at stable 60 fps @ 60Hz with mostly all maxed detail settings. I was very disappointed to get updated to 2.8.1 and see a solid and almost consistent 10 fps drop from where I was with absolutely no visual improvement to account for it. Granted I don't have a super high end system, 2.7 ran great. Both 2.7 and 2.8.1 run at the same fps with all terrain shadows turned off in 2.8.1 while 2.7 was set at default. Turning on flat shadows craters my fps in 2.8.1 ED, all of my respects to you and the phenomenal work you do. But please keep unstable and unoptimized implementations in the experimental branch until they have been thoroughly tested and proved fully functional to be promoted to the stable build. These are basic product development practices.

Hello! Can ED do more realistic gun smoke at low speed? This is current gun smoke on hover mode VSI=0 This ishow it must be:

All airplanes are very susceptible to stall at high altitude. The definition of “coffin corner” is the small difference in maximum airspeed and stalling speed at high altitude. Since stall speed increases at the square root of the G applied, it is very easy to induce a high altitude aerodynamic stall. Dog fights at high altitude are very careful, slow motion affairs. Without the specifics of a particular event, it isn’t possible to say if the high altitude stall of the DCS P-51 is accurate but given an altitude and surface temperature it is pretty easy to ballpark what sort of stall performance is to be expected. Above 30K ft. I would expect no more than 3 G with that probably on the high side and inversely proportional to altitude.

Oh, of course! The Gregorian calendar isn't flawed enough, to be honest. They did make a statement a while ago about how Current Events™ and personal issues have thrown a wrench into their plans. Whether they update the timeline is pretty pointless. They missed their goal, they couldn't do much about it. No sense in getting hung up on it, we just wait a bit longer.

Нут по мне все понятно, для чего пишу. Вы хотите продать карту. Я Вам намекаю, что за эту сумму её вряд ли продадите. Почему? Потому, в ДНС она стоила дешевле, и кто хотел, тот купил. Кто не купил, тот подождет когда она появится, и возьмёт возможно дешевле, если не дешевле, все одно возьмёт в магазине из за понятной гарантии на 3 года. Основной посыл в том, что продать карточку можно по цене ниже той, которая будет в ДНС в ближайшее время. Так, добрый совет..

So no updates on the timeline at least? I know about the 2023 AB video teaser having the F-4 but that's ED, nothing from Heatblur on missing the date?

Happy New Year to all the Eagle Dynamics team and as RWC says so well thank you for your hard work to make us happy to be able to drive thanks to you beautiful planes on beautiful maps. (Don't be upset if sometimes people grumble after an update, they have nothing against you but just disappointed that what they dream of does not materialize immediately) Continue to make us dream because without you we would be unhappy

Ok, I tested the same spot on High preset but with All shadows disabled (both terrain objects and main shadows setting to OFF), and the performance of both 2.7 and 2.8 is the same, hovering around 180 FPS. And looks like I'm still on CPU limit, so GPU is not skewing the result. I guess that is a good news, it shows that the shadows are indeed the main culprit of increased CPU usage in 2.8.

Walleye is a Navy/Marine weapon. I have seen no evidence of the F-4E ever carrying the weapon or it being listed in the USAF manuals for the F-4E. The photos you have posted of the USAF planes with the walleye are F-4D's one of which is definitely a weapons school aircraft and the other has a test weapon fitted. If I were to hazard a guess, I would say the Walleye was evaluated by the Air Force but not adopted by the service. The Air Force used the GBU-8, GBU-9 and GBU-15 TV guided weapons instead.

А зачем пересчитывать в уме координаты? АБРИС-у ведь можно сказать, что бы выдывал координаты в нужном формате: Вот так:

Hope to see at least J-8 or if possible some early Flanker.

I hope, if not a J-10 module then as AI or maybe some S300 counterpart SAMs.

DCS World On develop screenshots

I don't think we are playing the same 2.8 version. Still getting a lot of aliasing on some type of clouds, especially at dusk

DCS: BO-105 HKP-9A's TOW BGM-71A Missile done.

Dear all, A little update on the A-10C II. In addition to the primary task of addressing existing bugs, most of the A-10C II work is on the ARC-210 radio. We are nearing its completion that includes the radio head, HUD data, UFC functions, and COMM page. The remaining item is the STAT page change. Once that is complete, it will enter internal testing. Following its release, we will then add satellite radio functions. At initial release it will include VHF and UHF function (RT1). Once the ARC-210 is complete and delivered, it will bring the module to a feature complete state based on the listed features here: DCS: A-10C II Tank Killer (digitalcombatsimulator.com) Aside from the ARC-210, we still wish to add a 1st person pilot model, but this would come after the Hornet and Viper pilots are complete. To add DTC functionality to the A-10C II, we are also considering an update to the TADS that would entail changes to the TDL and CHG SET pages. This would allow both SADL and Link 16 data through a gateway. However, this is not a promise and something that would only come after DTC functions for the Viper, Hornet, and AH-64D. Merry Christmas and all the best for 2023, Wags

More drivable ships coming soon Even with some weapons, thanks to Currenthill