Vandaahl

Depends on the rest of the network, but that's a bit out of my league. I'm not entirely sure if traffic will take the shortest route, or if your headset will travel through the closest router/switch. I mean it has to get an IP, and your PC won't be the one providing that. So the rest if the network needs to be at least 1000mbit capable. Technically it is possible. I got a Raspberry pie that emulates an access point, but thats a controller for a telescope and not part of a bigger network. It all sounds a bit cross-link-cable-of-old to me, so I dont think it will work well. But you got the thing, so follow your curiousity, and give it a go. Can't hurt to try, if you got the time for it. Otherwise, a dedicated router is never a bad investement

Nice, you're almost there. The 5ghz bit rate should be enough, but latency might indeed be a problem. Also make a dedicated access point NO one has access to, but your headset. I bought a dedicated router for it. My WiFi sucked anyway, so it was well worth the investment, regardless what I use, VD or link

I bought an Asus RT AX-57. One of the cheapest, but still a potent thingy. The AX55 was recommended, but out of stock, so it was a bit of a gamble, but its performing good on my end.

Yes, I mentioned having the same issues at first. Going 1 step back when flying 20 steps forward. Did you install fraps to look at what happens with the framerate? Remember, I locked my framerate at half the hrz VD is using to SSW in NVidia settings, but since you have an AMD GPU, you have to find a way to do the same on your AMD card. Could well be this is the case on your end. We both have different systems, so it could indeed be you're convicted to use SteamVr, where I have to use openComposite, or stuff like that. I can tell you how I fixed my stutters, in the hope it fixes yours, but it might not

Oh thats ok Its just that I'm pretty new to this kind of VR as well so I'm far from an expert. Those artefacts seem to be the areas out of view that aren't rendered, but need to be rendered when you turn your head. So the higher the latency your wireless contection is suffering from the bigger those artifacts are. I see them as well, but I really have to start a horizontal headbang in order to make them obvious. I'm sitting right infront of a dedicated WiFi6 access point with only one cient, my Quest2 headset. I would reduce bitrate since: ...increases quality AND latency. Latency is delay and not a good thing, so I would of phrased that line in a different way.

If the VD version running on your headset is from the Quest store and not from the Steam store, than I'm out of ideas, sry.

Well, my VD streamer did hang a couple of times yesterday, causing a freezed image in the headset, while the game happily jogged on. Since I switched to one of the faster codecs, not anymore. Not sure if its really a fix, but I keep it where it is for now since it performce nicely. I've been flying about on Marianna's in the warbirds on a steady 45 fps. I noticed the mozzy didn't keep it at 35, an F16 dropped it to 40, so I'm not there yet. But coming from a CV1, this is a breath of fresh air.

Strange I dont have all that. I bought a Quest2 2 weeks back, installed VD on the headset, the streamer on the PC and was underway. I dont have the toolkit nor any force option in the DCS shortcut. I don't have the oculus client running when I run VD, nor link or airlink enabled, just the service. I don't even dare to touch steamVr with a ten foot pole Oh, one tip, I used fraps to see what happened. SSW did half my FPS, but the result was not smooth. Basically, I didn't see a difference between auto and always enabled, I had to do that myself with the nvidia settings. Auto caused all kind of lag, stutters and anomalies I don't like. I rather have it constantly doing its thing, than going yolo as it sees fit. So with the FPS locked at 45 AND SSW enebled, its buttery smooth. These are my headset settings: This is the streamer: And my NVidia settings: Hope that helps

But you mentioned you uninstalled steamVr to see if it would work, why did you even had steamVr installed with the stand alone version + a Quest headset? Afaik, you don't need steamVr at all. Or am I missing something? If your screen turns black you seem to be almost there. Did you have a working VD implementation while using the release version? (so not this beta)

Stutter can mean a couple of things, but in my case it was AWS not working (correctly). Set the streamer to a 90hz output, but lock the FPS in your NVidea DCS settings to 45 FPS. After that, force AWS to always enabled in VD. On my end, VD started to nicely fill in the blanks frames, while my GPU has an easy life while being locked at 45 FPS.

In order to make it work on my end, I have to execute DCS from the streamer app on the PC. So right click the little streamer app logo on the task bar, and chose execute... select the DCS shortcut from the desktop and you should be on your way. Mind you, I'm using the stand alone version, not the steam DCS version.

Thx for that! All the way from the back of the class... Does this add any value for stand alone (Quest) users? Or merely for Steam(Vr) users? As a Quest2 + non-Steam user, I can ditch any Quest-link already, and solely depend on VD alone. So I'm not sure what this would improve for me.

Btw, this https://teamwadafak.com/how-to-run-dcs-dedicated-server-on-linux/ works, like a charm. Only for the whole installing wine part I used: https://wine.htmlvalidator.com/install-wine-on-ubuntu-18.04.html Just install the server as described, and change the winecfg accordingly. The commands to create the system links are useless because of used characters (quotes and what not), I used this for the plugin: ln -s ~/.wine/drive_c/Program\ Files/Eagle\ Dynamics/DCS\ World\ OpenBeta\ Server/bin/webrtc_plugin.dll ~/.wine/drive_c/Program\ Files/Eagle\ Dynamics/DCS\ World\ OpenBeta\ Server/webrtc_plugin.dll This for the updater: WINEARCH="win64" WINEDLLOVERRIDES="wbemprox=n" WINEPREFIX=~/.wine/ wine ~/.wine/drive_c/Program\ Files/Eagle\ Dynamics/DCS\ World\ OpenBeta\ Server/bin/DCS_updater.exe I don't need the DCS.exe to start the server, in fact, it doesn't even work (login fails for some reason after which the process grenades). The updater however works, does its thing and starts the server successfuly when it is done. So I edited the command line of shortcut of DCS.exe on the desktop and put the executing statement of the updater in it. I'm running the server on a i3, 2.8 GHZ, 8 gig internal memory lenovo mini PC with Kubuntu 18.04 installed.

I got the dredded "address unavailible" message, ran out of ideas and checked the logs. 2021-11-05 10:40:31.391 INFO NET: disconnected: 102 The callsign is already taken. Do NOT give your obeserver the same callsign as the one you are using on the client. Check the logs on the client, and you should get an idea about what is going on.