Thinder

I noticed in another game an improvement in clarity when the on-screen display size was reduced, in DCS we only have resolutions to play with. In VR, the usefulness of having the view repeated in our screen is more than doubtful, the GPU has to render the headset visuals but also what we don't see when we play which is a complete waste of system resource. Usually I don't like to fiddle with DCS files (like adding lines to force VR to OpenBeta for example), but I wouldn't hesitate very long if I could change the on-screen resolution and size to the quarter of the minimum available in DCS setting options or even turn it off completely. Does anyone knows how to do this? Thanks in advance for your insights.

Good tip, I'm not too concerned about latency, I'm set up for low latency from my RAM-CPU bounding so this looks interesting, I take note. >>> Test with Mirage 2000C top three level test Caucasus map. Lag averages 13.5/14ms. There is a visible improvement in clarity but the FPS is way down compared to what I obtained in my last test video, the images from close objects and terrain are jerky and the DCS settings are also a lot lower than what they used to be. I had a reply from a development team member in reply from my insight, they hope the release for full support for multi-core processors will give a noticeable performance boost. This will go some way to get closer to the speed and quality I know my PC is capable of producing, then it will be up to AMD to sort their drivers because it also holds performances down a little... I know some players needed this update for their headsets but Pico users certainly didn't...

That's perhaps why nobody is using Hynix A/M die with Ryzen3 or 3D, bandwidth is not what matters with the Ryzen3, low latency is and if you ask AMD support, they will recommend B.die, 4 X 1 rank Cl14 kits, 3200 or 3600 MHz, not anything with higher latency because those CPUs are not designed for it... It's not you, your perception of "reality" or bias which dictate their controllers limits and the only reason why RAM manufacturers haven't lowered the latency of DDR5 is because their ships become unstable. AMD knew that long ago, that's why their CPUs architecture is now designed for larger bandwidth and higher frequencies, it doesn't change the fact that the day they can design a Cl14 DDR5, AMD CPUs will be running faster. So no, there isn't the equivalent of B.die for DDR5 yet and it certainly holds the CPU performances, especially AMD with their cache which benefit from lower latencies for an equivalent speed, it doesn't take a degree in physics to comprehend that. And something else, it's not "what I think" it's what it is, those 9 series clock faster, have larger caches but AMD made it clear that caches were designed for one purpose and it's data access time, otherwise said latency.

Hi! No I haven't tried this option. I tend to rely on what worked before the update and more on the GPU since it is quiet fast, most of my parameters related to VR on VD are shut down for this reason, I don't like the idea of having too many apps trying to compete vs each other, the fewer the better but I might try this.

No it doesn't, what surprises me is that this one happened not in a couple of decade but in a month and one update, I had better time flying VR with a 5600X, 32GB of Cl14 and a 1080Ti than with a 3 grand PC designed for the purpose, just saying, something went south, big time....

Support for VR that doesn't lower image quality and destroy GPU raw performance would be a good start... We'll see how this pans out. I'm not sure multithreading is going to be the solution for a top heavy implementation of VR in this game, the issues are not with the players PC performances but in the increased demand put on them, the heavier the app, the more we'll need from our PCs, not good enough. Then they think in terms of FPS when the image quality is way lower than what it was a month ago, I understand people want more FPS but if it come at the cost of clarity it's not the solution either... Vulkan API? Not sure about this one, watching the video...

Welcome to the club. Since DCS released an update with "VR Support", I experienced the worst loss of image quality and performances I've seen ever, then AMD joined the fun with their driver update... The point is, DCS developers needs to wake the hell up and sort out the whole thing up because with the same PC, other flight sims like Il2 or Microsoft F-S are playing like dream in VR with much better image quality, same for some other games like Elite Dangerous (not in the middle of nowhere but in a busy station it's close to DCS demands on GPUs), image quality is far better. Unless people start saying it loud and louder and stop swallowing the Fairy Tales of those who pretend to have a viable solution with added Apps, this situation is gonna perdure, after all we're customers and support the game by purchasing modules, we should be treated as such, there have been some improvement but it's not yet what it used to be. Just say it.

