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.

Kind regards,

Wags

•  

• 
• ED Team
• •  11.7k
  •  3

• Author
• Popular Post

•  

Posted yesterday at 09:31 AM

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

 

• 42
•  9

 

Wags

• 
• ED Team
• •  11.7k
  •  3

• Author

•  

Posted 1 hour ago

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

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

 

 

 

 

 

https://www.youtube.com/watch?v=001oQMPwwUw