Lange_666

@ Hiob: Could you take a look at the video in stormrider2's post above and explain a bit more what the dude is trying to say. Start around 2:20 in the video. I'm struggling with 2 phrases: 1: "Drag down the top of the curve to your desired frequency". - How do i determine my desired frequency? My 3080Ti has a base clock of 1365 MHz and a boost clock of 1725 MHz. However, the presented curve in my Afterburner graph goes to 1975 MHz from around 1090mV (and is flat from then on to 1250mV). In the video, the curve is dragged down 162 MHz overall but that is based on what? I have seen video's go to -300, most are in between -200 and -250 but on how much the curve needs to be dragged down or what the reference point is is never explained. Or do i need to bring the top of the curve down to my cards boost freq? 2: "Line that up with the voltage you want to run it at and press confirm". - Now all these video's use different values above the curve but how do they determine that value? That is never explained. Also, if i look at the curves in all the video's after they "applied" their choice, most of them (but not all) have a max value that is a bit lower then the max value presented by the default max value but at a lower voltage. I don't have a problem with the voltage value but with the value they move the frequency up again. Somehow i fail to understand how they determine the values they set.

I'm having a problem understanding how to get the reference clock speeds "all" these video's talk about. None of them makes that clear, they all drop de curve down -200 tot -300Mhz. Then comes the part where at undervoltage point, they move up that point particular point to a certain frequency (2:30 in the video above) without exactly telling how they defined that. What i don't understand is how the define that particular frequency. They get by with saying "what you want" "or your desired clock speed". In some video's they refer to the specs of the card, then point to the clock and boost speeds but then set a value that is never near the clock or boost speeds they just talked about. So what's the point then pointing to those values if they are not used? If i put all the video's i watched side by side (even for my particular card) they all set it to a different value, none of them near the clock or boost speed. Based on what then? So how do i determine the clock speed that i need to move up on the new undervolting value?

Or use this and never look back...

I just had a go on the BuddySpike MP server, Syria map with only 4 players, medium to low settings on my end (in single play i have a high setup (not ultra or extreme) and my 32GB got completely filled up although later in the mission it went down to around 29GB. Single player gets to around 17-18 GB RAM, depending on the map. Same for the 12GB VRAM on my 3080Ti, in MP it fills up entirely (on those medium to low settings), in SP (high settings) it gets by with around 8GB. Older maps like Caucasus or NTTR get by with 7-8 GB of VRAM. DCS for that matter is really RAM hungry, if i take MSFS as comparison, i barely get over 5-6 GB of VRAM and around 8-9GB RAM on standard settings. It all depends a bit on what happens when the RAM (and VRAM) for that matter get filled up (on 2560x1440, 60FPS locked). When everything fills up, i'll get stutter.

Instead of waiting the change may come some day you can make your life easy and get your frustration about switching out of the way: For example, you can have 2 DCS start icons, one for 2D and one for VR with this in the command line: "Drive:\Your DCS location\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR *You need a space and two dashes. or Use the app speed-of-heat proposed, is a super app to get DCS started in any mode you want without all the hassle you encounter.

Still on V42, won't update to V43. All info right now, like updating your headset is for Quest owners to get around the problem, Rift S is left in the drink and there is not much to find (and since the Oculus forums are a jungle to find stuff, i won't put my time in in). I did read that a possible cause was the code regarding updating to a Meta account (mandatory from 1/1/23 onwards). I'm still on my Oculus account, won't update before 1/1/23. I didn't try any other game or running without a game when i had V43 installed, my only concern was DCS because that's 99,5% of my playtime.

Edited my post, satisfied?

