Maddaawg

@The_Nephilim how are you measuring Frametimes? I have heard the DCS version is not accurate and when looking at it, the numbers jump so much it's kind of hard to see what it is actually showing. When using the overlay from OXRTK they are vastly different than the DCS version and according the OXRTK website, not accurate if CPU bound. DCS often shows me CPU bound but also often not. Since I moved to VD, I stopped worrying about the numbers because it looks good, but then I'm not competing on a server. I am also dealing with F10 crashes and want to see if frametimes are related to this.

This has been happening for a while now and is making DCS unplayable and I see that others are complaining of this issue and there was a closed thread from last year on the same subject. I'm using a Quest 3 in VD but I have had it happen using Meta Link wireless and wired. It always happens when using the F10 map, if I don't use it everything works fine. Doing the same mission that I created, if I preload waypoints using scratchpad in 2D, I can use that for the mission. This does not occur in 2D and doesn't always happen in VR, but the more often I use F10 the more likely it is to happen. The last two attempts it has happened almost immediately. The only mods I have running are VR Loading Screen Fix and a saved game mod 476RangeTargets. The issue predates these mods and the saved games one is not in use during this mission. I installed the VR Loading Screen Fix in hopes to fix this issue, and it didn't. The issue begins either in F10 or just after using it with irregular frames/distortions/flickering that increases until the headset freezes. Most of the time the game continues in 2D, but sometimes it also crashes. Most of the time the headset must be rebooted to have it functioning again, but sometimes just quitting the game fixes it. Attached are the DCS.Log and the Track file in case that can help, along with screen shots of my settings. My settings in VD are Godlike, but I have tried lower resolutions, and using HVEC and VDXR. I have also done full repair of DCS. My specs are in my signature. I run Process Lasso and QuickCPU, and two OpenXR apps: HTCC(Hand Tracked Cockpit Clicking), and XRNS(NeckSafer). And also Scratchpad. Edit: I was able to run this same mission for 2.5 hours without touching F10, landing and rearm/fuel and use my previously entered wpt's to target additional units. This went off without any issues until I quit and hit fly again, and it locked up on the mission start screen. dcs.log frozenhmd.trk DxDiag.txt

I'm mostly using the one I installed "VR Loading Screen Fix" to fix that loading screen, it gives my eyes a relief from that cross-eyed blinking hanger.

OvGME is no longer supported but I believe the same dev is supporting a new version called Open Mod Manager. Give that a try, but in the mean time I think you can just open the zip file and see "Your Drive"\Eagle Dynamics\DCS World\Scripts\DemoScenes is the path it needs and can copy the file sceneVR.lua to DemoScenes. So the main DCS World directory is the correct location. Save the orignal sceneVR.lua in case you need to repair it, or use OMM. I just used OMM myself to install VR Loading Screen Fix and it worked perfectly. DCS Forum Page on Open Mod Manager VR Loading Screen Fix Open Mod Manager YouTube Video on installing and using OMM

Thank you for the explanation of DCS mods. The need to remove them because? Can't OMM just put them back after the update or is it because DCS will have issues.

I didn't know what I was trying to achieve, because as I asked to start with, I didn't understand how DCS mods work. I've used MO2 for Skyrim for years and that tool just handled the work for me. My basic understanding was to install into the DCS directory and to me that meant the DCS World/bin-mt directory. Now that I understand that some mods are just put into the saved games folder and most mods have to be put into the actual directories with DCS World and overwrite parts of it, and that is where tools like OMM come in handy. Thanks for the app, its much appreciated. I am working on watching the video today, but I have also seen another manager called SLAM that uses symlink. I have to figure out the pros and cons of each. Edit: I got it working now just fine for both application mods and saved games which while not necessary, it is still a better organization.

Me too, usually if I exit and restart without rebooting the PC.

No it shouldn't, and I too have been having this issue for a couple of days. Mine occurs right after using F10 but not evey time but eventually in a mission the more I use it the more likely it is to happen. I've been searching for this on the forums and there was a reported bug with F10 last year with the same description. That was thought to be a VRAM issue. Most seem to report it on just a couple maps one of which is Syria where it is occurring to me on a mission I created with minimal assets launching from the SC. When I run without using F10, I have no problems. I intended to add some more ac to the carrier and not use F10 to see what happens. Mine usually locks up after it begins leaving F10 and looking around, the more I look the worse it gets. Water in the lens is a good analogy.

The Meta software login? You should contact Meta support; they are usually pretty helpful. I only get this when I switch PC's.

I just started having Quest 3 freezing too. It starts stuttering and then I know what's about to happen and it locks up. It's kind of like the screen is tearing/freezing and increases the more I move my head until it just freezes. Usually, DCS is still working and the last frame frozen in the Q3 headset but not every time. I had this randomly happen with Meta Link but now I am on VD and I have not seen the issue since changing over and it's been happening since yesterday and the only change I made was to try Open kneeboard again, but it was giving me issues of not seeing my keyboard commands. The headset has to be rebooted to clear its screen but often I can still close DCS with a mouse but this last crash I had to use task manager. Another thing I noticed is that it usually happens right after using F10. I have noticed that when returning to F1, there is a delay of 2-3 seconds sometimes. Both of the last two crashes happened after I completed the first leg of a mission, landed and rearmed. Then while on the tarmac using F10 to get my next targets and when returning to F1 the wobbling screen begins and increases until the crash. This also happened at the start while on the carrier and returning from F10 though I put 3 other F18's on the carrier so I thought that overwhelmed my system. Here are some screenshots and log file: dcs.log

