Wags

Just the cool kids.

Raptor is my AH-64D sensei.

Today we completed internal integration of L16 and IDM sharing of HTS/HAD emitter contacts. This will allow you to designate and share emitter location between Flight, Team, and Donors. Additionally, sharing of emitter triangulation data between flight members is also internally complete as part of the TDOA option from the HAD page. We've made further adjustments to SPI sharing regarding accurate HSD symbology that includes Flight/Team member ID. Finally, we've made good progress on adjustments to the ITR and G-onset, and internal verification tests will probably start next week. If testing goes well, we plan to have it included in the next Viper update. Progress on datalink is going well, but we still have some significant items to still complete. Once datalink is complete, work will commence on the CRUS DED page. In parallel to datalink and FM, DEST DED page, MAN bombing mode, and LADD bombing mode are in work. Kind regards, Matt

Can you please provide a link? I don't recall ever making such a statement a few days ago. Rather, for some time I have been messaging by the end of Q1 2022. This provides us some buffer, that we hope we do not need to use. We sincerely apologize about the delays, and we understand your frustration, particularly for those that pre-ordered. We can only provide our best estimates at the time, which sadly has changed much more than we had wanted due to team health and technical challenges. Kind regards, Wags

Closed Beta Testing Has Begun DCS: AH-64D has entered Closed Beta Testing, and this is a significant milestone. Our Closed Beta Test team consists of many community members that assist us in testing new modules near the tail-end of development as an addition quality control step. This has proved valuable for us to help identify bugs in highly complex modules that requires many eyes to ensure thorough testing. We sincerely thank all our Closed Beta Testers for their time and hard work. Testing is not always fun; it can be tireless work. A critical aspect of the Closed Beta Test effort is network play. This has historically been an area more difficult to test internally because of the requirement for many players online. Yesterday, the Closed Beta Test team conducted their first large-scale network test with excellent results. We hope you enjoy the attached images. We understand that you are eager for the release, and we are working at full speed to make this happen. We are still on track for an Early Access release before the end of March 2022. Thank you for your patience and support; it will be worth it. Kind regards, Wags

Some of our customers are visually impaired in their right eye. Kind regards, Wags

To finish out a busy Viper development week, we've added Markpoint exchange between flight members (IDM and L16 Steerpoint storage ranges) and hearing the "Lock" VMU message when an STT lock has been obtained while in an ACM mode. Have a good weekend, Matt

With the earlier release of the DTOS mode, I got quite a few "Christ-on-a-bike, Wags, where the max toss anticipation cue?" Well, it's now in the game and should be released in the next big Viper update based on final testing results. The maximum toss (45 degree) anticipation cue consists of a circle, 100 mR in diameter, displayed on the HUD (below the boresight cross at 0 degrees azimuth and -3 degrees elevation). The cue is displayed 2 seconds prior to a maximum toss pull-up (based on 4.0g in 2 seconds). When the solution cue is displayed, the anticipation cue flashes for 2 seconds before being removed from display. Weapon release occurs as the aircraft approaches a 45-degree pitch. Because there are multiple release points that can result in weapon release, release can occur any time after the solution cue is displayed. For less than a 45-degree toss, the pitch at release varies depending on the maneuver performed. Kind regards, Matt

Link 16 SPI sharing was implemented today. I think this will prove a very handy feature. With the HSD not SOI, pressing the COMM switch right (inboard) for greater than 0.5 seconds will transmit the player’s SPI to other Mission members. When a SPI message is sent, the XMT L16 label at OSB 6 will highlight for two seconds on the HSD. The sent SPI is based on the current SPI sensor track. If there is no SPI sensor track, then the current Steerpoint is sent as the SPI. When the SPI is sent, recipients see it as a large, white “X”, the same as a Mark Point. On the HUD, MKPT## will appear that assigns the SPI location to Steerpoints 71 to 70. “DATA” will be heard as a voice alert. As you can see, it is the same as receiving a Mark Point, but it based on a SPI location rather than a Steerpoint location. One difference is that if the SPI is created by the TGP or A-G FCR, there will be a lock line between the sender of the SPI (Mission members 1 to 4) and the SPI “X” symbol/location on the HSD. The line will disappear after 30 seconds or by pressing WARN RESET on the UFC. We look forward to adding this to an upcoming Open Beta. Also, to answer the posed question, yes, we plan L16 and IDM. Kind regards, Matt

Much of our Viper work is now centered on the Link 16/IDM interflight datalink. This is a very important and useful element of the Viper, and currently, our highest Viper priority. With this feature in place, you will be able to: - Share Mark Points between flight members - Share SPI between flight members - Network the flight together for HARM HTS TDOA mode to more effectively triangulate emitter locations - Sending SEAD contacts between flight members - Assign air-to-air target sorting between flight members - Support Primary Datalink Track (PDLT) - CAS mission assignments and reception - Battle Damage reporting support We also wish to roll in EXP HAD and HSD support. As you might gather, this is a very complex task, and we don't have a delivery date at this time. We look forward to updating you on this task as it progresses. In parallel, other Viper items continue development such as the instantaneous turn rate / available G tuning, pilot model, bug fixes, and more. Kind regards, Matt

About controls: With the release of the TADS Part I video, I’m seeing a lot of questions and concerns regarding controls. I can only speak for myself, but for the DCS: AH-64D, I use the Virpil Constellation stick and CM3 throttle (very versatile when developing a broad range of aircraft). This works exceptionally well, as I’m sure similar units from Winwing, Thrustmaster, VRP, and others will. We really are in a golden age of flight sim peripherals. When in the CP/G seat, I mostly just have the TEDAC controls bound. Given that the CP/G would generally only fly the aircraft if the pilot is incapacitated or eating a ham sandwich, you only need to really concern yourself with the TEDAC controls. When in the pilot seat, I just have the cyclic and collective controls mapped (no TEDAC in the pilot seat). As noted earlier, we have separate control binding groups for the CP/G and Pilot seat based on which you occupy. See attached. Kind regards, Matt