Not in my collection: - Mi-24P Hind - Gazelle - Mi-8MTV2 - FW-190A8 - Mosquito - Yak-52 - I-16 - JF17 - Christen Eagle (no idea what this is doing in DCS) - MIG-19P - NS430 - Mirage F1 (on the maybe buy list) - Most campaigns I own: i play (Yes: play or played in the past, No means never played). - FC3: - A-10A: Yes - F-15: No - Mig-29: No - Su-25: No - Su-27: No - Su-33: Trial landings on the Kuznetszof - Combined Arms: No - A-10C (and II): Yes - ASJ37 Viggen: No - AV8BNA: No - C-101CC/EB: No - F-5E-3: Yes - F-14: No - F-16C: Yes - F-18C: Yes - F-86F: Yes - Hawk: Yes (but is no more) - L-39: No - M-2000C: No - MIG-15Bis: No - MIG-21Bis: No - S-25T: No WW2 - FW-190D9: No - Bf-109K-4: No - Spitfire: No - P-47D: No - P-51D: No - TP-51: no Helo's: - UH-1H: Yes - KA-50: Yes (there was nothing else back then) - AH-64-D: No really... Mods - A4: No Terrains: - Caucasus: Yes: offline/online - NTTR: Yes: offline - Persian Gulf: Yes: online - Syria: Yes: online - Normandy + WWII Assets pack: No (still have to see one of those assets, lol) - Channel Map: No - Marianas: No (nice looking but to heavy on my system) - South Atlantic: No (far from finished) -----------------------

Since the latest update 2.7.17.29140 (and) using a Rift S there is a black screen between the splash screen and the game screen that stays black until i put on my headset. If one doesn't put on the headset, the monitor stays black looking like the game has crashed, hung or stopped loading. Before the update, the mirror image was visible on the monitor the moment the splash screen was gone. Probably related:

Nice update on the progress, count me in on the rage of testers, i have plenty of free time.

Update: The game doesn't seem to mirror the VR screen to the monitor as long as the headset isn't fully active. Just tried a few times, screen stays black until i put on my headset (Rift-S), seconds later the mirror is there and the black screen is gone.

DCS log: in VR it hangs on APP: Screen: MainMenu dcs.log

I'm having the same problem, Windows (10) is up to date. Only happened after the 24/8 update. Pancake mode works however it also takes sometimes quite some time before the game is loaded with a black screen in between the splash screen and the actual game screen. In VR it sometimes goes through to the game screen, most of time it hangs in the black screen. No mods installed, worked fine before the update. Guess this is the same problem...

I don't, i just used this link ( https://www.oculus.com/rift/setup/ ) which offered OculusSetup.exe which in turn installed V42 on my system. I blocked the future updates so V42 will stay there until the problems with V43 are solved.

When a new update is available, the software will tell you there is an update is being downloaded but if you then check the notifications it will be marked as queued. It will stay that way just until you remove de blocking folder/files. On the next restart then the download will take place.

For me re-installing brought back v42 but it directly offers v43 when run for the first time (and luckely also the option to postpone so i could block the update). V42 works nice.

PC software, i have a Rift-S

I have not been on PTC since like v16 or v17 and i was not on PTC either with v42 installed when the update to v43 got offered.

Updated to the latest Oculus release today, going from V42 to v43. Big mistake, after v43 was ready i went in for a little multiplayer and got big stutters every few seconds (it was playing nicely on v42 before). First thought it could be the server (quite a few people on), quit and started a simple single player mission, same problem. Oculus doesn't offer a revert option so going back to v42 was out of the question the only option was to delete and re-install. After re-installation i found that the software reverted back to v42 and was ready for an update to v43. I declined (postponed for 4 hours) and tested v42, no stutter. Reloaded, ran de update to v43 again, stutter came back. Uninstalled everything again, ran the setup which installed v42 again with he question to update to v43 or postpone, postponed, stopped the software and used the update blocking trick to block Oculus from updating to v43. All is good again now... A lot of people on the Oculus forum mentioned stutter/flickering problems after updating to the v43 beta. But somehow this wasn't adressed and the bug made into the release version of v43. A bit more of this and these guys are on the same level as Garmin. Prevent Oculus Client Updates.zip

It's not possible to zoom slowly in VR, only toggle zoom and spyglass are available.

Sure, that's the basic to set controllers up.

Thx for the heads-up. Back In Black

Somehow, i miss that "Language - Theme - Privacy Policy - Contact Us" part. This is FireFox, same on Brave or Edge.

See topic tittle...

Can only refer to the Rift-S but starting either the Oculus software of the Tray Tool first doesn't make any difference. But i have the habbit to start the Tray Tool first.