Horns

Up 30.2 KB/s Down 402.9 KB/s I’d kill for your “slow” speed :P

I used the command line ("dcs_updater update")...

I'm on Au West Coast (no I don't have a mullet!) and the download has started for me

Single, sorry forgot there is a multiplayer one around. And yes, I get that IRL RWRs pick up radar regardless, cheers

I definitely don’t pick up my flight’s radars in “Hunting the hunters”, which is why I asked.

As a “paying customer” you are entitled to a copy of the *release version” of the product. People who bought NTTR or Normandy were granted access to 2.x as a condition of sale. No one is entitled to the open beta. ED can make it available selectively or withdraw it altogether at any time.

Oh ok, that makes sense. Thanks, I think I’ve got my head around it now.

My bad, I did use the wrong term, I should have asked “how do we avoid getting radar emission indications constantly when flying with a wing/man beside/behind?” I meant to ask about the way this works with AI wingmen, I didn’t realise there was a difference in the RWR function for multiplayer or I would have clarified, once again, my apologies.

Something just came to mind, since we can't distinguish between known/friendly radars and others, how do we avoid getting radar warning constantly when flying with a wing/man beside/behind? Radar is used for searching by the wing/man as well as lead, correct?

Pitchfork anyone? :P

Sorry Django, I think NeilWillis may be right, future modules would need support that ED won't provide for 1.5.8 once the upgrade process is complete. I misunderstood and thought you meant that your installs would be both branches of 2.5. Apologies.

That is my understanding. I know personally that’s how it works currently, I haven’t seen mention of a change and I can’t see why they would change the current system, but I’m not ED so I don’t *know*.

Cheers. I have looked through the natops manual for flight envelope specifics and diagrams as well as loadout information, haven't found anything yet but I will keep looking. Thanks, that does help a lot, that answers the question about acceleration and it also tells me that if I want decent speeds I'd better stick to the altitudes where the Hornet performs best.

You may have a point. Can anyone advise what a standard strike mission loadout might be for the Hornet?

The image in the OP has changed as of Jan 26th, and it now indicates that 2.2 will get updated to 2.5 stable instead of reaching EOL. I got caught out by this and I think there is still some confusion, so I'll just leave this here. https://forums.eagle.ru/attachment.php?attachmentid=176690&d=1516860954

I'm trying to get a feel for what to expect from the Hornet's flight characteristics, so the questions below are framed to allow me to compare it to the Viggen. I know the Hornet is typically flown much higher but I may fly familiar Viggen-style strike missions while I get used to the new bird, and then work on adjusting to the Hornet's typical mission profile. 1. What is the Hornet's approximate max speed at sea level? 2. How does the Hornet's acceleration from 350 to 550 knots compare to the Viggen 650 to 1000 km/h? 3. Is the Hornet stable, maneuverable and responsive enough to employ at very low altitude (30 feet over flat terrain, 20 feet over ocean) at cruise speed? 4. What is the Hornet's usual operating altitude for A/A, A/G and moving between waypoints? Thanks for reading.

That’s how I read it. Works much better for 2.2 users now imo

True, provided that 2.2 is kept along with 2.5. I wasn't aware of that when I posted earlier, glad you posted that :)

1. Yes, the Open Beta will copy whatever it can from your 2.2 Alpha. 2. I think there will be a negligible difference in the size of download between the Open Beta and Stable. If you only want to download it once, I recommend you wait for stable. 3. You can download a standalone installer, but I don't think you can copy the download itself - I believe you would have to let it actually *install* the game on your work computer and then copy the directory. Would that be ok or would you get fired for installing a non work related program?

Ok guys, I'm going to try explaining this a different way. I hope this doesn't sound patronizing, it isn't meant to, this is just the best analogy I could come up with at short notice. Forget the version numbers for now. Think of a road with two lanes, one being "stable" and the other being "open beta". Stable will always join the stable lane, open beta will always join the open beta lane. If you only want one lane on your PC at a time that's fine, but if you want the other lane you will need the other version. Keemarcello, the open beta "lane" will continue to get each update (eg patches and bug fixes) before stable, as it does now. That's the point of having two versions, so they don't risk releasing something that will tank everyone's machine at once.

That I don’t know. You’re disinclined to install (or force to) stable after OB?

Good question indeed, hopefully one of the ED staff can answer. I'm sure that small change won't delay the release more than a couple of months. J/k :P

Try clicking "Last" on the page selector at the bottom right.

Sobe, I think that that 111 GB SSD would be cutting it fine, even without 2.2 on it. The 2.5 install makes use of usable files like the Nevada map is by *copying* it, so having the Nevada map on your PC will save download but not storage space. The additional space used by the 2.5 installation will be just as much regardless of whether the installation drive that has your 2.2 install on it because there would be two copies of the Nevada map on it from the time of the 2.5 installation until you remove 2.2 or 2.5. SSDs need free space in order to function properly, and for your SSD (I'll spare you the numbers) you should read it as having 103 GB usable. Art-J referenced comments made elsewhere by BigNewy and Chizh that suggested the 2.5 install size will be between 91 GB and 104 GB without Normandy (and that may not even count official campaigns), so you might not have enough usable space to start with, and best case you might have 12 GB usable space remaining before you even think about updates or new purchased content. Up to you if you want to wait and see how it works out, but personally I'd view that SSD as being too small and seek a solution before installing 2.5. Sorry to be the bearer of bad news.

Sure sounds like enough to me!