WHOGX5

When putting the FMU-152 tail fuze on the Mk-84 High Drag variant, the minimum arming delay is 2 seconds. However, if I put the same FMU-152 tail fuze on an Mk-84 Low Drag variant, for some reason the minimum arming delay is 4 seconds.

As per real world manuals as well as Wags own description in the DTC video which was released yesterday, the DTC page labels should only invert while a data transfer corresponding to that label is in progress, and then return to normal once the data transfer corresponding to that label has been completed. Currently, the label stays inverted indefinitely. You can see the DTC page in an older block of F-16C function in the same way here at 2:44.

Well, I'll extend an olive branch and say that he is partially correct. You have to remain stationary until the RDY indication is either flashing or solid, which will happen long before the alignment process is finished. After that you can move around freely, as the aircraft will automatically pause the alignment process while you're moving, and then automatically resume the alignment when stationary again. For a huge part of the alignment process, you can therefore move around freely. For a small part of it, you have to remain fully stationary.

DM sent.

Thank you, much appreciated!

This is incorrect. As soon as either a steady or flashing RDY is displayed on the INS page, you should be able to move your aircraft freely as it will automatically enter AUTO NAV mode, even with your INS knob set to STOR HDG or NORM. It doesn't matter if you're spooling up your engine, or you decide to taxi to the other side of the airfield, the alignment should not break. Then, once stationary again, the INS will automatically resume the alignment process without any actions from the pilot. The INS switch should only need to be set to NAV before takeoff, as AUTO NAV will only work on the ground. In fact, using these kinds of interrupted alignments should actually increase INS accuracy below 10, but this doesn't happen currently in the DCS F-16C either.

No, it wouldn't be ALOT of work. We're not talking about some complex full body animations here, where they need to hire a motion capture studio and then have a whole team of animators sit for weeks on end adjusting and finetuning the animations. We're talking about moving the arm from the throttle or stick, and lifting it up in the air. That's it, an animation which could be created by hand, probably in about an hour of work by a professional who knows what they're doing. Of course I don't know how the DCS engine handles animations and how hard it'd be to add, maybe it's a super complex and convoluted process compared to other game engines, but normally this would be quite a menial task to include in a game. Also, similar animations already exist in other ED modules, like the F/A-18C pilot body grabbing the canopy rail handle during the catapult launch. If they can do it in the F/A-18C, I don't see why they couldn't make the same thing for the F-16C? You'd just make the animation be triggered by the mouse cursor being in a specific region of the cockpit, rather than when triggering a catapult launch. And of course, this feature would benefit from being added to all DCS modules as they all could benefit from the physical pilot body not being a hindrance and an obstacle to operating your aircraft.

There has been quite a few messages since my last reply, and it feels like some people in this thread think I mention all the systems I did in my post merely because I want to sit and LARP useless features, and I can tell you that this is definitely not the case. All the items I've mentioned have a direct impact on the combat effectiveness of the DCS F-16C, as well as the user experience. That is why I mentioned the things I did. As it stands currently, the DCS F-16C is unable to employ most real world tactics due to there being so many missing or inoperative systems, and its performance in combat is therefore very lackluster. It doesn't matter if you're doing BVR, WVR, SEAD, AI, or just hurling some bombs on a target. There's always several aspects of this aircraft that's missing or not working correctly, limiting your combat effectiveness in each of these roles. In my post I also put special emphasis on the SEAD role as, after all, this is the primary role of the F-16CM-50, and the DCS F-16C's performance in this role is woefully inadequate. You also have to remember that the combat environment we have in DCS is quite dated and sterile. In the 2007-era which the DCS F-16C is based on, you'd have much more capable weapon systems to face off against, which for the SEAD role would include things like both datalinked and home-on-jam SAM missiles, integrated air defense networks with intelligent and coordinated SAM operators, GPS and communications jamming, ground based radar decoys, etc. That is why I really appreciate when ED models things in depth, like the INS and its fix functions as well as GPS reception, which now enables the future addition of things like GPS jamming, which is a staple of modern warfare that even civilian aircraft and airliners have to contend with on a daily basis. And if we get GPS jamming, this also highlights one aspect of why the Digital Terrain System is important, as it, amongst many other things, increases the INS accuracy over topographically varied terrain. And all of a sudden, this has ripple effects into mission planning, where you might choose to ingress towards a target over more rugged terrain if you expect to encounter GPS jamming in order to maintain higher INS accuracy, rather than ingressing over the flat desert or ocean and having to do manual INS fixes, or it might affect which weapons you choose to employ, opting for LGB's instead of JDAMs, or it encourages you to actually make use of Offset Aimpoints or VRP/VIPs when engaging targets, et cetera. Just with the addition of a few systems, it makes the experience so much deeper, and it also gives you very good reasons to learn your aircraft more in-depth and to actually make use all the functions that have already been implemented into this product to their full potential. And for those who mainly want to hop in their jet, fly out to the range in a sterile environment, and drop some bombs on targets to blow off some steam after a hard days work, they can still do that. But it also allows people to get so much more out of the product, to get more invested into DCS as a platform, to increase customer retention, and in the end increasing future revenue for ED. These dedicated people who go in-depth are also usually the ones who creates a lot of content which benefits the entire community, stuff like tutorials, complex missions and campaigns, video content, etc., which entices new customers to join the fray and turns their toe dipping in DCS into a full submersion. And certain items I mentioned, like having a damage model, doesn't increase combat effectiveness, but it is of course an important aspect of combat. As it is right now in the DCS F-16C, the "damage model" is basically a big boolean. Either you audibly hear things hitting your aircraft, but not a single system is affected, or you die. Compared to other ED airframes, like the DCS A-10C or DCS F/A-18C, those modules actually model individual systems getting damaged, and you might actually end up utilizing emergency and backup systems to limp your jet back to base, and you might actually need to use your knowledge about how the fuel, hydraulic and electrical systems work in order to survive such an ordeal, isolate busted fuel lines, circumvent broken systems and components, etc. So when people claim the DCS F-16C has a damage model, that is simply not true because none of these things exist in what we currently have.

