Hollywood_315

Hi Loz, how's it going. Well if you get your wingman to talk back then it does seem something is working :) But overall the devil can be in the details with this stuff especially in the beginning. All general advice for speech recognition applies, I'm sure you have these covered already: *) use decent quality mic, properly positioned *) if you're UK native speaker, use UK recognition engine *) train the voice recognition engine (control panel) using same mic *) add tricky words to MS Speech Library *) speak slowly an deliberately especially at first, leaving small pauses e.g. 'two.....break right.' *) recognition rates improve with time as you use it more. Anyway let's do some checks and have a look at your log: we'll figure out what else could be the issue. I'll be sending a PM. Grtz Verstuurd vanaf mijn SM-G935F met Tapatalk

Hey guys @x39crazy I haven't tested this myself but you could try if the P-51D profile works for those modules. @Orso Invalid Radio is sometimes caused by releasing PTT too soon, i.e. make sure you hold it long enough until you've heard the beeps, I'll send you a PM with some more checks. @MrMgrMatt Great suggestion on the Aux menu, this has been a somewhat unprioritized area in VAICOM. I recommend everyone who often makes use of the Mystery callsign to follow your steps :thumbup: Regarding the multiple tankers etc. that's certainly on the list for a future update version. What would be great to have to enable this is a universal comms menu-reordering mod that would not just sort ATCs submenu but also JTACs tankers, AWACS etc. by callsign name. As far as I know such a mod is not out there yet but hopefully Wartsell or others will feel inspired to get such a tweak in place sometime soon.

Should be the case I believe, but I didn't test it myself. Send me a PM if you encounter any issues. Cheers

@Bull PM sent

Interesting thread, thanks. For some shameless advertisement :D : people going with VoiceAttack may want to check out VAICOM http://forums.eagle.ru/showthread.php?p=2534446#post2534446 Many VR users report they find it very useful since it bypasses the comms menus which are unreadable in VR HMDs. Hollywood

Thanks for the comment! Whartsell's Static ATC mod is not yet compatible with 2.0 / Nevada at this time. If the situation changes I'll make sure to let you know, updates via this thread: http://forums.eagle.ru/showthread.php?t=138994

There's no specific VAICOM profile for MIG-29 at this time, but you can try with using the SU-27 profile. There's a good chance that it will work. Verstuurd vanaf mijn SM-G935F met Tapatalk

Hey SD Sounds like a good plan, reply here: http://forums.eagle.ru/showpost.php?p=2799642&postcount=340 Cheers

Hey SD Sure, sounds like a good plan to me. I'll put it on the list for when funding is available. For now I have planned to look into the L-39 first. Grtz

Simple tip @all: If like me you have no particular need for rendered tree objects in VR you can set the Trees slider below 1500 by editing the options.lua file. I set it to zero myself. ["treesVisibility"] = 0 @averagepilot Thanks for this. I'm using Mustangs High settings now and these seem to give me better overall results than the regular Low visibility range.

When watching the extended fps counter in-game during VR testing with the Vive I have the following observations, appreciate if you can confirm and share your thoughts 1) 'Surf' (presumably water) eats quite a lot of render time (1.5+) even though my Water setting is LOW and there is hardly any water surface in sight when looking around. 2) The 'Camera Angles' counter spontaneously resets to 90.00000 0.000000 every two seconds. This is regardless of whether Allow Reprojection has been set to ON or OFF. This could be innocent but I do find it suspicious i.e. could point to erroneous addressing of the VR driver. I have not seen this behaviour before with TrackIR in 2D but perhaps others have? Would be nice to hear if others can replicate and if this counter resetting is the same with the OR.

@DigitalEngine nice! @tkairshows From what I've read elsewehere I understood that the desktop view is just a replica of the Left (or Right) eye render, i.e. not a separate render. I could be wrong though. If it helps to increase fps I'd be happy to get rid of it.

You could be right, I'm puzzled now though, I thought the Instant Action missions each had quite distinct scenarios? Surely I've heard different voice-overs e.g. in the winter mission? I'm seriously doubting my memory now lol

Cool, good to hear! :thumbup:

That's well possible of course, setups differ. For myself everything including reprojection works like a charm now with DCS 1.5 without SteamVR running. I'm guessing the VR driver settings are stored in registry somewhere and don't need the SteamVR app to enforce them. I'm on Win7x64. Also I found some more perceveid gain in smoothness during testing, this time by disabling unnecessary background services presumably having to do with HTC's e-shop. Again: this helps for my setup, maybe not for everyone, but could be worth checking out if you want to optimize your system: *) service ViveFSM Service: change startup mode from Automatic to Manual *) service Viveport Services: change startup mode from Automatic to Manual *) service HTC Account Service: change startup mode from Automatic to Manual *) using msconfig (look this up on internet if you're not familiar with it) I disabled startup for HTCVRMarketplaceUserContextHelper Per ardua ad astra

