Tshark

So can the FSR be used in conjunction with Kegetys shaders and ReshadeVR? Also want to add my thanks to you for your hard work on this thread. It is always my "go to" when I get the urge to tweak my G2.

The fix for me was to go into VA options (the wrench bottom right of the VA window), go to "Audio" and uncheck "Notification Sounds" box top center of the window. I think it got turned on after updating VA.

Thank you Woflman that fixed it! I must have missed that in the guide and never would have guessed it was related. Thanks again

I have a strange problem here. I have a mission I created that allows me to practice against ground, sea, and air targets. I cannot get the F-14 guns to fire in the mission (A/A missiles work fine). I ensure I have loaded the guns (tried both pre-load out and re-arming). The round counter is adjusted. The Master Arm is on, A/A mode selected, and even tried ACM with no luck. The F-14 fires guns fine in "instant action", so I know my controls are set up correctly. In the same self created mission I can use guns in both the F-5E and F/A-18. The AI aircraft also have no problem firing guns. Any ideas? Thanks for your time

I noticed that shortly after I launch a Phoenix, Jester will call out the missile as inbound and yell for evasive. Granted I am new to the F-14B, but I don't recall this happening prior to the new update.

Last night I ran into this problem as well. I have tried all the VoIP settings (restarting each time) with no success. Everything was working correctly in SP with both the F/A-18 and F-14B modules. I was using the latest version of Vaicom with the 32bit VA. Both DCS Open Beta and the F-14B modules are the latest update. The problem arose when I disabled the AIRIO extension to check a setting in the F-14B module. After that, both the F/A-18 and F-14B have the problem. Re-enabling AIRIO did not fix the problem. Updating VA to 64bit made no difference. This morning, while composing this post, I wanted to check all my aircraft modules for troubleshooting purposes. I enabled AIRIO and tried "instant action" with my F-5 module (takeoff) and everything worked normally. I then tried "instant action" on the F/A-18 and F-14B modules (both on takeoff)....no problems. I went back to the same mission I had created, that had the problems, and tried both the F/A-18 and F-14B modules...everything works again. MP VoIP slider is set to "Broadcast Parallel" and the "TX Link MP only" box is checked. I am holding my breath around the Vaicom settings and not touching anything! I HATE INTERMITTENT PROBLEMS! Hope this helps

Might also try Aces High III. Free download and offline play. The VR implementation is pretty good especially the VR keyboard. https://www.hitechcreations.com I have also been enjoying Star Wars Pinball available on Steam. This title can also be played with an Xbox controller.

I bought the "2.0 Ultimate Comfort" set for my G2 from VRBalance. I have worn it on several sessions, each lasting over three hours, and found it to be very comfortable. It eliminated the top strap hot spot I was feeling. It also seems to require less sweet spot adjustment when taking it off and putting it on. I did find that it made me feel a little hotter and use a small desktop fan to blow on my face. https://vrbalance.net/ Hope this helps

Try "Aircar" from Steam. It is free and is a "VR experience". It is not a game, just a hover car that you fly around in a futuristic city. It was designed from the ground up for VR. I use it to test my G2's video, audio, and controllers. You can also plug in an Xbox controller to your PC and use it to control the car. Here is a link: https://store.steampowered.com/app/1073390/Aircar/ Hope this helps

Done. Also using Nvida GPU.

I realize this is an old thread, but has anyone figured out what DCS Supercarrier uses to determine the assigned approach times? My friend and I have flown a custom mission twice that involves a night Case 3 landing. Both times we were given approach times in excess of 40 minutes with no other traffic ahead of us. Does calling "inbound" closer than 50 miles help? Thanks

I am starting to use NVGs in VR. Sometimes the NVG display is the "goggled" mode other times the entire display is green. This has happened in several different missions, both single and multiplayer, with no changes between each play session. Any ideas on what I am doing wrong?

As a temporary work around, I have been using the "Notes" page on the kneeboard with dictation. For instance in a case III landing: 1) Bring up kneeboard 2) Say "show notes" 3) Say "start dictate" 4) With kneeboard still up I call the CV with "inbound" 5) As the CV responds the kneeboard page will switch to the ATC page 6) Say "show notes" to bring up notes page then dictate radial heading, altimeter setting, DME range, assigned angels, and time. 7) Say "end dictate" It is clunky, but does work.

It is a bug that came with the 2.7 update. Vaicom is aware of it and will fix it once ED has patched several other issues with 2.7. I really miss this feature as well. We just have to be patient.

Another company to check out for prescription lenses is VR-Wave. https://www.vr-wave.store/ I have had VR-Wave lenses for over two months on my Reverb G2. Their customer service is the best. The true test of a company is how they respond to problems. I noticed a small defect in the lenses after using them for over six weeks. I contacted VR-Wave and their response was immediate. They resolved my problem with minimal downtime. Throughout my entire experience with this company they never failed to impress me with their outstanding customer service and product!

What would be the best way to transfer my Vaicom Pro/VoiceAttack to my new computer? I will be moving my current DCS beta and the saved games folders from the old computer to the new computer. The new computer will be using the same HOTAS hardware, but of course Windows 10 will be assigning new GUIDs to them. Thanks for your time

Opting out of SteamWMR beta solved most tracking issues for me.

Thanks for sharing this info. Great timing, as I am expecting my new system next week.

I have had similar issues with my G2 since 2.7. I believe this is due to issues inside DCS, as I do not have any tracking or jittery problems in Aces High, AirCar, or BeatSaber. I did not have any tracking problems with DCS 2.5. If you are questioning your hardware I would suggest trying another program that is optimized for VR. AirCar, for instance, is available free from Steam. It is a "VR experience" and not a game. Good for troubleshooting your VR hardware. The SteamVR issue is causing a "critical error starting SteamVR" message when trying to start DCS. For me I found that I had the basic version of SteamVR and the beta version of SteamWMR. Opting out of the SteamWMR beta and going back to the basic version fixed this problem.

Try starting WMR first, then close SteamVR leaving WMR running, then start DCS. For me DCS will start up SteamVR then perform as normal. Hope this helps

I followed SR's advice and started WMR first, closed SteamVR (which opens with WMR), then start DCS. DCS restarts SteamVR and everything works normally. I am using the non-beta version of SteamVR.

Thanks SR. I have the same problem using the non-beta version of SteamVR. This start-up procedure works for me until the issues get sorted out.

Thanks guys! I created the autoexec.cfg file and added the disable track recordings entry. No change as far as shut down is concerned.

I cannot find this file anywhere is saved games or in the DCS program folders. Do I need to create this?

Did a little more testing. With the pagefile adjustments, DCS closes immediately from the menu screen. When a mission is loaded (I am using the same mission...F-18, Supercarrier, cold start, Persian Gulf) it then takes anywhere from 30 seconds to 1 1/2 minutes to shut down from VR. Occasionally DCS will shut down immediately from VR with the same mission loaded (I hate intermittent problems!). Starting from a fresh computer boot does not seem to make a difference. I think there is a memory leak somewhere or the cache is not getting cleared. Still better now than without the pagefile adjustment.