Gunnars Driver

You have to start DCS, then it shows in that list.

I think your CPU should be good, and dont bottleneck totally, at least not with rhe right settings. What VR-headset do you use ? Start with checking the CPU temp and that it actually runs at 4.7ghz all the time during gaming. What pixeldensity are you running ?

:smilewink: Cool!

I think the amount of GPU RAMis depending on the settings. Higher grapcic settings means more RAM usage. My tuned settings take it close to 11Gb but stays just below.

Check this post about how to check the CPU load: Also, GPU-Z is a good tool to see the load on the GPU in more detail than what you see in the task manager. https://forums.eagle.ru/showpost.php?p=4163309&postcount=288

4.7 is quite ok. 32gb also, do you know which memory freq they have and is the BIOS setup for that speed?( default is something like 2667, in most cases you have to set up this in BIOS. For example Xmp profile. I had a i7@4.7Ghz/16Gb RAM and a GTX1080 earlier - Your end settings would not differ that much from mine, I guess. You can use the Task manager/resource manager to see how loaded you CPU and RAM are (RAM shouldnt be a problem here, really), and there check the specifik core that has the highest load. in the task manager you can se the load on the GPU. These values tells you how changesaffect and also when the game doesnt run smooth, what is the limiting factor. The grafik card OC and 4-5fps is a good extra. If the ASW has set in and rhe computer is able to make just above or just under 45fps, it may do the difference between smooth play and stuttering. I always use OC on the GPU for DCS, but not for other daily tasks. I suggest you lower some settings and set cockpit resolution to 1024 every frame and then tweak the Pixeldensity to 1.6. Test fly and check for instrument clarity, if its then alter the other settings so that you get the game to run smooth enough for your preference. I think the slider on the right side, preload radius or something like that should be set to max value. ( think it loads ahead which makes it easier for the computer ( takes more RAM, but you have that). Threes and grass= start low. Start with settings like this, but maybe start with visibility range a bit lover, high ? Right side of Picture I didn have one with my actual used settings. I Think you can start with the sliders around the red star markings. The VR tab, set Pixeldensity to 1.6. All this should make the instrument Sharp an still not lower the fps that much. If it runs smooth, use the fps counter and test fly making one change at the time( to learn what is "killing" your game flow. The balance between smooth gaming and quality is a matter of personal choise so you just increas the settings until you fel it is enough quality but not too much stutter and ghosting. I Think you should disable any other VR tool that messes with for example PD when testing, so you know what values you actually is using.

What hardware do you have( CPU, GPU) ? Question is to be able to help with possible overclock of CPU and/or GPU to get extra headroom for the higher graphics settings that helps cockpit visuals. You also might need to lower some settings to release the computing power for imcreasing the important ones. I come from three years of Rift CV1 and if the hardware is up to it, use as high Pixeldensity as possible. I also used the setting for cockpit resolution “1024 every frame” or something like that. I have a friend with CV1 and quite weak hardware so Ive been helping with making it work ok and be able to see the instruments. This together made it as good as it gets with the CV1. When needed, lean forward to see what you need.

Nice ! :-)

You really doesnt notice any difference* in flight behaviour. The VNE is only the speed limit allowed, not the maximum possible speed. *) Some helos lit the warning “DOORS” on the warning panel. You may notice that, nothing more.

I dont see the smiley that I thought I would see behind that comment ? I got oculus rift CV1 around three years ago. Despite being a single software setup I think it took me 2 hours just installing and connecting the parts( stuck software when it came to sensors). After install, it took me at least two seeks before i thought the settings where good enough for gaming without feeling the need to tweek more. At the time I had the fastest GPU there was( except Titan). Reinstalled oculus recently after upgrading computer. The software install went flawless but it took time to get good settings on the Rift. The reason is it easily stutters and ghosts and you dont sant to leave all settings at minimum if you got the best CPU and GPU there is. So optimum settings is not found yet and if I would like to play dcs with the Rift I have some hours in front of me. With Reverb, only slightly more installing, then really quick to find settings due to thuds guide and the magnific fpsVR software. Total time spent maybe 1/4. :-)

