Chipensaw

Good morning, Any update with this issue? I have the same issue with Quest 2. Issue started with update to 2.8. Specs and setup below. 5800X3D 3070ti 32G RAM Dedicated M.2 SSD for DCS No mods, clean install. No 3rd party VR programs in use, FXO & Meta deleted. PD1.3, textures high, terrain textures low, shadows off, MSAA 2X, AF 16x, clouds high, other non related settings available upon request. @BIGNEWY 9L asked me to reach out to you regarding VR performance with my setup.

What do you think? Better performance, worse or no change? Did you fly this mission before upgrading, same track file etc?

Sorry for the basic question but first things first. Are you sure guns is mapped correctly for your HOTAS? Can you post a picture of your HUD when gun mode is selected?

+1 for what vision45 says. Here is a user with real world experience justifying additions to NTTR. @BIGNEWY @NineLine please consider expanding NTTR. I would gladly pay for an upgrade. Thank you!

+1, I thought it was me till I read this thread. Very washed out, Global lighting is very bright, I have lowered gamma from 1.9 to 1.7.

Hello Haptor, Yes there is a working IFOLS but as an example I love the overlay due to my Rift CV1 resolution, the CV1 screen door effect and my eyesight not being what is used to be when I was younger! I believe you will be able to move the overlay to a different location and disable if needed.

I would be happy to fly with you sometime as well if you like.

Practice, practice, practice. What I try to do is incrementally adjust nose up trim. What I mean is, a couple of bumps, allow airspeed to drop, couple more bumps etc, etc., until I am on speed / AOA. Extend out a little farther past the boat before entering the break. If you break at 0.7NM normally, extend to 1NM or 1.2NM. Once you get it down you can close the distance back up. Don't be afraid to give the stick some input as well to keep your nose down. All this along with throttle management. I am no pro by any means, still learning myself but this helped me.

Swiftwin9s wins! Swiftwin9s is correct. You have no signal from the Tacan station.

I agree, WIP. I am just happy it comes off the rail consistently now! ED will get the bugs out of it. :thumbup:

Admitting you have an issue is the first step. I feel for the support staff and the number of problems they encounter which are self inflicted by the user but I get a little aggravated when they always lean towards a user created problem, especially when it literally occurred right after an update.

Hello, Well I have closed my case with ED. At first I was leaning towards the "Mods" folder as the issue. Partly because ED support was leaning that way but I can confirm this is not 100% the issue. Although I can magically connect to online servers, the connection times are slow. ED wants to point fingers at connection speed, server ping and server load. The last one I can get onboard with, the first two I can confirm are not the issue. My gut tells me they have reintroduced the connection speed bug we had many months ago, plus the amount of users flooding the online servers to fly the F-14B Just my thoughts, Jay

All, Issue for me and I suspect others is the "Mods" folder under Saved Games/DCS Openbeta/Mods/ I removed this folder and saved to my desktop for testing. Connection issue has been fixed. I will narrow it down to what mod is causing the issue. If you try this and your connection issue is rectified please report back. Jay

Hello, Nothing concrete yet but try disabling all mods and perform a DCS repair. Curious if this fixes some of the connection issues? If you do please report back your results!

I inserted the autoexec.cfg file which appears to enhance the log file information. After running DCS and attempting a connection, which timed out, I attached the new log file. I will update as I hear word from ED. I would highly recommend everyone files a ticket with ED. This will move the issue higher up the more tickets are filed. Plus everyone issue maybe a little different. Cheers!