Peedee

Nice that MSFS 2024 (beta 4) has gotten better in VR. But I find it real puzzling how he (and other youtubers) talk about butter smooth performance when they are getting framerates in the mid 30's - like in this video. That is just ridiculous. As long as you don't hit the refresh rate of the VR headsets refresh rate you get judder. Stable smoother judder now?? Perhaps. But it is still not butter smooth performance. I have flown MSFS 2020 since release, though it didn't get VR support before sometime later. And also MSFS 2024. I have used HP Reverb G2, Quest 2, Quest 3, Pico 4, Pimax 8KX, Pimax Crystal, Pimax Crystal Light, Pimax Super in both simulations. Three different PC setups during that time... And judder judder judder - most notable when looking out the sides or when in a turn. MSFS 2020 was way better than MSF2024. But still judder unless I tuned everything down until I hit 72 fps or 90 - depending on which refresh rate I had set for my headset. "You don't need that high of a frame rate in Microsoft flight simulation" I hear many of them (youtubers) say. Well, you do need 72 or 90. And, I got that in MSFS 2020 with my OG Crystal with correct tuning, then no judder, no stutters. And also in MSFS 2024 Upate 3 (I am not using beta) - and eventually with the Super too - by tuning it correctly and sacrifice some resolution and graphical effects. I wish Pimax would fix Smart Smoothing. That would make it easier - just needing 36 or 45 fps...

The 5090 system. It has a better CPU and more RAM too. The 4090 system is not used these days as much, I keep it for now and it will probably end up as Christmas present for my son. But OG Crystal is a good fit for the 4090 system

I have RTX 5090 and I run my headset at 72hz in DCS. I'd rather use that than loose details or clarity and getting 90.

I have incredible performance and visual quality with Quadviews. And I see you have the same CPU and GPU as me, and even more system RAM. I wonder how our experiences with Quad views are so different? I can not live without it It might cause issues at night time, but I have yet to do any real testing with that. Hope you enjoy your Super. Try other things than just DCS too, it's an amazing headset

I think there's an issue with DCS and Quadviews. The change in light/brightness and contrast can be seen also in day time with quad views and the big square outline in the foveated area - which is discussed elsewhere. Not so obvious, but it is there. Overall, in DCS, with or without Quadviews, I have to lower DCS gamma setting to 1.9 or else things look too blown out during daytime. I have not played much night time yet with my Super. I have been playing other games, like Le Man's Ultimate racing, and it looks good when driving at night. Also Skyrim VR with a Light mod that makes the nights and caves truly dark unless there are light sources nearby, also look good. They don't use Quad views. So I don't think it is hardware related. I will check out iRacing, which use Quadviews, and see what happens there during night driving-

Thanks for explaining. And, in my house the Buttkicker absolutely does make noise downstairs. Norwegian wooden house from 2015. Not sure how much problem it would be in a concrete building.

Nope... I'm kinda slow sometimes.. And I am sure your advice is well appreciated by those who do need it, seriously But, 20% usage by the Pi service is a lot I think. But since my experience in computer programming is from programming The Vic 20 from Commodore in Basic, in the early 80's, I don't know much about how different programs use different CPU cores. For example, will the Piservice app always use the same core unless you use Lasso, or is different from system to system (even if they would have the same CPU I mean), or can it be different on the same system from time to time? I know this is way outside what we are discussing here, but.. For example, NOW I don't have problems - maybe that is because on my system Piserver is not on the same core(s) as DCS? And could I experience booting up my system one day and suddenly Piserver has moved over to the same core as DCS and impact performance? I have tried so many "Voodoo, Karate, Judo and Ninja" tricks on my PCs over the years to get them to run flight simulators better... And many have just been placebo when really looking in to it. Your advice is obviously NOT placebo since it's easy to see that they were on the same core and things improved when spreading them. I think I can remember, after the Falcon 4 launch in 1998, I also became semi-religious for a while, saying prayers hoping Falcon4 wouldn't crash... That was a nasty one...

That part, yes. But since I dont't experience stutters, freezez and such now... what do I gain?

Nice! But Voila what? I mean, did you experience any practical improvement during gameplay? Higher FPS? I installed process lasso on another PC than this one some time back. All it did was leaving me confused. Not sure what I was actually doing or if it improved anything at all. So, I uninstalled it. That was on an Intel CPU based PC. This new here is AMD 9950x3D. Not sure if it (lasso) will actually do anything. I feel I have smooth gameplay, I don't experience stutters with my Crystal Super. If it helped you - good.