Not being sure seems to be your thing, after your assumptions on the Pico, you missed the fact that those videos were a TEST and I don't think the last one was stuttering like crazy, in any case I didn't finish to set up my system when your beloved geniuses released the most destructive update I have seen for years of playing this game. Nothing subjective there. Now if you'll excuse me I have seen enough of your avatar and read the B.S you keep sputting. Ignore list. Bye.

One trick that can be used to compensate for loss of performance due to bad drivers that I use in Elite Dangerous: Reducing the screen replay to a minimum, so the card doesn't have to fill up as many pixels on top of that of the headset. On DCS it should be possible to rewrite the lines of the page giving the minimum screen resolution to let's say 1/4th of your screen size, I noticed a real improvement in E-D and it's not too far from DCS when it comes to demands on GPU, antialiasing was immediately looking way better among other things, if anyone knows where this file is and how to do it, I'm buying. That's why I specified that it was only my way to operate, I understand motion sickness but I'm more than happy to go through loads of disorienting events since I flew real A-Cs and jump from them a little later, we're talking +/-G forces, spin with or without the airframe etc, I sailed a lot too as a kid on a 35t pre-WWII racer and never got sea sick, so those issues are not dictating my settings, I guess I'm one of the lucky 1%. >>> Just another thing to say: This update have reduced the quality of the visuals and performances in VR to a point where even with reduced settings, I have jerky side details and can't even see the electric lines. Compare this to my flight with the Mirage F1EE at Nellis...

Well it is the way I obtained the results you can see in my videos, before the DCS update that is, because after that the loss of quality and performances was so bad I couldn't even see the three line in the middle of the HUD and the image on the side was jerky as hell. It's better now but not as good as it used to be in January when I started testing the GPU and uploading videos on Youtube, after that like most Pico users I tried the solutions on offer in the forum but none worked satisfyingly, for the simple reason that adding layers of app only make things worse, it had to be sorted by DCS developers. You have to understand, I only use Pico Streaming Assistant and when the headset is linked to the PC (USB 3.2 Gen 2x2 20Gbps), Steam VR kicks-in automatically, then I use Virtual Desktop to start DCS or I start Elite Dangerous directly from the VR Room without it, no need for two extra layers of apps. So I decided to seat it out and played Elite Dangerous Horizon a little more only to figure that the AMD drivers were causing the moons where we need to land to have access to engineers to distort like cracked nuts, I even had to fly through the moon surface to land on one station, then I was lucky because most of them are impossible to reach... So between DCS update and AMD drivers, I've been hit rather hard I think, a good thing that I managed to test my GPU before hell broke loose, at least I know what it can do...

I have no clue. First I'm never focused on FPS but image quality and playability, if 40 FPS looks good then I'll get the best image quality at this speed, I'd say in my best tests, the FPS must have been in the neighbouring of 55/60FPS, the fact that I pushed the card to those high settings is much more for testing its capabilities than anything else, then I lowered those settings to get the best image quality. You can see that in my last video (Mirage F1EE, Nellis AFB), where the side view of close objects (threes, buildings etc) is smooth and the sharpness enough for me to see the electric lines, that's how I operate, flying low has this advantage, you can see how your GPU performs with details in a way altitude makes impossible. Then to me, DCS doesn't need to be played at 80/90FPS, it's not like a footie or shooter game where the smallest timing matters, you even can have twice the lag and ping times, it won't matter much for as long as the game is responsive and looks good. I can't find Asynchronous Reprojection in my range of Pico or Adrenalin settings, and didn't bother with that, my Pico is set for Ultra Display Mode, 150 Mbps, 90 Hz and the rest is done entirely by the GPU including game settings override. I see that you fell for the same assumption than I did thinking that the latest driver would bring more performances... It doesn't on the Ace Max, it's 4X8 instead of 4X16, and to be honest, this mobo is probably the worst of the stuff I procured for my upgrade, accessibility is mediocre, you have to dismount M2 SSDs to access the battery, the GPU can't be installed on PCI_E2 with the USB2 connector cable under it. Then there is the little matter of how fragile the BIOS is, my problem with PCI_E1 was coming from a BIOS setting (Gen1 to Gen3) which would turn itself back to auto at the first opportunity, forcing me to remount the card back to PCI_E2 and reset the PCI_E1 to Gen1 in BIOS because I had no signal...

