ShaunX

..ok, spent the morning fiddling with OVR Toolkit settings. Ocasionally it works perfectly and I'm able to pop up a discord window and use the head cursor and mouse buttons to interact with it. When I close it DCS is out of focus but I've got an alt+tab button set up with solves that. Most of the time however, with exactly the same set up, DCS stutters or everything rotates upside down, or it crashes completely. EDIT... Solved it. It turns out the secret to stabilise it is to set its framerate in settings to the same as the motion smoothing you're using on your headset (so 45 FPS for my G2 with forced motion smoothing). Takes a little bit of fiddling with the settings after that, and you do need to assign a command to toggle the window and also one to ALT+TAB to restore DCS as active but after that I have to say it's really good and highly configurable.

Thanks, might give that a go, though I'm not crazy about installing Google Chrome on my DCS machine. RE OVR Toolkit. I may have just wasted £9.95. Setting it up in the SteamVR construct it's actually really promising. I can set it to pop up any window (which is also saved for future runs), fix it anywhere in world, then assign a keybind to pop it on and off (so I'd have to use Voice Attack to assign that bind to Hotas but that's fine). Even better it uses a dot in the centre of your display as a mouse cursor, and you can assign left and right mouse clicks to keybinds so the window is completely useable ! Perfect yes. Then run DCS, pop up the window and DCS takes a fit and crashes. It seems to minimise the VR mirror which might causes the problem. I'll play around with it a bit more tomorrow but not looking good for DCS.

OVR Toolkit has a "simulation mode" aimed at us hotas only folk. There's also OVRLay which pops up your Discord notifications, but that would just drive me nuts

Thanks, yeah, tried the VA option to send the command to the discord window and yep, DCS is immediately out of focus. Not only that, but tried wildcards, exact exe name, full window name and no option actually executed the command in Discord ! Had a chat to the folk who support OVR Toolkit, which would let me assign a Hotas button to pop up any desktop window in VR (i.e. the Discord Window). That would make it the active window (almost said SOI) so I could then send keystrokes to it. I would hope that when I then close that window, DCS would become active again. Might be worth a try at £9.29. Might actually be worth it just to view the Discord window to see who I'm taking to on Discord even if I can't send to it. It does have an option NOT to make the poped up window active.

Thanks, I hadn't thought of that. I solved it anyway using a Voice attack press and release set up exactly the same as it uses for the Viacom TX buttons. Works nicely. What I can't understand is why that only works for the Discord PTT function. Any other Discord keybind I map only works until I launch into DCS.

I'm just getting into Multiplayer in VR. Although I'd much rather use SRS, many servers require comms presence on their Discord voice chat. I've managed to map a PTT hotas button for it (though it took some doing as Discord doesn't recognise multiple USB controllers and so maps it to each button with the same ID on every hotas controller. Ended up using Voice Attack mapping identical to how Viacom TX's are mapped) What I have't been able to do is map other Discord functions like "Deafen" to cut out the chat audio completely. I can map it to a hotas button in the Discord Keybinds page, but it only works until I go into DCS, then it doesn't. Tried the Voice attack mapping method but that doesn't work either. I assume this is because the command is being directed to the active window, which is obviously DCS, not Discord. Though that doesn't explain why the PTT button DOES work! Does anyone have any tips on using Discord with DCS VR ?

Just an observation here.. I recently started venturing into multiplayer (only just enabled by a new FTTP connection replacing my old 4G dish (the "rural solution")) so I've moved from the CW to the IC pass version, and it's working perfectly, thank you very much. Perhaps there's a tiny performance drop, but what I've noticed as a big plus is that the shader rebuild time, following a DCS update or repair, is just a fraction of the time taken (for each module/theatre) when using the CW version. I think it's because it only generates 1 or 2 files in Metashaders2, rather than 10's of them. Anyway, for me this makes it worth sticking with the IC version even if I'm only planning to run single player.

Hey Strike, As I don't have the P-47 or the Channel map, I've created a KAOS mission for the free P-51 using the Caucasus instant action "Hot start from Batumi parking". I set KAOS transmission radio frequency to 124 AM (which matches the default for channel A in the ME). Running the mission, I switched to channel A and used the F10 command to start the KAOS radio transmission. I can immediately hear the KAOS transmission in the cockpit. So I think this demonstrates that KAOS can be used in WWII planes. Here is the .mizfile - Caucasus TF-51_Hot Test_KAOS.miz So we just need to work out why it's not working in your P-47.

