NineLine

We are looking at this now, but understand that there isnt a ton of good info on these as you might expect (although I have found some). We will see if it makes sense to tune where needed, but also we have to consider that some people might get grumpy if their sensor is downgraded some. Yeah, I would assume if a pod has image enhancement of any sort, there is a reason why they have it.

While I appreciate your feedback, both in the original post and in this one, it seems to me you did not read what I wrote. The F-16C development, bug fixing, and tuning is not stopping, and will continue to improve and grow. As I also mentioned to you, bug reports are much better than these lists. I do not agree that the F-16C is in a "sorry state" and I have been flying it a lot with the Sniper as of late, and as I got ready to show it off during the FlightSim Expo. Your 3 points are not missing but may require additional work, bug fixes and tuning. As I said, that is still going on. The module will leave early access as the features are added, but will continue to develop as we move forward and based on available information, both current and anything that is newly found. As an example, the F/A-18C left early access sometime ago; this next update it is receiving Terrain Avoidance Radar Mode.

Some damage model issues have already been reported. If you can't find them in the bugs section, you can make a report with all the needed info and tracks. Thanks.

As we have stated in a number of places now, the Sniper pod and supported software was done for only the Viper; you could not just simply copy and paste it onto another aircraft. Why isn't it going to be on the A-10C? 1) For the above reason, it was always planned for the F-16C and only that. I know most of you guys do your research and even if you look at the implementation of the same pod on two different aircraft, they can work, function or operate very differently. 2) We do not have the information for the pod within the cockpit of the A-10C. We do not have legal accessible documentation on how the pod functions within the cockpit of the A-10C, its possible its identical or close to the Viper, but even if we found out it was, the information is neither available or legal to use at this point in time. I know this doesnt always make sense, especially when we are working on even new aircraft, but it is an issue here. 3) Lets say we resolved 1 and 2, there is a matter of resources and time alloted for such additions, most certainly it would take away from new developments, current projects, etc. While all the A-10C pilots might rejoice, others might be upset to find their favorite project was held up by giving the A-10C another pod that maybe it doesnt really need right now besides being cool to have. But But you guys did a suite update to add new items for the A-10C II update. While we added some cool new items, we did not update the suite software, and the A-10C remains mostly a Suite 3 aircraft. Yes it has newer suite items but we did not do a complete and total suite update on it, the information is simple not available for us to do so. And as most of you know, we have a special relationship with the military and the A-10C and will not step on or risk issues by using things we should not be using. Now, with the news that the A-10Cs might be retired sooner rather than later, maybe we will see more info come to the public, and then maybe down the road we could do more with the aircraft, but right now we just cannot do this to the level we would want to be able to do it. PS the Pilot model is getting close, so that is still coming.

The issue with your list here is that some of these things are core issues, such as refueling, which has nothing to do with the F-16, but 100% a core game issue, as well as Wishlist items that were never promised and tuning/bug fixing. As has been advertised in the Roadmap for a long time, all planned, primary features of the early access version will be available following the next DCS update. While the F-16C is leaving early access, there are still several items being added that are listed in the Roadmap, as well it is a premier title for us, and will continue to be tuned, improved and such. As an example, there is a large Manual update coming next release.

Yes you will, thanks!

I have not heard anything official yet, so nothing new on our end at the moment.

I have a number of different offerings from WINWING, full disclosure, they were sent to me for support within DCS. I have had an issue with the stick twisting, but generally it was my own issue with the set screw. I am not saying this is this person's issue, but in my case it was my own issue. I have 2 throttles and both have worked just fine, no sticking. I have adjusted the resistance myself to firm it up a bit, but this is personal preference and I like to tinker. If you want, you could DM me your support info, and I can see if I can help you find more support. I have seen many throttles over different Expos now and never seen such an issue. So if you want, shoot me a DM.

That's not very GUCCI of you.

Would love to see more variants of different aircraft in DCS in the future for sure.

So you answered your own question then?

I would imagine the only news we will share going forward is a resolution, one way or the other.

I will ask if this will be adjusted or updated.

Due to how LODs work, it will all be based on settings, so if you cut it down in options, it will be cut down in game, whether viewing through a TGP or not.

There is some issue with medium and low settings that units are rendered farther out than terrain objects, which is a core issue rather than a pod-specific one, meaning it affects all pods. Is this what you are referring to?

