F-14

Benutzeravatar
I/JG27_Zimmi
OLt.
OLt.
Beiträge: 1135
Registriert: Sa 05 Sep 2015, 09:30

Re: F-14

Beitrag von I/JG27_Zimmi » Di 05 Sep 2017, 05:54

OLt. Zimmermann
Gruppenkommandeur

Benutzeravatar
I/JG27_Zimmi
OLt.
OLt.
Beiträge: 1135
Registriert: Sa 05 Sep 2015, 09:30

Re: F-14

Beitrag von I/JG27_Zimmi » Di 12 Sep 2017, 13:59

One of the most difficult parts of developing the F-14 is developing your AI RIO companion- JESTER AI. For Jester, we want to make sure that the AI feels as lifelike as possible.
We have begun work on the AI’s “Human” behaviour model, which will simulate the RIOs current task, visual focus and detection abilities.
JESTER will move his head to look at exactly where the switch/indicator being manipulated or used is in the cockpit, and thus will not be able to scan the sky at the same time. Thus the RIO will have significant difficulties with visual detection when under heavy radar workload, as his head is buried in the DDD and TID screens.
The RIO has a focused viewing cone of roughly 30 degrees, and a peripheral vision field of roughly 100-130 degrees. Inside the focused viewing cone, the RIO will more quickly detect targets, while detection range and speed is significantly reduced in the peripheral vision. We also account for the sun, the horizon and line of sight (JESTER will not see through mountains or clouds). Thus, the RIO might even notice contacts in his peripheral vision while manipulating radar controls, but at a much lower chance than if actively scanning the sky, and thus using his focused viewing field.
Making sure that the RIO is bound by realistic human limitations is in the very foundation of our work, and it is important not only for immersion, but also to maintain appropriate multiplayer balance.
Below are three screenshots showing the system in action!
In the first image; Jester is looking straight ahead and has seen both the Carrier and the aircraft in the distance (yellow markers denote detected units).
In the second, he is looking down into the cockpit and manipulating one of the backseat controls.
In the third, he's looking at the locked targets, the dropped flares and has also seen one of the fired missiles. Note that the second missiles has not yet been seen by the RIO.
OLt. Zimmermann
Gruppenkommandeur

Benutzeravatar
I/JG27_Zimmi
OLt.
OLt.
Beiträge: 1135
Registriert: Sa 05 Sep 2015, 09:30

Re: F-14

Beitrag von I/JG27_Zimmi » Mi 04 Okt 2017, 10:07

Der Freudenknüppel
Dateianhänge
22180091_783101311877489_8408649502322926864_o.jpg
22137096_783101315210822_5103815635663112270_o.jpg
OLt. Zimmermann
Gruppenkommandeur

Benutzeravatar
I/JG27_Zimmi
OLt.
OLt.
Beiträge: 1135
Registriert: Sa 05 Sep 2015, 09:30

Re: F-14

Beitrag von I/JG27_Zimmi » So 08 Okt 2017, 06:09

i Everyone!

We’ve just returned from our second research trip of this year to the U.S!
The first trip of this year was conducted by the art team back in april to collect boring, totally unexciting visual reference stuff.

The main goal of this trip was for the engineering and research team to meet with SMEs and give them a hands on session with our F-14.
Most important to us was to receive detailed in-person feedback on our Flight Modeling, and to then apply that feedback to our F-14.
We were also eager to discuss various systems and aircraft functionality, as well as things like crew communication for JESTER and carrier operations.

After a long and tiring flight from Stockholm to Oakland, we went through the usual routine of collecting our luggage, passing through immigration and getting our rental vehicle.
The moment we turn the key in the ignition, "You’ve lost that lovin’ feelin’" starts blaring through the radio.
We’re now about one overtime induced hallucination away from believing that developing the Tomcat is a divine mission.
No one will expect the Tomcat inquisition.

