Gunnars Driver

Do you use the shaders mod ? I saw some round obscuring parts that I dont see on my screen ? Just checked back in the thread that it looks that I got the right missions the fullfill imackens wish.

As per imackens req: Training-look straight(centered with keypad5) Lookleft lookright P.G Ready on the ramp look straight: PG lookleft PG lookright [Edit]Just remembered, there is a few red spikes just when starting the mission, but I missed them when aligning the headset straight ahead and changing the Active window to the fps window to make the screen dump of it. DCS Settings(PD 1.0, SS100%/2207x2160) It would be possible to catch those but its not representative for the rest of the time…?

And some time the WMR bug set the headset to 60hz despite the settings is 90. Solution is to pull out the headset connector and put it back, enabling 90hz as it should. Only time I saw flickering is when headset unintentionally get to 60hz.

Are you running Vsync when using TrackIR? If not I guess that core works as hard as it can to produce frames, hitting close to 100% if nothing else stops it. If you enable vsync and stay at 60fps( i guess) it lowers the cpu load. There should be other cores working during VR, steamVR, WMR etc that uses som äe cpu power. In my case an VR theres really only two cores doing anything, core 13 at 30% or something and 15 doing 60-90%. I do not se that spread, or at least my other cores are quite low with cpu total at 8-10%

Could you maybe make a print screen of the mission selection in the DCS menu, so I dont run the wrong game again? I dont feel that sure about which selection to make from the description above. I have almost only done multiplayer with my gaming friends and really not used any other features. Feeling a bit stupid about this, but better ask before than putting up print screens with values that confuses you guys again...:cry:

Ok, I went for “missions”. I’ll do a test after removing 1 feet of snow from the drive...:cry:

Quote from that linked page: The guide is old(2018). In all new firmware the line already exists. Just delete or add the //. Its crystal clear really. Automatic or off. There is off course a third setting, enable it always, but it would be rare to use I guess. I do not really see how you can understand this any other way? When it is in auto reprojection is always: -Off when PC delivers 90fps or more( of course ad the PC has one new frame for each frame to show) -On when PC delivers between 45 to 90 fps, to lock fps at 45 and reusing each frame once, making it 90 fps to the VR headset( but only 45 true new) -Off when producing less than 45 fps as there isnt enough frames to make 90 if doubled anyway. [Edit]Reprojection is either on, or off. There is no in between. You can let the computer do all 90 frames for itself or you can use reprojection and then you only use 45 fps from the computer( like vsync), and you double this frames. Reprojection can not be anything else than on or off.

Just saw the VirusAM screens. I nitice that I didnt use the same mission. I thought I followed the request but I was standing on a carrier with a few F-18 ahead and also a helicopter in the view. Maybe specify more exact which mission to use? It would have to be the same to make sence :)

I have a 9900KS@5.0 during the test and a RTX2080ti 11Gb. 32Gb@3200Mhz RAM The RTX overclocked to 2080mhz or something like that I looked straight ahead, I pressed numpad 5 to get it straight forward( I thought the question stated straight ahead?)

If I understand you correctly you mean that the difference between this two lines doesnt make any difference? and Not true. Not for me at least. When I first started DCS with the reverb, I got around 75 to mostly 90fps with the settings I had and in that/plane/Quick mission I run. I didnt even really have a smooth gaming even though the DCS counter said 90fps. there was some small stuttering regardless of what at least seemed as 90fps on the counter. Only change I did was remove the // from that line (according to the difference between the two quotes above), and I got very smooth gaming with either 90 or 45fps on the DCS fps counter. I have resett the REM-marks( // ) a couple of times for some setting/tests, and the counter did start hunting up and down and I also got that stutter again, each time. After each test I removed the REMs ( // ) and ech time it Went back to 90 or 45 with smooth gaming. If I understand your statement, I Think you should consider the possibility that thuds guide is correct and if it doesnt work the same for you you still have a problem with the setup. Maybe, after more than one install, you have two or more different and maybe the WMR/Reverb do not use the one you are changing…?

That link you refer to actually says the same as I say: So this is only in the "Home Environment room" where you start you WMR experience for WMR...something...only was there 1 minut during setup. This is not important for me as such, but I Think its good for other reading this thread so that they dont use that much time believing that that setting is important.

Just tested mine with mission/persian gulf, mission qualification - Cold start CPU at 5ghz currently(otherwise 5.1/5.2). GPU slightly overclocked(2085mhz) SS 100% = 2207x2160. DCS Settings(PD 1.0) No mods. 1909 recent install(upgraded computer) Settings mostly as thuds guide at vr4dcs.com

I dont feel it that way. I got the Reverb running better than OR CV1 have during the three yeasrs i hade them for DCS. New upgraded computer, still got the CV1, tride them...DCS running smooth for the most but not 100% of the time, and when not its ghosting. And stuttering, oculus ASW doesnt even come close to the reverb smooth gaming in DCS. All other games(not thast many really) is smooth with 90 fps with the CV1. I am very happy with the Reverb.. I did plan to get Pimax 8KX but they wasnt availabe and also I need to se that it possible to make it a good gamiong experience in DCS. So, the reverb came to be some kind of emergency buy but I’m happy I got them.

So you dont have any number of red spikes that might cause problems ?

I’m not sure, but you are most probably having a regular pc monitor connected, my guess is it is set at 60hz(fps) when using VR. Vsync might maybe get the 60 fps as the limit and I think vsync will cut the framerate to 30fps When it is set to 60fps if the computer cannot manage to produce 60fps which should be quite common when doing DCS in VR.

