kelmcguir

I just did a very thorough deletion and reinstall of steamVR and that seems to have solved the issue. I'm not sure what changed in steamVR to cause it.

This just started this week for me. I have a Vive Pro 2 and it was working without issues. I am getting really bad screen tearing but I haven't changed any settings recently. I tried re-installing steamVR, Vive console, and DCS. I deleted the shaders. I changed settings. Tried MT and ST modes. I thought it might be my headset, but my other VR games work just fine. I am not using any mods at the moment. AMD Ryzen 5950x RTX 3090

I am setting up a multiplayer mission, blue v red. At one base there is a B52H bomber. If red captures this base then it can take off and bomb a certain blue base runway. The same thing can happen for the blue team if they capture a separate base. I have the B52H set with late activation to take off on runway. If the correct coalition captures the base the B52H group is activated and then it should take off. The trigger is Once > Coalition has airdrome > activate group (B52H). This part works. However, the B52H just sits on the runway for 1 hour and then decides to take off. Why is there a delay of 1 hr before it follows its waypoints? Why doesn't it take off as soon as it is activated? Also, instead of the above, is there a way to have the B52H just sit on the runway and then when the correct coalition captures the base they get a new radio command to tell the B52H to take off and then it follows its assigned waypoints? Thanks!

What is the indicator in OpenXR Toolkit that DCS is in OpenXR mode?

Tried that, didn't work. Should DCS show up in the Enable OpenXR Toolkit selectively for each application section? (see image).null

Ok so I tried: 1) In the main menu 2) In a plane 3) Made full screen using alt-enter and trying in the menu and in a plane Does not open still. Did I miss a step in between the ones I listed above? I followed the guide except of course for the WMR stuff since I have the Vive Pro 2.

I cannot get OpenXR Toolkit to open when in VR. So first I put the openvr_api.dll file into the bin folder, then in OpenComposite I click set to OpenComposite. In Configure I have DCS as Always Use OpenComposite. Next I open the OpenXR Toolkit and then I launch DCS through Steam. I get to the main menu in VR and try ctrl+F2 but OpenXR Toolkit does not open. I am using the Vive Pro 2. Does OpenComposite, OpenXR, and OpenXR Toolkit not work with the Vive Pro 2 and Steam?

PC Specs: RTX 3090 ftw3 ultra, AMD Ryzen 5950X, G.Skill TridentZ 128 GB 4300 MHz, Samsung SSD 980 PRO 2TB M.2 No mods used, but I do use Reshade.me version 5.1.0. I haven't had any problems from reshade.me. Even after I installed the DCS update I didn't have this stutter right away. It developed over time. It's to the point where looking to the left or right completely freezes the game, drops to the grey screen for 5-10 seconds, and then DCS comes back.

Since the new patch, my VIVE Pro 2 is getting large stutters that are more like screen freezes, and the DCS VR loading screen appears (often times going to the Steam VR grey screen) and then 5-7 seconds the game continues. I verified file integrity, but that didn't help. I am not having these issues in any other VR game, so it is DCS specific. Could be a Steam connection to DCS problem, but it gets worse over the course of a mission or gameplay time.

I installed this mod and Kegetys and it works in single player. I couldn't get into a server with it though. Does it not pass the integrity checks?

This is my first time hearing about Reshade CAS. I found the AMD Fidelity FX CAS. Is that the same thing you are you using? I just got the Vive Pro 2 and it's great so far, but I'd like to try the Reshade with it. Where can I find it and how do I install it for DCS? Thanks!

Sacarino, that's a good thought and I tried that. I had it on xmit, rec, and stdby. Even when the ECM is not emitting, my AIM 120s (especially in TWS) failed. This last attempt, it took 5 120s to kill one Mig-29A at 10-20 miles.

It's not just you. I just put up an ace Mig 29A with no loadout and tried fighting it one-on-one with 6 120s. Every time I am at 20,000-30,000 going about 400 knots and fire my first 120 around 20 miles, then 15, and then 10. I then switched to AIM 9s and shot 2 at him within 3-5 miles. Nothing hit. He either notched perfectly every time or my missiles went dumb. I tried that about 10 times. My lock kept dropping. I even tried TWS and he immediately takes evasive maneuvers even though he shouldn't be getting a locked signal. I then tried waiting until the In LAR switched to flashing SHOOT, but I had to get within 6.5 miles before I saw that even though we were on a head on course approaching at 1000+ knots. I launched at 6.5 miles and my 120 still did not hit. Something is definitely different, at least fighting the ace Mig 29As. I even tried a couple of dogfights with it and all of my AIM 9s missed, but he was able to get on my six and never leave. This is the first time I haven't been able to kill an AI Mig 29 and to get completely owned by it. In the past I've been able to easily get AIM 120 kills farther than 30 miles and AIM 9 kills in dogfights. Not anymore.

in the F/A 18C, the TDC slew controls the radar cursor position on the A/A radar attack screen and the radar elevation controls the radar elevation on the AZ/EL screen. However, when I go into an ACM mode (i.e. bore, HACQ, VACQ, or WACQ) and then back to a BVR mode, then the TDC slew controls both the radar cursor position and the radar elevation on the radar attack screen and the AZ/EL pages simultaneously. Is it supposed to do that?

@Dave317Do you mean like in 2D where the rain droplets move across the canopy looking more realistic? Are they working on that for VR? Because right now the droplets just kind of stick to the canopy and don't go anywhere.