As I mentioned in my previous reply, there is no way that ED does not have documentation on these things. If they didn't have the relevant manuals, they wouldn't have gotten as far as they have in modelling an F-16CM-50 M4.2+. I feel like the "no documentation" or "its classified" is often used to avoid responsiblitity, and I've even heard of people reporting issues referencing old manuals which are definitely in the public domain, and they still get told that they're not usable due to classification or similar.

That AIM-120 thread of yours is an absolutely incredible piece of work on your part! I also agree with your sentiment that the DCS F-16C does not feature the level of detail needed to simulate basic true-to-life operations. On the topic of AIM-120's, you cannot employ SKATE tactics properly as there is no HPRF mode, and guiding the missile until pitbull will 99% put you inside of the desired out range unless you're up against a vastly inferior platform, and in addition to this, the AIM-120 in DCS is seemingly incapable of reaquiring a target after a lock has been broke. And I don't need to reiterate myself regarding SEAD operations, as I covered that in my post. And regarding the CATM-120 and other training munitions, one of the features I really wish DCS would implement, which is present in other combat simulators, is that when you use training munitions and you "launch" them, then an invisible copy of your munition which does no damage would be launched so that it shows up on tacview and can be used for training purposes without actually killing each other. As far as I know, in real life the ACMI pods even provide kill indications on the HUD of the participating aircraft if and when the simulated missile would've impacted the target, allowing actual aerial combat to be simulated in real time without firing live munitions. This would be great to have in DCS, especially for online communities. This could also extend to other training missiles too. Well, I chose not to run the risk of breaking forum rules by adding any mentions of specific documents and such. Suffice to say, ED definitely has access to all the necessary documentation to verify my claims.