Unfortunately I can't tell you anything about it, if there is a subject flying way over my head it's drivers, I haven't studied it in any form or depth. I only can hope that AMD will get their singer out and sort those drivers issues asap, they are already in the red with their customers and losing market share, I don't think this eludes them. For this sort of info, the best echo chamber is the AMD forum people don't hesitate to post their grievances there because it looks like it is where AMD support get their info from unless I get it wrong it's the worst I've seen of all companies I had to contact for support and it looks like the driver issues are not only affecting my GPU generation... The worst about it is that they removed the drivers that were working well and it doesn't seem like we can get them from anywhere, I don't care about the fancy stuff they added, it made my card lightning fast with excellent visual clarity and it is what I expect from a driver . I had an EVGA GEFORCE 1080Ti previous to this one and was delighted with its performances, especially because I procured it second hand from CEX and it served me two for years without a glitch, if it had been sufficient to run DCS at 4K, I would probably still have it. Having said that, I'm happy I get this GPU, it's damned fast as I know from my tests, it's only a matter of drivers and has little to do with the card...

Yes, the visual quality was close to on-screen replays, what I did was to push the DCS settings close to maximum with Pixel density up to 16 for example and at the time I had an issue with my motherboard and the card was running on PCI_E2, meaning not at its max capacity, this have been sorted since. I flew low level and looked at the terrain near me to see if the play was jerky or not, if it is, I lower the game settings until everything looks smooth, I also do a vertical climb into clouds when possible to see the quality of terrain and clouds. Now when it comes to raw performances, the card can easily run 10% faster than it does now with proper drivers only, in fact, my 3DMark tests show 9.3% loss of performance since the drivers issues started to creep up, as for my settings you can see the details on the topic I posted for the first run. Same thing here, I didn't know yet how to use Afterburner so the overlay is that of the screen recording, I haven't done any in-game FPS recording yet, I'll wait until a driver allows me to recover the full performances of the card, lesson learned, I wont trust driver updates before I read comments on AMD forum about it. I think the XT will be perfectly capable of running VR in DCS, only not with the same high settings (drivers sorted for both), but still adequate. Sapphire Radeon RX 7900 XTX Nitro+ Vapor-X 24GB GDDR6 first run.

I couldn't comment on the 7900XT since my GPU is a RX 7900 XTX, there are no issues with my card, it runs fast and cool and if you look at my videos you can see this for yourself. The issues are with VR support in DCS and AMD drivers at the moment, they both holding the VR performances the card is capable of, AMD with the last 3 drivers release, although they made progresses, and DCS since the last OpenBeta update which caused a significant loss of visual quality with the Pico4, there too progressing but not level with what it was. Since I was lucky enough to do my testing before both those drivers and DCS update releases I know what the card is really capable of, AMD are visibly working hard trying to sort their drivers out and there have been a slight improvement with DCS too but it is not what it was when I first tested my GPU both in visual quality and which level the card is allowed to perform. Now if you want to know if I regret my choice, hell no, the Sapphire Radeon RX 7900 XTX Nitro+ Vapor-X 24GB GDDR6 is a hell of a piece of hardware and it proves that all the gossip about AMD GPU exploding were just that, Youtube gurus material, they make their money with this and keep pushing it. Those cards were mainly mishandled and that's the reason why they had issues, you could as well get the wrong Nvidia 4090 and see it burn because of bad connectors and , bad drivers too, only it will cost you a minimum of £450 more for your trouble, and not one of us AMD users cared to spam the stories because it is not worth it. My tip, go for the manufacturer offering the best cooling solution, not because those cards are at risk to explode but because they have thermal limits that causes them to throttle down, so pay attention to this aspect as well as your case cooling and in passing it goes for Nvidia cards too. The overlay is that of the on-screen replay NOT the actual game recording.

Here at 5:37, they explain why they developed the 3D cache and it's all about access time, otherwise said; latency. That's why I have a problem with the DDR5 thing, there isn't a single RAM manufacturer who came up with the equivalent of B.Die and their chips cannot run stable at lower latency (Cl16) and high frequencies together, so I'll seat this one out and wait until the technology is there for other purpose than financing their R&D, because right now, it is what it going on.

