mattag08

When hot or cold starting in SP or MP I have issues with either: 1) Hooking up to the catapult at all. 2) Getting the catapult to launch once I am connected. #1 seems to be random depending on the exact starting conditions of the mission. #2 is reproducible 90% of the time, though I found one instance where if you air start it will allow you one catapult shot, but the second time you trap and attempt at cat shot, you cannot. Before I get the slew of "you just don't know how to do it right." I've done hundreds if not thousands of catapult launches in the F-14 since launch. Myself as well as all of my F-14 squadron mates are having this same issue. I'm also aware of similar catapult problems for the F-18, so I assume this is a DCS level bug, but I wanted to make sure HB was aware in case there were fixes needed on their end.

Thank you so much for fixing this HB. It is much appreciated!

The new implementation of the Jester radar is awesome, but it makes the other system basically useless. Can we please get a change so Jester's High, Middle High, Middle, etc. are more useful? There are times where you want to adjust the radar elevation by degrees and not strictly by distance/altitude. If the feature was changed to have Jester adjust the elevation by smaller degree increments that would be awesome. Currently having each increment move the radar 16 degrees simply is too excessive and not useful in any realistic scenario. Also there needs to be overlap so that switch from one mode to the next does not leave holes in your sanitization plan.

The F/A-18C SA page generally lists a 4 character call sign for friendly flights (i.e. "CT11" for Colt 1-1). I made a mission to figure out what each call sign translates to on the SA page, but the SA page is not showing the call signs for some reason. D/L is working on my F-18 and I included an AWACS for good measure. All AI F-18s have "EPLRS(on) -a" advanced waypoint actions. What are the conditions required for a flight to show the call sign on SA?

This seems to be very close to what I'm looking for. Thanks for the help!

Tower doesn't give you QNH IRL. You're expected to listen to the ATIS and get it for yourself.

Some Jester functions are multiple menus deep. If you choose the wrong menu you cannot go back and must start over from the beginning. The ability to back up one step would save a lot of time and effort. Biggest example is with radio inputs which can often be 5+ menus deep.

This has been a bug for quite awhile. Jester will swap from AM to FM modulation for no apparent reason. Needs to be fixed HB.

Bumping for an answer from HB

The manual states the HDG knob on the compass control panel is, "Used in DG and SLAVED modes. In SLAVED mode it’s used to sync the directional gyro with the magnetic azimuth detector and set magnetic heading on the BDHI. Button should be held until the syncronization indicator needle is over the null mark. In DG mode the button is depressed and rotated to select desired heading on the BDHI. The button can also be used to fast erect pitch and roll of the AHRS by depressing the button for up to 3 minutes. A new fast erect attempt can be done if a 1 minute wait is first observed." This behavior does not work. Placing the compass mode in SLAVED or DG and left or right clicking and dragging the mouse does not adjust the BDHI. Rotating the mouse wheel also does not work. Also the compass still doesn't have a lubber line...

Bumping for visibility.

Because DLC makes carrier landings much easier IRL.

This. The F-14 lacks a large number of bindings for seemingly no reason other than HB won't make it a priority. Why do we STILL not have axes and buttons for things like CRS/HDG knobs? Jester needs these binds desperately: -STT closest enemy -STT closest target -TWS next track -Set radar elevation 0° -Move radar elevation down 1° -Move radar elevation up 1° -Move radar elevation down 5° -Move radar elevation up 5° -Set Pilot Flare switch to Pilot -Set Pilot Flare switch to Multi Also Jester's functionality for adjusting elevation low/low-middle/middle/middle-high/high is the most ridiculous thing I think I've seen. It's like HB have never done an actual intercept. There is no reason that the normal operation is to move the radar 16 degrees up or down completely skipping whole segments of the sky in the process. During an intercept the maximum typical adjustment to the radar is approximately 5°. The elevation movement should be: Low = -10° Low-Middle = -5 Middle = 0 Middle-High = +5 High = +10 We STILL need the ability to adjust the elevation in 1° increments. 1° equates to 10,000' at 100NM. In what world do we need 16° adjustments?

