epolta

hey Wazoo, The Odyssey is in the box headed to Amazon today. I did the setup and testing over the weekend. It really kills me because the vis was so MUCH better in the Odyssey. Pretty sure I did Steam VR for mixed reality beta - as I had the file on my hard drive to edit with notepad ++. Man oh man what pain to get that windows mixed reality setup too? Over 3 hours of updating windows and then rebooting computer only to have the setup process seemingly fail or stuck on "hang tight". After all that the visuals were worth the pain, but I couldn't get over the sweet spot or ASW. I'm so tempted to give it another shot, but my time is limited and the Rift just WORKS out of the box.... thanks for posting this for others to see. Maybe you could take it one step further with a step by step guide. so many moving pieces. Steam VR beta, windows MR beta... yada yada... cheers!

I downloaded the steam VR Beta client and edited the file following instructions from this link: https://steamcommunity.com/games/719950/announcements/detail/1652133167137673234 I'm sad to say that it did NOT resolve the issue as you describe above for me. I too noticed the ghosting/stuttering - especially when moving my head back and forth rapidly in the cockpit. I was "upgrading' from a rift to the Samsung and although the visuals were WAY Better in the Odyssey, for me that ghosting issue was a show stopper. Additionally the "sweet spot" in the Odyssey was so small that I had a hard time keeping the headset positioned in the exact correct spot. After a few moments (especially when looking down at the cockpit) i noticed the headset would shift slightly and everything would be out of focus again. I really wanted to keep the Odyssey, but these two issues were enough to warrant the return to amazon. After putting the rift back on the colors are now desaturated and not as crisp, but the smoothness with ASW and the bigger sweet spot were a welcome return. only my .02 cents. I think if I spent enough time messing with the strap I could have overcome the sweet spot issue and i'm sure in time they will fix the ASW, but for now I'm back in the rift.

Thanks a ton! much appreciated!:thumbup:

Great video! that helped a ton. However after deleting the old and pasting the new I hit finish and close out of the edit profile window. Then after I restart VA I get the same message that the "keywords database was updated: apply FINISH steps to update the VA profile. I've tried the update steps multiple times, yet each time VA restarts I see this message in the startup text box. Am I doing something wrong?

Can anyone help me with some sample code to get me started? I've read a lot of tutorials and watched a few videos, but I keep striking out with tweaking the LUA code. I'd like to add additional switches from the clickable cockpit lua for these functions that are missing in the default A-10C keybinds: Add Emergency Flood Off Add APU Gen Power Off/Reset Add AC Gen Power off Left Add AC Gen Power off Right Add Battery power off These switches only exist as On switches right now, but I'd like to be able to discreetly map them to an Off state as well. thanks for helping!

thanks OK, thanks!

OnShape Download Possible? Great Designed Switch Headers. Is it possible to download the STL files from OnShape? It shows read only for me at the top of the page. thanks!

yes! thanks!

I bet your export.lua is bugged. Maybe rename the export.lua to something like export.lua.bak and let SSA create a new one, maybe Vaicom then needs to reinstall it's stuff again... __________________ f4l0 Developer of Simshaker for Aviators

yeah chap actually a young chap or yank you might say.. LOL

Does anyone know how far back you have to go to still have simshaker for aviators working. IIR 2.51 was causing issues. Anyone have any idea?

Also Voiceattack (like for external views, VR Re-center) and the excellent Vaicom for even more ATC/Wingman commands. A button box will add to your HOTAS capabilities and different switches can be learned by touch

LUA Files I always run VA as admin, and I've gone through the motions of rebuilding and replacing all the LUA files. I still can't get it to to work. Vaicom receives commands and beeps in acknowledgment, but wingman/atc never respond. As an added measure I turned back on pilot/player voice and sure enough, even though Vaicom beeps, the player voice doesn't go out - telling me that Vaicom is not sending the command to DCS. I'm at a loss as to what to try next, since all the lua code has been rebuilt from scratch with a clean install.

Sound module is no longer working for me with my butt kicker.. allowed app to update and sound module installed separately but even though it shows the wave file being played my buttkicker does not vibrate in any way.. doesn't work in game either even though jetseat still works. Simultaneous Output is checked and sound module launches.. windows will output sound to kicker so buttkicker is functional just not the sound module

Hollywood, I've tried all the steps you outline for updating LUA files with absolutely no success. Commands are received and understood by DCS, but wingman does NOT respond to commands in anyway. Latest DCS build. Have even tried deleting all LUA entries outlined on page 33 and doing full DCS repair, with VA and Vaicom reinstall/reinitialize. Something isn't working still. Even re downloaded latest 252 Vaicom file with no luck whatsoever. Any ideas? Did a Win 10 update break something. Anyone else having issues?

Same Here I get the beeps and I see the subtitle issuing the command, but wingman/game doesn't respond to anything I say, even though I get the confirmation beep that VA has received my command. Running latest version downloaded from page 1 of this thread.

Count me in... Finally got around to installing 2.5 today (clean install) after migrating my data from 2.2 to 2.5 I don't get any functionality from SSA in 2.5.. Love to hear a fix if someone figures it out?

Hollywood, Enjoying the new 2.5 immensely, but have a question about using just voiceattack with another sim. Once I add the Vaicom 2.5 pro app to voiceattack it appears voiceattack tries to reference it for additional profiles. Is there a way to use a separate profile for another sim without it using Vaicom? I know this is beyond the scope of your product, but thought you might know how to do it? thanks!

https://forums.eagle.ru/showthread.php?t=164892

Just flew a mission in the harrier with Easy Comms On. JTAC flows were not working. I would give the voice command and Vaicom would recognize my voice and issue the correct command to DCS (Subtitle and player voice could be heard), but DCS was ignoring commands. When I used the Options menu and hand selected the same vaicom response the game would recognize the command and continue the JTAC flow. I also had the same issue with Tonopah tower. My command was heard and passed to the game, but it ignored the command until I used the options command and hand selected the command I wanted to send. Hope that makes sense? Update: Just ran through the F-5 Cold start instant action. Same issue as above. I can issue voice commands, they're recognized by Vaicom, Chief connect Air.... Roger Air Connected. Chief Apply Air. Chief says air applied, but nothing happens. If I go to Chief-Options and select apply air, then it works! Seems like commands are being recognized, and maybe even passed to DCS, but they are being ignored unless I select the commands manually from the menu using the options menu. Edit again. F-5 startup. Chief, Place the wheelchocks... recognized... awaiting additional input... what more input can he possibly need?

Thanks! That was it.. Jumped into an old profile to export a few of my custom commands and that messed it up. Restart worked as advertised. So Far this is much better at recognizing my commands and much "snappier". when I went through the training mode following your excellent instructions I noticed windows offering "solutions" to my spoken command with both caps and lowercase word suggestions. like, "Two Engage" or "two engage". This seemed to interrupt my success rate being recognized by Vaicom. Is this normal or a windows "feature" that I can disable :) ?? thanks! :pilotfly:

Hollywood. Jumped into A-10C with no issues on all three radios, but when I tried to cold start the F-5 I'm getting an error in VA Log: "UNABLE TO INVOKE PLUGIN. PLUGIN NOT VALID FOR THIS VERSION OF VOICEATTACK. Any ideas?

Maybe weather has to be below certain ceiling and vis limits? That's the way they work IRL?

I've drastically reduced ghosting by making sure I "Alt-Tab" into the game so it's running full screen vice just running in the window. I still have a few micro stutters/ghosting "glitches", but overall much better when I make sure and go Full-Screen... Placebo? have settled on running 388.59 lately..

Thanks for the helpful and thoughtful reply