9 7950X3D and the rest of them running of DDR5... It's the opposite. Since I upgraded from one to the other, I had the opportunity to test them back to back with 3600 MHz RAM kit, using the same settings in testing with 3DMark Pro, the 7 5800X 3D run circles around the 5600X, results with Cl14 and 4 X 1 rank for the 5600X are good but they are nothing short of impressive in the case of the 5800X 3D. Percentages of scores are computed comparing to the previous RAM kit or CPU. 5600X. 32GB of Cl14 3200MHz. 4 X 1 rank. 5800X 3D 32GB of Cl14 3600NHz. 4 X 1 rank. Improvements over the 5600X. So obviously the combination of 96MB L3 Cache and Cl14 RAM (plus interleaving in the case of a 4 X 1 rank kit) is a lot more efficient than Cl14 on its own with 5600X upgraded from a Cl16 kit. The 5600X clocks faster at 4.7GHz vs 4.5GHz and during the test was boosted with Ryzen Master, so was the GPU (EVGA 1080Ti) with Afterburner, no boost for the upgraded configuration. Note than instead of O-Cing my RAM, I upgraded it to a 64GB kit, Cl14 3600MHz 4 X 1 rank, same manufacturer, so when they said lower latency was the goal of the chache on the 5800X 3D video, it really was a clue.

What worries me is the RAM support for the 9000 series. It looks more flexible with the possibility to use 4 X 2 ranks per stick but in a 4 X sticks configuration, the 9 7900 is limited to DDR5-3600, but if one really wants to take advantage of the cache, you'll need a hell of a high frequency and if possible, interleaving as well. The whole idea of the cache was low latency, with DDR5 it can be compensated with higher frequencies but this frequency range is not it yet, so unless AMD allows their CPU controllers to support faster RAM in 4 X Stick configuration, the gain will remain limited. At least we don't have this issue with the 5800X3D, with Cl 14 the gain is very noticeable, low latency, 3600MHz, interleaving... it would be much better if the CPU designed to take DDR5 could see a similar RAM bounding made possible.

Whatever works for you. I haven't tried this solution but what I was suggested by all the specialists of the forum and none of them actually managed to recover the loss of visual quality I obtained before the update... As for me misinforming people... Funny one could think that I would try to get people to believe I ran DCS at 1200FPS with near maxed-out in-game settings... Disclaimer I note that while I am accused of posting misinformation, the guy who claims that haven't replied to my question, did his solutions recovered the quality lost after the update? The answer is NO, and he explains why it was impossible to be done earlier in this topic, the more apps, the lower the quality... I also noticed that despite some improvement in native DCS settings now, it is still not as good as it was before the update and at the time of the first test, I wasn't able to use PCI_E1 with the loss associated with PCI_E2. End of debate, DCS screwed up and corrected it but it's not as good as what it was then.

Get lost, it's not my fault if you're feeling insecure and need to resort to character assassination plus other attitude driven B.S to make your points. I'm not one of your groupies. Copy? You're now in my ignore list, as I said the day I need an opinion I know where to ask, you're not one of them. Bye.

The Pico4 is a good pick for anyone wanting to play VR on a budget, it is a mid-range headset and works rather well as such. The problem is support because it is new and neither DCS nor Steam truly support it fully, with time it will become a viable replacement for the G2 which is no longer produced and there is little difference between the two; the G2 had a slightly better clarity from its hot spot but it is very small, whether the Pico had an overall clarity allowing to see details without turning your head. With proper settings it is nearly ideal for playing DCS, I couldn't wait for Pimax to release their Xstal and saved the money to send chocolate to my family for X-Mass and treat myself as well with a new RAM kit (Cl14 64GB 3600), I'll see in the future what come out, looking for similar-to-better visual performances but increased FoV. I'd say that I don't think that there will be a significant improvement in visual quality from the next generation of headsets, the Pico4 can last you for a few years, time for the technology to get cheaper and it will fill the bill all that time, but that's only my opinion.

