Wali763

Hi. The problem is, that once below 45 Im out of motion reprojection and everything gets a bit jittery. So its actually a visible difference between 40 and 45fps, especially when looking to the side. And if the GPU were maxed all the time, Id be much less often below those 45fps. Actually with my current low settings only being low should drop the fps below 45fps. Looking at my pic from before, one can see, that in that situation even I have GPU-frametimes of ~15, that should result in someting like 60fps, I actually only have 35fps, hence no motion reprojection and a jittery image...

Addition to above: Gamemode and Hags is off. Motion vector on and off is the same low GPU usage.

Hi. Testing a ReberbG1 right now. Normally Im still on Monitor/TrackIR. Plz look at my fpsVR. I have (with my low settings) good frametimes of around 15ms and also CPU frametimes around 10ms. Doing other flights I dont see often CPU-frametimes close to 20, let alone above 20. So to my understanding (CPU-frametimes lower than 22ms), there should be no reason why my actual FPS (using motion vector always active; but its same same when turned off) that low or my GPU is not maxed. Often I have 45fps, but quite often it drops to 35 with no reason I can understand. I somtimes see GPU-usage in the 90s, but much more often than that its around 60 or 70...... When on Monitor/TrackIR (and the fps-cap of 60 is off) I have consistent 98 or 99% GPU usage. Running a 5600x and a RX 6700XT at stock with 32GB Ram and all off SSDs in Win10. One interesting thing. I have not FOV-mod running; it seems ED have implemented this already to help VR. But most probably you all already know.

Thx for the help. The link on the HP-site did not help, since the cable mentioned there has 3,6m, which I guess is the cable from the connecter to the PC. I have the problem with the cable coming out of the headset to the connector. A friend also tried the headset with his PC (also AMD based with with a Nvidia-videocard) and experienced the same problems, so Im pretty sure, its not me or my system but just the cable. Or it also could be a bad connection at the connector, even I have the later added clip Yes, the headset had the clip holding the two cables (second cable is the audio-cable) in place attached. For now I try to use the headset as it is with disabled audio, that I will get from bluetooth earbuds. I will try to fix the cable to the headset to releave it from strain, so the cable will not get damaged further. And I will keep looking for a solution. If I find one, Ill post it here. As expected the seller (private person) right now is unwilling to "settle" the situation; Im not sure, if persuing this legally is worth all the hassle coming with it. After all the Reverb still is usable, maybe even until Valve brings along it new headset, codenamed Deckard.

Hi. Sorry for making a new thread, but most G1-realted topics seemed too old for me. I tested a few headsets in the past but always struggeled with DCS-VR. Still on TrackIR and happy. But Ive tested a Reverb G1 when it came out in 2019 for two days and sent it back. In spring 2019 I bought a new one and found it actually quite ok. But I had quite a few stutters (I guess related to my then PC) , that killed the experience forme so I resold it again. A few days back I got a used Reverb G1 with the intention to check the state of DCS-VR in 2022. The unit came without receipt but was reasonably cheap. I also specifically asked if there were any cable-problems, but the seller denied this and said he had no problems. Well, yesterday I got the G1 and within 30 minutes I told the seller, that I think the unit has a cable-problem. Within DCS the audio of the headset went silent within a few minutes and the sound went to the speakers of my monitor. I also had two crashes. Within SteamVR-Home I had those audio-disconnects too, but they lasted for two or three seconds and then the sound was back. This was accompanied with a Volumesigne in the center SteamVRHome of "34" (when silent) that went back to "100" as the sound came back. I also tested GoogleEarth and also there the sound went away. So it seems, that SteamVR-Home can handle short disconnects, that DCS and GoogleEarth cant. These disconnectes usually happend on some movement of my head and I was also able to partly reproduce those when manipulating the cable close to the headset. So I immediatly suspected a problem with the cable. HP-Support was not helpful either. They confiirmed that there was a problem with the cable but since warrenty was over they could not offer help. They simple do not offer repair for VR-headsets nor do they offer to sell a spare-cable. I know its not that easy to remove as with the G2, but looking at a vid on youtube it seems quite doable for me. Does anyone have any idea, what I could do? For now I can use the headset with bluetooth earbuds and with those I used the headset for two hours without any problem. But I suspect, if the audio makes problems, someday (soon) also the video might. Regarding the seller, he has only responded once yet but my gut tells me, that me might up for a legal problem, that could cost us more (money and trouble) this is all worth. Im thankful for any input on how to "repair" my headset. Thx.

icecapped mountains of the Andes, And a full fidelity-Intruder.

Hi. I also had this problem with SSAO on, so I turned it off. But I had it in the F-86- or L-39-cockpit. Posted it here.