Thank You

When I was looking at a YT video on making a mission with the supercarrier, the instructions showed him adding a template for Super Carrier Group, but I don't have this template. YT Video

To be clear, you mean OXRTK and not OVRTK? They both exist for different applications. Your title says OpenVR and I assume you mean OpenXR because DCS is native OpenXR but I think the Steam version is OpenVR. There are also some issues with scheduling on the Ryzen 9 7950x3D that Windows causes and use of the 3d cache. I'm on Intel right now and don't remember the fix but probably a tool like Process Lasso will restrict DCS to the correct cores that have the best 3D cache access.

VD doesn't work with a cable. You have to chose either Meta Link with or without a cable OR VD which is wireless only. Also, your not trying to compare your 2D monitor to VR are you? You will give up clarity in VR and gain realism.

At 72hz it will be a PD of 1.3 as in my screen grab and resolution of 5408x2912. From there I recommend your first try is to use the VR preset and no other tools or changes. Then work upward in your settings. I use VD with a dedicated 6e router, and I will post my settings for you when I launch that PC. My GPU is less capable so you should be able to get at least similar results. Make sure you're running from an SSD or better yet an NVME drive. Kill everything else running that you can. I use Process Lasso to prioritize DCS and Quick CPU for the processor. Mines Intel, so I have to eliminate CPU parking, and I am not sure for AMD. But QuickCPU will let you max your CPU. Process Lasso will let you use a few cores just for DCS and then the rest of the processes can go to the other cores. You can also set the affinity of DCS to high. You're likely CPU bound with that GPU, so helping out your CPU is a good idea. EDIT: As I posted I see you posted your settings. You can use either Meta Link or VD, not both at the same time. The cable does nothing except charge your headset at a slower rate than you use it. I use a battery headset just for that reason. Follow Qcumber's recommedations on Godlike and bandwidth. The VD settings affects how VD looks while streaming is what affects you headset. You have that at 90hz, I recommend you set that for 72hz

I don't see hand tracking listed as a feature of the Super. They list the MR plate as compatible, but it doesn't yet exist as a product, and I don't know that it includes hand tracking. I have a PointCtrl on order that should be ready around the first of the year along with the Super, so I may get one, but I don't want to give up hand tracking. I feel like the Slugmouse is a better choice between it and PointCtrl because of its ease of use and cableless design but I won't really know until I have both in my hands.

Yep, I didn't notice that it defaults to HVEC.

In VR I settled on '2' for the ticks. Can decimal numbers be used, like 1.5? Targets are finally being hit accurately.

I've actually not had any issues with the JDAM's in the past, just the scratchpad entry. I have in the past just copied and pasted the first waypoint and started on 1 waypoint early. Then I get my correct waypoints and enter the JDAM info using TOO 1 and TOO2 and all 8 will hit accurately. I'm sure it was just because I was in 2D and not going over my INS settings since my HOTAS and keyboard are setup for VR, I can't even look around the cockpit.

So, my first try was 100 and that was so slow I went to fix something to eat, and it was still on the first waypoint when I got back. So, I changed it to 3 and that worked, from 2D. However, the JDAM's were way off now. It might have something to do with my setup since I am starting just outside the range of the JDAM. I'm using active pause, so maybe that is screwing up the settings. I tried it twice and zoomed in all the way on the targets for the 2nd try and had the same results with the JDAM's going all over the place, not even close misses. The second volley of 4 JDAM's I took it off of active pause and still failed. I did confirm the GPS of the first 4 waypoints once entered and they matched scratchpad. I'll have to check but maybe INS is not set correctly from a flying start. I'll try a full run from VR in a little while.

So I was filming it in 2D, but I am usually in VR. I slowed down the capture to 1/10th speed and it is not pushing in the OSP buttons on the first WP until altitude. I'll change to the 100 and give it a try in 2D and then VR. Maybe VR can have a shorter tics?

So, I removed all previous files from Saved Games, including the ScratchPadConfig.lua in Saved Games\DCS\Config, and the scratchpad folder with 0000.txt, the lua in scripts/hooks and the scratchpad folder in scripts. Then used the Draken35 download and the new 02-QWERTY KEYBOARD and LOAD COORDINATEs.lua. Still no joy. When I watch it loading waypoints, I can watch the entries in the UFC and the first ones are all ERROR, then it moves onto the next waypoint and enters them from there. I have noticed it is entering the feet, but not the coordinates. 20240819_093304.mp4

That is the version (0.7.0.240617a) I have and downloaded it from Draken35. I will look at the other two, thanks.

Scratchpad is often skipping the first entry in the FA-18. A couple of times it did work, but I don't know what I changed to make it work. I use it in VR and get 10 GPS locations from F10 map, then when I set up the DDI into HSI and data and select precise I select a starting waypoint such as 10. Then when I click to import the waypoints, it will skip the first one, in this case 10, but then enter the rest correctly. So, if I had 10 waypoints, I would get 9. To manually solve it, I duplicate the first waypoint and start one waypoint earlier, so in this case waypoint 9. Then 10 through 19 will import.

So, you are using hand controllers? I see so many reports of issues with them. If not, uncheck use hand controllers.