backspace340

It feels like they both have the new flight model - you can get lofted kills from 30-35 miles with the MH. I don't think it would've got anywhere near that with the old flight model, even with lofting.

I believe it actually uses the tracking radar for its gun, but the missiles are optical/command guided. So I think you *can* see the Tunguska lock you, but it'll only happen when you're very close and it's trying to gun you down. It can fire missiles without locking you.

It definitely feels harder than the KC-130 - I'm not sure if the hose is shorter or something, but it feels like you've got a lot less room for error than with the KC-130.

I've been trying to learn recently too, and have hated it with a passion up to this point. My problem has always been immediately after contact - I found it almost impossible to stay in a place where the hose would keep connected. I had my first successful run tanking till full off the S-3 in the instant action today. What helped me a lot was jumping on the Aerobatics server, taking three bags so I had plenty of fuel to spare, and then finding the KC-130 tanker and just trying to fly formation with it - and every now and again topping off with fuel. I had enough fuel that I didn't *need* to get gas so I wasn't rushing myself, and it meant that once I was confident I was keeping formation I was confident I could keep myself in the right position on the hose. It was much, much easier than the instant action refuelling mission - for one, the KC-130 mostly flies straight, whereas the S-3 makes a turn basically as soon as you get to it, and it also just seems to be easier to keep formation with (though I'm not sure why). After a couple of hours doing that, I switched to the instant action and managed to stay connected until I was topped off (though it was a lot harder, and I was all over the shop).

You could ask Georgia to change their timezone - the difference is the difference between zulu (GMT) and local time.

Wags was saying in the YouTube comments that they are based on trackfiles provided by your plane or by datalink. Given we can only create one trackfile by locking in STT right now I'd expect we'd only be able to see the caret / half circle on whatever we've got locked (so one contact at a time).

It's not implemented yet - but it is a priority for them: https://forums.eagle.ru/showpost.php?p=3596058&postcount=74

That is awesome, and exactly what I was hoping for - you wouldn't happen to have any videos/pictures that show how that works would you? That'll be such a benefit - I'm guessing it'll basically be like having labels turned on and as a VR user with not perfect eyesight that sounds amazing.

I think I was wrong in my earlier comment - I had another play today and it seems like the AIM-7M doesn't loft, but the MH definitely does. Not sure how I got that mixed up before, thought I'd seen the M lofting but it doesn't look like it does (even with LOFT on the Hornet's HUD).

Were you in multiplayer by any chance? Lots of multiplayer servers haven't updated to the new patch and have stayed on the stable version - but you can still access them on the Open Beta version with some strange side effects. One of those side effects is that the AIM-120 doesn't work properly and won't lock. It works fine in single player though. For the OP - most of what you have written about (TWS etc) is still to be implemented, some of the others (AACQ, active timer on the 120) are fixed and implemented in the beta branch. If you want Hornet updates as soon as they are available, switch to the beta branch. The release branch runs at least a week behind.

I had a play around with them yesterday and they seemed to perform identically - both were lofting as far as I could see and both seemed to have the same range.

I was ecstatic to see that the data link functionality is now a 'Priority' for development as I think it's going to be a big game-changer for the Hornet (and DCS in general). However, something piqued my interest in the list of priority features that Wags announced: I'm pretty sure I understand how MIDS / Link-16 helps/functions on the SA page and A/A radar - it gives you trackfiles/airborne targets identified and transmitted from outside your plane (i.e. spotted by an E-2 or the Stennis etc) as well as wingmen's positions etc. However, I've got absolutely no clue how it would help/function on the HUD or JHMCS - does anyone know?

I bet you've bound radar elevation to an axis and are using a slider for it - that essentially doesn't work, it's designed to be used with a joystick-type thing that returns to center. Bind radar elevation to buttons instead and your problem will probably go away.

Yes, you can just use the command line to switch branches (or utilities that people have made): https://forums.eagle.ru/showthread.php?t=114030

Are you sure that the problem isn't the headset? Is it moving in 3D space when you're in the Steam VR lobby bit? I've had it happen a couple of times and it's normally easy to fix by re-running the setup, for me I just go to Windows Mixed Reality and click run set up, click seated and then click centre and it starts tracking properly again.

There is some logic involved to determine whether it lofts or not, IASGATG was talking about it on hoggit - I believe he was saying you need to be at least 15nm away from the target for it to loft at all, and it'll stop lofting 5nm from the target. You wouldn't want it to loft any closer than 15nm anyway as it'll waste too much energy climbing/descending when it may as well just go straight at them!

Just Open Beta for the 9x (120 went into stable last week, but it doesn't have the new changes from this week) - they always update the beta first and then their usual programme is to update stable the following week. If you want the new stuff as soon as it's released switch to open beta, but there's a decent chance of nasty bugs (I. E. Last update broke a couple of modules for a few days).

Pretty sure that IvanK guy who replied first is an ex-Hornet pilot (judging by some of the photos he's posted) and has been working with ED to get the drag numbers right - he's saying they're now essentially as they should be.

It might be called Sensor Select Switch Right.

I think there's some kinda heat attribute at play - I noticed it up against the L-39, where head-on you can't get tone with either missile till about 1.5nm, but switch it out for the Mig-25 or something and you can get tone at 15nm. Right now it seems like the M and X are using the same seeker head, I'dve thought the X would be able to lock a small head-on target at better ranges than the M - is that not the case in real life?

You can deselect ACM by just pressing Undesignate/NWS. It makes sense having the missiles just in their visual/flood modes when you're not locked to me - also cage/uncage is used on the AIM-7M/MH to switch between loft mode and normal mode when locked.

Here's another track from Caucasus showing the same behaviour, and a video of it too: radarlosCC.trk

Radar still losing lock too easily I did some simple testing in the new Open Beta patch (released 15/08/18 ), and the radar is dropping lock very easily while performing relatively simple and gentle manoeuvres. It's very simple to reproduce - simply lock up a target that's in front of you, roll 90 deg left or right and turn to between 30deg and 60 deg away from the target, as you roll out from the turn to go wings level the radar will drop the lock. Track attached. radarloss.trk

Thank god - I thought I was just going blind in my old age, the Hornet DDIs have been so much harder to read than any other module.

A big difference, LTWS is like RWS+, TWS is TWS. For both, the main benefit is they turn the raw bricks into trackfiles - which'll tell you whether it's friend or foe, which direction it's going, what speed it's going and it's altitude. It'll give us the ability to soft lock and to IFF without STT. LTWS is activated in RWS mode, and lets you generate three trackfiles at a time - one you get by putting your TDC over the top of any brick, and you can soft-lock two targets (which you can then flick back and forth between as your primary target). This is possible at any scan volume you can use RWS in (i.e. max 6 bar / 140 deg). TWS only works at restricted scan volumes (I think max is 80 deg 4 bar, but not sure if that'll actually be even less and something like 2 bar 80 deg / 4 bar 40 deg / 6 bar 20 deg). It'll automatically display the top 8 targets/trackfiles it's prioritised. So essentially RWS = raw bricks, LTWS = three track files but you have to manually pick which, TWS = automatically shows the top 8, but comes with a scan volume penalty.