Swift.

When using the TADS to lase and store a target, and then slave back to that stored target, the TADS will no longer point at the initial location. In the following video, notice how the TADS indicated LOS on the TSD correlates with the location of the target (T04) when it is stored, but when slaved to T04 the TADS indicated LOS on the TSD shifts noticeably away from the point. This is also seen in the TDU itself where the LOS shifts several hundred meters to the right and closer. I do not have a track at this time, because I've so far only experienced it during 3 hour sorties. I shall be attempting to reproduce in the coming days and will update here.

Slightly related is what we noticed last night, that if the pilot not on the controls presses the FMC disengage button, it will disengage the FMC and show a caution only for the pilot not on the controls. If he then re-engages the FMC it will disengage for the pilot on the controls. So basically the state of the FMC isn't being synced, just the MFD presses, toggling on will cause toggle off in the other cockpit.

Can we have an option to add modifiers to a control binding that work on time. eg, double tap, long press(on release), short press(on release). Selected under the existing GUI for modifiers so you just pick one from the drop down list.

So its been a while since I made a request for this to be added to MP, and whilst we wait for a vanilla solution: You can mod this into the FA-18C.lua with a single line change. line 791 reads net_animation, if you add 99 to the bottom of the following list it will make your head nods be seen by anyone looking at your aircraft in MP. PS. ED pls, this is such a simple change. Please can we have it in the vanilla version.

The problem is that if you employ that technique from an already trimmed position, pressing the trim release will 'reset' the original trim position.

This is the way. I don't understand why people aren't grasping this concept, you can gain down the map to total darkness if you want, so you can most definitely get to a point where you have map info and can still read the symbology.

...thats how its down IRL. Pass the codes with the check in

Adding onto this. It would be possible to have all the FCR bindings on a single 4 way hat with either of the following logics: Forward Long - Zoom FOV Forward Short - Narrow FOV Aft Long - Wide FOV Aft Short - Narrow FOV Left Long - C Scan Left Short - S Scan Right Long - Cued Right Short - Mode cycle (GTM>RMAP>ATM>TMP) Forward - Decrease FOV Aft - Increase FOV Left Long - C Scan Left Short - S Scan Right Long - Cued Right Short - Mode cycle (GTM>RMAP>ATM>TMP)

A Chicken-and-the-egg argument could be made here. Not a lot of FFB exists because it's not widely supported.

Yeah this certainly seems suboptimal... I know the 'answer' is just going to be 'wait for DTC', but hopefully everyone recognises that some stuff needs to be controllable before the turn of the century...

I probably wouldn't call it MSI at that point, just datalink. IDK though

And FWIW, these would also be useful for the Collective FCR bindings.

As Scaley said. My best guess is theres some odd behaviour where the sprag clutches don't disengage. Which would explain why a sharp reduction in the power levers is met by an equally sharp reduction in the rotor RPM, and why power on collective full down autorotation has both the engines and the rotor matching at about 103%. Additionally, 'sticky' sprag clutches would explain why the single engine performance is much worse than charts indicate, as an example if your dual engine torque for a regime of flight is 40% then you'd expect the single engine torque to be 80%, but what we see is more like 110% for the single engine(in this example). Which would match with the remaining engine having to drive both the rotor and the dead engine.

Any chance we can see this added soon?

To aid in binding the plethora of TEDAC controls to something simpler like a gamepad. Would we be allowed to have a few concession bindings such as: TADS FOV Increase/Decrease - a Two way binding to cycle through the 4 FOVs rather than discrete controls FCR FOV Increase/Decrease - Same as the TADS FLIR/TV Toggle - Toggles between FLIR and TV FCR Mode Cycle - Cycles through the FCR modes eg. GTM>RMAP>ARM>TPM FCR Scan Special - Long Press = C-SCAN Function, Short Press = S-SCAN Function STORE/UPDT Special - Long Press = UPDT, Short Press = STORE LST Mode Special - Short Press = Automatic/Off Toggle, Long Press = Manual IAT Polarity Special - Short Press = White/Black Toggle, Long Press = Auto