The next day, it was down to business. We met our subject matter expert, an experienced US Navy Commander and F-14 / F/A-18 aviator.
We hooked him up to a high performance VR-rig in order to have him evaluate our Tomcat and the game was on!

His overall impression of the simulation model was great, and he was able to provide very detailed and absolutely invaluable feedback regarding parts of the flight envelope or controls that need further improvement.
Having brought our development machines with us, we could immediately implement some of these changes and get immediate feedback on them.
Some of these include changing the thrust moment arm, adjusting and tweaking the ground effect and control surface actuator speeds.

Look at that amazing 'stache!

Now that we’ve returned home, our goal is to fully incorporate the feedback into our model, and within the coming weeks set up further remote testing sessions.
We’ve already spent some time tuning the AFCS which was a point of much feedback, which should alleviate some unwanted roll and pitch oscillations. We’ve also adjusted longitudinal stick pitch damping at high G’s.

Through these evolutionary changes, we are able to finely tune and polish our flight model.

We are already immensely proud of the F-14 FM, and as the foundation of the entire DCS: F-14A & B product, we hope its’ accuracy will permeate throughout the entire module.
We wouldn’t be able to get as close as we are without the fantastic contributions by all of our SME Pilots and RIO’s.

On a personal level, the most amazing part of the testing sessions was to watch him ace the carrier landings again and again (which even our own testing team is not able to do consistently) - something we believe speaks volumes about his skill as an aviator and our FM!

Here’s one of those landings. Smooth as silk!

https://www.youtube.com/watch?time_cont ... SrFSv2H60Y

Being able to discuss all things related to Tomcat also gives us some added perspective on the project as a whole as well as assisting us in the creation of JESTER, our two Campaigns (-A and -B) and just satisfying our nerdy needs in general. We're obviously all huge Tomcat fans and this was a great opportunity to delve into less technical details.

We then spent some time running intercepts as a two person crew (we had a second machine and Rift with us) - with one of our team members operating the Radar. Flying DCS: F-14 as a two man crew is simply one of the most enjoyable flight simulation experiences one can have, and doing so with a real F-14 pilot up front was the cherry on top.

I was inverted...
That’s it for this trip!

The entire team is hard at work at bringing you the best F-14 experience we can possibly craft, and we’re looking forward to the early access release and the F-14 roadmap beyond.

There’s still plenty of work to be done, and we’ll keep you updated on our schedule and progress.
Thanks so much for reading, and stay tuned for more updates.

We'd also like to sincerely thank all of our SMEs, both pilots and RIOs (you all know who you are!) and museums and associations that we have been working with for their amazing help and all of the contributions that they have made to DCS: F-14 so far. Thank you!

Sincerely,
OLt. Zimmermann
Gruppenkommandeur

Benutzeravatar
I/JG27_Zimmi
OLt.
OLt.
Beiträge: 1135
Registriert: Sa 05 Sep 2015, 09:30

Re: F-14

Beitrag von I/JG27_Zimmi » Mo 20 Nov 2017, 06:57

Pit_01.jpg
Pit_06.jpg
Scan, Lock, Fire!
Heatblur F-14 Radar & Weapons Development Update


Dear All,

The entire Heatblur team is very hard at work on both the F-14, Viggen and other new projects. While we’ve tried to keep you up to date with smaller updates over the past few months; now may be a good time to give you a better overview of some of the systems development on the F-14!

Much of the focus currently lies with high level, core elements of the F-14 that made it such a valuable replacement for many aircraft in the Navy and probably the most formidable and diverse fighter aircraft of its time. Much effort is currently being spent on our recreation of the Hughes Airborne Weapons Group 9 (or AWG-9), it’s various modes of operation and weapons, as well as continuing the development on JESTER AI, our AI RIO pilot companion!