Thanks, it works now after enabling it.

Nice! Thanks. Will check it out.

@Calvin.Pimax Hi, I am on the latest Pimax Play, 1.42.1, and latest Crystal Super firmware. If you read my post above this I am rather happy with these updates. But - the last few days I can not use the volume buttons on the headset to access menus any more. Pressing the Volume up for 4 seconds (or even more) does not work to get to menus. That was a nice feature to have because that let me just keep my hand controllers safely in the box The volume buttons do work for adjusting the volume with short presses. Is this a known bug?

No image with Quad views? Try disabling Open XR Toolkit if you have that installed. Here’s a word from the guy who made both: Not sure if this helps you. Worth a try? And I am sorry to say that with your cpu and gpu you will have to make rather big compromises to get DCS run well on the Crystal Light. By running well I mean either stable over 72fps using 72hz in the headset or 90fps in 90hz mode. But it should be possible to get it run a bit better than now anyway. The Tallymouse video mentioned is also good.

That is disturbing to hear… how long time does it usually take before it happens? Maybe you already have answered this, but is it only in DCS?

My nVidia driver is from before the Summer I think..

My experience with the 1.42.1. PP update and Firmware update today. What kind of wizardry is this?? I did the 1.42.1.177 update of Pimax Play. And I updated my Pimax Crystal Super firmware from 1.07 to 1.08. As some of you might I have read here I have been a bit nervous about this because I think that my Crystal Super was running pretty well with 1.40.4 Pimax Play version and the 1.07 firmware for the Super. And I hate to break things. Especially the firmware update made me a bit nervous. And for a minute or two there right after the firmware update I was extra nervous. Pimax Play started to complain about USB connection - which was a problem that my Crystal OG used to have in the beginning "back in day" with my old PC. (But that became better and was eventually solved). But my Super never has had that issue before on this new PC. But I thought - "oh no..." My Super headset is bricked! And looking into the headset ... just a big yellow or green square that seemed to move randomly around. I unplugged the headset, re-started my PC and now it seems like it is working like before. I have not tried DCS yet. But I did a few short flights in MSFS 2024. Struggling with frame rate in MSFS 2024 with this headset is... as expected. So what I did some days before this Pimax update was to set Pimax Play at 0.75 resolution. Use Quad Views inside MSFS 2024, edit the MSFS 2024 config file to lower the Quadviews area from 0.5 to 0.3, and also with DLSS at Quality settings I have managed to get 72 fps with almost no stuttering either! Maybe not in the big cities and biggest airports, but elsewhere at least. Now - that fluidity has come with a price. Going from 1.0 to 0.75 in Pimax Play still gives a fairly big resolution, but of course it is not as sharp as 1.0/High setting. And then DLSS on top of that... But I have preferred the fluidity with 72 fps. When I read about people saying they have good and fluid experience with 35-40 fps i MSFS 2024 I just don't understand what they even mean. It's horrible. Anyway--- not as sharp then with these settings I had. But fluid. And still sharper than with my Quest 3 anyway - and much bigger FOV. Now here comes the 1.42.1 update... and I didn't know it applied 0.6 sharpening inside Pimax Play by default. So when I started up and got into the cockpit of the Comanche in MSFS 2024 I almost fell out of the chair. Everything was sharp! I thought I had forgot to set DLSS on, or forgot to lower the resolution in Pimax Play - but I had done all that. And secondly - the sound of the Comanche aircraft was really loud! I had to turn it down a bit. (It was not like this before the updates today). And that I am fairly sure is because of the 1.08 firmware update I also did - which I think I read was improving sound. So it sounded great, things were really sharp and crisp - almost too much - I think I will reduce the sharpening a bit. Right now it's sharper than my OG Crystal at 1.0 and no DLSS. That is my first impression. And it's so sharpened that I think it looks a bit over sharpened. But that's good. I can always tune it a bit down. And it's fluid at 72fps, stable outside the big cities. So, this sharpening feature - I really like. And I can't wait to try No Man's Sky in VR. I have to use DLSS there to get the performance, but there seems to be no in game sharpening there. And of course DCS later. Thanks Calvin and the team. Hopefully I won't run into trouble later on

What firmware on your Super? And what Pimax Play version?

Thanks!

