gyrovague

Not sure why this would be, the AGM-84 has the same RCS in DCS as the AGM-86 as far as I can see, 0.1691.

The green isn't a filter, it's the natural CRT display colour. The red IRL is a physical frame with translucent red material which attaches over the VDI. The 3D modelling for this is not implemented yet, so you don't see the frame when clicking the VDI, only the red effect, but you can see where the frame would clip in if you look carefully. It might not be that that unrealistic for the reflection glare to be red in this case... I don't think we have much control over that in the engine either way though.

Thanks for the report, fixed the mak79 on rear right station.

I think you're describing the 1:4 pitch compression in HUD A/A and cruise modes, but this has been like that for a very long time (years before initial EA release). Your post makes it sound like a new issue ("with the latest update") though? I tested it in-game now with 29167, it seems fine to me.

This should work already, check axis bindings for RIO.

Thanks all for the submissions! We've implemented the following low-hanging fruit items now, but they will only be in the ED build in the neeeext openbeta cycle, not today's release unfortunately. Fix pilot ICS hot/cold/override keybinds. Fix sticky master caution keybind. Add some community-supplied keybinds for: throttle mode, oxygen, emer wing sweep cover, eng/probe anti ice, asymm thrust limiter, hydraulic transfer pump, fuel feed, anti skid. We'll check the top post in this thread from time to time, and systematically start adding items from that list.

OK. I can't reproduce locally, and that code hasn't been changed since well before initial release.

Actually... > On a hot start, the counter will read 676 so there must be a way to set it exactly. I can't reproduce this, it shows 670 for me... plus the 3rd digit anim arg isn't even in the code anymore.... So I'm not sure now what to do about this?

Ah, the last digit being there on hot start is a slight bug, will fix. We used to have it showing all 3 digits, then SME feedback was that the last digit was fixed 0 and the counter could only be adjusted in tens. We changed it thusly, but evidently forgot the hot start setting.

Fixed

Done

Thanks for the report, filed bug reports for this internally now.

We do have a potential fix uploaded to ED, but they are resolving some other issue on their end and latest info we have it seems they won't issue a hotfix patch until next week some time unfortunately. If they do issue a hotfix sooner, it should contain our fixes too. In the meantime, to just avoid the crash at least, you can either delete the file named 3.lua in Mods/aircraft/F14/Cockpit/KNEEBOARD/pages directory, or edit that file and comment out (by prepending with double-dash, i.e. --) the line starting with TDS_Str.controllers (should be line 52, two lines before the end of the file).

f4l0 has already added F-14 support to SSA ;) (I have a jetseat, and interacted with him about this)

Thanks for the report, will fix in due course. These are non-functional in DCS anyway.

:O never seen this before!

Thanks, known art issue, tracked internally.

Nice milestone! People with jetseat will be pleased to have support for F-14 from launch day! :thumbup:

The DDD is closer to a raw radar display, with some additional symbology. The TID is purely processed targets only, and can only show targets in P-STT, PD-STT, RWS and TWS (not P-SEARCH or PD-SEARCH). Both have their uses, and DDD is quite useful in pulse search for rudimentary ground mapping, navigation fixes and finding carrier group at sea for instance. See here for some details:

By coincidence, one of our SMEs told us about the external lights for night catapult a few weeks ago. Interestingly though, he said the cat would activate "a fraction of a second later", maybe it depends on how alert the shooter is or something, or maybe the SME misremembered it.

No, not involved actively in A-4E anymore, due to lack of time and being "tainted" by the ED NDA since I'm working with Heatblur on the F-14. I'm sure somebody (you? :) ) will fix it though. Oh, interesting! I wouldn't mind getting a copy of that (or link to it), just for posterity at least. I just remember at the time I couldn't get docs on it, and had to figure it out just from the switch labels, sounds like I made some serious mistakes. I haven't checked in-game yet, but sounds odd that I wouldn't have understood that ripple should release multiple based on the intervalometer and count.

Yeah, you're right, should be an easy fix. I suspect I misunderstood how it's supposed to work at the time I implemented it, we didn't have any docs on that IIRC. Similarly, I think pairs isn't implemented correctly either. Hmm yes, I see. Should be easy to fix too, just need to check for state change of get_elec_mon_arms_dc_ok() in update() and then call check_sidewinder again.

What are the bug symptoms?

That might affect the AFCS PID controllers, since they use trim to perform the autopilot functions. Would need to be tested.

\o/ woohoo! Congrats!