backspace340

You can adjust the settings from the VR Desktop by finding the floating Steam VR box, and clicking the down arrow and clicking settings. You don't need to navigate the Steam VR world (or at least I've not needed to), I've left my controllers in the box as I just play DCS.

Yeah like the guy above says - in DCS (and aviation generally) we use nautical miles, not imperial miles, and your link is imperial miles. From that same website you linked: https://www.metric-conversions.org/length/us-nautical-miles-to-kilometers.htm

Sorry, but you're wrong and it's easy to see how it's wrong with real footage. Skip to about 2:30 in this video and you'll see an Iraqi Mig-21 marked with a square on a Hornet's HUD. Square cannot mean definitely friendly. If DCS were properly modelling IFF then we wouldn't see the diamond at all (until we have datalink or the ability to change designations ourselves) - we'd just see square for unknown and square with FRIEND on top for friendlies (which would work exactly as you've described diamond/square working). Track files can apparently be designated hostile by the pilot themselves manually or by the AWACS operator and sent over datalink (which is probably what caused that track file to turn to a diamond in the video - the AWACS had already declared that contact a bandit a while before the shootdown as the pilot explained on the fighter pilot podcast). I understand that everyone understands how IFF works, but ED have modelled it in a way that is counter to everyone's understanding - we do not have a 'friendly' marker in the game, so there is no positive-only IFF working at all. All the game does is tell us when something is hostile.

It toggles the JHMCS display on and off.

That's cause you're fighting what it wants you to do - honestly, it's better to just forget you've got a monitor. Switch the PC on, put the headset on, use the desktop in VR to start the game and once it's up and running press alt + enter. You will never lose control of your mouse again.

You can use a mouse & keyboard to navigate the Microsoft VR main screen - just press Windows key when you're in the cliff house and find the 'Desktop' app and open that, then you can just start games like you normally would on your monitor. To switch into the game once it's running, click the Steam VR window that'll be floating around. To get back to the cliffhouse from the game, just press alt+tab and then the Windows key.

Yep it was driving me nuts (and getting me killed), it's a lot easier to just give in and then Alt + Enter once you're ingame so you don't lose the mouse.

You don't need controllers to play DCS - just switch them off and use the keyboard and mouse. Not sure what you mean by 'I can’t seem to the UI layer to enable the center command' - go to settings, and controls, and then there's a drop-down to select which controls to edit, the one at the bottom is 'UI Layer', click that. Then you'll need to map 're-center VR headset' (and map 'VR Zoom' as well as you'll need that).

It's closer to 1:2 when it's nautical miles - 1nm = 1.852km, so for rough quick maths just double it to get the metric. One other handy thing to know is that knots are nautical miles per hour - e.g. if you're going 120kts, it'll take 30 mins to fly 60nm.

To be honest, I found it easier to just give in and go with what it's wanting - once you put the headset on just use the WMR Cliff House desktop and ignore that you've got a monitor. Press the Windows key to go to the cliff house, and again to open the start menu - then just open the Desktop app and you can use your desktop from within the headset. You just click SteamVR when you want to go into the game once it's running (or it'll take you automatically the first time it starts up). It honestly makes a lot more sense than constantly fighting for control of the mouse and I've come to prefer it - most days I don't even bother switching my monitor on. For the OP, I think it's probably something different - it sounds like the headset isn't centred in the game - if you have a numpad, hit numpad 5 and it should center it. If you don't have a numpad (like me), disconnect the headset and start DCS, go to settings and controls, and in the drop-down pick UI layer and map 'recenter VR headset' to a button you can easily find in VR (I've got it to the button just below escape). Press that and the game will put the 'center' of the game in front of the 'center' of whichever way you're currently looking.

You're not landing properly - you're meant to get the E-bracket aligned BEFORE you make that final turn. There's no point trying to land before you've done that - in fact, you should learn that first - just fly to 10kft, go below 250kts, drop your gear and full flaps and then trim up till your velocity vector is in the middle of the E-bracket and then adjust your throttle so you aren't losing any altitude. Once you're settled just practice gaining/losing altitude with the throttle to get a feel for how to do it - this is how you fly the approach when you're on speed, using your throttle for pitch. Best to check out some tutorials on how to land - you have to follow a really specific process and style of landing, otherwise it all goes to hell. Edit: To actually answer your question, you're probably clipping the back of the ship with your wheels, because you're in the wrong landing profile and not doing it correctly.