I get that this is not a 100% simulation of the F-16C, and I get there are diminishing returns, but most of what I mention above is just basic core functionality, all of which is well documented in the real world manuals that ED must be using in order to model an F-16CM-50 M4.2+ circa 2007. I mean, if I had my way the DCS F-16C would be the most detailed rendition of an aircraft ever to be produced by man, but I get why that is unviable. As mentioned, I just want a rendition of the F-16C that lives up to the bar set by ED modules like the A-10C, and preferably goes a bit above that bar which was set over 10 years ago, which the DCS F-16C has already done in certain respects, like the superb INS modelling for example. And on the topic of diminishing returns, many of the features I mentioned are not strictly F-16C specific, but could be ported to other ED products as well, both past, current and future. Like the DBTC "terrain following" functionality would be great to port to the Tomahawks and other cruise missiles in DCS, who cannot fly over rugged terrain without barreling into the side of a hill. Or perhaps a PGCAS implementation could help AI fighters avoid CFIT-ing themselves during maneuvering. Or the external IR lighting, which Polychop couldn't implement into the Kiowa either as it's not supported by DCS at this point in time. Or an implementation of the IFF MODE 1, 2, 3 and 4 interrogations, which we've seen already in the F-15E, which could be added to all compatible airframes currently in DCS. Investing in the F-16C now by implementing these kinds of systems would not only satisfy the community, but also decrease development costs for future ED (and non-ED) projects if they are developed in a smart and modular manner. And for me, as a regular member of the community, seeing a roadmap with all the systems and functionality that I've mentioned in my post being either marked as completed or not mentioned at all, does raise some worries when ED starts pushing for a full release. In your post I'm replying to now there is a lot of "can" and "may", and I get that you're a community manager and can't confirm or deny whatever you want, but it doesn't do much to reassure me of anything. I think it's not a stretch to say that ED tends to be quite opaque in their communication with the community, and it is often impossible to know what ED's intentions are, or what the status of their development is. Like regarding the DTC, it could either be close to finished, or it could still be on square one where the developers are still outlining features, I literally have no idea. The same thing applies to all the different bugs and missing features in the DCS F-16C, but in regards to those I don't even know if they're planned to be fixed/implemented at all. And like I mentioned in my post, I don't see how the DCS F-16C in its current state fulfills what ED themselves have claimed the goal is for this product, and I don't see or know if or how ED is intending to fulfill those promises. You also have to understand that for me, as someone who has been leading an DCS F-16C milsim community since the day the DCS F-16C released, I need to manage retention of my squadron members in spite of the constant issues that have plagued the F-16C since day 1, all the systems that break or degrade every single patch, the slow rate at which fixes and new systems are added to the aircraft, and all this in face of the black box that is ED's future plans for the F-16C. That is a big part of why I'm as active as I am on the forums, to stay on top of these amorphous issues and to try to prevent my squadron members from spending many hours planning and flying a mission, only to find out that some system didn't work as it should because of a recent patch and therefore the mission needs to be aborted and all those hours people spent and set aside to have some fun were unceremoniously dumped in the proverbial trash bin (which has already occurred several times this year in spite of my vigillance). My mantra to my members has always been that we should have faith in ED, and that I'm sure that the DCS F-16C will be an incredible product at full release, and I've said this because I honestly believed it and it's held true for previous ED products in my experience. If ED moves ahead with this full release, my mantra is null and void. Then my mantra will have to change to something like "maybe, perhaps, at some non-descript point in the future, ED will fix or add this or that system that they've never even mentioned in the roadmaps or newsletters, and by the way, this is all based on pure speculation" which understandably isn't too convincing. I'm honestly worried that our squadron will start haemmorhaging members to other units which either operate other airframes, or other simulators entirely. We're already seeing our F-15E squadron teetering on the edge of collapse for understandable reasons, and I don't want our F-16C squadrons to meet the same fate. This is the operative reason for me even beginning to write my very lengthy post. And if ED policy or ToS regarding early access pricing is the main obstacle to keeping the DCS F-16C in early access, then please just change your policy or ToS and put the DCS F-16C on sale while it is in early access. I cannot imagine a single member of this community objecting to that. I can, however, think of many community members who would object to the DCS F-16C being slated for full release before it has all the expected reliability and functionality.

Correct. Thanks for renaming the thread, and like I said, if you want to discuss or get clarification on any of these points, just hit me up.

The reason for this "panic" will be clarified once you have the time to read the post. I'm also saddened to see my post be merged and buried into another thread which is already solved in what seems like a backhanded moderation move, presumably to make it harder for the community to find my post. I put a lot of effort into this post and think it deserves its own thread, so I would appreciate if it was unmerged back into its original thread. And if you or any other ED employee wants to discuss any of these points, I'd happy to converse with you.

