A Dick

This one got me too : ) Haven't played DCS for a while. Got into the Harrier yesterday and started it up as usual. Nope, glued to the ramp. Tried everything... well almost, not the chocks! So here's the bit where you get to make fun at the noob. I actually went as far as re-installing DCS before reading this thread (face palm) haha.

Not sure if this has been raised before (or if I've overlooked something) but would help if the download size was shown. E.g. the Las Vegas map was 31GB. I started it in the mid-afternoon and it didn't finish until the late evening, which pretty much meant that I couldn't do anything else on the internet for most of the day. Had the download size been shown I would have waited until bed and let it go overnight.

Nice clear summary thanks. Bookmarked : )

Thanks Willur. That could be quite a wait based on the DCS 2018 road map. Might think about getting the 2.5 Open beta. : )

I have the 2.5.0 stable release and don't mind waiting until it updates to 2.5.1, but does anyone know when the beta will likely end? (I purchased the Persian Map, but can't use it until the stable release is updated. : - ))

Good stuff Ramasy and Alfredo. Will give it go when next in game and drop an update post in this spot. UPDATE: Alfredo, spot on buddy. In the default settings LWin + U keys are double bound. Cleared the key binding for REQUEST AWACS HOME BASE and problem solved. Worked like a charm. Thanks.

Thanks Ramsay, will take another look at it but just to clarify, here's my routine with four 4 x AGM-65D's and the TPOD: In Weapons screen. - Select AGM's. - Wait for them to ready. - Master arm, quantity, fuse. - uncage to go into the AGM screen. In the TPOD screen. - Wait it to be ready. - select standby. - Select TDC. - ground the target, slew, etc. At this point have the correct view in the TPOD and AGM screens, but pressing sensor select FWD doesn't do anything i.e. AGM screen wont go to IRMV. So AGM doesn't acquire a lock and can't fire. As said, will take another look. If I missing something, then anyone please feel let me know (I'll take it on the chin). Have checked the key binding BTW, seems OK.

Not sure it's confined to 2.5.1. I have 2.5.0 and have not been able to get into IRMV mode regardless of how many times I spam sensor select fwd. :)

Thanks BigDuke, will give it try. Also update - since my first post have mapped the left and right mouse clicks onto my controller so can click cockpit buttons quickly and don't have to rely on VA. Much better. So shaping up - losing the mouse cursor is really the main problem ATM.

Thanks BigDuke6ixx. Did consider both solutions. I didn't want to move the task bar because it means changing other stuff on my set up, but I agree this could work. Just reluctant to change my set up for one game. As for using VA to move the cursor to specified pixel co-ordinates, couldn't get this to work in VR because the pixel co-ordinates returned by VA were for the mirror which uses different coordinates depending on the screen, resolution, etc. Was only able to get accurate readings for generic locations like center of active window, etc. Did you have success setting the pixel co-ordinates for the HMD (screens)? Maybe I need to fiddle with it some more. Noticed that a few players favour a track ball, so may be worth a look, although I'm not having problems moving the mouse with my controller. Main problem IMO is that it disappears after a few seconds and is susceptible to head wobble because its still tied to head tracking in the HMD (even though the mouse option is selected in the VR game settings).

New to DCS but have used VR for a while and agree the mouse cursor is a problem in VR. I have the mouse movement bound to my controller and can move it independently of "look at", but it still moves with the HMD as well, so it can be tricky. My comments are based on the Harrier cockpit. My observations: - Its a little hit and miss because the mouse cursor can wobble off the button hit box with slight head movement. Can be frustrating for the hard to reach buttons e.g. DECS switch. - The cursor disappears after a few seconds. Good for immersion, but frustrating when trying to keep the head still to click a button. Have to then realign the cursor. I ideally needs the option to keep the cursor on screen until expressly dismissed. - Despite selecting "keep mouse cursor in window" option, still find it is possible to hit the Win 10 taskbar and loose game focus. The Alt + enter (full screen mirror) option helps, but then the cursor will centre outside the cockpit (next point). - Can center the mouse cursor in the cockpit using Voice Attack. Works reasonably well with the default mirror, just say "center crosshair" and it moves to the cursor to the centre of active window. However, it does not work well when using a full screen mirror as the centre of the screen is then outside the cockpit. As for suggestions (and I accept I only have a few hours in the Harrier cockpit in VR), mine would be: - consider making the "use mouse" option in VR 100% independent of the HMD head tracking. ATM its a hybrid (i.e. partially independent). This would solve the head wobble problem and the hit box issue mentioned below. If the hybrid is kept then those issues remain. - increase the time before the mouse cursor disappears or allow it to remain until actively dismissed. - increase the size of the hit box around the switches (dials are ok). For switches, I like to see a small square or circle painted around the switch when it has mouse focus. Anywhere within the square or circle is clickable. ATM there is a narrow two way green arrow which is really hard to keep still in VR because of head wobble. - default centre mouse cursor when recalled after fading, so its always in the centre of my HMD (where I'm looking) when needed. This may not work if the mouse cursor is 100% independent of head tracking, but I could live with that because at least the mouse cursor would be where I left it, so my problem. Cheers.