In the next DCS update, George AI Copilot/Gunner (CPG) will be receiving a significant upgrade, along with some improvements to his existing logic and behavior, in an effort to make him more realistic, interactive, and capable. It is important to note that no changes have been made to any existing AI Interface commands or control functions. Rather, additional commands have been added to the AI Helper Controls (Left/Right/Up/Down) when the AI Interface is displayed and set to NO WPN, and the Consent To Fire command has been modified as a contextual, multi-purpose button. In the graphic below, the new AI Interface is shown, with the new commands identified. New search tasks (explained below the AI Interface graphic) may be configured using the Left-Long and Right-Long commands while the AI Interface is set to NO WPN. The function of the Consent To Fire command under the current conditions is displayed in the center of the AI Interface, with the short press (<0.5 seconds) function displayed above the long press (>0.5 seconds) function below it. It is worth noting that the Consent To Fire commands may still be used without displaying the AI Interface. For example, if the player wishes for George AI CPG to begin performing an Area search, a long press of the Consent To Fire button may be used without the AI Interface displayed. However, to select a different Area search, the AI Interface will need to be displayed and set to NO WPN. New Search Tasks Up until now, George AI CPG could only be commanded to perform a direct, momentary search for targets along the line-of-sight of the Pilot’s helmet or the TADS sensor turret, and would rank those targets based on threat priority (i.e., air defense units would be at the top of the list). The player may now choose from 7 additional methods for George to search for targets, facilitated by the new changes in the AI Interface. Direct Searches. These are two searches that George was already capable of performing up to this point. PHS SEARCH - George slaves the TADS to the line-of-sight of the Pilot Helmet Sight (PHS) and performs a momentary search for targets. Targets are ranked by threat priority. TADS LOS SEARCH - George performs a momentary search for targets along the current TADS line-of-sight. Targets are ranked by threat priority. Area Searches. These searches allow George to proactively search for targets in a designated area or based on FCR target locations, visually identify FCR targets prior to an engagement, or perform battle damage assessment of engaged FCR targets after an engagement. FWD AREA - George slews the TADS in a 90-degree search pattern directly in front of the helicopter and continuously searches for targets. George will verbally announce when targets are detected but will not generate a Target List unless the AI Interface is displayed. Targets are ranked by threat priority. PHS AREA - George slaves the TADS to the line-of-sight of the Pilot Helmet Sight (PHS) and then slews the TADS in a 45-degree search pattern centered on the PHS-directed azimuth in relation to the helicopter nose and continuously searches for targets. George will verbally announce when targets are detected but will not generate a Target List unless the AI Interface is displayed. Targets are ranked by threat priority. FCR TGTS - George generates a Target List based on FCR target data obtained by the onboard FCR scans performed by the player or received across the datalink via FCR TGT Report or RFHO. George will enable C-Scope and attempt to identify the FCR targets highlighted in the Target List. If the target cannot be seen due to visual obstructions, George will verbally announce it. If the target is destroyed, George will verbally announce it and remove the target from the Target List. OWN PFZ - George slaves the TADS to the PFZ assigned to the ownship and continuously searches for targets within the geographical boundaries of the zone. George will verbally announce when targets are detected but will not generate a Target List unless the AI Interface is displayed. Targets are ranked by threat priority. ACTV PFZ - George slaves the TADS to the activated PFZ and generates a Target List based on FCR target data obtained by the onboard FCR scans performed by the player or received across the datalink via FCR TGT Report or RFHO. George will enable C-Scope and attempt to identify the FCR targets within the geographical boundaries of the zone and highlighted in the Target List. If the target cannot be seen due to visual obstructions, George will verbally announce it. If the target is destroyed, George will verbally announce it and remove the target from the Target List. Point Searches. These searches allow George to search for targets in the vicinity of a TSD point or the FCR Next-To-Shoot (NTS) target after the Player has Linked the TADS to the FCR in the Pilot seat. POINT - George slaves the TADS to the selected TSD point to perform an indirect rocket attack from behind cover; or may be commanded to adjust the TADS field-of-view setting, toggle the selected sensor (FLIR or DTV), or fire the laser, to assist with performing reconnaissance. If subsequently commanded to search for targets, George performs a momentary search for targets. Targets are ranked by geographic proximity to the TSD point, regardless of unit type. LINKED - George may be commanded to adjust the TADS field-of-view setting or toggle the selected sensor (FLIR or DTV), to assist with performing visual identification or battle damage assessment of the FCR NTS target. If subsequently commanded to search for targets, George performs a momentary search for targets. The closest target that matches the classification of the FCR NTS target is ranked as the first target in the Target List, and all remaining targets are ranked by geographic proximity to the NTS target symbol, regardless of unit type. New capabilities and procedures George must be commanded to perform start-up procedures if spawning into a cold start AH-64D. However, George will assist with more of the start-up checklist items such as powering on the FCR and RLWR, and will verbally announce to the player as he completes major items such as boresighting his helmet or when the FCR has finished its power-on sequence. George may also be commanded to perform the relevant shutdown procedures. George is now capable of engaging multiple targets in sequence. When presented with a Target List, the player can select multiple targets from the list, as shown below. In this image, the player has selected 4 targets from the list by pressing the Consent To Fire button as each target is highlighted in the list. If the player presses Right-Short to command George to begin tracking a target that has been added to George's "shoot list", George will slew to the first target in the list (tagged as 1). If the player presses Right-Short to command George to begin tracking a target that is not added to the shoot list, the shoot list is canceled and George will only track/engage that single target. As before, George will still wait for a Consent To Fire command before engaging the target if set to HOLD FIRE. However, once his current target is destroyed, he will automatically slew the TADS to the next target on the shoot list and wait for another Consent To Fire command before engaging the next target. If set to FREE FIRE, George will begin engaging if engagement parameters are met, and then automatically slew to the next target once the first target is destroyed, and immediately engage the next target (again, assuming engagement parameters are met). When tracking a target and GUN or MSL is selected, a short press (<0.5 seconds) of the Consent To Fire command will direct George to fire his assigned weapon as before. If the Consent To Fire command is pressed and held (as signified by the ADJ+ label in the center of the interface), George will adjust the crosshairs onto the center of the target to prevent laser overspill beyond the target itself, and then re-establish an auto-track on the target when Consent To Fire is released. However, the player should fly in a stable manner while George is commanded to refine his aim using this function, which is why the player has been given a command to coordinate the timing of such actions. Improvements to existing logic and more verbal communication The existing logic of George AI CPG has been improved, with more realistic behavior and procedures. For example, if the player has set the RF MSL PWR to OFF, and the player subsequently commands George to use RF missiles, George will set the MSL PWR back to AUTO. George will also verbally communicate to the player what is required for him to perform a command or provide verbal feedback if he is unable to perform a command. For example, if George needs the player to maneuver the helicopter into launch constraints before he can fire a missile, George will verbally request the pilot do so: "Get me in constraints". Previously, George would not fire an AGM-114 missile if any Performance Inhibits or Safety Inhibits were displayed, even if the Player pressed the Consent To Fire button. This would lead to confusion as to why George was announcing "Engaging" but did not actually fire a missile. Safety Inhibits cannot be overridden, but a Performance Inhibit may be overridden if George pulls the weapons trigger to the 2nd detent, which he will now do if ordered to do so. If any inhibit, Performance or Safety, is displayed when George is ready to fire a missile on his current target, George will announce "Constraints" to request that the pilot maneuver the helicopter into appropriate launch constraints. When and if this occurs, the player may now order George to override a Performance Inhibit by pressing the Consent To Fire button (except BAL LIMIT if the target is out of range). However, it is important to note that the presence of a Performance Inhibit increases the possibility the missile may not hit the target, either due to failure to acquire a laser or not being able to maneuver to the target. Therefore, the player (as the "pilot-in-command" of the helicopter) must be judicious with this command when a Performance Inhibit is displayed. This gives the player the freedom to make tactical decisions regarding when it is appropriate to override an inhibit, at the risk of expending a missile without striking the intended target. An updated DCS AH-64D Early Access Guide will be included in the next DCS update to fully describe these new functions and features in detail. We hope that these new features to George AI CPG will provide a much more engaging gameplay experience in the DCS: AH-64D.