The AWG-9, heart of the F-14 Tomcat
Typical_Radar.jpg
Typical_Radar.jpg (170.84 KiB) 10 mal betrachtet
“The AWG-9 is made up of a radar, computer, interface between AWG-9 and weapons and the associated displays” James Perry Stevenson writes in the Aero Series 25 book “Grumman F-14 Tomcat”. He says further: “The primary purpose of the F-14 is to act as a weapons platform. To that end, then, the primary purpose of the AWG-9 is to control the four weapons it carries – the gun, the Sidewinder missile (AIM-9), the Sparrow missile (AIM-7) and the Phoenix missile (AIM-54). The AWG-9 weapon control system uses inputs from the radar and in conjunction with the computer, establishes target identities, establishes priorities, processes data for intercept geometry, establishes launch envelopes and monitors some of the F-14’s other black boxes.”

What really set the AWG-9 apart for its time was the many functions it offered to both Pilot and RIO that no other aircraft had at that time. The AWG-9 radar can use both Pulse Radar and Pulse Doppler modes with six basic modes, which in its time made it absolutely second to none. These six main modes are:
PDS: Pulse Doppler Search,
RWS: Range While Scan,
TWS: Track While Scan,
PDSTT: Pulse Doppler Single Target Track,
PS: Pulse Search,
PSTT: Pulse Single Target Track.
The AWG-9 also offers some ACM modes that would allow the crew to quickly lock onto a target in a high G, maneuvering fight, including:
PLM: Pilot Lockon Mode (the pilot could lock on a target directly ahead of him),
VSL: Vertical Scan Lockon (A vertical beam ahead high between +15° and +55° or ahead low between -15° and + 25° elevation and 4.8° azimuth from the aircraft datum line)
MRL: Manual Rapid Lockon (Also called NRL or NFO Rapid Lockon) - which would give the RIO the possibility to manually steer the radar with his Hand Control Unit (or “HCU”) towards a visual target and lock it. This mode was rarely used.
In addition the F-14 had a separate antenna for AIM-7 Flood Mode, which could be used in a situation when the radar would fail- alas this was considered fairly useless. (It has been described by our SMEs as a “Holy-shit-bad-idea-mode”, and pilots weren’t scored a kill during training if they used this mode).

All of these radar modes have now been implemented and their functionality improved over the past few months. To some extent, JESTER AI is now able to operate some of these modes as well. Modeling the AWG-9 in great detail will make the experience of being an F-14 RIO great fun and challenging- as well as accurately representing the real world effectiveness of the F-14.

All 4 air to air weapons of the F-14, both provided by ED (AIM-9M, AIM-9P and AIM-7M) and Heatblur (AIM-54A-Mk47, AIM-54A-Mk60 and AIM-54C-Mk47), as well as the M61 Vulcan Cannon, are currently implemented and available. These weapons constitute the core of the early F-14 experience.

Sidewinder capability in the F-14 is fairly standard if you’re familiar with other western aircraft. The sidewinders support active cooling (must be activated on ACM panel to get a tone) and the SEAM (Sidewinder Expanded Acquisition Mode) function. In SEAM slave mode, the Sidewinder’s seeker head is slaved to the target that is locked with either the radar or TCS (Television Camera System) and starts tracking the target before the missile comes off the rail. The seeker can be commanded to SEAM lock by a pilot HOTAS button. The aircraft can carry a total of 4 Sidewinder missiles on 4 separate wing stations.
TCS.jpg
One of the most unique features of the F-14 is the optical sensor known as the Television Camera System. Apart from the ability to track and lock a target with the Radar, the F-14 provides the ability to observe camera footage of targets through the TCS. Acquisition of targets for visual identification on the TCS is super easy. You can slave the TCS to your currently locked radar target, or vice-versa if you’ve acquired a target using only your TCS.