I have a funny issue with my Instant Action missions for A-10C. Repair DCS World doesn't fix it. Maybe other people have the same, or someone here has ideas? DCS version 1.5.3.53279 Release. All my A-10C quickstart missions now start with exactly the same voice-over speak and subtitles: Two supply trucks are ahead of you at the fork in the river, left of the town, 9 klicks ahead. Winter, Fall,Spring.. all the same. This doesn't make any sense and I'm quite sure it didn't used to be like that. No idea when it started the only thing changed recently is that I have a new VR kit that I played with. What the f* happened? Anybody else have this problem? When I inspect the miz files (5 in total, Easy/Hard/Medium) which are just zip files I see in them they all have the same WAV audio files. Mission files also all start with the same subtitle descriptions. Suggestions to fix? Thanks!

While doing some more testing I seem to get a much smoother performance in DCS when SteamVR / Steam are not running in the background. It appears to me you don't need it for anything when flying DCS anyway, my Vive is recognized just fine by DCS without SteamVR running. Could be specifc to my setup, but thought it might be useful to share.

You may want to check this out http://forums.eagle.ru/showthread.php?p=2534446

Sure enough, VSync OFF seems to be a big improvement for getting rid of stuttering. Thanks all!

Hey guys I'm trying to optimize my Vive setup for smooth DCS gameplay with 970GTX. Have people been playing around with NVIDIA settings yet? I seem to get *reasonable* results with below (not fantastic, still some stutter when moving my head around but other than that reasonably smooth). Appreciate if people want to have a look and let me know their thoughts: SteamVR: Reprojection ON DCS: (low graphics settings) DCS: VSync ON NVIDIA Control Panel: VR pre-rendered frames: use 3D application settings NVIDIA Control Panel: Threaded Optimization OFF NVIDIA Inspector: Frame Rate Limiter: PS_FRAMERATE_LIMITER_USE_CPU_WAIT This seems to get me to a pretty stable 45 fps all-round also around city areas. Investigations continue, I'm particularly annoyed still by this stutter of head movement I wonder what could be causing it, looks like a buffer thing or something or perhaps its pre-rendered frames that cause these hickups? All inputs are appreciated as always :pilotfly: Thanks

Hey Nic Thanks! Good to hear you appreciate VAICOM. Yep during stetup you can come across some potential snags and indeed it seems you covered just about all of them :) Can be a bit of a pain but the rewards are high once you get things working properly. So let's have a look. *) The one thing I don't see mentioned is that VA must run as Administrator. But I assume you have that covered. *) For VA I recommend upgrading to 1.5.8.18 beta version. It is stable and gives you the option to set up your TMWH HOTAS button presses directly for PTT, which is a much cleaner way of doing things than via keyboard emulation. Of course if you prefer release version 1.5.8 with the Tartarus for now then that's fine too. *) For this one: It could have to do with VA not running as admin but more likely it is related to the Non-US International keyboard i.e. the OEM102 setup. This can be tricky to get right, even though you seem to have followed the correct steps. VA must send the same key as is used in DCS config and keyboard mapping mismatch can screw this up. Let me send you a PM and we'll get it out of the way :joystick: Grtz

Having played with the HTC Vive for about two weeks now I can testify that it is a truly awesome piece of gear, well deserved of the praise it gets. Stand-out features like room scale experience, superb all-aspect tracking, built-in camera, and the excellent controllers seem to put it ahead of the competition at this time. However it looks like for DCS there's work to do to get some improved Vive support in place, specifically in the area of reprojection. I for one would really appreciate if ED changes the 'auto detect Oculus Rift' label into 'auto detect VR' to signal they take equal support for the HTC HMD as seriously as they should.

I have good overall experience with Mirillis Action. https://mirillis.com/en/products/action.html It's a powerful tool for in-game video recording but also has benchmarking options to capture fps performance. Could be worth checking out.

Thanks mate! :thumbup:

Thanks Kozmyk, Same for me actually. I can reproduce this error in 1.5.8.17 beta, but in 1.5.8.18 beta this seems to have been fixed already. @NatoBoomerang can you double-check that you are running .18 and not .17? Version .18 should be ok. Thanks.