TADS Part 1 is planned for Saturday. Kind regards, Matt

This is the cable I used: Amazon.com: StarTech.com 2m USB 2.0 A to Right Angle B Cable Cord - 2 m USB Printer Cable - Right Angle USB B Cable - 1x USB A (M), 1x USB B (M) (USBAB2MR) Mounting is only possible on the right side, but with sufficient bolt tightening, it worked out fine.

As an F-16 throttle, nothing else comes close.

For those interested, it is possible to mount the throttle to a MonsterTech desk mount. However, you'll need to purchase a different USB cable that has the 90-degree connector into the throttle.

Today we completed one of the biggest gating items for early access release, multi-crew sync. When in networked multi-crew, this is a critical feature that allows both crew members to set the Direct To location, set a Terrain Point, and set a Waypoint/Hazard/Control Measure/Target Point. As you will discover, this is a rather unique aspect of the AH-64D and really shines in network play. Work on the hold modes is going well, and heading hold us just about done. While you can certainly maintain a stable hover and very easily fly the helicopter without the attitude and altitude hold modes, the implementation of these will allow "hands free" operations and make concealed attacks that much easier. The cold start procedure is proceeding well, and we can already bring a cold and dark AH-64D to life. Most of the work is now focused on the correct ENG page indications and fire suppression arming and test system. Initial "George" as the CP/G is now integrated and undergoing initial tests. This allows the player to fly from the rear pilot seat and instruct "George" up front to search for and engage selected targets that it has located. These are probably the biggest four to-do items for the early access launch, and all are making good progress. Kind regards, Matt

Dear all, Since I created the Viper ECM video, we have been able to enable separate SPJ responses for the XMIT switch in Position 1 and 2. We hope to include this in the next update, but it will depend on testing results. When XMIT is in Position 1 we have Radar Priority. When in Radar Priority and the jammer is transmitting and ownship radar and HARM/HTS performance is reduced by 40%. When XMIT is in Position 2 we have ECM Priority. When in ECM Priority, the FCR and HARM/HTS are silenced unless an AIM-120 is the active weapon. In this case, it behaves the same as Position 1. The overall jamming effect on hostile radars has also been substantially increased. We plan to also implement this for the Hornet's jammer, but I do not have a time estimate yet. Electonic attack will be playing a bigger role in DCS in 2022. Kind regards, Wags

Dear all, In addition to the ECM pod functions coming to the Viper, we will also be introducing jamming effects on the FCR. When the FCR can generate azimuth, range, Vc, etc. data for a target and the target is jamming, a yellow double-chevron symbol is placed over the contact. If, however, range cannot be resolved due to jamming, a yellow, double-chevron symbols is placed along the top of the FCR page along the detected azimuth angle of jamming. The attached image shows examples of both of these conditions and a non-jamming contact. This is planned for January 2022. Kind regards, Wags

As has mentioned a few times over the past few months, most of the team that were assigned to the Hornet have moved their focus onto the Viper. However, we’ve still have staff on the Hornet with the focus on completing the Automatic Carrier Landing System (ACLS) and correcting bugs. Please see our change logs for the long lists of corrected Hornet items. Following early access exit, development will certainly not cease. When development resources allow, we all plan some additional changes and improvements regarding: MSI tuning and some functions Radar tuning Flight model and FCS tuning ATFLIR tuning including offset logic HARM tuning Flight Director Mode Static MUMI Page GBU-24 auto-pilot TALD We also hope to add the Mk-77, Multiple Fuze Types, IAM Terminal Settings, Loft Mode IAMs, and GEN-X, but these rely on tasks outside of the Hornet.

When considering your profiles, you may wish to consider that we will have unique bindings for the Pilot and CP/G based on which cockpit you occupy.

Edited first post: moved ACM Slew mode and a couple DED pages from 2022 to 2021.

Dear all, Although the Viper Sustained Turn Rate Data document was included in a discussion thread, I thought it useful to include as a post here to make it easier to find. DCS_ F-16C Viper Sustained turn rate.pdf Kind regards, Wags

Dear All, Time for a little update on the DCS: AH-64D. As you may have gathered from the videos, progress has been excellent, and we are well on track for both the pre-order and early access release this year. We hope you have been enjoying the sneak peek videos and Cato's fantastic show cases. These are created for the dual purpose of building customer awareness (one of our biggest challenges as a small company) and providing you a better appreciation of what you would be pre-ordering. An informed customer is a happy customer (generally). Although we’ve been able to show off quite bit, there is still much work to do before an early access release. Some of these items include: AI flight takeover AI command system Front seat/Back seat cooperative multiplayer synchronization Add attitude and altitude hold modes Tune flight model, SCAS, and SAS Radios and radio pages Damage modeling (art and systems) Complete all systems required for a cold start Voice message and tone alerts UI art Training, instant action, and single missions And more… So, while I understand many you are repeating the “release it now” mantra, I think you will agree that all the above items much first be addressed. No one wants a repeat of the Viper launch. Also, once the pre-order starts, I will pivot to the full-up training lessons to help prepare you for the early access release. Kind regards, Wags

I thought some of you might like to see the full FLIR image behind the WPN/RKTS page. Kind regards, Wags

Ah, NIIRS, brings back memories of my old NPIC days.