Cutter

Hah! Thanks @MAXsenna, that did the job!

Hi, not sure if I'm just being dumb but... I'm trying to buy a campaign as a gift but there's no "BUY" button, just a "Requires another product" message. I do see a "BUY" option on modules. All my DCS content is on Steam, but I'm buying the gift for my brother who has the non-steam versions. Is the e-shop detecting I don't have the appropriate non-steam content?

My son, who's (at least) a next level IT professional compared to me, appears to have solved this issue for me. He did some research and found the solution on another forum, that I see has been noted above by @StiC: TLDR: Went in to BIOS and switched from PCI-E 4 down to 3. Longer version - I think the bandwidth management of the B550 chipset (or maybe its implementation in this ASUS board) is causing the issue. I know that the manual says you can't use certain combinations of PCI-E slot and also use both SSD slots without degrading the potential bandwidth of something. It's probably the nature of the cheaper chipset that it has to divide up a reduced performance across the demands of whatever you plug into the board. By reducing the GPU's PCI-E slot bandwidth requirement it frees up room for other components. My son found the solution by looking at the Windows and DCS logs and noting the failure codes, then researching them to see what they mean't. There were also a number of "textures not found" errors preceding the crash, which I don't fully understand as that seems like a memory issue. But, confusion aside, it seems the PCI-E bandwidth limit has solved this for me. I've no idea why VR worked fine for me for so long and then broke so recently.

Thanks @speed-of-heatI'll try it anyway. I'm going to knock off for tonight, but I'll just list the other things I've tried - including brief success: I then disabled the old Oculus devices as they're not used currently, including in "Sound, video and game controllers" (this removed the devices from the "Audio" section); No joy. Next I removed all my gaming peripherals except the G2, to see if there was a driver conflict (I set up a keyboard shortcut to re-centre the VR). Same result, so I moved on to rolling back WMR from "open beta" to "None" - and it loaded OK. I was able to sit in the F-14 cockpit for the first time! Alas it was short-lived; after several minutes I looked down left and it blue screened in the G2. The area in my room I was looking at is pretty dark, so the G2 sensors might have been unhappy. Being scientific about it I changed WMR back to open beta but again it closed WMR before the cockpit ready screen. Same with the "LNG_beta". So I went back to no beta and it still wouldn't load - so that was disappointing. Enough for now!

Alas, the pagefile change didn't work. I then turned off power management for the other USB devices in the "Universal Serial Bus Controllers". Looked at what changes happens in Device Manager when WMR is ON or OFF. These are the only changes I could find: Audio section - WMR off Audio section: WMR on Monitor section - WMR off Monitor section - WMR off

Thanks for the suggestion @speed-of-heat My current pagefile (System managed) was 10752 MB (10.5 GB) I've changed it to Custom size: Initial size: 32768 MB (32 GB) Maximum size: 65536 MB (64 GB) and I'll give that ago...

Thanks for the suggestion @edmuss I've checked and Hardware-accelerated GPU scheduling ("HAGS") is OFF. And referring to above posts I've just disabled the Power Management "Allow the computer to turn off this device to save power" for the HP Reverb Virtual Reality Headset G2 in Device Manager I've also done this for: 2x Generic SuperSpeed USB Hub 5x Generic USB Hub 3x USB Root Hub (USB 3.0) ...and I've disabled "Selective Suspend" for USB Settings in Control Panel/System and Security/Power Options/Edit Plan Settings. Finally I've opened WMR settings and set "Sleep Time-out" to Never. Tried the above settings but the results are intermittent. At first nothing ran in VR, including the F/A-18 I've been playing since I began DCS, But gradually I was able to load everything (including the A-10C II) but still NOT the F-14A/B. I also had a couple of messages saying SteamVR couldn't see the G2 headset, which I fixed by unplugging and re-plugging the unit. Looking at Device Manager, even when the WMR stops and seconds later the VR window gives up and dumps me back at Steam, I can see that the G2 headset is still seen. It has NOT disconnected after all. I'll continue looking at this tomorrow - I found a bunch of "USB Input Devices" under Device Manager/Human Interface Devices that still have Power Management set to "Allow the computer to turn off this device to save power", so I'll try them. Also I'll flush the caches and let them rebuild. Might then step back from open Betas of SteamVR, WMR and DCS.

I have the G2 and, after initial problems setting it up I've been mostly fine (I had to get the "new" cable because the headset wasn't stable in "Device manager", the USB connection kept looping between detected and not). But... I got the F-14 a few months ago and it won't run in VR. - I launch DCS with SteamVR using WMR - Loads up the menu OK - I select F-14 cold start in the Caucasus - It loads up to the cockpit ready screen - I select start and immediately I get a blue screen and the WMR window closes. The on screen view of the VR remains momentarily and then closes too. - I'm left with the Steam library window with DCS stopped. I've tried multiple times with the same result (The F-14 will load up in desktop mode but not WMR VR). Sometimes I get a message that WMR cannot detect my USB device (The G2), so that does suggest it has disconnected from "Device manager". Recently I added the A-10 II and have a similar problem; it'll load up and I can get past the ready screen into the cockpit but after a few seconds I get the Blue screen/WMR window closes/Desktop repeat of VR screen closes. I've tried my other modules (I used to fly only the F/A-18, bought the Apache a while ago and have also just got the UH-1) - all these load into WMR VR without this issue. [Also note I'm running an AMD 5600X in an ASUS ROG STRIX B550-E GAMING, 32GB RAM, with an MSI GeForce RTX 3070]. It doesn't make sense to me that AMD are responsible, and that WMR, SteamVR, the G2 and Windows 10 are also common factors where some modules work and others don't. It's got to be something different in the individual aircraft coding that doesn't like something in the system that works for other aircraft. But then, although 3rd party Heatblur developed the F-14A/B the A-10 II is by ED themselves, so the coding should be good. I'm guessing other non-Intel setups can run these aircraft on a G2? I'll have to look at other factors in my setup.

