Jyge

299 $ is a bit salty price tag for my presumed needs ...

Every now and then I have a moment that I miss VR Controllers. Also I would like to test couple of other games in VR. So the question is, what is the easiest way to get controllers for Varjo Aero? I saw that there is some - I think Steam application - that emulates Vive controllers, but I think it may not work as, for example DCS does not start SteamVR. The software also costs about 20$ so I do not want to give away that money for nothing. It claims to be able to emulate handcontrollers with two mouse or xbox controller, so basically I might be interested, just do not know if it is of any use with Varjo

I don't really think that the cableless stuff is without performance hit, additionally, I would be loath to recommend anything from Zuckerberg, I am still sour how he shot down the Oculus development, if Oculus would have pursued Santa Fe, it might be that we would have had foveated rendering and depth focus already earlier. But that is besides the point, the headset is maybe a secondary question, I think the selection of a good GPU is where I would appreciate some tips.

A friend of mine indicated interest for rig update and getting into the VR business. Now I myself have had my experiences. I had 1080 Ti for years, it brought me through original Rift, Samsung Odyssey 2 and both HP Reverbs. Once I went for Varjo Aero I updated my own rig and got myself 3080 Ti. Now some might disagree here but I was pretty happy with 1080 Ti and the funny part is that somewhere there coming down from Rift I was always able to reduce the Pixel Density so I actually felt that Reverb G2 was hardly any heavier than the previous low res headsets. With G2 I set it to 1.0 and never touched it ever since. So if I am asked for an affordable solution that runs with an adequate enjoyable experience I would go for 1080 Ti and Reverb G2, but it does not really make any sense to go for 1080 Ti on year 2023 AD, so I am wondering what is the one that matches the performance and comes with a reasonable price tag. I think 2xxx and 3xxx cards costed more than they were worth and 4xxx seems to provide more with less money, so after a quick look I got the impression that 4060 Ti would be the way to go (and Reverb G2). Any takes on this? I personally have not even installed MSFS, so I can not tell how everything works there, not even, if it is heavier than DCS. So I would appreciate some pointers on this one as well.

Just an update. Since I had other problems with headset not coming up after the boot, connection and stuff like that I got a new connection box and cables from Varjo. I do not know if this was the crucial factor, but after I updated my DCS to the latest beta (Varjo base version 3.10.1.14 - fw 0.17.0.486) it just simply worked. I keep my fingers crossed...

So what is the actual take on all this. I have been three weeks on a vacation and this weekend I wanted to fire up DCS. I still have the older DCS build and I do not play online, however, I think it would be still better to get the other improvements, so is it going to work if I update DCS to the latest beta and go for an older Varjo Base? How do I get an older version of Varjo Base? Just in case, does the rollback in DCS still work (DCS_updater.exe update 2.8.6.41066@openbeta) if I give the latest beta a go?

Too busy at the moment with this irritating thing called work, I am afraid it will drag into Friday, but please give an update how it went.

Yes, it works just fine for me now, you will certainly get the feeling and yes, I think the multi-thread version in the end is the way to go.

No, I am actually running the 2.8.6.41066, I'll have to see in one month or so if there is then the next version out and then try that one out. Eventually it will work, it always does.

Like I said I used the command line entry with the DCS Updater - "DCS_updater.exe update 2.8.6.41066@openbeta"

I got my Varjo Aero on Monday and it was running VR only on single thread DCS.exe. And no, the issue was not the checkbox, that was active on my DCS all right. In the end I got the hint on Discord to roll back to previous openbeta. I gave I gave .\DCS_updater.exe update 2.8.6.41066@openbeta and it immediately started in VR with bin-mt/DCS.exe so there is something that was broken on the new version. I hope this information helps to fix it on the oncoming releases.

Ok, somebody gave a hint in discord about rolling back the DCS version. I gave .\DCS_updater.exe update 2.8.6.41066@openbeta and the rollback seemed to work, afterwards I got the VR, most likely with foveated rendering as well, as I installed the Varjo-Foveated-0.2.0.msi somewhere there when I was trying to resolve the VR issue. I even installed the OpenXR toolkit only to be able to disable it... Anyway the rollback seems to be the solution for now. Hope ED will solve this one in the coming versions. I think I need to post the heads-up on that Bug thread as well

Meanwhile I looked at the log in DCS and saw this. 2023-07-19 19:28:22.649 ERROR VISUALIZER (Main): OpenXR exception: runtime is not available Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:322 After looking up, I saw this discussion - did not solve my problem though...If I launch with I launch with --force_enable_VR I get this narrow feedback window on desktop, like I usually do when the game is running VR (it does show only single view to DCS, "distorted" like viewing through the headset, not the quad one). If I launch without that force option, I get full desktop size 2D window of DCS. Also the "VR-like" window does not follow headset movement or anything. It is like the game would be running with VR, but completely oblivious to the existence of a headset... P.S at least Varjo support answered - they suspect my connector box or something may be defect and they are going to send me some stuff...we'll see how that will turn out...

Yes, I merely mention the single thread in order to point out that the system is actually running or that the start options that I am using are correct, indeed I want to get to the multi-thread and foveated rendering and anything that the headset can provide, but I think it helps to narrow down the errors to have hat comparison. Yes, I will try out the discord. That should be fun, I am admonishing my kids all the time since they hang around discord all the time and now I am falling down the same way. I need to close the door and see that they don't catch me red handed...

Is it then so that the single thread executable employs OpenVR? I mean, I have --force_openXR on the command line, doesn't it force it with single thread executable anyway. Where is the actual difference to multi-thread? I could disable the OpenVR switch and try it out both with single thread and multi-thread. Ok, I tried --force_varjo_VR and it did not work with multi-thread executable. I tried switching off the OpenVR and VR worked with single thread but not with multi-thread. So I am kind of running out ideas? Can I somehow try a fresh install of DCS? How would I do it? Copy my actual installation somewhere, uninstall DCS and start installation? I mean I do not even need to reinstall any modules, it is enough to see the GUI comes up? Is there something on Varjo configurations (where ever they are?), should I somehow first disable the foveated rendering completely and see if the multi-thread runs at all without it? As I said I haven't (at least knowingly) installed any wrappers or stuff. Would it help to install that mbucchia's wrapper. I do not run SteamVR, I guess there is no need to start it from Varjo Base?