backspace340

Cycle the flaps before taking off, the bindings should work then.

I saw this today - was working fine in one mission, then I tweaked some settings (I turned MSAA off) and the map stopped displaying. I tried putting the settings back to see if that would fix it, but no dice.

You might want to try a more general part of the forums - this is for the Hornet specifically. I assume what you're talking about is the game mode, but I (and I assume most people) have no idea how that works.

Workarounds for both those issues in these threads: https://forums.eagle.ru/showthread.php?t=219278 https://forums.eagle.ru/showthread.php?t=219275

Set your desktop resolution to 1080p and it'll fix it for now.

Got a video of it here as well, using a Samsung Odyssey with a 4k desktop: And can confirm changing desktop resolution to 1080p fixed it.

It was working fine last patch (and what's currently stable), was locking up the closest contact consistently - you're right that it wasn't working at all in the one before that though (or any earlier ones).

Get the Mirage (or wait for the F-14) - I wouldn't bother getting any maps, they don't on their own add anything 'new'. Everything else is either AG, 'flat' or too old for you.

Make sure to vote for the AA radar here so you can get it as quickly as possible: https://forums.eagle.ru/showthread.php?t=219023&page=19

Hah, he's going to be really upset when he hears I never have my HUD or FCS page on any of my screens :eek: it's not like anything is going to magically break in the simulation that needs it. I normally have the HSI on the left, Attack Radar on the right and EW page in the middle.

It's this on the changelog: New label option added: Off, Full, Abbreviated, and Dot Only Just wasn't explained very well (and default probably should've been on!).

Go to Settings, Gameplay and there's a new labels drop-down which will have defaulted to 'None' - set it to any of the other options and the labels will come back.

Congrats - and welcome to the future :)

Whenever that's happened to me, it's because I've just gone into the F10 map and come back out of it which causes the lighting to go all screwy - normally fixes itself if you go to the external view and back to cockpit view.

You need Steam VR and the Windows Mixed reality app for Steam VR installed before you can use the Odyssey in DCS (even if it's a standalone install!). Install Steam, install them both, run Steam VR and then start the game - then you'll have it working. So just to be clear, you need three things: 1. Install Steam 2. Install SteamVR 3. Install this: https://store.steampowered.com/app/719950/Windows_Mixed_Reality_for_SteamVR/ 4. Run SteamVR and then run DCS using your usual shortcut.

I don't have any definitive sources, but a quick Google has the 7M labelled as a Mach 4 top speed missile which would suggest it'd go up to nearly 5,000kph rather than just 2,500kph. But I'm sure someone cleverer and more informed than me will explain why that's not the case.

Yeah they've changed it so the EW HUD is on by default now in hot starts, which is great!

I don't think the planned guidance updates made it into the new OB patch - it wasn't on the changelog (even after they corrected it to put missed items in) and the missiles seem to act just as they did before the patch.

What version number does it say you're on on the main menu? Not having those issues on the new 2.5.3 on standalone.

You sure? I noticed they weren't appearing when I first tried the new build, even shift+F10 wasn't making them come on. So I went into settings and there's a new labels drop-down (with 'Full' / 'Shortened' / 'Dot' / 'None' as far as I can remember) which had defaulted to 'None' - I set mine to shortened and then they appeared fine for me from then on.

I have noticed that you have to first move one of gear/flaps before those bindings work - I'm not sure why. If I just do a hot start for example and take off, then I can't raise gear/flaps until I flick the physical switch myself first - after that the bindings work. If I do a cold start and move my flaps to half myself, then it seems to work fine. So perhaps try cycling the flaps switch before you take off and see if that fixes your issue.

It's on both stable and open beta. Don't bother messing with your build - it happens to everyone, I've got a 960 Evo like you, and a 1080ti, 32gb RAM and i7-8700. I don't think you'll see any results from wiping and reinstalling either. It was introduced with the Memory Manager, and will probably stick around until ED tweak it further. I wish they'd just give us a slider / option to turn off the Memory Manager if our rigs are beefy enough to handle it - I had no issues before they brought it in (though I know lots of people on lower end rigs did).

Seems like it's only affecting the Oculus Rift btw - can confirm fine here on an Odyssey (and I've heard anecdotally it's okay on other SteamVR headsets).

This is new and very broken in the new patch.

Similar issues are happening in VR (I can see it on Odyssey, so imagine you'll be able to see it on your WMR) - the icons move as you zoom in and out or move around, and if you try and draw a ruler it's in the wrong place.