Hi there, you seem that have generated this impression of the community that people expect as you'd put it 'a 30MM navy jet for $80'. However, what you will hopefully soon learn is that there are a *lot* of things that people accept we won't ever see because its just an $80 game as you say. Now sure, it would be *fantastic* if we could get those things, but its understandable that we won't. Now, having said that, there *are* some things that we do 'expect' (for lack of a better word). For the most part, the things we 'expect' are things where clear evidence exists from which such a feature could be modelled (eg MSI being the big one). So yes, we do 'whine' but we whine because we know DCS *can* be better, and it can be so much better with not a whole shedload of more work. What you won't see (hopefully ever) is people 'whining' for unrealistic expectations, for example CAS page was a big request and would be a fab feature, but its accepted now that not enough evidence exists. So its been dropped. As you've said, we've come such a long way since Janes F15 and Falcon AT. Now wouldn't it be a real shame if people suddenly stopped pushing for better? If people just accepted was is as is and moved on?

Yeah, but I dont see how that relates to what I said

HARM is listed as a sensor for contribution towards MSI tracks. Along with FLIR, Radar, and Datalink. Note that MSI tracks are, as far as we know, Air to Air only. So it stands to reason that the HARM integration will be in angle only.

I mean thats not the only functional difference. Having that new rotor system significantly changes the handling characteristics. Also you know the whole completely different avionics suite thing. A Whisky would be a lot easier, but a Zulu is definitely possible in terms of info (perhaps not in terms of licensing), and frankly if we got a W then every time I stepped to one Id just wish it was a Z.

It's also worth noting that these corrections are only prescribed for catapult launches. Shore based take offs can just be flown out. Also also worth noting the amount of correction required for roll is only ever 1 or 2 degrees difference. So it's not a lot of work to trim it

So there's an issue with SRS and DCS Apache right now, to do with the foot button PTTs and the cyclic PTTs. Effectively you cant use the foot buttons when P and cyclic when P* because of SRS limitations. The solution to this is to have the foot buttons (and/or the cyclic RTS rocker) be animated. This would allow users to bind both foot buttons and the cyclic PTTs to one of these controls, and have the animation drive SRS. So to summarise, adding animations to the Foot PTTs and/or the cyclic RTS switch will significantly increase the usability of the DCS: Apache in Mulitcrew applications.

Not JHMCS. And my understanding is its projected on the single visor as you guys have described, but it's projected on the right hand side in front of the right eye. So if you close your right eye I think you'd be able to see it still out of you left peripheral but it wouldn't be useable. There is a development of JHMCS that allows the visor to be swapped for NVG and allow JHMCS symbology to be projected inside the tubes. But they don't use it IRL and definitely didn't use it on the legacy hornets.

Spanish hornets are very different to any other hornet, unrecognisable almost. And the asym trim us done exactly as Tholozor said, you use the chart which is asym loading in ft.lbs against difference in degrees between the stabs. It's exactly the same technique for measuring trim that you use for stuff like carrier trim settings. So you calculate let's say 2 degrees difference: 1. Go to FCS 2. TO trim > Both stabs show 12 3. Trim into the lighter wing until the stabs show 11 and 13 (a 2 degree difference) And you don't need to keep pressing the trim, just hold it down.

11 03 page 11 paragraph 88 This response will contain directions to paragraphs, but no extracts from said paragraphs, from a document that cannot be posted under the forums rules. I shall PM the extracts in accompaniment. Please refer to: A1-F18AC-742-100 011 03 page 3 paragraph 18 - For description of what an MSI trackfile is A1-F18AC-742-100 011 03 page 11 paragraph 88 - For description of what happens when you use the cursor on one of these MSI trackfiles. The handling of MSI trackfiles as Harker describes is explicitly laid out in these paragraphs, thankfully leaving no room for confusion on this matter. It can be said confidently that all trackfiles can be designated as L&S, DT2 or be the target of an STT command, using all normally available means (acquisition cursor, undesignate, etc).

You've got to reproduce it in a small offline mission. So just spawn, do the steps, exit.