The VRFree webpage is gone. It appears this company/product has disappeared, along with several other varieties of glove, according to a "Ten best VR gloves" listing from 2018 where most are now crossed out. There is a $2000 option for the rich still available, but no sign of this technology being available for the rest of us anytime soon.

So, first of all I'm glad I found this topic as I've had this issue appear last night; same as above - the "Can't run, Important files are damaged: Please, repair. Check dcs.log for details." === Log opened UTC 2021-11-21 15:10:34 2021-11-21 15:10:34.112 ALERT SECURITYCONTROL: Can't run Steam! 2021-11-21 15:10:34.116 INFO APP: Command line: G:\SteamLibrary\steamapps\common\DCSWorld\bin\DCS.exe 2021-11-21 15:10:34.116 INFO APP: DCS/2.7.7.15038 (x86_64; Windows NT 10.0.19042) 2021-11-21 15:10:34.116 INFO APP: Application revision: 195037 2021-11-21 15:10:34.116 INFO APP: Renderer revision: 22490 2021-11-21 15:10:34.116 INFO APP: Terrain revision: 22438 2021-11-21 15:10:34.116 INFO APP: Build number: 687 2021-11-21 15:10:34.116 INFO APP: CPU cores: 6, threads: 12, System RAM: 32694 MB, Pagefile: 8704 MB === Log closed. Before reading this post I uninstalled DCS (except the Mods folder with it's 200GB of dlcs which would take me a day to download - I moved it before uninstalling via steam, then replaced it). I then re-installed with steam, which took several hours overnight. Trying to run DCS just now has given the same error messages. Having read this post I was a bit confused, as I opted into the DCS Open Beta ages ago. But checking it again I find it is not selected - when did that happen? Is it automatically de-selected when the Stable release catches up with the Beta? Well the 2GB of Beta has just downloaded... and it works! Thank you ED.

I've just been reading about this on another post on the forum: tl;dr version go to http://www.avweb.com/news/pelican/Pelicans-Perch-16-Those-Marvelous-Props-182082-1.html for the suggested explanation. It worked it for me!

I don't know about adding a voice but one thing you can do is make a kneeboard checklist - that's what I've done (although mine is customised to me and includes notes on Voice Attack settings I want to set up, so I can't really offer it to you as it's not finished). - I've seen a pretty comprehensive kneeboard posted in the user files that is available to download right now.

I'm setting up the controls for the Mosquito in VR and want to create a custom view for the fuel levers behind the seat. When I created custom snap views outside VR, because it was easier, and saved them I found they were not carried across to VR. I tried again by running VR and just moving the headset around by hand to where I wanted it, but it seems the best I can do is save the location my head is positioned in the cockpit - but it is still looking forward. So I've now got a snap view to a position under the armrest and I have to turn my head over my shoulder to see the fuel panel. Is this normal for VR or am I doing something wrong? @Gun JamI agree the initial head position is too high and to the left. Just switch the gun sight on and you have to crouch in your seat to line it up (without using the built in snap view). I'm going to try your system for saving a corrected initial view. Am I wrong in thinking the F1 cockpit view is different from the Numpad 5 default centre view? (Snap views are just there while you hold a button right?) Edited: Yup! I like your lua settings.

I'm looking forward to this too. I forget where it was reported but I it was said that the coder working on the LITENING pod had to finish that and then the DTC was the next job. So with any luck it's in progress. Don't know if you've seen it but in the "mission" lua inside a .miz there are already lines of code specifying the data cartridge - they just don't have any data in them yet; ["dataCartridge"] = { ["GroupsPoints"] = { ["PB"] = { }, -- end of ["PB"] ["Sequence 2 Red"] = { }, -- end of ["Sequence 2 Red"] ["Start Location"] = { }, -- end of ["Start Location"] ["Sequence 1 Blue"] = { }, -- end of ["Sequence 1 Blue"] ["Sequence 3 Yellow"] = { }, -- end of ["Sequence 3 Yellow"] ["A/A Waypoint"] = { }, -- end of ["A/A Waypoint"] ["PP"] = { }, -- end of ["PP"] ["Initial Point"] = { }, -- end of ["Initial Point"] }, -- end of ["GroupsPoints"] ["Points"] = { }, -- end of ["Points"] }, -- end of ["dataCartridge"] I found this because I've just started learning INS/GPS weapons like the JSOW and wondered if there was a way to get the info from my stored waypoints in the Mission Editor into the game directly for PP attacks, without the button pressing. Seems this is a common wish as there is a remarkable hack with "Waypoint Editor" using OCR to read your F10 map and then press the UFC buttons for you. Pretty bizzare to watch the ghost in the machine!

I don't think this is the same thing, from what you said about different aircraft having different things happening but.. I had a weird zoom in to the HUD like you describe which I couldn't figure out for a while but was actually my own stupidity; I have a Thrustmaster T16000 joystick and when first trying to get to grips with HOTAS I had used the slider on the joystick to be the zoom, because I thought it would be easier to find from inside VR. I didn't need to use it for throttle as I have a separate CH throttle unit. As I got more used to DCS and the controls I set the VR zoom to a button on my throttle and then forgot all about the slider on the joystick. You can guess what happened, I knocked the slider while in game and all I could see was zoomed in! Resetting zoom didn't work, nothing worked, it just jumped back in to zoom. Unplayable. I forget how long it took me to notice the slider and remember. Arg!