There's a reason why DLC is a requested item for new naval aircraft.

Since the TID has no indication of the radar gimbal limts, you should reference your heading before the crank and just turn 55-60 degrees of heading change as opposed to trying to use the TID for cranks. Make sure to begin rolling out at about 45 degrees because you will continue to turn until the wings are completely level. I just tested it again and had no issues. You can reference the MB (Magnetic Bearing) which is the bandit's bearing relative to your nose as well and keep it between 300-60.

You didn't understand what Victory said and you didn't watch your own video carefully. The Tomcats do exactly what Victory said both in the video and in game. The current setup in game is fine even if we don't get the aft stick movement due to the bob weights.

A scenario with an F-14B and a JF-17 isn't realistic to begin with, so who cares if the RWR library is updated? If you don't like that, just don't put those two aircraft in missions together. For those of us that participate in PvP on servers that allow any module, this is vital and would be perfectly reasonable that the RWR library would be updated on the real jet if it was still in service.

Ah, interesting. I've never used the assisted start in all this time.

Can someone explain what this does? I've seen it, but never really understood what it is telling Jester to do. When I use it nothing happens.

The compass doesn't have a lubber line. It should unless we are saying that it rubbed off or wore away. Generally (at least in the civilian world) one of the aircraft instrument maintenance items is to make sure the lubber line is visible and to repaint it if it is not. Technically an aircraft isn't VFR certified if it doesn't have a working compass, which includes a lubber line for reference. Our F-14B is currently not airworthy technically. :P

Nah, these aren't radar tracks though. They are datalink position locations which isn't the same. Back in the day I could see basically everyone on the server, which was approximately 30 people and all of their missiles. I know it's different because I used this to very good effect to maneuver vs. the enemy at ranges in excess of 100 NM.

I'm having the same issue except mine is showing it bind the same axis on the same device twice. The only current work around I've found is to click on that box and hit "Default" which allows it to work again until DCS is restarted. See attached image. I've tried uninstalling and reinstalling the module to no avail.

That's not what AC stab and ground stab means though. It's just the point that the TID is locked to. So A/C stab = your aircraft doesn't move on the TID. Ground stab = your aircraft moves on the TID.

Perhaps something changed I'm not aware of, if so please advise. I have been flying the F-14 since launch and playing with it on multiplayer PvE and PvP servers. Yesterday I encountered something I have not seen to date, a complete lack of datalink contacts on the TID. I believe only approximately 8 were shown. Up until the last few weeks I'm sure that I've seen dozens of datalink contacts on the TID. I know there was a recent update to some of the TID functionality, so did the number of allowed datalink contacts change or is this a bug? Is there a realistic limit? If so, does it preference the closest contacts? Does it preference enemies over friendlies? My issue was that after taking off, every datalink contact around me was friendly (about 8 total) as I got close to where the actual air battles were taking place enemies started to appear as they got close and the friendlies disappeared if they were further away. All the friendlies, enemies, and myself were in LOS and range (<100 NM) to the AWACS (an E3). It seemed that the enemies only appeared because there were less than 8 friendlies around me. This seems very counter-intuitive as you would want the D/L to preference enemies over friendlies generally. The server I was on was heavily populated (60+ people), so I don't know if that played a factor. Unfortunately this has made the datalink quite unusable and stripped the tomcat of one of its main advantages over older and less well equipped aircraft.

Is there anywhere where ED has said if the new carrier will have a proper wake? For instance, https://www.youtube.com/watch?v=RBntiTDu7rU&t=18m17s You can see how dramatically different a real carrier wake is from the DCS carrier currently. This is important because it is used as a reference during the turn to the groove. It's also one of the ways to find and identify the carrier visually.