Hi. Im having this problem too. Its not big or really annoying, but still its there. I upgraded to a AMD 6700XT just around the release of 2.7 and with that it started for me. But it was only occasional, I maybe saw it 5-10 times in 20-30 hrs. But the Tomcat-IA-mission "Normandy-DissimilarAircombat Training", that I recently flew a few times seems quite sensitive to this problem, since in that mission the glitches happen quite often, maybe even every second mission or so. Sometimes, they are black, but also colorful and the shape also changes. I had dots and I had objects, that looked like someone had scribbled a few letter over each other. As I said above, just reporting. Right now, I dont have a problem with that and am just happy, that its probably DCS and not my GPU, that in other games worked flawlessly up to now. As always: latest OpenBetaDCS with latest Windows (21H1; auto pagefile), no mods (not even SRS or Tacview) and no OC or UV on CPU or GPU.

I did not have much time in the last days to properly test the new patch. But right now I feel the same optimism I had after using Win8-comp-mode for three days. But it only maybe 50+ reloads in 5 DCS-loadings, but up to now I had now crash of any sort (end of mission or on the load-screen). I hope it stays this way.

Hi. Im posting this here, because its quite easy for me to reproduce the problem with the Normandy-IA-mission vs the Mirage with them terrible Matras. Right around release of 2.7 (+/+ 3 days) I got a 6700XT as my new videocard. Ever since then I had occasional graphical glitches, not sure now on which planes. Actually pretty rare, but only recently when doing the Normandy-AI dissimilar-mission, I quite often get this glitch. Often around sending a Sparrow to meet the Mirage`s. Not sure, if its related to 2.7, my GPU or the Tomcat. I just can say, that I never had such problem with the GPU in other games, which should be a sign, that the GPU is ok. Personally I suspect 2.7 a bit more then the Tomcat, but Im not sure. Anyone seen this problem too? Did not witness this with 2.5. The glitches are usually maybe a few frames (3frames on a 30fps recording, so I guess 5 frames in my 60fps-setup) long.

Did not take much longer for those crashes to come back.....

Up to now I had no "classic" 2nd-mission-crash with the new patch. But I did not have enough time to be somehow remotly confident at this point. Also because of the crash I just had. But this crash was odd. When I hit LShift+R the screen just frooze still in the aircraft even before I got to the loading screen. This is not "classic" since 98% of my recent crashes happened at the end of the loading with "Mission load done" and I never before had a crash just before the loading screen. Maybe my files help. dcs.log dcs.log-20210528-103148.zip

Hi. Saw this topic just now. Im not around much in the VR-forum, since Im on 2D. I changed from a 9600k (quite the same as 8600k) at 5Ghz to a 5600X and saw only little change. In CPU-limited situations maybe a small gain in fps. Maybe +5fps on the SC with lots of planes around. The rare stutters in some scenarios I had, were not resovled by this upgrade. Also had tried 5,2Ghz on the 9600K before with no change. Only going from a 2070Super to a 6700XT resolved that stutters, which is strange since those scenarios all were CPU-limited. Maybe SAM or the supposed smaller overhead of AMD-GPUs?? But I know other people that say, they had good gains going from a 8700K to a 5900X. I guess, different configurations are too different to make a good judgment. And the CPU is also only one part of the system. When I still had the Rift S I often used fpsVR, which showed the frametimes for CPU and GPU seperately. I mostly had (tuned to 25ms framteimes) the CPU in the green or yellow, while my GPU was red, red and red.... So a new CPU would not have helped much, only in select CPU-limited situations. But in general I still keep saying: investing lots of money in hardware for DCS will only give you a small in increase in experience. If you look at the fps, you may see a small increase, but does if overall increase your experience? Will going from 4x MSAA to 2x MSAA or from 150%SS to 120%SS completly ruin DCS for you? If you dont conentrate on those small changes, I guess not. But thats only my approach.

Short lived hopes with 2.7.1. Just had a second mission crash again. So Im back to Win8-comp-mode....

Yesterday aternoon I deleted the Scrips folder and then DCS was updated to 2.7.1. This update was done only when I switched back to non-Win8-mode, I was using all week. Since then I had one 1st mission crash, when DCS crashed during loading of the first mission after DCS-startup. But no 2nd mision-crash so far. Did not really have extensive time to test this, but I did al least as many reloads (30?) and restarts (4?) of DCS, that with 2.7.0 DCS for sure would have crashed. Other than that, with Win8-mode I had "only" two crashes, that were not during loading. First crash could be due to undervolting my GPU too much (as Flappie sugested OC as the reason) and the second crash was in MP and the other players had problems with AI-aircraft and ships not moving for a while too. Upon restarting DCS, after some time all the unit-icons on the F10-map disappered and upon leaving the sever I had no aircraft-icons in the DCS-menu. Most probably not related to this here I guess.

Hi. Just had a crash in Win8-mode. But its an "unsual", meaning maybe 5-10 min into a mission, so I dont think its related to the 2nd-mission-loading-crash. I got a Discord-message, hit ESC, tabbed-out and did somting in the browser too. When I wanted to go back to DCS a few min later , DCS had crashed and I got the crash-send-box. dcs.log

Yes, I got the tip from tunuki44 in the other thread and it works for me as well. For five days now, no crash. Usually since 2.7 I had one every few reloads...

I have for sure 150+ reloads in W8compmode without a single crash now. Disable it and the crashes are back... I dont care about the longer loadtimes right now.

Im using W8 compatibility-mode right now and even Im pushing for it pretty hard, I still have to witness my first crash. Only two days now, so Im keeping my fingers crossed, but actually Im pretty optimistic right now. Went back twice to normal mode and pretty fast had crashes, but not so in compatibilitymode. Except for the bad loadingtimes I did not witness a perf-disadvantage up to now. @flappie: dont have Tacview installed and also Onedrive is not visible in my test-account. Since I uninstalled it with my admin-account, I assume, it will not automatically activated, when a new accout gets created.

Lastest version of Windows here. Up to now, after deleting or clearing the mentioned folders, DCS would start making trouble at latest at the third start, but often already at the second mission of the first start. Since my last post (2hrs ago), I started my PC three times and DCS maybe 6 times with 15-20 missions (10s to 20 mins) with many (usually 2 or 3 reloads). No Problem except for the loadtimes. Then I removed the compatibility-mode and at the first mission (Caucasus-F18-Freeflight IA) the reload (LShift +R) frooze and DCS crashed. Put the compatibility-mode back in and the same mission and two other missions also reloaded three times each without a problem.

Im trying hard to not even get a bit opitmistic. But for the last two hours (I know, not much) I really very hard tried to crash DCS, using all my normal supects and many reloads, but up to now, no crash. Id say normally I would have crashed DCS by now. Im pretty good at that recently... Dont have to mean nothing of course. Loadtimes are bad and shutting down gives me almost 1 min of a black screen. But if it dont crash, I dont care for that.

This logfile is shorter since it contains less Windows-related stuff. Needed three restarts of DCS though to get to a crash. This is above my normal average where crashes happen more often. report.html

Here is my first result. Had to cheat a bit though. Here is what I did. New local account. Log in, enter browser (Brave) and download the Folderchangeview-app, unzip and open it. Then TrackIR and then DCS. No changes to DCS whatsoever. Then I did 10 runs of the Su-25-IA-mission, alternatly hitting LShift+R or quit and choose "Fly again". No crash. Then I restarted DCS and did the same 10 missions again. No crash. Restarted DCS again and at the end I added 2 missions with a fast (not one minute in the mission) reload. No crash. Restart DCS again and only did two Su-25 missions and then swapped to the Syria Hornet Freeflight IA-mission (was problematic in the past), with one or two reloads but no crash. Restart DCS go to Hornet Caucasus IA-Mission and at the second mission (reload with LShift + R) DCS frooze at "Mission Load Done" on the loading screen. Saved the log of FolderChangesView to HTML. Its attached. After the Crash I noted the time: 12:43h. I restareted DCS inbetween since I have the feeling, that if it dont crash after about 10 reruns, chances are small that I will crash afterwards. When it crashed before usually it was at the first mission-reload or sometimes at the second. But thats just an unscientific feeling though. report.html

Next account. No changes to DCS also. Just as default as a Win-account and DCS-settings could be. Took me two restarts of DCS and about 6 missions overall to get to frozen "Misson Load Done". Log-files are here: dcs.log dcs.log.old dcs.log-20210512-210810.zip debrief.log

Hi. Created a new account 20 mins ago. First thing, I started TrackIR then DCS. Did not set anything, also no controls. Did a Hornetfreeflight and a F-14 refuel-mission from IA-missions with a reload. All good. Closed DCS and restarted. Did Syira-Hornet-Freeflight with two reloads and it was ok. Then change my settings to my standard settings, first mission-reload frooze at "Mission Load Done" I saw the checkbox to send report, but that went away with DCS. No sure, if the change of standard setting caused it (likly not) but I will try again tomorrow with a new account. Here are all the files in my Savegamefolder: dcs.log dcs.log.old dcs.log-20210512-202833.zip debrief.log