Thanks Calvin! I believe I run version 1.40 or something right now with firmware 1.07 on the Crystal Super. If I update to the newest Pimax Play, and also update my Super to 1.08, would it be possible to go back to Pimax Play 1.40 even with the new 1.08 firmware installed? I mean - if I run into trouble with the newest Pimax Play.

Thanks a lot again! And, have you tried flying at night without Quadviews? The transparent big square that haunt some Quadviews user seem to cause trouble at night too. Though there has been quite some time since I did some night flying. I have, however, played Skyrim VR with a mod that makes the nights truly dark and caves totally dark if they are without any light source, and all variants between light and dark of course depending on the number of nearby torches/light sources. AND, I think it looks good! The local dimming seem to do its job. So, the night flying must be fixed of course, but I don't think it is the hardware. But I will try and do the update then, tomorrow. Also I will do the Crystal Super firmware update...wish me luck..these updates always scare me.

Thanks. Have noticed any issues with 1.42.1?

@Calvin.Pimax - and anyone else who has done this update: Does Pimax Play version 1.42.1.177 work with mbucchias Quadview? I know there was one version that did not work with mbucchias "external" Quadview and one could only use the one inside Pimax Play. Then there came a version that did work, but was not this latest 1.42.01.177 that Pimax Play today prompts to update to. So, anyone tried or know this? I am thinking about updating today. But still I would prefer the "external" quadviews and Tallymouses Quadview companion app. For now it gives a bit more control.

What resolution do you run your headset at, and are you using quadviews? I have to admit that I have not read or remember your other posts about jittering. Also - this might be a far stretch but I found this about jittering and Pimax AND Quadviews in MSFS 2024: https://forums.flightsimulator.com/t/image-shake-when-foveated-rendering-other-that-0-50-and-eye-tracking-enabled-on-pimax-crystal-og-wrong-resolution-division-when-fov-ren-scale-slider-introduced-in-su4/737911 Probably not the same thing. But, if you want, take a look at it.

@BIGNEWY SSAO OFF does not work. I have turned SSAO off, other things ON/OFF - all kinds of variations. It doesn't matter. The SSAO "solution" I think first spread on Reddit, but in reality it is not an solution. Maybe it lowers the visibility for some, but not for me and others. How much testing has the developers put into this instead of repeating the "solution"? In Eagle Dynamics defense I don't think they are to blame for it either. It is a Quad views problem - but likely in combination with other things. The only thing that reduces the problem (for me at least) is turning sharpening in DCS graphic settings down. It does not go away totally but it becomes more playable. Certain scenarios and lighting conditions makes it more or less visible. I thought I got rid of it after turning down sharpening, but then - new tried a new terrain, new lighting conditions and there it was again... Also having a very small foveated region makes it more pronounced I think. For the record, my visible sqaure is not as dark as the original poster here. It is more bright. Also, other screen shots I have seen of this, in DCS Forums and elsewhere have brighter squares than in the first post here. Now, in MSFS 2024, Quadviews was implemented some time ago. And there they have discovered the exact same problem. And it is not just a Pimax Quadviews problem, but people using static quad views with Quest 3 and even HP Reverb G2 sees it too when activating Quadviews. I have also seen people with Varjo headsets reporting this. See this thread: https://forums.flightsimulator.com/t/quad-views-brightness-difference-in-clouds/715212/14 That thread started in April, but the problem still persists even in the latest beta for Update 4. Hopefully ED will look into it, and see what they can do on their part. SSAO OFF does not solve it. Certainly not for everyone. Never hurts to try, but we have to keep it real. My suggestions for those who are bothered with it: 1. Try increasing the Foveated rendering area 2. Try increasing the Transition thickness area Both of this will decrease perfomance so not an ideal solution. But perhaps play around with it and see what is tolerable. 3. Turn down sharpening in DCS Settings. Can give a negative impact with image clarity compared to what you are used to. But again, what is worse? Big square outline or loose some sharpness? I tried lowering sharpness in Tally Mouse Quadviews companion app too, but that didn't seem to have such an impact. Though I am not sure. So in summary - SSAO OFF is not the solution. This is not just a DCS problem - it is there in MSFS 2024 too when using quad views. This is not just a Pimax problem. Quest, HP Reverb and Varjo users reports the same thing. Certain lighting situations makes it more visible.

72 Upscale mode? No thanks For now it seems I have reduced/removed the issues I had with Quadviews, so I will use that. 72 Upscale mode might make better sense for people with 4090 or less powerful graphic cards. If you are happy with your settings then be happy, and thanks for sharing them. Others might find them useful