Gunnars Driver

Well I did that already before the post yesterday. You know, the hope still is there for a even quicker resulotion. When I woke up, there was an answer from the support. Good. They asked med to uninstall varjo bae, nut I just installed it on my former gaming rig (now my sons). No joy. After installation there was no connection between the varjo base(computer) and the headset. A brief "a usb device is not recognized" and blue flashes on the headset. I guess something is broken. As everything worked very very nice with DCS I was reluctant to uninstall varjo base and install it back. My long term experience is that a new install with low numbers of "fixing things" is best. Yes, I have a mirror of the operative system disc saved, but anyway.... So, tomorrow I will see if I still need to uninstall and install varjo base only to find some hardware broken. Remember, I have had these headset dropouts since last spring when the headset was only a couple of months and maybe 20 hours of gaming. I thought it was some kind of software bug. Hope this fix these dropouts. Not good in assetto corsa at 300km/h as well as in DCS in combat, or close formation.

My Varjo Aero headset stopped working today. Initially it shut down and started up during gaming ( lens movement each time) several times, then it stopped working. Now the Varjo Base say that the headset is not connected. (all regular tests done). Any tips on what happended? ( I have contacted the support and sent in a log file etc).

Do the post processing increase the load on the CPU or the GPU ? I use openVR and it works fantastic, there’s a lot of headroom on the CPU but the GPU is on the limit of coping with 90fps over land.

VR Optician was perfect for me on the Reverb. Only needed one lens to that one. For Varjo they also fit perfect but for one eye did not get the right strength so it is not sharp. I need to get that fixed, otherwise the quality and the mounting is perfect. Varjo has a quite close viewing distance (90cm?), so it probably cause other people to need lenses than the reverb.

Have you checked the frame time with for example fpsVR ? (I guess fpsVR can not be used with OpenXR…) My guess from seeing my frame times with fpsVR, that in moste cases it will be the GPU/4090 that will set the limits. I started DCS with my old quite high settings for the Reverb, only adjusted the resulotion to 100% (so about 3600x3400?). I did get 90fps most of the time and found GPU frame times to go slightly over 11.1ms at low level over land. @Supmua’s guide pointed to 80% with resulotion about 3300x 3300(?) but it did not change my GPU frame times noticable. All is working so fine that I didnt even try to change settings yet. My point is: Maybe people wrongly believe its the CPU that cause the stutter but it actually is the GPU that is the limit if you have a 13th gen intel like the 13900? 4-6ms and ”clean green” in the CPU frame time graph like I have point to that the CPU can handle the load without stutter. There might be a difference between Win 10 and 11 but reading the threads and posts from supmua and dburne etc. imply that win 11 is as good as w10 these days?

Just an update to the above: - Did Varjo fix this? Im still on the latest 3.7.X (havent installed 3.8 yet, away from home). I have a Z790-mobo(Asus z790-f), 13900KF and I have [b]not[/b] disabled the e-cores and everything works fantastic. No stutter, there is no high load on any e-core. I have mostly 90fps and average at least 87 fps, even playing as the server etc. I would guess this ussue is fixed?

To disable to e-cores it should be done something like this: Enter the BIOS and go to this tab: The change these settings: But basically, there is usually very small performance differences with or without e-cores. (Its been tested to zero or e few percent up or down). Also, I have not disabled them and my system runs verey nice. A fresh Win10 install and fresh DCS install. Also, even if I do not know what CPU you got i guess it is a 13th gen intel (because of the z790). In my case the CPU is newer limiting the performance in DCS. It is the 4090 that is the bottleneck for me, and probably for you too if everything runs as it should… With fpsVR, if you can use that, you’ll see the the frame time for both the CPU and the GPU. In my case I have 4-5(6) ms on the CPU, which is enought for more than 120 fps. Will not cause stutter on 90fps in normal cases. The GPU have frame time that is about 1.5-2 times the cpu so about 7-11 ms. It sometimes go up to low 12, and anything above 11.1 ms will cause stutter as there isnt enough time to produce the frames. I get an fps averade in dcs of about 87-89 depending on the game.