In order not to drag this out too much, as this post is quite lengthy as it is, I'll get straight to the point. The DCS F-16C is not ready for full release. This thread is in response to a post by BIGNEWY saying that the Sniper XR is the last major item before the DCS F-16C is ready for full release. Below I've listed some of the reasons why the DCS F-16C is not ready to leave early access, even with the Sniper XR added, by describing the current state of this product. This post was written with the help and contributions of several community members, who I want to send my deepest thanks to; you know who you are. Lastly, this is not an all-inclusive list, but rather a summary of the major aspects which are currently missing or unfinished in the DCS F-16C (there are A LOT of smaller items remaining in addition to this, including quite a few bugs). It's quite lengthy though, so go get a bag of crisps, crack a beer, and lets get on with it: - Damage model: Practically nonexistent, with no real damage being simulated except fuel leaks and your wings getting blown off. I put this at the top of the list because I cannot see how you can have a digital combat simulator without combat damage being simulated. - Maintainance / Pilot Fault List: Practically nonexistent, still only shows a single message which is the "FLCS BIT FAIL" if the FLCS bit fails. This is the entire error reporting system of the F-16C and is therefore an essential system in order to keep tabs on the status of your aircraft, even when you haven't taken any combat damage. For example, if your L16 time isn't set, you should get a "LK16 TIME REQD" message to tell this to the pilot. At the moment, you will eventually notice that something is wrong with datalink, and then you have to figure out what the issue is on your own through troubleshooting, rather than just checking the PFLD and immediately knowing what's wrong. This is just one example of many where proper MFL and PFL messages would be incredibly helpful, and the reason why those systems exist in real life. - Steerpoints: Exists in a very limited state. Only supports regular steerpoints, markpoints, and a partial implementation of D/L steerpoints. Many types of steerpoints are completely missing, like pre-planned threats, geographical lines, SEAD steerpoints, a plethora of LINK 16 steerpoint types, etc. We're also still missing different CRUS TOS functionality, like having DES TOS reference HACK time instead of SYSTEM time, and also the ability to blank DES TOS times and have the CRUS TOS required velocity be calculated for a steerpoint without a DES TOS, based on the DES TOS of a later steerpoint; an incredibly useful feature for improved timekeeping. - Digital Terrain System: Completely missing including its subsystems like PGCAS, TRN, OW/C, DBTC & PR. An essential system from the earliest tapes of the F-16CM-50 where you load the terrain data of a 480x480 nautical mile area wherein the DTS has features both to avoid CFIT (controlled flight into terrain) which was the biggest cause of death in the USAF at the time, to providing various subsystems to facilitate safer low altitude operations including a kind of digital "terrain following radar" mode, to decreasing INS drift by comparing your radar altitude to the know terrain elevation in different parts of the map, and also to allow more accurate targeting without using active sensors. This is for example what makes high angle JHMCS markpoints accurate, as it can reference the known ground elevation of the location you're looking at. Without the Digital Terrain System implementation, the DCS F-16C has much higher risk of CFIT, much higher risk of flying into terrain/obstacles during low altitude operations, much lower targeting accuracy (especially at longer ranges and in uneven terrain), and higher INS drift over non-flat terrain than a real F-16C of our block and tape would. - ECM: Barely implemented. Currently only barrage jamming is kinda working, and even that is extremely ineffective most of the time. MODE 1 and MODE 2 self-protection jamming is wholly inefficient under all circumstances, as the ALQ-184 currently is seemingly incapable of breaking SAM radar locks. There's also no ability to choose which bands to jam, making it impossible to jam certain surface threats without jamming your own radar for A-A sanitizing. Neither MODE 1, 2 or 3 should inhibit your radar, but rather MODE 2 & 3 should reduce the effectiveness of your radar while actively jamming in the same band as your radar, and not impact the radar at all while jamming in other bands. The AN/ALQ-184 in DCS also has 360 degree coverage, whereas it would have roughly 120 degree cones fore and aft of the pod in real life, with diminshing effect closer to the outer limits of those cones. MODE 1 should only use the aft emitter to jam threats, while MODE 2 & 3 use both fore and aft emitters. It should also have high/low settings to angle the jamming emitters downwards for surface threats and upwards for higher altitude A-A threats, as well as cooperative jamming where multiple F-16C's in close formation boost jamming effectiveness. As an aside to this, chaff is completely useless against certain threats. You can drop 120 chaff in 1 second and you still will never be able to spoof an SA-5. This in combination with an inability to break locks during jamming, means that your only real defense once an SA-5 is locked on to you is to dive towards the ground and break line-of-sight. Other emitters have similar issues. - SEAD: This point encompasses a lot of different systems which are necessary for efficient SEAD, which after all is the primary role of the F-16CM-50 in the USAF. As mentioned, the AN/ALQ-184 is completely useless in self-protect mode (MODE 1 and MODE 2) as it cannot break locks, decreasing survivability, as using barrage mode will constantly transmit your location, and also disable all your active sensors as well as the HTS pod. Most importantly, the AN/ALQ-184 is unable to break locks, meaning it can only be used pre-emptively (not very good when employing wild weasel tactics). The AGM-88 has modes like TI/GS/DL which have not been implemented, limiting the AGM-88's effectiveness in the SEAD role. Also, many different AGM-88 HOTAS commands are completely missing. HAD priority targets are missing. The LINK 16 Special Channel net has a very rudimentary implementation. The ability to target/blank pre-planned threats is completely missing. The ability to store detected emitters as SEAD STPTs is completely absent, greatly decreasing your ability to engage SEAD threats as they will just disappear after going inactive for a while, and the only way currently to target these emitters once they go inactive is if you have a human wingman, because then you can send that emitter to him via L16, and then he can send it back to you. If you've got no human wingman, you're out of luck. The AN/ALR-56M Radar Warning Receiver is still incorrectly implemented, making it useless for any kind of high threat environment (the kinds of environments where SEAD is required) as it conveys no relative lethality of detected emitters but rather displays all threats as equally lethal, being especially useless for pop-up threats and active missile avoidance as you can never tell how much of a threat a detected emitter poses to you. In real life, the late cold war saw multiple datalink capable SAMs which don't give RWR warnings at all, increasing the need for the kind of relative lethality displaying of threats that the AN/ALR-56M does in real life, especially for SEAD operations. Currently, we don't have any datalink capable SAMs in DCS, but if it's ever added, the F-16CM-50 will be completely unable to operate in that kind of environment, unlike its real world counterpart. The AN/ALR-56M should also use data provided by the INS to update detected threat locations during maneuvering when emitters may end up in RWR blind spots, and even flip the symbology when rolling the aircraft upside down, so emitters are displayed in the correct direction under all circumstances. Having a functioning RWR is maybe the most important aspect of being combat effective in the SEAD role, and currently we don't have that. - AN/ALR-56M: Even though I mentioned the issues with the RWR just above, I'm still making this a separate point just to emphasize the importance of this system. If I could only pick a single thing that'd be fixed in the DCS F-16C, it'd be the AN/ALR-56M. Right now, the DCS F-16C is completely handicapped, not merely in SEAD, but in all combat situations, because the current RWR implementation is not merely incorrect, but it makes the RWR close to useless. The AN/ALR-56M was chosen as the new standard RWR for the USAF because of it's incredible capabilities and the added situational awareness it provided to its pilots, and this is also why it was rolled out so early on the F-16CJ/CM-50, the USAF's primary SEAD platform. However, in DCS, the AN/ALR-56M is the single least capable RWR in the whole modern US fighters lineup, and in many ways it's even inferior to the old 1980's SPO-15 mounted on the MiG-29A. If you get an AMRAAM fired at you, the SPO-15 (and the real life AN/ALR-56M) will indicate how quickly the missile is approaching and how close it is to impacting you, allowing you to plan your missile defence and perform last ditch maneuvers. With the DCS AN/ALR-56M, you have no indication of how far away a missile is except when it impacts your aircraft. This really, really, really, really needs to be fixed, especially for a SEAD platform like the F-16CM-50. - Air-to-air: This is also a collection of different things. AIM-120 is still missing many features, including target size options and not least the HPRF mode, greatly reducing the maximum effective range of the AIM-120 and making the bread and butter SKATE tactic non-viable against most threats, as you need to guide it all the way to MPRF mode, a.k.a "pitbull". The Uplook Search (ULS) radar mode is still completely missing. STT mode is extremely ineffective at long range, and even against a high aspect non-maneuvering target which is detectable in RWS/VSR, it will not be able to produce a stable lock. A-A, MRM and NAV master mode are also unable to have different CRM modes selected and retained. COAST mode is still missing, meaning that notching will immediately break your radar lock and the aircraft will not even attempt to reacquire the target. On the topic of notching, the current radar implementation is EXTREMELY suceptible to notching. You can be 5 nautical miles away from an enormous KC-135 in look-up conditions against a clear blue sky, and it will still notch you as it reaches 90 degrees aspect, even if it's only for a split second, which should be physically impossible with a modern radar like the AN/APG-68V(5). Even notching against ground clutter should be extremely ineffective unless the target is very close to the ground or has a big chaff cloud next to it. Auto range scaling in SAM/DTT modes still automatically decreases the range scale, which it shouldn't, making those modes useless for situational awareness as you should still be able to freely sanitize the airspace beyond your bugged tracks in those modes. Also the HAFUs are completely unreliable, making TWS especially useless as the art of upgrading tracks is a complete black box. Blanking LINK 16 symbology will often blank all the correlated bricks as well, meaning you cannot even see the things which you've detected with your own radar. You can lock them up though and launch missiles at them, you just cannot see them on the display. Contacts which start jamming will often get snapped to exactly 99.0 nm distance on your FCR, often forcibly rescaling your FCR and requiring you to reset the FCR range settings in the middle of combat, to be able and reaqcuire that same threat. HAFU identity is also very unreliable, with enemy threats often being displayed as green friendlies for no apparent reason. And when you're in ACM mode, the bore cross in the HUD and bore ellipse in the HMCS still do not show true radar line-of-sight like they do in real life, but are instead completely static paintings giving no information at all regarding where your radar is actually pointing. - Air-to-ground: Ground radar is still extremely janky and cumbersome. Ground maps will regularly instantly blank itself during maneuvering. When entering many different radar modes, rather than the radar moving quickly to it's starting angle and then sweeping to generate a map, it often moves really slowly to it's starting angle and just does nothing for a couple of seconds, and only then does it actually start mapping. GMT mode doesn't actually lock onto the target, but rather just the point on the ground your cursor happens to be over. Gain/Contrast/Level settings for the ground radar are not granular at all, and it is often very difficult/impossible to achieve a good balance between them. Changing these settings should also only apply for what is mapped after changing those settings, so if you raise gain in the middle of a sweep, the first half of the map will be low gain and the second half will be high gain. On some maps, like Persian Gulf, you seemingly cannot ground map terrain, only objects. JDAMs still cannot be programmed properly. JSOWs cannot be programmed properly. GBU-24 is there in spirit, but still hasn't had its guidance modes properly implemented, making it quite useless and unable to even reach the target when dropped at max range and high altitude. IFF interrogations are not possible in A-G mode, which they should be. There are also missing munitions, like the CBU-89/104's, various training munitions, possibly even the JASSM. - Lighting: Some things are completely missing, like the external IR emitters which our tape and block of DCS F-16C should have, being selectable through the COVERT modes to allow external lighting at night which isn't visible to the naked eye, and also to only illuminate the lights on top of your aircraft, to stop ground threats from spotting you. If you look at the the external lights through NVGs, you'll see that the green lights seem to be NVIS compatible, but the red lights will completely fry your retina. Cockpit flood lights have very low intensity even at the max setting, and also little to no light scattering, meaning they don't actually flood the cockpit. They're more like focused spotlights, leaving many parts of the cockpit completely in the dark, even at full intensity, including the new pilot body kneeboard which is completely unreadable at night even with every single internal light source set to maximum. On the topic of spotlights, the actual Cockpit Spotlights under the glareshield are completely inop. The Cockpit Spotlights are also the only light source in the entire aircraft which are usable purely with battery power, and are commonly used in real life to monitor engine instruments during startup at night. They are also used to illuminate the pilot body kneeboard when the pilot don't want to illuminate the entire cockpit with flood lights, in order to be more NVG friendly. In addition to these points, there are also issues with light intensities. Some lights like the left indexer or external formation lights, etc., usually go from slightly dim to quite bright between 0% and 5%, and then every setting above is just almost indistinguishable amounts of extreme brightness. With other lights, most notably the cockpit flood lights, you can barely see them at all between 0% and 50% intensity, and then they go up to kinda bright at 100%. This becomes even more troublesome because of the way light brightness works in the F-16C, because when the flood lights are set to high brightness, every other malfunction and indicator light in the cockpit will go to max brightness too. This means that we can't have a bit of flood lighting without getting completely blinded by every other light source. Some lights also don't seem to be NVIS compatible at all, especially the RWR panel which is extremely bright and will wash out your NVGs. The right indexer lights seem fully NVIS compatible and won't blind you even on max brightness, while the left indexer will wash out your entire NVGs at max brightness, and still be very bright at only a few percents intensity. - Textures: The default DCS F-16C textures (including those available in the texture template) are of incredibly low quality, with not merely bolts and screws missing, but entire panels. Also the textures themselves are just poor in quality compared to what you'll find in the DCS User Files section. ED should honestly just pay Roughmaster to make a new texture template for the DCS F-16C, and remake all the low-quality liveries which are currently available for the DCS F-16C, as Roughmasters liveries are of such incredibly high quality that it's almost incomprehensible. Cockpit textures are also missing textures for multiple things. - Tankers: When refueling at a KC-135, the boom still has no resistance and exerts no force on the aircraft. In real life, the boom will push back against the aircraft when connected, allowing the aircraft to "rest" and stabilize itself against the boom. This currently doesn't happen in DCS, making aerial refueling more difficult as you need to have more accurate thrust management than real pilots do in order to stay in position. Tankers in DCS also will never extend the boom farther than the halfway point when connecting even if the player is close to center and fully stabilized, so the player always has to move closer than the halfway point to connect, rather than like they do it in real life where the boom operator will extend the boom to meet the connecting aircraft. When it comes to tanker external lights, they will not turn on their position lights until the receiving aircraft is less than 1 nautical mile away, making night rejoins extremely difficult unless you want to fry the boom operator with an STT lock. Also, there are no external flood lights on the tankers, making them practically invisible while refueling at night, except for the fore/aft and up/down lights. Also, the background lighting on the fore/aft lights is very bright at night, making your fore/aft position incredibly hard to see. During daytime, the lights are very dim and the glass on the fore/aft and up/down lights is very reflective, with reflections often obscuring what the lights are indicating, especially when the sun is low in the sky. Lastly, tankers still do not transmit TACAN in A/A mode, but you have to use T/R mode instead as if they were a ground based station, meaning you also cannot see the tanker A/A TACAN distance on your DED/HUD. It would also be nice to have some basic boom operator functionality, like giving break-away calls and raising the boom if the player is to close/unstable (including an actual boom collision model), giving heads ups before entering turns, reading off the amount of transferred fuel at regular intervals, maybe even having the player be able to request a certain fuel amount via the radio menu. - DCS F-16C manual: This manual is still not up to date, and new features which are added to the DCS Stable branch still aren't updated in the manual, leading to a lot of unecessary threads on the forum as a lot of information about how systems work are lost to the sands of time in the Viper Mini-Updates thread, and usually have to be conveyed through word-of-mouth. For the things which are correct in the manual, the systems are in many cases bugged and not working according to the manual, leading to further confusion in the community when being referred to the manual. Honestly, everytime a feature is added or changed in the DCS F-16C, this should also be reflected in the manual, including a changelog of added/changed features in the manual itself. If systems are not functioning correctly, this should also be noted in the manual with a small notice in that section. After all, DCS is now a unified stable branch and then it'd make sense for every change to be in the documentation, since this isn't a beta build anymore. - The jealousy: Things which have been implemented in other ED modules, but not the DCS F-16C, even though they should be present for our block and tape. Things like the HSD Expanded Data, whose equivalents are present in the A-10C and F/A-18C, but which for some reason isn't planned to be implemented for the DCS F-16C even though it was present in the simulated block and tape IRL, greatly reducing situational awareness via datalink. Or the decision of ED to not implement the AN/ARC-210 radio which was already in active service for our block, tape and year of F-16 (confirmed by multiple ED active duty SMEs + non-ED active duty SME's + US DoD fiscal reports showing amount of quarterly AN/ARC-210 unit installations for USAF and ANG + the actual real world documentation for our tape of F-16CM-50 describing AN/ARC-210 functionality) because "it was more common later", leaving the DCS F-16C as the only modern US aircraft in DCS without the AN/ARC-210 (A-10C, AV-8B, F-15E, F/A-18C), and therefore it is the only modern US aircraft in DCS without the ability to tune multiple UHF frequencies and use a single radio for the entire UHF/VHF/FM range with HAVE QUICK capability, even though it could do this in real life during our tape and time. The AN/ARC-210 would be a very simple item to implement too as it requires no 3D modelling changes, but merely new DED pages, and seeing as this radio is already implemented in other ED modules like the A-10C and F/A-18C, it should be quite simple to port to the F-16C, making ED's resistance to implementing this radio even more of a question mark, seeing what an enormous improvement it'd be to the F-16's communications suite. There are also other things, like the HAVE QUICK page being available in the A-10C, allowing HQ functionality through SRS (SimpleRadio), however the HAVE QUICK page has not been implemented in the F-16C, making the F-16C unable to use HQ via SRS. The ability to choose Fighter/Mission Channels on LINK 16 is present in the F/A-18C, but not the F-16C forcing them to send D/L points to every F-16C on the server. Or the IFF page which has been implemented in the F/A-18C and allows setting Mode 1, 2, 3 and 4 codes, has not been implemented in the DCS F-16C, meaning we cannot set our squawk codes as you would IRL through the DED/ICP. We can only set Mode 3 via the analogue backup IFF panel. Also, the A-10C even has Mode 1 and Mode 4 timetable support, giving alerts at specific time intervals when the Mode 1 and Mode 4 codes change. The F-16C should have similar functionality where the aircraft will, instead of alerting, automatically disable/enable transponders, as well as change their transponder codes, based on certain time and position requirements. More importantly, none of these features require DTC as they can all be set from the cockpit. And even if DCS does not support HAVE QUICK and IFF functionality at this point in time, these things are supported through other softwares like SRS and LotAtc, and is as mentioned already present in other ED modules, so I don't see why we wouldn't get the same treatment in the F-16C? There are also some amazing features from non-ED modules like the Datalink Mission Assignment API in the M-2000C, which allows external sources (either AI GCI or a human via LotAtc) to send taskings via datalink to the aircraft and have them be viewed on the situational displays in the aircraft. The F-16CM-50 of our tape and year had that same kind of functionality via L16, where C2 assets can send a plethora of mission taskings which get received as a data messages, with the ability to view and accept/reject taskings via the HSD, and also send tasking completed/aborted messages to the C2 station. This would be a huge deal for human GCI/AWACS in DCS, especially with players speaking completely different languages, and it'd also open up a tonne of opportunities for mission creators to access this functionality via scripting. I'm not going to delve into why the DTC and its related functionalities are absolutely essential, as they're already in active development. Other systems like the IDM functionality and towed decoys are at least on the roadmap. For all the other points mentioned above, there seems to be no light at the end of the tunnel. If these kinds of major systems are completely missing at a so-called "full release", that would set a new benchmark for what level of quality we can expect of DCS modules. In addition to all the essential features which are still missing, the amount of bugs which still remain is impossible to overlook, to the point where you cannot even cold start the DCS F-16C according to real life checklists, as there are several inaccuracies which would force you to abort the mission and put the jet into maintainance in real life. In regards to BIGNEWY's recent comment that the DCS F-16C "is complete in regards to what we intend for the module. Our modules are never intended to be a 100% replication of the real aircraft.", I would like to point out that we're not even remotely close to a 100% replication, and people aren't even asking for 100% replication at this point. Making a 100% replication would mean adding things like the need to cycle the flight controls before initiating the FLCS BIT to warm up the hydraulics and get rid of any air bubbles in the lines, as the FLCS BIT will otherwise most likely fail. It would mean adding things like accurately modelled startup sequencies for individual systems like the FCR, MIDS terminal and other systems, where they run their own internal bits and take time to power up before being available for use. Or maybe some realistically modelled magnetic drift of the HMCS, sometimes requiring re-alignment in the air. These types of things are available in other F-16C simulators available on the civilian market, and I think we all would've hoped that the DCS F-16C would reach at least a similar level of depth and, as ED themselves have said, the DCS F-16C would be "the most realistic simulation possible" and offer a "detailed simulation of the Viper’s engines, fuel, electrical, hydraulic, comms, lighting and emergency systems and many more". I don't know how you can claim that the DCS F-16C delivers on any of those promises in its current state. I realize that ED probably wants the DCS F-16C out of early access since it's been there for over four and a half years now, but it would be a huge mistake to do so at this point in time. For ED's own sake, for their own reputation, and the communities faith in their current and future products, they should never allow a module which is in the dire state of the DCS F-16C to be considered "full release". Full release means finished, irregardless of what your post-release plans are. You might add a feature or fix a bug later at your whim, but in the end, the full release is supposed to contain everything we customers paid for, a complete and stable product, and anything which is added to the product free of charge after full release is merely charitable work on the developers behalf. It is not the fulfillment of some obligation to their customers, but rather a completely voluntary act which goes beyond what the customer paid for, in order to increase customer satisfaction. And to say "here it is" and give us what have currently + the Sniper XR would be an incredible betrayal of trust, and I for one would never buy a DCS early access module again, if this is what I can expect from it. I'm happy to support ED and third-parties early in the development process even by purchasing pre-orders as long as they deliver a decent product upon full release, which is what has happened previously in my experience. But if the F-16C is pushed out like this, that'd be a turning point for DCS as a platform. And this is something I say as a long-time DCS customer, who has been flying DCS on a regular basis ever since the A-10C was released over a decade ago, and has spent so much time and money on DCS that I don't even want to attempt to add it all up due to fears of what I'll be faced with. Without mentioning any specifics, I think we can all agree that the current drama in the DCS community is testing the community's faith in ED and DCS as a product. Pushing the DCS F-16C out of early access in its current state would do nothing to improve that situation, but would rather risk pouring fuel on the fire, which I don't think neither ED nor the community wants at this point. DCS isn't a perfect product, but it has the most potential of any combat flight sim on the market, and has been making strides to become the best combat simulator on the market. Please cherish this and do not make any reckless decisions in order to meet internal deadlines, while alienating your own customers. All I ask for is that when the F-16C reaches full release, the level of quality will at least be the same as other ED modules. The DCS A-10C which was released a very, very long time ago when ED was a much smaller company, was an incredible product. It had practically all the systems modelled that it would've had in real life to an incredible depth, only excluding certain systems which couldn't be modelled due to classification and such. It also had very few bugs, making it an absolute joy to fly, which it still is to this day. That level of quality is what I expect of an ED product, based on the benchmark that ED themselves set. Not only would a DCS F-16C release in anything close to its current state be well below this benchmark, but it'd also not even live up to what ED themselves have claimed their goals are for this product on the DCS F-16C product page and in promotional videos and press materials. So my final words in this very long post is simply a plea to ED: Please do not push the DCS F-16C out of early access before it lives up to the level of quality and fidelity which the community has come to expect of ED products.