Brinkyeti

+1 ED pls fix edit, also: you may want to update https://gitlab.com/overlord-bot/srs-bot/-/issues/15 to reflect this:

+1 also would like to be able to toggle the MLC filter between auto and off.

First things first: thanks for your (absolutely amazing) guides chuck, and especially for the continued updates of those guides! I do have a rather specific request though: On page 499 (Part 10, section 2.11.1) of your current FA18 guide you describe the flight profile of the AGM-84E SLAM: which currently deviates a lot by what is implemented in DCS. (Made a bug report here , TLDR: FLT setting is ignored: Missile always flighs at launch altitude, then goes into ~9° dive to target. Terminal attack flight profile not affected by DIST parameter. -> no matter what FLT and DIST settings, flight profile is only affected by launch altitude and speed) BigNewy responded in that thread, that the observed cruise altitude is wrong, however the terminal guidance is fine. (With the current terminal guidance the target comes into the viewport of the SLAM roughly 7 seconds before the SLAM impacts) I tried to find some documentation about the SLAM flight profile myself, but couldn't find anything. Most useful documentation i found was this document, which btw at least says that the SLAM has and uses the same radar altimeter as the HARM: Are you able to shed a bit more light into how the SLAM should fly or do you have any documentation on that matter? (A simple "no" if you don't want to disclose your sources for whatever reason is a perfectly acceptable answer for me btw ) Thanks for reading, and thanks for all your guides again

Hi, No matter the selected FLT height (low, medium or high), the AGM84E seems to fly the same: First the SLAM tries to hold it's launch-altitude until the target is roughly 9° below the horizon line, at which point it'll pitch down to also roughly 9°. (In case the target is lower than 9° below horizon ON LAUNCH, it'll immediately descent at ~9° pitch down) The SLAM will keep holding those ~9° nose down attitude until it's ~10NM away from it's target (no matter the selected DIST setting), at which point it will level out. Flying level until ~4NM from target, at which point it'll go into it's terminal attack phase. streamable link of ONE slam launch (FLT set to high, DIST to 15NM): https://streamable.com/fmon9t Note: (obviously) i did not at any point adjust the course of the SLAM. Track and tacview file attached to this post. IMO it's obvious that at least the FLT parameter is broken, possibly the DIST parameter as well: At least according to chuck's guide (Part 10, section 2.11.1 (page 499)) the flight profile should look as follows: (SLAM going terminal upon seeker activation, which would make aiming the SLAM a LOT easier, considering one does not really know at the moment when the slam is looking at it's designated target location until impact, see streamable video above) That being said, it could very well be that chuck's guide is wrong in regards to the DIST parameter. slam_broken-flt_high-dist_15.trk Tacview-20210505-220230-DCS.txt.acmi

online manual (http://heatblur.se/F-14Manual/general.html#detail-data-display-ddd-and-panel) still doesn't mention that the 3° are in relation to the horizon and not the total look-up of the radar.

can this be fixed in the manual? relevant section: section 3.18.1 Detail Data Display (DDD) and Panel, PDF page 203 (document page 195)

So what's the best procedure to get rid of the gimbal limits warning now? I used to do short-china-hat-aft + long-china-hat-fwd to reset my TGP in the A10C-1. Anyone know of a better solution to reset the TGP than to switch between STBY- and AG-mode ?

patch notes of today: Temporarily disabled automatic TWS MAN to AUTO mode change on phoenix launch pending TWS-AUTO final implementation Thank you devs :)

As TWS Auto is currently not working, would it be possible to disable the automatic switch from TWS Man to Auto upon Phoenix missile launch? Or maybe have an option to disable it in the Special section? I tend to manually switch back to TWS Man in order to not loose the contact i just foxed on. Edit: If you guys are just weeks away from having TWS Auto implemented then ignore this :D. But in case it takes a couple of months i would appreciate if you would consider this option.

Still have this bug, any updates on the progress of fixing this?

@Slap_Chop: Sorry i'm just now replying. I wanted to use my Xbox 360 Controller in the RIO Slot of the F-14B by Heatblur. Assigning the left trigger of the controller to the HCU dual-stage trigger and the right trigger to the dual-stage trigger for the LANTIRN targeting pod. In short what XInputPlus does is modify the controller layout of the Xbox 360 controller -> it being possible to use the "Xbox button" as an actual button ingame, have the trigger axis show up as two axis (instead of one) and/or as buttons. This is being achieved by placing modifed .dll files inside a specific game folder -> The changes only happen to a specific game and every other game uses the Xbox controller as normal. Also another minor update: the bug only occurs in case i assign one of the XinputPlus axis to the aircraft pitch/roll axis. Will update the original post.

Update: Turns out using XinputPlus with DCS results in such behavior. Could reproduce the same Trimming behavior in the A10C and the MiG-21bis. Weirdly enough the F-14's trimm worked fine. I still think Directinput device handling might be a bit wonky in DCS, but that's a DCS issue at best and not an F-5 issue. For now i'm no longer using XinputPlus with DCS.

Game Flight Mode was disabled. Or do you mean something else?

edit: bug only occurs when using XinputPlus to reorder buttons/axis of an Xbox Controller for PC AND using one of the Xbox Controller axis as pitch and/or roll. It is also NOT F-5E specific, so this thread should be moved to a generic Bug report section of DCS. Steps to reproduce: Create or use an XinputPlus controller profile for use with DCS (unzip attached .zip file and place files in "DCS World\bin") Load the instant action mission "free flight" trim Workaround: Unassign the pitch/roll/yaw axis from the "XInputPlus for DCS" input device (Maybe restart DCS, at least reload the mission) XInputPlus for DCS.zip

I assigned a slider each to the following axis commands: HCU dual stage trigger (axis thresholds) LANTIRN Trigger Axis (Latched, Lase, Designate) But i can't seem to control either via the assigned axis. Instead the behavior of the two triggers is rather erratic. Sometimes sticking to the half-action when the trigger is fully pressed down for example, most often not reaction to trigger presses at all. Should i tune the axis within the DCS controls options or are these two axis assignments currently buggy?