Seems that we might be thinking the same thought? Reprojection maybe not working. First thing is to make sure reprojection really is activated and works. We need to know the windows version, I think

I tried a few different visual quality settings but I dont think I saw any difference. I left it at ”ultra(beta)” or something like that. Ive read earlier that it only affects Windows Mixed Reality Home and nothing else, trying to find that reference I found this: He basically says it doesnt affect games Yes, I can see the rainbow effect if I make actions to see it. They doesnt disturb me and the two first projectors was DLP( but chosen with extra DLP-wheel speed to minimize these effects.)

Reverb dont use base stations. It uses inside out tracking. You can not play in darknes because the tracking need some light level to work properly. Installing Reverb with WMR: Its more to it. But its not hard and do not need rocket scientists to manage. I followed Thods guide for Reverb on vr4dcs.com and the setup itself took less then an hour. Because the good guide and the excellent software for tuning the settings( fpsVR from Steam) It only took me another two hours until I had managed the settings to get the perfect combo of smooth gaming and good visuals( its a matter of personal choise, of course). In total, comming from oculus rift cv1( still have them), I know that tuning to find even acceptable settings for DCS an take many hours. I think the extra 30minutes of install is worth the easy tuning and the excellent result.

The activation of reprojection by going and editinc a setting document: All settings are in this link, actually a few mire that I forgot about also: https://vr4dcs.com/2019/09/10/reverb-settings-for-dcs/ I did follow Thuds guide in that link, just as he said. All credit should go to Thud!

I had big problems taking a single photo with my iphone to show the reprojection-indicator. Gopro, I used my iPhone connected to the gopro so I got the videostream visible on the iphone, that made it much easier to find optimum position an FOV setting to get it clear. Probably very lucky, it only took that one first try. Anyway, as long as you can believe me/us that DCS actually plays smooth without stutter and absolutely no ghosting we dont really need to see your video. There is one thing that we would need to know, if the reprojection really is active. If I disable reprojection I only see the FPS number steady when flying where the system delivers steady 90fps. In all other cases it will vary constantly between 90 and lowest fps it bogs down to. With reprojection on it should only show 90 or 45, or a lower value when it doesnt reach at least 45fps. For brief moments it can show values between 45 and 90, when it switches between reprojection or true 90fps. All settings is per the Thuds guide at: https://vr4dcs.com/ Windows 10 version 1909. The guide at vr4dcs.com said 1903 a few weels ago, so I guess that version also works. I actually think that make sure you have version 1909 would be the first point to success. Means going in and reading version no number in windows system. Windows mixed reality, I use highest setting of quality(I dont think it matters in gaming though, the steam vr and the game settings is setting the levels). Theres a choise of 60 and 90 fps, of course use 90 if trying to get settings like I do ( and the guide at vr4dcs.com). In nvidia control panel there is a setting for pre rendered frames. Should be set at 3. All other settings default to begin with. There are some settings that help some people but makes problems to others so they should not be messed with initially. Basically, the idea is to get it working good with smooth gaming first, probably some settings a bit low, and when it runs good then increase settings step by step until the individual mix of smoothenessand quality is fullfilled. After this, maybe start trying the odd settings that may be helpfull or harmfull to fps. ”Windows Mixed Reality for SteamVR” should be i stalled via Steam. One setting needed should beta-public version or something like that. This is to properly see the correct resulotion settings: 100% equals native of the reverb.(actually not exactly native but 2207x2160). ”SteamVR” should be installed, and NOT use the beta on this one. In steam VR you set the resulotion to 100% ( and the redolution at the slider have to say 2207x2160 to begin with. This runs the reverbs at normal resulotion without supersampling). In DCS settings in the VR-tab, pixeldensity/PD should be set to 1.0. You should use supersampling in steamvr i stead of DCS because it draw less calculation power that way. And, do not start to increase supersampling initially, it will most probably stutter. The specific dcs graphiccsettings I dont have them in the head so Ill get back later. I also overclock my 2080ti with ( in my case) asus gpu overclocking tool. It may give you around 10% extra GPU power. I have read that msi afterburner is really good on this, so i think others would recommend that one. There is a cheap software, fpsVR ( like 4usd) that run inside the vr headset and show you in real time the liad of gpu, cpu and the time it takes to produce the frames. Priceless for tuning. The best tuning tool I ever used. Incease ome setting and in game immediatly see that for example the GPU frame time rises too much, or that the GPU RAM fills to 100%. A must to save time in vr tuning.

