Stubbies2003

You want a crazy AAR challenge try to keep the hornet hooked up to a boom refueler. You can get connected but trying to stay connected is the hardest thing I've ever attempted in AAR. Makes basket refueling look like a walk in the park.

Okay I have that one programmed to chaff/flare as well and it works just fine for me. Perhaps try a repair? I've flown the F/A-18C, F-16, and AV-8B all using that as chaff flare and all work fine. Basically it isn't a DCS general problem with the WH as even you had it working fine at one point. Something in your DCS install might have gotten borked and needs repairing to work correctly again.

True but regardless of RWR you are using it must be able to sense that something has changed (PD to CW as an example) or it must be able to sense the datalink. If it could sense the datalink then there is no method of launch that the RWR couldn't detect it. Very true. This wasn't my area of work in the USAF and obviously if it was I wouldn't be talking about it here. I learned this info by studying for my BMS F-16 virtual flying way back in the day. The above logic will still hold true though. The RWR must be able to sense something to warn about it. If it can sense it in STT then it could also sense it in SAM/TWS. We aren't going to get any better than that. Educated guesses and working on logic.

Yeah I didn't mess with unrestricted SATNAV option so I cannot speak to the efficacy of that. I only followed the procedure in my second run of that mission when it didn't work in the first one and I saw the exact same indication, or lack thereof, that you did. When I followed the instructions the second time it worked perfectly thus why I think you are right in that you missed a bit of the procedure.

And with a bugged track it definitely depends on what your scan pattern is like to if you will lose lock. If I tried 40 wide and 6 bar it couldn't maintain the soft lock. If I went 40 wide and 4 bar then it could mostly maintain a soft lock.

Which switch(es) are those? I use the full WH setup and haven't had any issues with buttons refusing to work in DCS.

If it was in the side lobes then STT wouldn't make any difference to SAM or TWS. The data would still be there and you would get a warning regardless.

They don't. Reference my last post. Until the AMRAAM came along most F-16s were AIM-9 only.

It probably does lack that. I worked on the USAF F-16s for 20 years and the vast majority of F-16s do NOT have CW hardware installed thus couldn't carry and use a Sparrow even if they wanted to. They are pulse doppler all the way thus the OP is correct that STT launches of AMRAAMs should NOT trigger launch warnings as there is no change in the signal for the RWR systems to detect and warn about.

So this very well might be my lack of knowledge on doing replays but when I loaded that track it was set to follow the E-3A. Not helpful. There were a LOT of F/A-18s in the list and I didn't see anything that stood out about a human controlling any of them and I was certainly not going to select every single aircraft in the F/A-18 list. That being said what you are describing is basically what I see when the SIL (Silent) option is highlighted on the FCR screen which means your FCR is not transmitting at all. Whether directly selected or via some emissions control option. You will see the top and bottom numbers of the captains bars change without seeing the relevant change to the antenna position itself until you come out of silent mode. Now I don't know if the captains bars numbers should change or not when in silent but that is what it does. If that is how it should work and if you were in silent it is neither a bug nor a broken radar but operator error.

Well if so then the brief and the aircraft weren't updated to reflect it as you have to go through that process to get the moving map and steerpoint distances working correctly as well as the briefing still stating that GPS doesn't work for REDFOR. I went through this just yesterday doing the first mission after arrival to Nellis. Playing live side not OB. Perhaps it was a OB fix that hasn't made it to live side since it has been a minute since live was updated.

SkaldDKO was almost on it as I made the exact mistake you are making. It has nothing to do with the INS alignment other than you have to be done with it and in NAV. Then you go to the HSI page, then verify you are on waypoint zero, hit the WPDSG button (like he said BEFORE you taxi the aircraft) then it was a button on the upper left to get to the UPDT and ACPT option. Might have been DSG if I remember correctly. Just like they said the procedure is in the briefing and if you follow the procedure verbatim for the aircraft hasn't been moved it will bring up the moving map and your distance to steerpoint data will change as you move around. Worked for me so it'll work for you. Also it doesn't matter that the date is 2016. The briefings specifically say that REDFOR don't have access to GPS thus these extra bits need to be done. Suggest you pay closer attention to the briefings as obviously important data is being passed on.

I do it the lazy person's way in that I will lock up the possible target which will drop all other emitters to see if that is the one I want. If not unlock, RAID switch, and lock again to see if that is the one I want. A bit clunky yes but if you have those set up on your HOTAS it can be done quickly.

Well first off you have to be within range to get a lock in the first place. You will be able to see your target in the Mav page and still be out of range of the target. Then yes you can get some targets that are close to something else that the Mav likes to lock onto other than what you want it to. Just comes with the territory.

I've seen changes from yellow to red in LTWS so STT not required.

True but even having a manual IFF interrogation won't change that. I can interrogate one and not get a change from yellow until it goes nose on and I get some NCTR.

Just practice flying at first in training missions. Practice makes perfect. That and learning your systems as well as knowing what you are up against.

SRS is pretty straight forward to use on the 18 and since people tend to stick to 305.000 which is what the radios dial to automatically it makes using SRS in the 18 very easy. Only problem I had at all with SRS was the default output volume was REALLY low. Once I cranked up the boost I haven't had any issues with SRS at all. As NVidia would say "it just works".

Another reason you can see price differentials like this is some binning done by Intel prior to them selling the CPUs to OEMs to verify their CPUs would OC the best. Just like BP says I'd wait a bit since not only is 10th gen Intel coming out but this year we are also scheduled for some more Ryzen. Even if AMD isn't your choice it still controls pricing thus better for consumers.

Also UHF is locked into Comm 1 and VHF to Comm 2 on the Viper.

Since when is a Roland SAM EWR considered to be a armored vehicle? Try to strafe that with an 18. Mission impossible. As soon as I can option that in to the 18 load out I'd love to...

The 18 doesn't even have this yet and the F-16 is missing a LOT of items still. Yer a bit premature in this request.

Another thing to verify is if you also see the flaps light turn yellow instead of the green for half or full. If you are seeing this at the same time it is the plane letting you know you are too fast for your flaps setting and the plane is ignoring the flaps position and is in auto.

Have never seen this before on the hornet and I fly it exclusively. Your configuration or HOTAS is borked somehow.

Just edit the lua for the 18 and put in what you want then also save that file to a temp location if you want to do it manually and only have to mess with it after the 18 gets patched. Did that so manual 1 and manual 5 are chaff and flare only so I don't waste flares trying to get rid of a radar missile. Yes it would be nice if this was fixed but the work around is easy. Unless you change your programs around a lot.