Wags

Hello, This is primarily in regards to guidance. We're working on some comparison graphs for real world and game data for flight performance based on thrust, acceleration, drag, alpha, etc., and we will let our clients draw their own conclusions. In a related matter, we plan to do the same for the Hornet and Viper flight models. Although we added Augmented Proportional Navigation (APN) earlier (as apposed to pure PN navigation), we believe there is room for improvement in regards to the loft trajectory. We want to investigate this and make improvements where needed. Thanks

Hey everyone, I hope you all gearing up to have a very merry Christmas and well-deserved holiday break! As most of you are aware by now, we will be releasing Track While Scan (TWS) radar mode for the Hornet today. The system is largely complete but there are couple of items we still need to address in a planned hot fix for Friday, such as the missile fly-out cue and target vector stem. We have several other great Hornet improvements for this week. Added TWS radar mode. F18 REDFOR (US Aggressors + NATO) will be able to use GPS. Fixed significant performance drop on SA page with big amount of contacts. JDAM/JSOW STEP Logic changed JDAM/JSOW Power Logic changed Fixed JSOW not releasing from stations 7-8 Fixed several AA radar mode issues. Reworked AA modes transition logic. Corrected target designation logic via undesignate button. In January, after the team is back from holiday, much of the focus will be on the Hornet targeting pod, AACQ and SPOT radar modes, JDAM/JSOW improvements, Viper radar-directed gunsight and general gunsight accuracy (EEGS Level 5), and improvements to the AIM-120 AMRAAM. Once we have specific Open Beta release dates for these items, we’ll be sure to let you know. The improvements to the Hornet targeting pod have taken longer than expected due to needed fixes to some of the air-to-air missile avionics systems. We apologize for the delay; we know how much you are looking forward to them. In February, much of our air-to-air radar development will shift to air-to-ground radar development. This will use the air-to-ground radar API that is already being used by 3rd party developers. Thank you for all your support and once again Merry Christmas, Wags

Good track and thanks. Reported.

The Hornet guide will be updated with the TWS chapter internally this week, and should be available in the following OB. Once we are 100% sure TWS is final, we'll create the interactive training lesson. Thanks

Correct. We are still working on the fly-out symbol, filed target stems, and L&S target heading. Thanks

It operates just as our documentation describes for this aircraft and software version. Thanks

DCS: F/A-18C Hornet – Track While Scan (TWS) Radar Mode FOR 18 DECEMBER 2019 OPEN BETA In the next Open Beta for the DCS: F/A-18C Hornet, we will be including the Track While Scan (TWS) acquisition radar mode. This is a powerful mode to create situational awareness, engage multiple targets at the same time with the AIM-120 AMRAAM, and break-out targets in close formation. It also integrates with the data link and IFF systems. Important commands: Undesignate button = cycle L&S, swap L&S and DT2, and TDC designate [ENTER] = set L&S or DT2, set AUTO/BIAS center

DCS: F-16C Viper - Wing Flex Demonstration A new element being added to the DCS: F-16C Viper is wing flex and twisting. This provides a much more dynamic and interesting behavior to the wing as you takeoff, maneuver the aircraft and high-G, fly low and fast in turbulence, and even release heavy ordnance. This is the next large element that we are adding to the external model of the Viper. Following this, our next external model task for the Viper is to complete the texture template and create several more skins.

Just about ready for the 18 Dec OB. We just need to add the RESET function and it should be feature complete. Thanks

Weekend before last I spent a good 8 to 10 hours online on various servers (under an alias). I did see this on a few, but with others I never saw it. Given this, I suspect it has something to do with how the mission was created. I'm afraid though that I don't have an answer yet as to what mission creation variable is causing this for some online servers. Thanks

In initial testing, the deck crew and carrier model have very little impact on performance. The bigger impact can be the number of aircraft the mission create places on the deck. Even with a crowded deck, I've never had a "slideshow". Thanks

It would be quite silly to copy and paste the JF-15 AG radar as it operates quite differently than that of the Hornet. However, the JF-17 uses the AG radar API we created, so it will look quite similar. Thanks

I don't think putting targeting pod work on hold so we can push on AG radar would go over well... to say the least. Again, we need to focus on priorities, and the targeting pod improvements are critical. Thanks

Actually, if you go back and review past newsletters, that is exactly what we did. Thanks

Thanks for the report, but it's working okay here. A track file showing the error for you would be helpful. Thanks

It is a "must" to be addressed for the project release. Thanks

We originally had a Supercarrier project with a much narrower feature scope. We decided to put in the extra time and money to create something special. The deck crew and full carrier comms were greatly expanded. Thanks

Hi, Based on client feedback many, many more are looking forward to further AA radar and TGP development. Also, for aircraft like the Viper and Hornet, the AG radar has very limited utility these days. Most of the AG sensor work is done with the pod now. Thanks

Hi Cinatra, The strategy is simply based on priorities. The current Viper and Hornet priorities are the AA radar and TGP. AG radar is lower priority. We'll get to it though. Thanks

Colt 11 and Colt 12 are the donors that were telling you of those contacts. Thanks

Colt 11 and Colt 12 as the donors for a contact on the FCR. Thanks

In our march to added TWS on 18 December for the Hornet, we've now added SCAN RAID and EXP (Expand) sub-modes to TWS. Expand (EXP). When there is an L&S target in TWS mode and EXP is pressed, the display will change to a 10 nm range with a 20-degree azimuth scan. The display range on the right side of the display will indicate the 10 nm scan area (for example: 30 at the top and 20 at the bottom). Despite the 20-degree azimuth scan, the legend will still indicate the previous setting and the b-sweep line will not freeze on the L&S. This mode simply zooms in on that area, but the TWS scan operation, target rankings, etc. does not change. Filed tracks that are outside of the display will be on the edge of the display and flash. SCAN RAID Mode. This is selected from the SCAN RAID button on the throttle and it concentrates the TWS scan to a small area to break out closely spaced targets. When enabled, the scan is centered on the L&S target. It is displayed in a standard range and azimuth format in 10 nm zoomed in display at 22-degrees of azimuth, with a 2-bar elevation. The b-sweep line is frozen on the L&S target and SCAN RAID appears at the bottom of the display. When in this mode, track files and raw hits are displayed. If a new L&S target is designated, the RAID SCAN will move to that location. Filed tracks that are outside of the display will be on the edge of the display and flash. When selected, AUTO scan centering is automatically selected and cannot be unselected while in this mode. --- We will continue de-bugging these and TWS as a whole, and we still need to add L&S HUD indications when in TWS. Thanks

I should have been more clear. The brakes were set by the available charts and then the SMEs confirmed that all looked fine. We try to double check such matters. Thanks

I’ve had a couple F-16 pilots take a look at this for me and both indicted it was fine. Thanks

10 nm is an average range and the range and lock times have been adjusted for the next update. Thanks