As ^ he says. I dont like at all when the game isnt flowing. I rather lower quality a Little bit than supersample and get stutter. I know some like it the other way around. But from the context of coming from the CV1, the clarity of Everything is much better anyway. Its not only the resulotion. A big part is that the screendoor is almost invisible with Reverb compared to the CV1 where the screendoor actually covers a quite big portion of the Picture. Coming from the CV1 you absolutely dont need supersampling to get a much clearer Picture. You might want to supersample anyway, but it is not needed to make a big upgrade.

I know what tearing is. I've been in the home Cinema bussiness for 20 years and had a lot of problems with video rendering software between the years 2000 and (cirka) 2010. What you saw on the former 'vid I made was not tearing. It was the problem that comes from trying to catch 45 frames per second source with a 60fps recording. One of three frames of the source will be chatched two times on the recording. This will make the Movie flow not smooth as the third frame will be visible a longer time. I managed to shoot the video of the flight you wished with my gopro, at Full HD and 120fps. Still, the source in the VR headset is 90fps and the fram rate of new explicit frams is 45fps. Theoretically, we have a bit of same problem but there is a much smaller percentage of the frames catched 3 or four times. The Youtube video doesnt look as nice as the source, they convert the frame rate to 60fps. I think it can be seen in the video that it doesnt stutter and that there is no gosting. If not, I still have the 120 fps source and it vould be put in some kind of cloud service, and viewed directy on your screen after downloading it, there is a need for you to have a 120hz monitor though. (or, play it at half speed on a 60hz monitor). Did you by the way notice that bn880 solved his stutter problem(or problem of not getting reprojection to work) by updating Windows to 1909 ?

Cool ! :thumbup:

I guess theres mostly v2 out there. I ordered directly from HP to minimize the risk of nit getting v2. My actually says it during install i think. For the pixel density, I’ve of course tested higher supersampling and seen some smaller increase in clarity but also a lot more load and very quickly reached the limit of my 9900KS/RTX2080ti overclocked etc. so I very happy to stay with 1.0 / 100%

The Intel standard for turbo mode is not a constant turbo speed over time. It vill go down to the ”normal speed”(3.7Ghz in your case I think).The reason is that the small stock coolers dtc may not be able to keep temperatures ok during longer times of turbo mode. There is a possibility that your mothercard already run the cpu att the higher speed constantly( even though the intel spec says ”not”). I dont know very mich of this because I have never used those standard settings. Make sure that your CPU runs at least at turbo mode(4.7) constant during gaming. The CPU usage tell you very little about CPU load in DCS. Only one core will be highly loaded( probably 85% or more) and this core will limit your DCS performance. The total will be shown as a much lower value( 8% in my i9 case, becase there is virtually 15 other cores/threads doing almost nothing). Check the cores individually in the recource monitor from the task manager. You would need to google an maybe search this forum, I dont know this answer, maybe anyone else knows? You need WMR, steamVR for VMR and Steam. But you do not need Steam version of DCS Steam is needed to make gaming via WMR work, nothing else than this. I do not have the Steam DCS, I have the regular version starting from the shortcut on the desktop. I guess so. I have only used the reverb with my upgraded computer.