The cpu utilizes different clock frequency depending on how many cores that is used. i dont know what cpu ypu have but the 13th gen has about the same principle: if only one or two p-cores is used, you get a higher clockspeed. When all P-cores is used you get the same lower clockspeed on all cores. I do not use project lasso or anything. since some time I see two cores with more load ibstead of only obe loaded CPU core so it seem like dcs already can split the load on two cores? ( I did see this with my i9 9900 before i upgraded the computer as well, but i hsve only used fpsVR to see this in-game. Did not check it wth the task manager or otherwise.

Do you know exactly what motherboard you have? Also, are you familiar with changing settings in bios? We can help you, but then we need to know the above questions. I have a i9 13900KF with a lot of E-cores but I havent had any problem at all. I have not disabled the E-cores. I can see (with fpsVR for example) that all (high) cpu load is on the P-cores. I guess the issue is that E-cores is much less powerfull so if the main load is on a E-core it is not powerfull enough too the task. I have very good performance with the 4090/13900 and the aero. I do not get 90fps 100% of the time but I have quite high settings and it is always the GPU/4090 that is the limiting factor. Frame time on the CPU is 4-6ms. I would suggest to use fpsVR if possible to be able to see what is causing the stutter.

Is it that bad? Away, so I havent tested it yet. can it be used with ”Force_steamVR” or do it only work in Varjos default? I actually do not really need it after my upgrade, but was still hoping. That VR Sim guy vid was promising. I get 90fps in most situations now, but for the few exceptions it wouldnt hurt. As a side note, I noticed that there is teo cores sharing the high thread since some time back, and not only one. I get 4-6ms frame time with my 13900KF and the 4090 is at 8-11 so always GPU bond.

We can only really show the difference between 3090 to 4090. If it is worth it, will be totally depending on a lot of personal stuff, other hardware and whicjh which VR-headset or screen used. I had a 2080ti —> 3090: it was worth it. Got a 4090 now, yes it was worth it as well. I did average about 65fps with 3090 on a specific own mission with 3090. 4090 pushed it to 75-80 or so. changed from 9900KS to 13900KF pushed it to very close to 90fps in average. As Varjo Aero do not have reprojection, and I am sensitive to stutter (and all not ”flowing” gaming, all steps above was worth it.

I just upgraded to 13900KF, DDR5 6.2 (32Mb) and a 4090. (Coming from 9900KS@5.2 DDR4 32Mb 3090. I havent tweaked anything yet, steamVR set to 100%, havent checked the resolution( did but dont remember). Varjo at 39PPD. I get 90 FPS most of the time. I was hosting the server tonight with three friends on a quite complicated misson with quite much asssets, most of the time 90 fps and it aversged 87 fps. Not 100% stutter free but almost. I took a lot of screen shots and it hickups the fps for a short while as usual. In do not use the VR-preset but the settings I ised with the reverb.

Win 11 did have a couple of months more to mature. What is the latest, W10 or W11? I only do VR gaming, DCS open beta, Asetto corsa and maybe a little FS2020. Doing an upgrade with new install tomorrow. (13900KF, 4090.) I have a hard time deciding, but for now it leans towards W10.

And I do only multiplayer, but I do not think it really differs. I have the TM warthog Throttle + Stick and all funktions is already in use. F-functions is needed for me, most of the F1-12. Select weapons, refueling both in air and on ground/supercarrier etc. Print screen is nice when the right Kodac moment appears. Numpad 5 for resetting the VR View.

I 3D printed reference points and add ons to glue on F1, F5, F9 as the first in each group. And also print screen, enter and the F-menu opener to the left of enter. And also Numpad 5. Have to see how it works out.

I'm about to 3D print som things to make it easier to navigate on the keyboard when gaming DCS with VR. With earlier VR sets I could glance under the VR above the nose. but with the Varjo I just cant. I'm thinking tactile keycaps and maybe a few "wings" to make the blind navigation on the keyboard easier. I did not find much on this on the net but I guess I'm not the first that need these...?

Just passed this thread looking for another thing. A decent VR mod should show the cockpit very blurry, as the NVGs is set to more or less infinite focus. NVG do not see NVIS adopted MFDs, and what can be seen is blurry.

That did it, Thank You very much!

Im trying to get the debug tool to appear but it doesnt. I had it appearing a long time ago, but no joy now. I'm about to set up for the Steam OpenVR settings. The cross eye issue is there so I need to adjust.

I can not get the debug tool to show up with OpenVR. I didnt have any issues a long time ago in the normal Varjo OpenVR. But now it just wont work, and I cannot find out why....

Good to know! The 2.8 debacle probablu is the usual one, get solved later on. So then I just need to w8 until the right cardbis available

Did you see a big difference with the 4090 (comming from 3090 i I dont remember wrong?).

Yes, it is kind’a true. Better feel of speed in car games but also in DCS at low altitude. First impression was for some parts ’Waow” but it did not last so long. The vertical FOV is not that big in the extended part of the view, compared to normal FOV VR sets. Also, the sharpness is not good in that part I think. 8KX has a quite good/big sweet spot in the normal FOV part though. I hardly see any big difference between the wide FOV and the medium(150degree) FOV because of this. I would like to have the FOV of the 8KX with the sharpness and pixel density of the Varjo Aero and at the same time the good fps flow of the Reverb. But this wont be possible with the curremt graphics cards. Until that is possible, I will select high pixel density and sharp picture. I rank Varjo Aero way higher than 8KX for DCS, and also the reverb as way more playable than 8KX for DCS. I am about to sell the 8KX because I do not think I ever will use them. Of course there is other people with other thoughts about 8KX.

I (still) have Reverb G1, Pimax 8KX and Varjo Aero. Befor I got the 8KX I was dure that the wide FOV was king. But a Oc 9900KS/RTX3090 etc do not have enough power to drive the 8KX in DCS with my reference for settings. The swrtings needs to be tuned diwn too much. Also, the pixels per degree is not that high on 8KX. 8KX has good resolution (as in the number of pixels) but as these are used for a huge FOV, the resulotion per degree or the sensed resulotion for the eye is not very high. The Reverb G1 has higher ”density” of pixels and the cockpit screens etc is clear enough in G1 but not in the 8KX for my standards. I have had the 8KX for over 18 months but only used them about 10 hours. 8KX Is good for Half Life Alyx, racing games etc but not for DCS as i see it. I did always use G1 since O found the 8KX ”useless” in DCS. With DCS in dog fights etc I more or less did loose snt time as the quality was not good enough. With G1 I have very good kill rate. Varjo Aero is very sharp, the small FOV was anoying initially( being used to 8KX and G1), but after some time I got used to that. I only really miss reprojection in the Aeros, otherwise they are really good. But somehow I also can not stop thinking how good the G1 (and G2) is.”, specially if you think about the pricing.

I had the Reverb G1, and decided that I needed the Pimax 8KX when it was revealed. Waited long time. When I got the 8KX I found that the resolution, (pixels per degree) was much lower than I could guess on the 8KX. I could not longer see the displays and visual combat in DCS got very hard. In my friends game setup Hueys vs Hueys I started loosing every time due to not being able to see the enemy. In racing games, Asetto Corsa for example, the low resulotion isnt a problem and the wide FOV give a lot of extra speed feeling, which is nice. But DCS with 8KX is not good enough for me, saidly enough. ( I have a RTX3090, i9 9900KS@5.2Ghz and even with high settings to maximize the picture quality it is not good enough and the framerate suffers. I would have liked a much higher resulotion in the KX, to be on pair with the Reverb. This is not possible with the CPU/GPU calculation power of today, I think. So my conclusion is that even if I would like better FOV, I need to sacrify FOV at this moment. Ive just used my Aero briefly due to work away, but the resulotion is VERY good. The FOV is smaller than G1/G2, and the man issue is that the FOV looking down is much smaller than other headsets. Its disturbing to not being able to see downwards (lowwr psrt of instrument panel etc) as with most other headsets. I need to tilt the head down where with other headsets I would se it without tilting the head. Probably I will lger used to this quite fast but I think thatis the main issue/disturbance during the first hours for me. The sharpness of the Aeros isnt compatible today with the FOV of the 8KX so one needs to decide what to sacrifice.