Gunnars Driver

Yes, my second cable broke recently. Varjo had at least 4 weeks of lead time until shipping So I did get the amazon cable. Bought this: It Works fine. Feels smoother than the stock cable and much less rubber grip than the stock cable so it doesn’t kink everywhere. Whats important is that the cable delivers quite some power to the headset, so any cable used must be able to deliver that power.

Found another thread locked. Thinking of upgrading to the 5090, from 4090. The thing is, the used price for 4090 is insane today, making the delta after selling the 4090 and getting a 5090 taste quite good. I get the ~15% performance difference. Someone wrote in a locked theead about having issues to get the 5090 to run with certain VR-sets ( I use Varjo Aero). Is these issues still present, anyone?

Thanks! Much appreciated I had a very nice setup with mbuccia and multithreading before the reinstall (W11 would not upgrade for some reason so I had to perform a clean install). I had 90fps constant with MT and Mbuccias so I’ll try to get back to that convinient setup

Thanks, good the get that verified (I did find info about that on the mbuccias page after writing the post).

Did a new install in the beginning of the year and havent used DCS since. But it's time! Is still the first post valid, like using How to: Varjo OpenXR Mode which worked very fine for me with foveated rendering etc ? Or do we have any other way to use the varjo today?

Ohh no . Rip dburne Thanks for the information, even if it was not one hoped

Old post but still: There will not be Icing conditions in a snow storm. The snow is already frozen, or wet. Icing conditions happens in clouds, of fog or (barely) dense mist. Happens also from freezing rain or drizzle, but other than these = no.

Been out of the DVS for quite a while… does 2.9 work as before with MT and DFR ? Only need to update or is there any things needed to be done ? Didnt see anything on first page….

Anyone having issue with the F-18 radar with either Varjo DFR of DCS MT? Did a little gaming today, and my friends didnt have any issues with the radar but I saw it omn the first flight with DCS MT and Varjo DFR, and I had it today also. The altitude numbers of the radar lobe at range is faulty, always same number for upper and lower limit, and the radar setting SILENT is boxed, which seems like it would be off. Sleving the lobe up and down dosent work, and also, it doesnt see anything. I now remember I didnt check that is was set to ON, but autostarted A/C have had it to on before.

There seems to be headroom for other adjustments, if the framrate is locked at 90fps. I saw a few pages back that there could be a problem with setting pheriferal resolution too low? What level is recommended by you guys that have tested this? (I do not use any vsync, and no motionsmoothing/reprojection etc.)

Nice! What settings do you use for the rendering (fovea/pheripheral) ?

Well, I made that update that came today. Started with steam openVR, worked just like before. Same frametimes, same fps, maybe a tad lower at low level over land. Then I tried MT again, after re-running mbucchias DFR setup. Now…. ….it works flawless. For 25 minutes of flying I had 90 fps all the time, even at mach 1 at low level and landed at senaki kohlki and still had 90 fps. Second test was pheriperal set to 0.8 and focus/fovea at 1.5, still 90 fps all the time I did not have a single stutter or like yesterday, frame time that cause the game to stop shortly….it just flows all the time. I think I always have seen the threes on ground move slightly choppy even at 90fps but now they actually flow around very smooth. I do not get how being GPU-bound and having good CPU overhead can turn into this, but I-m sure will not complain This feels like the biggest step forward since I started with DCS, so some very big thanks to mbucchia, dcs people and also you Supmua that is so helpful -Great work!

Just tried Steam OpenVR and it still works very nice, all settings still the same, so i might stay with that for a while. CPU framtimes 4-6ms same as before GPU frametimes 7-13ms, same as before average FPS not that far from 90, same as before.

I followed the guide for DCS multi-threaded via Varjo OpenXR, it seem to work like it should whennit cones to geting it to run with MT and DFR. Witouth any settings changed I did get (much) worse overall performance compared to the old steam openVR. (that turbo mode is still activated, will try it of. Never tryed Resizable bar). I did run the steam openVR without any sync to 45 etc, and did get 90fps most of the time, at low level overland about 75 (average in fpsVR about 87 or do) but just because the GPU frame time went slightly above 11.1ms, some 12-13ms. Gaming was of course not always 100% smooth but the stutter was ”proportional” to the GPU frame time, so not that bad. The CPU frame time was mainly 4-6ms and never ever above 9-10. With MT /DFR i can not see the frame times other than the built in DCS coubyer that shows CPU bound all the time. I get quite bad stutter from time to time, feels like frame times briefly goes well above 22 ms. Between the stutter I get 90fps sometimes but not as often as in ST with steam openvr. With no tools for evaluation, it feels strange going from Single thread with no CPU limitations but sometimes GPU bound to ”always” CPU bound as the DCS tool states. No DCS settings is changed.. Any tips where to begin sort it out? [Edit]13900/Z790/32Gb DDR5 6200mhz and RTX4090.

If you follow the setup tips for new owners tge missalignment will dissapear. it is the standard Varjo setup that causes this. Read the setup information in post 1. I suggest beginking with B steam openVR. the setup is easy to follow and the win in experience is very good. https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/#comment-4960863