Yes, I followed the thread and and I made some post earlier. The VSYNC setting in DCS as someone aksed about is a valid question, to confirm its really is off. (It would make a frame wait longer than needed to be projected most of the times, and this would add ms between each produced frame. Just emphraising, due to the actuall problem. Another thing, fpsVR iinfo on Steam: The latter part; I dont really get it, but anyway it should mean that frametime actually can be longer than the reported. I havent seen this, Im quite sure that I keep 45ps all the way to 22ms or 90 to 11ms. https://steamcommunity.com/app/908520/discussions/0/1735462352484917218/

So, how long until I can have a 8KX in my hand ?

Something dont add up. Having for example 20ms frametime on the slowest of CPU/GPU vill render 50 frames per second. Each frames takes 20ms, 50 of this sums up to 1000ms, one second. Is it possible that VirusAM doesnt see the hickups in frame time on fpsVR ? The continous drawing graph over frame times, green is max 11ms, amber/yellow is max 22ms and red is above. I made this for another thread to show, by risning settings and provoke by flying low over a city. (My normal settings will keep at 45 or above almost all the time.

Cinema and computer fps is not really comparable. Classic Cinema movies are per default 24 frames per second. In the cinema they show each frame twice( like ASW or reprojection with VR). This is to smoothen the picture and minimize the flicker. The movie frame is shot during a short period and catches things that move during some time. This means the picture is a bit ”un-sharp” due to motion blur. This makes the the human eye percieving it less like a still picture and helps make us see it as a smooth flow. Computer frames are per default still frames with no motion blur. I see a clear differens between 90 - 60 -45 fps in gaming. 90 is really good. 60 is ok. 45, it isnt perfect but acceptable. I can percieve that there is a lot of pictures coming after each other. By accident my reverb starded in 60fps, i noticed the difference, it was okey but when reprojection put it to 30 fps I sure did not like it. We are all different and percieve things different. If you are happy with it below 45, be really happy and dont start thinking about it. If you do, it might get expensive :-)

You followed the thuds guide on vr4dcs.com ? Updated win10 to 1909 ? I cant be really sure becausae I upgraded my computer just before getting the Reverb. Doesnt feel like they need that much extra performance. I actually get better smooth framerates with the reverb than with the Rift CV1, samt settings exept PD wich is 100% on the reverb and 1.6 on the Rift. I have a feeling that it should be fixable in your case. I overclock my GPU, always have with DCS. But in your case you should get everythin working good and nice first, then the OC can get you a few extra frames, keeping you above 45fps more of the time.

Thanks for the answer. Got a optician booked in a week via the job, Ill bring the values from the vr optician site.

Anyone using vr optician lenses ? Always had better than 20/20 each eye(Airforce pilot) but the age is kicking in, and right eye is slightly off today. I can see everything in my VR-headset but it isnt as Sharp as it should be. Im thinking of getting one lens, for the right eye. Anyone using only one? If so, does it work ok?

Of course the industri want you to believe stuff, buying their more high tech stuff....but... I did a lot of car racing (IRL, and also on computer) during the 90:s. When internet came along, of course online also. I know for sure that for example TOCA and TOCA2 was games that had FPS dependent calculation for keeping the car on the road. You didnt have to have a 144hz screen, but you had to have a very good computer and disable Vsync to get the good stuff. I built a PC specific for this with Overlocked dual SLI Voodoo2 cards and with a highly overclocked CPU I actually had the possibility to be among the fastest there was. My friend, also TOCA2 gamer couldnt run ass fast on his computer(same steering wheel etc) so he came to me, also using my computer for the fastest laps. I dont know if this is the reality today. Hope not, of course. If calculations of speed, G-forces etc. is’nt involved in the graphic part it should really matter what FPS you see on your screen. (Maybe a side note to this thread...)

No plan to try to push you over that line...but... :) I was ready to get Pimax after 3 yrs with Rift. Upgrades the computer to be able to cope with it. Then the 8KX wasnt released so I more or less had to get something else. Ive only read about the Index, never tried them. I dont think they was in stock when I ”had to” buy new VR so I got the Reverb. Setup isnt a big deal at all. Actually it took less time to get a proper setup with the Reverb than with the Rift( I did setup Rift on the new upgraded computer.) You save a little time in basic install with the oculus but before graphic settings in DCS is done so I was happy with quality and smooth gaming, it took more time. If doing evaluation of which set to get, do not countthe install on Reverb as a big minus. Cause it really insnt. You can choose the Index for FOV, thats a valid evaluation point. But not setup.

If CPU OR GPU -time exceeds 11.1ms you cannot reach 90fps. Its nature laws, really. 1000ms/11.1111 = 90fps. If you are Above 22.2ms you cannot reach 45fps. With ASW or motionReprojection in auto, the computer will switch from 90 to 45 as soon as it cant produce 90fps( = when fram time is more than 11.1 ms) You will see 45 doubled frames in VR. If fram time is more than 22.2 it can not longer procude one new frame for each needed and it will not(per definition) be a smooth ride. This is a question avout perfsonal reference, if you dont have any problem with fram rate, dont dig into it. You might find things you didnt see and that might cost you either quality settings or $ :cry: ___________________________________________________ I use the fpsVR, might be something like steam VR graphs. Green = time to produce frame less than 11ms = 90fps. Amber= time to produce frame more than 11ms = 45fps. Red = time to produce frame more than 22s = lower than 45 fps. ___________________________________________________