gonvise

Please, can you clarify a bit more about the use of the Quad Views option in the VR section? Is it just showing if we have QVFR mbucchia installed or is it necessary to activate this option for it to work?

Are you telling me that if someone wants to enable mbucchia's QVFR, in addition to following the installation instructions on github, they will have to enable this option in DCS or it will not work? Or the first time the layer is installed this option will appear checked?

Solved, Eye tracking had been mysteriously disabled from the win met aapp.

Hi, I don't know exactly how, but I no longer get the eye tracking option in the open xr toolkit within DCS. I think it's been since the MSFS2020 installation, but I don't rule out that it was before and I didn't notice, since I don't fly much lately. I've tried reinstalling but nothing. Any ideas? Thanks! null

Thanks, but It's a shame, the tube should be visible, in VR at least, and move when you turn your head just like the shadow changes when you do so; on the other hand, the movement of the body when you move your head is unreal.

Hi... I always fly in VR, and the addition of the pilot's body has been a turning point due to the realism and having the kneeboard at a glance, but I can't see the oxygen tube when I look at my chest, in fact, I found out it existed when I forced my head forward and "suddenly" it appeared. On the other hand, when I move my head, the body also moves from one side to the other, I don't know if it's intentional, but it's not very real.

Hi... I always fly in VR, and the addition of the pilot's body has been a turning point due to the realism and having the kneeboard at a glance. I don't know if this problem is exclusively mine and my quest pro, but I can't see the oxygen tube, in fact, I found out it existed when I forced my head forward and "suddenly" it appeared. On the other hand, when I move my head, the body also moves from one side to the other, I don't know if it's intentional, but it's not very real. Does the same happen to you?

I finally changed the 10900K/32GB/4090 for a 7800x3D/64GB/4090 and I've gained 8fps with more stability (in VR and tested in the same situations). I hope it gives you an idea.

Hi, so far I only replace nvngx_dlss.dll in the /mt-bin directory with the latest version from https://www.techpowerup.com/download/nvidia-dlss-dll/ , and within DCS I select DLAA. What is the default profile without using dlsstweaks?

I don't know why, but I have better results with VRS foveated of toolkit. Even after update muy CPU to 7800x3D, the stutters free and fluidity of VRS is better in my case than QVFR. Perhaps is because I use a high resolution multiplier or ASW always enabled... Give It a try!

Do you have infinity ammo enabled?

Perfect, the stall vibration is very important but seems like engine cut off suddenly.

And inside DCS vsync on or off?

Stall sound mute engine (tested in F18)... It is done this way intentionally? If so, shouldn't the engine vibrations still be felt even though we have entered a stall?

Some of you say that VD is the way to go, but you're not giving all the information, there are people who are going to buy a dedicated router for this (like me) and are going to be very disappointed (like me). 1. If you are used to ASW, VD doesn't have it, instead it has SSW, which is not nearly as good. For me, ASW is pure magic, with very little ghosting these days, and maintaining 45 FPS in all conditions gives me the smoothest and highest quality experience since I started in VR with the first Oculus. Is there any chance that VD will implement ASW? 2. If you don't care about ASW, ok, then it's a matter of matching the quality modes that VD has to what you have with cable link, but even so, I haven't found any codec where I didn't notice some compression effect (MFD a bit blurry) that I don't have with cable link. By the way, cable link still works with stopping updates (mine is nor updated) or with replacing by v67 files, meta has already said that it will be fixed in v69, so let's not go crazy. Whoever wants to try it can do so (like me), but VD is not the new panacea; Yes, it may possibly be an option, especially if we fly in medium quality, but if we push the link cable's capabilities to the maximum, at least I, who have been trying things for days, don't know how to do it.

Ok, we are clear that meta are the devil (not sarcasm) and that they don't give a sh*t about PCVR. On the other hand, we have VD that seems to listen, but no cable link, only wifi and, then, it must to stream the video from PC to googles. I have already posted in several posts the configuration that I have in cable link that gives me the quality and fluidity that I would like to achieve with VD. Taking into account that QVFR and toolkit work in VD, that supersampling can be done via PD in DCS or even with QVFR, I still have the problem that, no matter how many codecs I change in VD, in all of them I get that blurry scene that I don't get in cable link at 960. As @slughead says, ok, it's not a question of bitrate values, but of the combination of that bitrate and the corresponding codec, so... Can someone tell me which code I should choose to get the least compression possible and get it close to what I see with cable link? It's just that no matter how much I want to use VD, and I do, I can't get rid of that blurry halo due to video compression.

Sure, it's a matter of taste. I for one can tolerate a bit of ghosting on jets, especially since I'm not flying alongside other jets very often, and with the last nvidia DLSS DLL ghosting is no longer noticeable anywhere, not even in the trees, but what I can't change is the quality and fluidity of that setup. With no ASW or with SSW the head or plane turn is not constant, depends on the fps at that time, if you look at the sky it is...meh

ASW always enabled, It goes like silk as long as you have those 45 to spare. I used to use QVFR, but even though it worked fine and did its job, being CPU intensive in some situations with many objects it caused me stutters, and since the last DCS update I started using the eye tracking from the toolkit, which as mbucchia said is another FR implementation that gives less performance improvement but at the cost of GPU, and since I have plenty of GPU, it works much better for me. Right now DCS is a dream. Here all my settings: Be careful, as @slughead said, this only disables updates to the windows quest app, to disable the quest pro firmware (SO) updates:

I'm not trying to compare VD and Cable Link at same parameters, what I want is to have the same quality and fluidity with VD as with Cable Link with the settings specified. If not, I have no reason to move on to VD which, on the other hand, is what I would like for the future. Meta app x1, OTT x2. Sharpening set in DCS. Latency doesn't matter to me at the moment, I would just like to achieve the same quality. Considering that with "godlike" and QVFR at 1.5 I don't achieve the same quality as with cable link, I can only think that it is a codec "bottleneck" and yes, I have tried both compatible ones.

Sure! But the problem is I can't, max VD bitrate is only 400! I can't find any combination in VD that gives me the quality/fluidity that I get with the link cable. And the difference is not subtle, it's much more than that. If I could at least match the quality, then I would optimize the performance, but I can't. If you know how to do it, please tell me. I think the problem is that you are used to a scaling of at most 1.3 or 1.4, and you don't perceive almost any difference between VD "god like" and the link cable... also, the link cable comes by default with a fairly low bitrate. I think that if you haven't done it and you try these parameters with the link cable you would be surprised by the quality that the quest pro can get. I bought a 300€ router among other things to try to make the VD work, so imagine how much I want it to work well.

Exactly, I have even put the DCS PD at 2, just like I have it by cable via OTT, I think it is because of the encoder bitrate, the scene is a bit blurry compared to the cable, no matter how much scaling we put on it, via VD "god like", DCS PD, etc.

Unfortunately, at the moment I cannot achieve the quality and fluidity of the cable link with VD.

For me the important now is quest pro is not updated to v68 after stable release, since toolkit/eye tracking works like a dream for me in this momment. However, I hope they fix the current toolkit bug with v68 PTC. Firmware/SO quest pro disable update -> https://www.youtube.com/watch?v=1qAGmqXrOG0&t=1s Windows quest link app disable update ->

I've always thought the windows app was backwards compatible with the different Quest firmware versions, but who knows, I'll do that too, thanks.