Right now it's just using the game logic - it's really not simulating any real aspect of it other than checking what coalition (i.e. Blue or red) it belongs to as far as I know. In real life apparently the only thing that can designate a target as hostile is either the pilot themselves or other people doing so via datalink. NCTR apparently can't change the designation. So we've got a bit of a fudge right now but it was always meant to be a short term fix - it'll probably get fleshed out later.

That's not true - diamond means hostile. Square means unknown/no IFF response. ED have not modelled friendly yet (which is a square with FRIEND written on top). We just have a simple check of whether something is hostile and it'll show the diamond if it is (if it's within the pitch ladder) - it's not an accurate modelling of how IFF works.

Did you try putting a USB hub with a power cable in between the pc and the extension? There seems to be power issues with the extensions (I'm guessing the Odyssey needs a lot of power) - my headset would turn off every 10 mins or so with 10ft extensions, until I put a powered hub in and then I've not had it happen since.

You just had to install Steam VR & the WMR plugin for Steam.

I saw this video on Hoggit and thought it would be worth showing it here, it taught me something I didn't know that really helps explain the inconsistent IFF that I've seen in the Hornet and might help prevent some friendly fire - the IFF status is only accurate if the target is within the pitch ladder (afaik that's not how it is in the real thing, guessing that's just an EA limitation). Credit to aceofspades:

I don't think any false consequences should be added in - the real life consequence is a talking to and extra maintenance hours, which obviously we don't have to deal with (though I'm not part a squadron so maybe that's simulated too). Also, we play in lots of uncommon scenarios - there's probably a handful of times in the last 40 years of aviation where a pilot's life was in genuine peril in a dogfight whereas it happens several times a day for most DCS pilots. I'm sure the attitude to the paddle would be different if it was the difference between coming home and not - that's just not a common thing in real life normal activities.

Though you make a good point and I do wish the Hornet had more of an A-10 control philosophy - the Hornet actually has a big red DISP button on the left wall of the cockpit which I'm guessing would be used in exactly that first scenario where you're fiddling with your DDI, can't quickly get your hands back on the throttle and you need to pop flares. I'm guessing they'd just mash it with their elbow. I have a feeling our jammer is going to be a fair bit more advanced than what we've seen so far in other modules - I think the normal mode will be to leave it in REC where it'll be 'smart' and only jam when we're locked. So it won't necessarily be a case of switching it on and off like you do in FC3 modules or the Mirage/Harrier etc. None of that invalidates that it'd be quite nice to be able to switch screens / AG weapons without taking our hands off though (though the fault lies with MD/Boeing for that, not ED). Guess we'll just have to wait for the F-16!

I think it's going to be a lot closer to the Harrier's way of doing things than the A-10's. There is a button on the HOTAS for changing FOV though, so at least zooming will be intuitive.

If you're on the carrier, you need to set trim to at least 16 before the warning goes away.

They're probably just going to update stable to be the same as the open beta version we got last week. Next open beta update (so the next chance of new features) will be the 21st.

Could be related to this: https://forums.eagle.ru/showthread.php?t=223272

You can basically get a hit from wherever the seeker locks from (which is about 16nm) unless you are properly on the deck - I've hit at the max seeker range at 7kft.

The correct button for locking a specific brick is Sensor Select Right (AACQ) - if you use TDC depress and there are two bricks on the same azimuth separated by distance, you run the risk of locking up the wrong target (TDC depress just does a spotlight search and locks anything within 20 degrees of the TDC, AACQ when your TDC is over a brick will lock that specific brick).

I think you're all being a bit optimistic to be honest - before Wednesday the last new feature was either PRF in early September or the EW HUD in late August. If it took two months to get these features, I wouldn't expect new ones in two weeks!