MadMonty

I had the same problem with the top strap, somehow nothing seemed to fit. The solution came by chance - I always had the strap above the mask (as would be intuitively correct), but the headset sits much better when the top strap is inside the mask of the headset at the upper edge. So the top strap touches my upper forehead directly and then the mask lies on top without any negative influence (distance to eyes or incident light)

Due to very limited testing time, I could only play DCS. But as mentioned before by Chris, after a couple of restarts my lags where also gone. I still find it hard to get a proper room tracking due to my setup. Waiting for the lighthouse faceplate for the Super…

I'm glad it finally worked out. As one of the lucky ones who has been able to test the Super for a few weeks now, I can only say that it was worth the wait. Have fun unpacking and enjoy!

Great research Calvin - haven´t found that reddit article... It is SSAO - disabling it removes the grey veal. MANY THANKS!

I guess too... After installing the latest Pimax Play version my FPS went down low and I was shocked. Just found out that Quadview/FR was deactivated and after activating it, I was back on track. Just Eye tracking on/off can´t have such an impact.

Submitted a ticket with a log file (had to use wetransfer since logfile was too big to upload) The gray, visible area in the cockpit is independent of foveated rendering, regardless of which settings I change, even in the Super settings (contrast, brightness, etc.). The gray veil remains as a rectangle and moves with my pupils. I have attached the log file for this. By the way, even if I reduce or enlarge the area of foveated rendering, the gray rectangle remains the same size; there seems to be no connection here.

Thank you very much, I am fully aware that tracking with Lighthouse is a completely different matter. Unfortunately, the faceplate is not yet available for the Super, but yes, I will definitely buy it, as with the entire cockpit setup on the platform, there is always a risk of restrictions in head tracking. Incidentally, the new version of Pimax Play seems to improve room tracking, but I did experience some strange lags while flying, which caused movements to be delayed briefly, which was very unpleasant. I'll look into this further and try rolling back to the old Pimax Play version when I have a little more time to see if that's the only reason.

Thanks Calvin, I already featured the video here: Despite using the settings I have the reported problems...

I know that my cockpit on a motion platform creates very challenging conditions for a VR headset. However, tracking always worked without any problems with my Reverb G2. I'm still experimenting with the Crystal Super. I've hung dozens of QR codes on my walls, I'm sitting in the basement, and I've darkened the only available (dark) window. I've tried a wide variety of lighting scenarios and, especially with passthrough, made sure that the environment provides good contrast without flickering. Nevertheless, I still experience the phenomenon that the Super loses tracking over time. I have already read about a similar problem on Reddit, where tracking is increasingly lost when the headset is taken off and put back on. Has anyone had similar experiences or already found a solution to improve tracking with the Super (or, if the Light is affected, there as well)?

Under certain lighting conditions in the cockpit, I see a grey veil or frame, probably related to foveated rendering. This wouldn't be too much of a problem in itself, as it covers a large area and the transitions at the edges are not very noticeable. However, this area moves with my pupils, which is probably why it has something to do with foveated rendering. The movement of the grey area is sometimes terribly annoying because it destroys the immersion. Does anyone know this phenomenon and, above all, what settings I need to adjust to get rid of the ‘grey veil’ in the foveated rendering area?

I found the cause of the stuttering during low-level flight. I reduced all graphics settings and only achieved minor improvements. I stumbled upon the solution by chance: The video recommends setting the maximum frame rate in DCS to the HZ-value of your VR glasses, e.g. 90 FPS. Other videos even recommend going 10-20 FPS below the actual value achieved. The reasoning behind this is that the game should not render more frames than the VR glasses display. However, this causes severe stuttering in low-altitude flight for me. When I set the maximum FPS in DCS to a higher value, e.g. 120 or 180, I have no problems whatsoever in low-altitude flight and everything runs very smoothly, despite the maximum graphics settings. However, with my PC, I can't achieve a consistent 90 FPS at maximum graphics settings, so I set the Pimax to 72 Hz, which gives me a wonderfully smooth gaming experience. I have no objections to the Pimax Super; the software and hardware run without any restrictions, and the resolution and FOV of the Super are really a quantum leap compared to the Reverb G2. I will now complete the final purchase and keep my fingers crossed for those who are waiting, that they get the Super quickly and are as satisfied as I am. PS: One last change to the settings compared to the video: In Quadview Companion, I set the value for ‘Horizontal Focus Size’ to 30% FOV instead of 20%, as the edges of my focus are too blurry, especially with lights in the evening or at night, and with 30% I get a more natural field of view.

I recommend this video to all Crystal Super beginners: It significantly improved performance for me. Without these settings, I had 70-80 FPS in F4 Free Flight Israel (with reduced graphics in DCS!). With the measures described, I get 90 FPS with maximum graphics settings (!!!). However, this is also due to the fact that the foveated rendering area has been greatly reduced. This doesn't look so good in the above flight in the evening, because the lights outside the FR area become blurred. If I enlarge the area significantly, I still get 80 FPS, despite maximum graphics settings. However, there was some stutters during low-level flight. I will try to optimise this next, but unfortunately I won't be able to do so until Sunday...

I unpacked and connected the Super last night. It took a while to get it working with DCS (I forgot to disable Openxr Toolkit). First impressions are very good, the FOV is significantly larger than on the G2, I don't really need the necksafer software anymore to look behind me. The resolution is brutally good, both in air combat but especially when detecting ground targets, it's worlds apart from the G2. When I fly over a city, I can see every vehicle and person without having to search for long. I couldn't detect any effects such as mura or other problems at all. Performance is surprisingly good. With ‘only’ a 4090, I was worried that I would reach the limits here. Currently running at 72 FPS, which is mostly maintained, only dropping when starting a mission with many aircraft. But I haven't adjusted or optimised anything yet, I'll do that in the next few days (also with the goal of reaching 90 FPS). Anyone who, like me, was very concerned about what to expect and, especially as a new Pimax customer, might be disappointed, I can reassure you that the Super works flawlessly and offers really high quality right out of the box, which can certainly be further improved with settings. The only thing I'm struggling with is room tracking, but that's because of my Simpit with a large cockpit on a motion platform, which the Super has to ignore and orient itself exclusively to the room, as the cockpit is moving. This is a special configuration that probably doesn't apply to 99.9% of users. I'm trying to solve this with better room lighting...

I will. Tracking shows delivery is already tomorrow!

Made by reservation November 11th 24, bought the 57PPD November 22nd 24, switched to the 50PPD later, got an email to confirm 50PPD and address last friday and a shipment notice (to Germany) today.

Perhaps because the patch, at 24 MB (for me), was also the smallest ever distributed

Waiting for my Crystal Super. Would be very happy to read about your decision of keeping it or not...

did that several times. But only get a max of 3 MB/s and often it drops to zero...

Any server problems known? DL-Rate is very poor...

Germany? Gekauft! THANK YOU ED!!!

I tried to not male it too kompliziert for Herrn Newy

Jawohl Sir

It does feel very Deutsch today. Daumen drücken!

Look at my other post regarding the problem: I have the same problem, only entering key settings and exiting it (without any changes), solves the problem for this flight.

When I press F2 to select the external view, I cannot change the view using the mouse. I can see minimal movements, but the position of the view is fixed (so there is a slight jerk when I move the mouse). In this respect, I can see that the mouse is providing input, but the view remains unchanged. There is no other input device connected to the axes for the view, so that's not the problem. Yesterday I found out that I only have to go to the menu of the key bindings once (without changing anything) and then back to the simulation and I can already move the view with the mouse. Does anyone know the problem? Is there a solution?