Just to be clear, I have made no statements, and anything I share is from ED management. I am sure you are aware, but for lurkers and such.

Per the video, the AIM-9 only.

In this DCS: F-16C Viper video, we’ll continue from the earlier basic functionality video of the AN/AAQ-33 Advanced Targeting Pod to discuss some of the more advanced and unique capabilities of the ATP like Extended Range (XR), Maverick handoff, Multi-Track (MT), Laser, Infrared Pointer (PTR), Laser Spot Track (LST), and air-to-air mode. NOTE 1: Later, we plan to add the MENU function that includes other PTR options and Fragmentation Ellipse settings. NOTE 2: This targeting pod has a much common name, but it is trademarked. NOTE 3: The ATP is not planned for the F/A-18C (USN/USMC) and A-10C II Suite 3 basis as it would be inaccurate for the versions of these aircraft we simulate. NOTE 4: At 13:53, I misspoke. Use Cage/Uncage to enable/disable LST via the HOTAS. Not the Enable button. NOTE 5: ATP MT detection range of aerial targets will greatly depend on the target type. For lower signature/small sized targets, NARO mode will work best compared to WIDE for larger targets/large signatures.

I will allow this to stay, but the discussion of the above video like certain sus subreddits are purely opinion pieces fueled by bias for one side or the other with a heavy mix of speculation. If I were to give my opinion like these sources as you could imagine it would be seen as heavily biased no matter what facts I personally know. So I don't want to see people crapping on Spuds as I am sure that is coming, rather take it for what it is and realize the original post in this thread is all that's really known for sure and we all just want to see this resolved for the best of our customers.

You must have bought the Flaming Cliffs version as the Full FIdelity one is not released yet. https://www.digitalcombatsimulator.com/en/shop/modules/fulcrum/ This one here does not have an interactive cockpit like all other Flaming Cliffs version aircraft. https://www.digitalcombatsimulator.com/en/shop/modules/mig-29_flaming_cliffs/

I would prefer Adam Ray for me, please.

Thank you for the log. I will pass it along to the team to review.

Sorry, forgot to update this, it is reported. Thanks!

Reported, thanks!