ody81

Hi there, I'll check it against my testing build tonight and see if it's still there. Thanks for the report. Edit: Reported! Thank you.

Haven't forgotten you, it's storm season here :/ Anyhow, taking a look now. Edit: Just checked this out and couldn't see this problem with mine. Maybe due to my only having 2 screens, maybe due to dumb luck. We'll have to find someone else with a 3 screen setup to check against. Apologies, but thank you for your report all the same.

Interesting, I have only 2 screens and only use one for DCS but I'll try and reproduce this tonight. Thanks for reporting, I'll get back to you.

Hmmm, well I'm not the guy for VR (I'd never get off the computer :/), I'm happy to go over any bugs or missing functions that aren't already noted in this thread that you may have found, don't be shy :book:.

Also reported. Cheers.

This sounds like an issue I reported. If you can give a little more detail I can be sure. Cheers.

I'm 99% certain I've reported this.

Well if it works on one monitor then this is where my help gets less helpful :/ As I only use (and have only ever used) one screen for DCS I can only recommend this thread: https://forums.eagle.ru/showthread.php?t=60815 Take a look, see if there is something you're missing, you never know. Hopefully it can help you or someone with multi screen can chime in here and reproduce the issue.

I'm not too sure, I only use two screens. I'm only using a single screen for DCS though, I don't spread it out so perhaps if you use multi-screens for DCS, limit it to a single screen and test it out. I can't say it's DCS that's the problem at the moment if you are the only person reporting the fault and I can't reproduce it myself. Do you have any mapping software running in the background? (xpadder, pinnacle, keyboard software, etc...) So try the one screen and see how it goes. By the way, is your graphics card AMD or Nvidia?

Very weird, have you tried using a different combo? Other than that maybe deleting your /saved games/dcs/config/input/ns430/ folder so it can repopulate the default mappings might help clear things up.

Is the key combination conflicting with anything in your Mi-8 mappings?

We'll see what happens, with that in mind though it's hard to please everyone. Leave it to the boffins :)

But for those who want to use a button or hat switch, setting a waypoint could be a time consuming nightmare.

Perfect, cheers!

I'll check this out tonight. If you can upload the .miz file you are using for the FARP takeoff, that'd be great. Cheers

I will take a look at this tonight. I've been a little sloooooow lately :/ Edit: I'm back and I Just reported something similar, thank you.

I think it's normal.

Reported, ta. Well, I reported something strikingly similar (I believe it's the same) so I'll keep an eye on this one.

VR issues reported!

That should do it. Thanks guys! Will check back when reported.

I don't actually have VR myself (such a luddite!). What I'll do is collect everyone's VR woes from here and try to get them verified and dealt with.

I'm a bit late but yes, it's now reported thank you.

This has been reported, thanks.

Groovy, leave it with me. Ill drop a note here when I'm done reporting. If I find a problem of course.

Thanks! It's getting late here and the sandman's calling but I'll get on it first chance tomorrow unless someone beats me to it. One more question though... Which aircraft are you using?