The RIO’s main displays for the interpretation of data delivered by the AWG-9 are the Detail Data Display (or “DDD”) and the Tactical Information Display (or “TID”). While we’ll go through these displays in more detail in upcoming updates, videos and the manual - one can simplify the distinction and note that the DDD is akin to a raw radar scope display, while the TID is a computer processed overview of that same data. Thus, a skilled operator will have to be proficient in using both the DDD and TID displays to achieve maximum efficacy.


A typical TID display repeated on the Pilots HSI (placeholder cockpit!)

The pilot is also equipped with two displays, the Vertical Display Indicator (or “VDI”) and the Horizontal Situation Display (or “HSD”). The pilot can select what these two indicators should display. The HSD can, for example, display navigational data, ECM (RWR) data - or serve as a “repeater” for the RIOs TID display. Note though, that keeping an eye on TID data and flying effectively is a tough challenge! So a good pilot will know when to trust his RIO.

The VDI displays an artificially generated horizon, steering cues, navigational data or can also be switched to display TCS video footage. The VDI is sometimes also referred to as a “Heads DOWN Display”, since it can largely reproduce almost everything shown on the HUD.
repeater.jpg
repeater.jpg (132.44 KiB) 10 mal betrachtet
OLt. Zimmermann
Gruppenkommandeur

Benutzeravatar
I/JG27_Zimmi
OLt.
OLt.
Beiträge: 1135
Registriert: Sa 05 Sep 2015, 09:30

Re: F-14

Beitrag von I/JG27_Zimmi » Mo 20 Nov 2017, 07:00

The DDD (Detail Data Display) and TID (Tactical Information Display)

The DDD is really the lightning rod for all things AWG-9. A skilled RIO making great use of the DDD will make the F-14 an amazingly effective weapons platform. Being skillful in distinguishing single from multiple targets, picking out targets amongst ground and weather clutter and defeating defensive aircraft maneuvers is challenging. The F-14 radar controls allow the RIO to finely tune the radar and DDD display to really pick out targets with great precision (and in many cases, where other more automated radars of the era would fail!).
In all Pulse Doppler modes, the vertical axis on the DDD shows target blips on a range-rate (relative radial velocity) scale, which can be somewhat difficult to interpret.
DDD_Targets.jpg
A compiled example of AWG-9 Post-Processed Targets. Click to Enlarge!

The DDD also, due to its nature as a raw type radar display, means that it has rudimentary ground mapping radar capability!

We’ve further refined our ground radar technology which we created for the AJS-37 Viggen. While ground mapping is, perhaps, not as useful in an F-14 as in the Viggen- it can still be a helpful tool in bad weather, navigation and low light flight situations. The SMEs we’ve spoken to considered it to be an invaluable tool at times, especially in poor weather situations.
DDD_Compilation.jpg
A compiled example of AWG-9 Ground Mapping capability. Click to Enlarge!


As important as the DDD is, it is however only really half of the equation.

