key_stroked

I've checked both the HB manual and NATOPS, and I still don't fully understand some of these items. STEER CMD For the pilot, I understand the difference between TACAN and DEST steering modes. I also know that AWL/PCD will give you ILS bars, but what about the PCD part? The HB manual says: I've tried using AWL/PCD while bombing (in both CCIP and CCRP modes), and I don't see any extra info on the HSD or any other display. What is the VEC mode specifically used for? And is the MAN mode just an extra mode where you can set your own course and heading carrots? ILS/ACL I know that ACL is automatic carrier landing, and it shows you the ICLS bars when in range of the ship, but ILS seems to also show the bars. I had my HUD AWL switch set to ACL, and my VDI AWL switch set to ILS, and both were showing the same bars on approach to the boat. What's supposed to be the difference between the two?

I just explained how you can add that input above. While not realistic, neither is a RIO like Jester with limited commands. Adding your own functionality lets you expand the scope of what you can do while flying solo.

Can confirm, the knobs won't move unless you're in TACAN mode for the HSD.

You can add the following block of code to DCS/Mods/aircraft/F14/input/F-14B-Pilot/keyboard/default.lua and assign it to whatever you want from the front seat. -- TID {down = device_commands.TID_range_knob, cockpit_device_id=devices.TID, value_down = -1.0, name = _('TID range: 25'), category = _('TID')}, {down = device_commands.TID_range_knob, cockpit_device_id=devices.TID, value_down = -0.5, name = _('TID range: 50'), category = _('TID')}, {down = device_commands.TID_range_knob, cockpit_device_id=devices.TID, value_down = 0.0, name = _('TID range: 100'), category = _('TID')}, {down = device_commands.TID_range_knob, cockpit_device_id=devices.TID, value_down = 0.5, name = _('TID range: 200'), category = _('TID')}, {down = device_commands.TID_range_knob, cockpit_device_id=devices.TID, value_down = 1.0, name = _('TID range: 400'), category = _('TID')}, You can also do this with any of the code from the RIO default.lua. This is how people are able to control the LANTIRN from the pilot seat, as well as things like radar range and changing the TCS FOV. Just keep in mind that Jester will often change the range knob after you try to manipulate it, and every time ED patches DCS you have to copy over the code again.

I have a blank audio .wav file that I use to replace sound files I don't want to hear in various programs. I uploaded it here -- http://s000.tinyupload.com/index.php?file_id=88269579683830737802 Just make copies of it and rename each copy with the file name you want to "blank" out, then overwrite those files. I would keep a separate backup set so you can quickly copy over the blank files every time they patch.

Yes please. His starting volume is way too loud.

I usually look at my fuel flow gauge and whatever number the bar is on is how much fuel I'll burn in 30 min. There are max conserve tables out there somewhere, but you can get pretty efficient with your fuel burn. I'm typically around 4-5,000 lbs FF at the cruise speeds I keep, so I know that whatever groundspeed I'm at divided by 2 is how many miles I can go with roughly 5,000 lbs of fuel. I also generally want to keep at least 1,500 (that's just my number) lbs of fuel for go arounds or a divert if necessary. I know from experience the jet will flameout at about 300 lbs of fuel left. There's a little in the tank that doesn't get used. Edit: According to real F-14 drivers and RIOs from the Fighter Pilot Podcast, max endurance was around 220 knots which gave you roughly 2,000 lbs/hr per engine. Unknown if Heatblur modeled it similarly. You can listen to the bit about fuel and endurance starting at 13:05 -->

I kind of agree that Jester doesn't sound like he's talking to you over IVC from his helmet. It really does sound like he's in the room next to you instead of over a mic. Fortunately Audacity has filters to make it sound more AM. If Heatblur keeps the audio files as is, I plan on keeping my own set of modified files that I can copy over after every patch.

The ship's BRC (course) should be put in HSD, not the runway angle. You want to know the direction the ship is moving so you can keep a decent profile when landing case 1 or case 3. That's assuming you want to fly boat ops as they do it for real. If you don't care about that, then just take the ship's course from the F10 map and subtract 10 degrees from it.

I've gotten locked, constantly, while sitting in a hardened aircraft shelter on multiple online servers. So you're saying that I'm somehow always perfectly in line with dog fights happening over 100nm away, and that buildings and terrain don't matter? I don't think so. I strongly believe it's a bug.

Fyi, you can copy any command from the keyboard or joystick default.lua files in the Input folder to the Pilot's default.lua file, and thus give the pilot position the ability to map those RIO functions to your keyboard or HOTAS. Basically you can control anything from the RIO pit you want while in the pilot seat, with the disadvantage of not seeing the actual switches/buttons. Also note that every patch will reset these default.lua files, so you have to keep backups and constantly update these files after every patch.

That's the most accurate description of interacting with Jester I've seen so far! :D Technically PAL is usable at 15 miles, which is significant because if you lose lock on a target at 20 miles and you're switching radar modes, that target can potentially launch on you with a medium range missile, like the AIM-120.

On one hand, it's an early access product, and one can assume that some things are missing. That said, how can people who paid for early access give proper feedback on functionality of certain systems (i.e. Jester) without knowing how everything works? If you release Jester with a "spot" command, then you should put something in the manual that says what spot is actually supposed to do, so we can properly bug report it if it's not working as advertised. Isn't that the point of early access? Introducing your product to a broad audience to increase the chances of bugs being caught? Hard to do that when we don't even know what's normal and what's not.

Anyone have a link for those that don't know what you're talking about?

Ask that person if they're sitting in a real jet.

Searched if this was already reported for World 2.5 bugs, and it's not from what I can see, so here it is. Originally this was reported on the F-14 bug forum, but their dev team said it was an ED issue and affected all aircraft.

https://forums.eagle.ru/attachment.php?attachmentid=207413&stc=1&d=1553680552 https://forums.eagle.ru/attachment.php?attachmentid=207414&stc=1&d=1553680552

You can already see them. Just look left at any of the cats. Two red hash marks painted on the white edging.

Where did I shout down anything? Quote it for me. I gave my own opinion. Sounds like you're trying to suppress mine! :)

There are already red markers painted on the edge of the deck. You're supposed to line them up with your shoulder to know you're in the right spot to attach to the catapult.

No one from ED responded to the original thread in General -> https://forums.eagle.ru/showthread.php?t=236724 ...so I'm posting it here. Maybe it can get tagged and looked at?

You'll die before you please everyone. The sounds are fantastic, and from what I've heard and read the majority of your customers think the same.

I disagree with the OP. I think the sounds are great.

So am I supposed to submit a bug report for the bug reporting tool not launching?

It was bothersome before the 3/22 patch, but now it's on another level of pure frustration. For me, just flying the simple 1v1 instant mission against the Mig 21 in the Persian Gulf results in freezes every 5 seconds or so while dogfighting. Whatever performance issues are going on with the F-14 are making this module simply unplayable. It's bad.