You'll only benefit visually if your optician says you need a far prescription. However, plain lenses can still be a benefit particularly if you opt for the "blue light protection" coating which supposedly protect your eyes from a certain frequency range of blue light which can harm your eyes at close distance. They also project your headset lenses and I find they steam up less.

That's a great resource, thank you.

The mission file looks good to me, KAOS radio frequency is correctly assigned as 140 MHz and the generated .OGG file plays correctly in VLC player. Unfortunately, I'm unable to open your .miz file in the ME to investigate further as I don't own the channel map (or indeed the P-47). Could you create a basic mission on Caucasus and try that please ?

Damn. Ok, by all means PM me your .miz file and I'll see if I can spot anything obvious and get it to work myself.

Hey Strike, I don't own the P-47 and must admit I've never tried KAOS on any WWII planes. Can I ask, have you been able to use it successfully with modern aircraft ? Can I also just check that you used the F10 menu command to start the transmission while in mission ?

I actually find VoiceAttack's joystick/button mapping functionality to be excellent and extremely powerful, and as I use it anyway for Viacom, I see no need for additional software. For the Discord PTT, I mapped an unused key combo in Discord, then seperate press and release commands for it in VA, exactly as Viacom uses VA for its TX buttons. Works perfectly.

Correction.. Just for completeness. Discord will indeed assign assign a throttle buttton, however, as @Hoirtel stated earlier, it also assigns a button it recognises with the same Id (e.g.GAMEPAD1) on every other controller, in my case the pickle on my joystick and a button on my button box. Does't seem to be away round this in Discord, hence back to Hoirtel's original suggestion.

Sorry to hijack your thread man. I finally managed to get a throttle PTT directly assigned in Discord. The problem was that some of my warthog switches were set to on when I tried the Discord record keybind function, so they were getting immediately picked up before I could press the mic button.

Thanks. Interesting that the seperate press and release doesn't work as that's exactly how it's done for the Viacom PTT TX buttons I have a bunch of key combos defined in DCS, which Voice Attack executes via voice commands and some via joystick / button box so just worried that they may conflict with Discord. I guess I'll try and see. Personally I'd prefer to use SRS but some servers insist on Discord.

Thanks for verifying, I just thought it was worth a punt.

Thanks for this. I'm just getting round to using Discord for PTT for a server requirement and couldn't work out how to assign a throttle button to its PTT. So I actually need to assign a key combo in Discord, then map that to a throttle button in Voice Attack ? (Actually seperate press and release actions in Voice Attack, similar to the Viacom TX set up). Question: Discord appears to have a load of default keybinds. Don't those conflict with those set up in DCS and Voice Attack ?

..That's exactly who we are asking. And he responded 10 posts above. ..I also suggested that a seperate request for a generic keyboard might be more appropriate in my first post above. ... unless @kaltokri is able/prepared to add that functionality to his variation. I've no idea if it's possible. It just seemed to me that if someone has gone to the trouble of adding a keyboard to scratchpad, and as scratchpad can be popped up anywhere in DCS, it would be nice if it could also be used to type directly into other DCS text fields.

As stated I don't have either a keyboard or screen accessable from my VR pit. I set everything up from my desk then go over to my VR Pit to fly. I like the separation of the 2 activities. I therefore find the VR keyboard on the scratchpad very useful in mission. As the SP is also available throughout DCS it would be great if its keypad would also allow typing into any selected field. Perhaps for naming a track file or renaming a test version of a mission I'm working on. Maybe I need to change my callsign to go into a different mutliplayer server. Maybe I've incorrectly named a script. These things are possible now with the keypad version, but require text selection and voice commands to copy and paste. We know that, that's why we're asking if it's possible.

It would be useful to any of us who fly exclusively from a VR pit with no keyboard or screen access (like me), to make changes in the ME and then fly again without having to hang up our headset and walk back over to our desk. Perhaps a request for a generic pop-up VR keyboard integrated into DCS would be more appropriate.

It does also work perfectly well with OvGME Agreed on the .5 ms sacrifice. With 2.7.8 I claw that back with FSR (With FSR sharpening set to 0 and let Reshade do the sharpening)

My performance tests are almost identical to the last 2.7.7 patch. No improvement for me.

Have you tried other SteamVR games ? Just to determine if it's just DCS you have issues with ?