The TID is a large 9 inch circular display (sometimes aptly named the “Fishbowl”), and will show tracked targets (in RWS, TWS, STT modes) with velocity vectors (TWS and STT only).
Targets can be “hooked” on the TID using the HCU (Hand Control Unit, basically the RIO’s “Joystick”, and additional detailed info like range, bearing, heading, ground speed etc. can be called up on the display depending on selected settings and the current radar mode.
The TID can also show navigational data like waypoints, and marked ground positions relative to the aircraft, and is thus like a simple TAD system, but without a moving map.

The most complete track file of the target in the scanning modes will be given in TWS, which can track up to 24 targets simultaneously and fire up to 6 Phoenix missiles. In TWS the targets are not locked, as they are in the PSTT and PDSTT modes. Instead, the computer tracks them by taking their last seen position and predicting the new position of the target in 2 second update intervals. During these updates it tracks the target’s information and can calculate the heading vector, ground speed and other required parameters. This gives the F-14 the advantage that its opponents will not know that they are being tracked by its radar, as their RWR will not register a radar lock.
TID_Compilation.jpg
A compiled example of some AWG-9 TID Screens. Click to Enlarge!

The limitation of the TWS mode is that only the Phoenix missile can be fired with guidance, and though it provides the same detection range as RWS (around 90NM for fighter sized aircraft under ideal aspect conditions, where 1NM=1.852km), the field of view is tied to the 2 second update and thus limited to a 2 BAR 40° or 4 BAR 20° search.

TWS also has both manual and auto modes implemented, which means that the computer will prioritize targets automatically and suggest launch queues which the RIO can use to line up his targets. The TWS auto mode will also adjust the scan pattern by itself.

The biggest field of view is provided in RWS which can be set to a 10, 20, 40 or 65 degrees left and right search pattern from centerline in either 1, 2, 4 or 8 BAR search mode, with the biggest pattern using a full 13 seconds to update (but covering a truly massive volume of sky) and the smallest pattern updating in a quarter of a second. While PDS provides only range rate (and thus cannot display targets on the TID), RWS provides range and range rate. PDS and RWS can be used to launch missiles in boresight modes. PDSTT and PSTT provide launch modes for all missiles and the gun. PS however provides a smaller detection range and is useful against beaming or notching targets. This comes as a trade off though, as it is very poor at detecting targets in front of ground clutter.
PulseSearch.jpg
Non Post-Processed radar returns in Pulse Search modes differ greatly. Click to Enlarge!


The various radar modes also have somewhat differing parameters for range resolution, range rate resolution and angle resolution, depending on factors such as pulse length, pulse compression, pulse repetition frequency etc. This comes into play especially when trying to distinguish targets in close formations at longer ranges. We believe we have made a reasonable emulation of this within the confines of the DCS environment.

Datalink is a hefty development task for us, and we’ve made good progress on this particular feature of the AWG-9. Currently, the F-14 receives data linked targets from the E-2 Hawkeye, other F-14 Tomcats, and U.S. Carriers. Eventually, commands like WILCO, CANTCO and other small bits of information will be able to be shared among flights. Communication systems, such as the Datalink, of course adhere to the laws of physics and both occlusion and range play a part in whether datalinked targets will be transmitted. Another aspect of Datalink that is already included is the Automated Carrier Landing (“ACL”), which is one of the examples how the AWG-9 can also provide navigational functions.

We hope that this general overview of what parts we have already implemented of the powerful AWG-9 is giving you an idea of the many possibilities the F-14 will provide for you both in the Pilot and RIO role. Fighting in the F-14, be it BVR, WVR or BFM is already a very fun, dynamic and challenging experience. We’ve barely scratched the surface in this post when it comes to the full gamut of features available in the AWG-9, DDD and TID!
The complexities and depth of so many modes of operation and available inputs and output details are best left to future updates and the accompanying documentation.

Which in the end brings us to the question: how are we going to use all of that without a RIO in the back seat?

The answer is of course Jester-AI, and this is probably a good moment to go through the latest on your AI companion!
OLt. Zimmermann
Gruppenkommandeur

Benutzeravatar
I/JG27_Zimmi
OLt.
OLt.
Beiträge: 1135
Registriert: Sa 05 Sep 2015, 09:30

Re: F-14

Beitrag von I/JG27_Zimmi » Mo 20 Nov 2017, 07:01

The Jester-AI – your very own RIO

For those of you not aware yet (are there any of you out there? ) JESTER AI, is our proprietary AI, designed specifically for multicrew aircraft. Our goal with Jester is to make him (or.. it? Is that mean to JESTER?) both feel alive, adaptive and flexible, but also realistic in terms of the limitations and capabilities a real RIO would have. Jester will not make it easier for you than any real human experienced RIO would in Multi Crew, and we've already spent a lot of development time and resources to model things like a rudimentary human component model, which accurate models where the RIO is looking, what switches he is manipulating and more.

The ultimate goal and plan is to make Jester capable enough that you won’t have to jump into the back seat at all, as long as you don’t want to do something very specific.

A lot of effort has been put into making the underlying framework for Jester is as capable as possible. This allows us to create complex behavioral trees that dictate Jester’s behavioural patterns and actions in many different situations that might arise due to internal cockpit events (e.g. RWR spiking, fuel reaching bingo state), player interaction (e.g. telling Jester to lock onto the closest enemy), or external events (e.g. Jester having visual on a bogey or noticing a missile launch).

At this time, we’ve recorded well over 2.000+ different voice files, ranging from single numbers, to entire phrases. A big challenge for us has been the creation of a voice library and voice synthesis system which will allow for more naturally generated procedural statements. In our early design discussions, we decided to opt for a combined approach of sentence building, as well as having many complete phrases and sentences. In this way, we’re able to combine the flexibility of a fully dynamic system with the authenticity of entire phrases.

The entire Heatblur team would like to thank Grayson Frohberg for putting his amazing voice to great use, and putting in a monumental effort in recording thousands of voice lines. You’ll all be grow to be very familiar with Grayson’s beautiful timbre a few weeks into flying the F-14.

We expect that Jester’s list of capabilities will be somewhat limited at early access launch, but by having focused on the main underlying structure and behaviour trees, we are now able to rapidly grow its’ functionality. The last couple of weeks we’ve focused on adding BVR capabilities and in the near future we will switch over to WVR, start and landing procedures, as well as navigation. Here’s a sample of what JESTER is already capable of:
  • Using TCS and Radar STT modes
  • Spot and IFF bogeys both by radar and TCS, including making BRAA calls
  • The ability to spot and call out incoming missiles detected by RWR
  • The ability to react to RWR detected threats, both surface- and airborne, as well as their type and direction
  • He visually detects missile launches and calls them out (when in his field of view)
  • You can order him through a command dial to look into a certain direction
  • You can order him to lock differently prioritized targets, lock the closest or next bandit, lock the next target ahead, launch the next missile, break the STT lock and much more.
  • He will identify the target type via TCS in BVR
  • He will advise you to break if he spots the missile very close (and in time of course)
  • If spotted properly and in time he will advise you the direction to break
  • He will call out SAM launches and threats both visually and in RWR
  • He is able to call out groups of targets
  • He provides the player with an action system that works like a radial command that can be bound to both HOTAS and Keyboard.
  • The command radial menu allows the player to easily navigate through the command menus and submenus in a very short time.
The commands build on each other logically, so that the player has a quick and easy overview and does not lose much thought navigating the commands.
In time we will also add more modalities for Jester that will give the Player a deeper impression of having a “living RIO” in the back seat with a great range of possibilities for the Pilot to interact with the AI.


That’s about all we have for this update! We've dropped some sneak peeks at what the art team has been hard at work on in this post,
and it's likely the next update will focus just on that. Stay tuned! We're super excited.

As mentioned in various community outlets recently; we’re also hoping to do a “Road to Release” type update soon, where we can better update you on the state of the F-14, our current projections for release and what is left to do until we consider the aircraft to be feature complete for Early Access.

We say this a lot; but the F-14 has been a massive undertaking for us, and the amount of time and effort spent on recreating this aircraft will hopefully be readily apparent throughout early access and into release. Thank you for staying so patient and all of your support!

Sincerely,
Heatblur Simulations
Dateianhänge
Pit_03.jpg
Pit_05.jpg
OLt. Zimmermann
Gruppenkommandeur

Benutzeravatar
I/JG27_Zimmi
OLt.
OLt.
Beiträge: 1135
Registriert: Sa 05 Sep 2015, 09:30

Re: F-14

Beitrag von I/JG27_Zimmi » Di 21 Nov 2017, 06:53

OLt. Zimmermann
Gruppenkommandeur

Antworten

Wer ist online?

Mitglieder in diesem Forum: 0 Mitglieder