No, tearing isnt a problem in this case. Tearing was very common in the home theather PC world earlier, the movie video renders had problems. Basically, if the computer is in the process of rendering a a frame and during this process takes the unfinisched frame and tries to show it, it can end up in two different parts of pictures shown together. Ive think Ive seen tearing in PC gaming also, but it was a long time ago and mostly when trying to do things the video card couldnt...in some cases maybe glitches in drivers etc. In this case, both shooting via the lens with a camera or capture via the mvidia software, the whole frame will be shown. Id say the camera shutter time is way longer than the time it takes for the monitor to draw the complete picture, making each frame complete.

No, I wasnt able to take a descent shot. It either focused on the lens itself or nothing which made the movie useless. I think I can maybe try with a gopro and shoot 120fps. That should be such hi fps that we not get disturbed by the unevenes comming from non matching frame rates. But to se it, it has to be the raw movie put for example on droxbox or another cloud service. I didnt find any online movie serviceprovider that offers more than 60fps. Im not sure it is worth the time( for me anyhow, already knowing I get a smooth experience for the most on REVERB+DCS). I actually think discussing the settings you use on WMR, SteamVR etc. I think the problem is in that area. What resulotion do you run for dcs ( steamVR)? You should use the beta and 100%( it has to say resulotion 2207x2160) if you supersample it higher you most likely will not have smooth 45fps. This is because you bog down the GPU. The small software fpsVR will show you very important info avout what it limiting or even close to limiting. For example when I can see the videocard RAM reaching 10.7Gb of 11 Gb possible I know that inreasing for example visibility range vill inrease the RAM, probably reach the limit. Withput this software(4usd) I do not kniw what is limiting me. Have you updated to windows 10 version 1909? WMR updated ? The thuds guide at vr4dcs.com tool me straight to nice flow. I only needed a couple of hours to get really good settings with the close to optimum setting with smooth 45 or 90 fps and high quality.

Updated the same video, just new rendering with lot less compression: The judder we see is the catching of 45 fps with a 60 fps recording. ( 60fps = 16.67ms and 45fps 22.22ms). If we start both projecting and recording at the same time, after 4 frames of 60fps there has only been 3 frames and at frame 5 of 60fps, there will be recorded two frames of the same projected 45fps movie. This will create a non smooth video in 60fps, because the frames that is shot twice causes the movie to appear as ”frozen” during 1 frame. This will happen 45/4 times per sekond or roughly 10 times/second. This is also what we see in this movie.

I upgraded my H/W Before getting the reverb, but I still have the CV1. Same settings, much smoother ride with the reverb. Despite having PD1.0 and mostly 90 fps with the CV!, they get som stutter and rahter much ghosting. The reverb just doesnt, as long as you keep the load on the computer to keep at least 45fps. Almost no ghosting at all. There is a guide that you have to follow when getting the reverb. vr4dcs.com, and the thuds guide on reverb. It not as simple as with oculus, but with the guide you'll get spot on on the first try. It is not difficult, its not whqt Im saying. But if you follow the guide the settings will be better to begin with and you save a lot of time. For the overclock part, if you play DVS, overclocking is a almost needed part of the setup. Specially the CPU, that often reach the limit on one core. You should at least see to that the CPU is running att the turbo speed all the time, and not throttleing down when gaming. There is small software that helps with automatic O/C of the GPU, that might give you 10% of performance(which you need all 11 % of…) for free. IPD of reverb is softwaredriven, no Changes of lenses etc. It is sad to be ok if you dont have too much difference of you IPD from stock 63.7mm(or something like that). Im quite Close to that so I really dont know how bad it is if you are way off. The IPD in DCS is said to not be a real IPD-setting but rather the total scale of the Picture you see in the vr headset. (lika zoom in or zoom out I guess, havent used it)