LOL! It's so funny to read you guys because you always jump to conclusions before knowing HALF THE FACTS, that's because you don't inform yourself properly for a starter. I mentioned this in a disclaimer saying something like "don't pay attention about the FPS it's NOT the game FPS but screen recording of the replay". SAVVY? And btw, after testing OpenBeta again today, I don't have any of the loss of quality I experienced after the infamous update anymore, back to where I was then, still using the same (as few as possible) APPs and testing different settings, it took time but I got there simply seating this one out. And to nail it, I even posted a request for information on how to get the overlay showing in replays instead of recording of the replays, I didn't know how to set up Afterburner... My bad. For your info, my GPU offers the option to override game settings, I've been testing different anti-aliasing methods, the best being SSAA for AMD and I use it for at least playing Elite Dangerous, perhaps I will use a different profile for DCS to get a smoother play. I don't have to add layers and layers of stuff which as you mentioned yourself in this topic are causing the issues to worsen, not get better, image quality is great again so I can play around with game and GPU performances. Now you can return the favor and tell us, honestly, did you manage to restore the visual quality of the Pico4 as it was before this stupid update ? You don't have to reply... So as I said in this topic, it can only be sorted by developers, the rest is never going to cut it for the precise reason you mentioned, at least we agreed on this point. ps I use a cable plugged into a USB 3.2 Gen2, with 20Gbps, a X 5 higher bandwidth than WiFi 6E. Have a nice day.

What doesn't make sense is your assumption that you know everything, down to what other players experienced. FACT: Steam VR doesn't start with Pico4 without Streaming assistant, it has to detect it first, I could make a video of the procedure to start DCS just to make my point but it's wasted time apparently. 1: Streaming assistant. 2: Steam VR. 3: Virtual Desktop, you can start the game from there, That's how I managed my 4 videos happy or not, you can keep banging chest pretending you know better than me what I did, it doesn't work, as for the geezer who has an issue with frame rate, not everyone plays with bottlenecked PCs. About "incredible frame rates", I never mentioned it, since I didn't test Frame rate but visual quality first and the videos are there to prove it, plus I just tried it again and it works, I lowered the settings to get a smoother play and was about to start testing with Afterburner when this stupid update caused the issues. In short, I know where to ask for opinions and you're not on my list. By a margin. For the others. All those half butt solutions are not going to change another fact: The update is buggered, and the problem can only be resolved by developers, all the rest isn't going to bring back the lost visual quality of the game previous to the update if they don't fix it.

Read my replies in P.M.

Well, yes it does. This is what I used to do all my system set up and it worked, not only it did work but I had very good through the lens image, as for the quality, watch the videos, after the update, I just never was able to reproduce those settings and get my headset to work properly. That's probably why so many players are complaining about it since this update, right? Now instead of trying to tell me that all I experienced before never happened, perhaps you could quit the attitude and think about it. I've been through all of this before and am not going to take more of it... Pico doesn't start without Steam VR or Steam without Streaming Assistant, now you can tell me how you manage to get it to work without it and yes it works since I am using it right now. Same here, waste of storage space, one of the solutions proposed to users after they experienced issues AFTER the update, and... I didn't know about Pico's VirtualDesktop Streamer, Open XR app or anything else until I hit those bugs and was suggested those solutions, as you mentioned, they don't work as well as what I had before. = FACTS. I do, and it's FAST, SMOOTH and TROUBLE-FREE. Now watch the videos and come back when you figured you missed something, here are the settings I used.

This is my find as well. I experience a lot of it which is particularly annoying when flying at very low levels where it's where I do most of my testing, I also do vertical climbs for scenery and clouds rendering quality and this occurs mainly at lower levels. I'm not sure how to get rid of it, but I lost a lot of image quality through the lens since this update, when I first started setting up my new GPU, I maxed out nearly all DCS settings to push it and it was fine with the Pico. I could clearly see the electric lines and if you watch the replays there were nearly no flickering on the side of the screen where it tends to occur when you pass by ground objects at high speed. Rig set up in VR My VR settings were simple: Streaming Assistant. Steam VR Beta. Virtual Desktop and go. In DCS I had the pixel density up to 1.6 without problem too. Now I can't run this rig at stock DCS settings without this cyclic degradation of central area, if I try higher settings, the HUD is completely fogged... I upgraded to Windows 11 Pro because Win 10 crashed so often it became nearly impossible to reinstall it, there clearly was an issue, also I got a brand new kit of 64MB Cl14 Win 10 didn't support, my PC runs smooth, no fault, high performances in tests with 3DMark Pro and my replays looks great, only this VR bottleneck remains to be resolved. I'm gonna try to play with and without the --force_enable_VR --force_OpenXR line, I'm not convinced Open XR works for everyone...