Kempleja

Man, you seem to have very short memory. Just about an hour earlier you replied to a question about "successful AIM-9 shot from 7-8nm away" and suggested reading "Mig-29 shootdowns over former Yugoslavia", which turned out to be bollocks, again. Are you on a mission to say something absurd every time you post?

This is so weird, why someone would want to discredit himself so severely on this forum for no apparent reason.

Incidentally, I also had a weird A-A radar issue last night that I have not had before. I played one of the default missions that comes with Hornet, on Persia map, where you have to shoot down six Su-25's with Sparrows. I shot down 5, but one got away and I started scanning around for it and just did not find it. Then looked it up on F10 map and saw it was heading north towards a distant airfield. I took the bearing from F10 map and went after it, pointing my radar at it, but it was just not picked up by my radar. I got closer and could see it visually, pointed my radar at it in TWS mode and RWS mode, switched between HI and MED (I was directly behind it, rear aspect), tried different scan zones, put my radar control to HUD and tried with LHAQ mode, still nothing. Dusk was setting in and the Su-25 was about to land, when finally from about 5-6 nm distance my radar picked it up.

I think the manual (at least Chuck's guide) says clearly that turning on jammer automatically turns off radar. So my guess would be that since AMRAAM would not get any guiding from plane's radar, it would turn on own radar and try to lock on the closest target, as with VISUAL mode.

Ok, yes, that part was working from the beginning, with A/A, A/G and other lights being synchronized to DCS in-game lights. The issue was, if I shut down PC entirely the lights stayed on. I could of course dim these lights entirely by taking led slider in SimAppPro to zero, but now there is no need for that as the backlights go dark during shutdown, only the blinking light stays on.

Thanks, mate. This fast startup option was not present on my power settings at all, but was able to make it visible with this instruction here. Still the System Status Indicator keeps blinking when I shut down my PC, but I guess I can live with that for now.

And one more update about this issue getting partly solved. I ran firmware update through SimAppPro, even if it already appeared up to date, and now the backlights go dark, when I shut down computer, but the System Status Indicator keeps blinking. You mean select the option in "Run when windows start"? That's the only setting I find in SimAppPro related to that. Default is "true".

Doing more trouble shooting, ran into another weird thing related to this device. The USB port where Winwing Orion 2 is connected to has "Disable Device" greyed out. All other devices I could disable from Device Manager, but not this one. Anybody else has that?

Thanks for suggestions, @Bwaze and @silverdevil, you are definitely pointing to the right direction that it is not entirely device issue, as I tested my throttle on laptop and there it shut down properly, when I shut down computer. On my main PC the issue is still there, however, and the suggested solutions did not work, as my BIOS does not have LED or ErP related settings and also in the Control Panel Power Options there is no "Activate Fast Start" option to disable. It is weird that this issue is present only with this Winwing throttle on my main PC. VKB stick, Saitek pedals and old X52 and Logitech keyboard and mouse all have leds and they all turn off when I shut down my computer. And as I said, I have switched these devices around also and Orion throttle stays lit, no matter to which USB port it is connected to and all other devices go dark with shut down, no matter to which USB port they are connected to.

It is plugged directly into motherboard, but the lights do not turn off when I turn off my PC. Also, all the USB hubs have this power setting:

Orion 2 throttle lights do not turn off when shutting down computer. Any idea how to handle this issue, without disabling USB port or unplugging the device? I have also tried switching devices to different ports (VKB, Logitech, Saitek), but no matter which USB socket I use, Orion lights stay on and other devices shut down, when I turn off computer.

Yes, fastest way to get these DDI's on, just push SCS right, you get radar there, push SCS left, you get AZ/EL there, push SCS down, you toggle SA/HSI there.

About trimmed landing, basically you just put the velocity vector in the middle of the E-bracket, line up with the runway or carrier and just use throttle to keep the velocity vector pointing to where you want to touch down. If velocity vector starts to go long, reduce throttle a bit, if it starts to go short, add throttle a bit. I don't even touch my stick during landings, just correct my course with pedals, if I drift left or right.

I think that in general it is a waste of a missile to launch a missile against a fighter from 30 nm. Sometimes I also do it for fun and variety, but it is more like a half court shot in basketball, sometimes it might go in, but you should not really count on it. A higher probability shot against a fighter is below 15 nm for AMRAAM and maybe around 10 nm for Sparrow.

Are you sure that you have actually locked him? TDC depress in RWS mode, if LTWS is enabled, just designates a target, but does not lock it. Second TDC depress puts it to STT lock. Better yet, try using TWS mode and make sure that AUTO is selected, so radar will automatically center on L&S.

You can definitely acquire A-A target with Litening and without using radar. Related to AMRAAM, if there is no L&S designated, it will be in Visual mode and you can of course launch it in Visual mode. Missile's own radar will become active and will target the first contact it finds, no matter where Litening is locked to.

My intention is not to capture a different bug report, but as it is related to replays, I have had occasions, where replays play out differently than what actually happened during gameplay.

Ah, nice. Did not read his second message and did not know that elevation and azimuth can be cursor-selected. But when using OSB, is the current behaviour correct, as it should be? To me at least it would make sense.

I have no idea, what is the correct behaviour in reality, but this described correct behaviour would be a downgrade from current behaviour and I wonder why would they design radar to behave like that. It would require pilot to press more buttons and could cause accidental track drops. For example, if a pilot has 4B-40° setting and has a contact on lower half of search cone. If he wants to narrow azimuth to 20° to get better track, he would actually command azimuth from 40° to 60° and elevation to go automatically from 4B to 2B and actually skip scanning the lower portion of initial cone? So if in current behaviour it would require one press to get from 4B-40° to 4B-20° then with the described correct behaviour pilot would need to press azimuth button three times (40°-60°, 60°-80°, 80°-20°) and then elevation button again (2B-4B). Is also a lot easier for brains to remember that you first have to set elevation and then can cycle through azimuth (or vice versa) rather than having to adjust both settings.

You can turn the HMD blanking over HUD on an off on HMD DDI page. I think that the "recce event" button on stick also blanks HMD, no matter where you are looking.

It would change the meaning of the sentence, though, and be incorrect. If dispenser switch is "OFF" (down low, middle console), then you can't run a countermeasure program. I think the easiest way would be to say, if the dispenser switch is in "ON" position (= not in BYPASS mode or OFF), then ... The main point in this report here is about what the HOTAS "Aft" switch is doing, when Dispenser switch is in "ON" position and "MAN" is selected on EW DDI. Would it release single chaff / flare, as stated on page 69, or would it run selected countermeasure program, as stated on page 386. And same for "Fwd" switch, would it run selected countermeasure program or program 5.

For me, radar behaviour is very erratic when playing online (Growling Sidewinder), but generally no problems, when I set up a mission with a couple of AI planes. Online, radar drops tracks a lot, or L&S might just jump to a contact 60 nm away, when I have a hostile 30 nm in front of me or AMRAAM's gets LOST, even if track is not lost. I have considered it to be some kind of lag or netcode related issue as there are no such issues when setting up missions against AI.

Thanks for tips, @Tholozor and @Harker, after more testing, NCTR indeed works in STT.

Thanks for the reply. I am pretty sure that I have been tracking the bogie in STT lock also, locking it both through manual TDC depress as well as through auto-acquisition, but I can check once more. Still, looking at Wags' videos about IFF, both about manual interrogation as well as AZ/EL, it does not appear that STT would even be needed for NCTR.

Hello, I am quite confused about the IFF and NCTR part. Whatever I try, the NCTR part just does not seem to work as I would expect. So I set up a mission where I fly head-on with a Su27, starting with 80 nm distance and I never get hostile HAFU on my DDI's. I tried to interrogate it manually with SRS depress, try auto-interrogation with AZ/EL, keep it in STT lock, from less than 40 nm, 20 nm, 10 nm, 5 nm, but no luck. Both IFF and D/L are on. As you can see from my screenshot, even with 3.4 range, HAFU is still ambiguous and on SA page the bogie is still "UKN", after we have been going head-on and it has been on my radar constantly from 80 nm distance. Any idea or advice, what is going on here?