Nedum

Quad views customize, what is hidden behind all the fancy names? How does which slider make differences in visuals and better fps/frame times? A single pictures can say more than 1000 words! I always have to ask companies why they are unable to work with the most powerful human being interfaces, the eyes? Make a picture of the expected visuals, name the zones with the names of the sliders and tell, what will happen, if you move the slider to the right or the left. Only one single picture could catch thousands of questions. What's the reason, companies still trying to compress all the necessary information into 2 text lines, and at the end no question mark of the customer is erased? Click the Information point (I) and open a single picture with most if not all information. Thousands of questions less for the support, because now most people can !!see!! what each slider will do! It could be so easy, so good for both sides, and perhaps the good idea behind all the work, would get the attention it deserves. To let the customer fiddle it out by himself is the worst way to get acceptance of what you try to sell. At max 10 hours of work could bring you more customers and spare you thousands off dollars for the support. Please, give us pictures! And if PIMAX wants to act like a pro, make an animation pop up, if you change the sliders, and with each move of one of the sliders the customer can see what he is !!doing!, in real-time. Too hard for Pimax? I don't think so.

For me, it looks like you have a big problem with your PC. I am pretty sure it has nothing to do with the Pimax Software or the Crystal Super. Your CPU can be one of the those which has the degenerate issue. Ones it has started, nothing can stop it. Your CPU will die! You should check this at first! Have you OC your PC? If yes, try to test all this with a BIOS reset. Still Problems? Open the consol as admin and type the following: sfc /scannow Windows scans your System and if it finds issues it will try to repair them. After each repair, you have to restart the PC and repeat this till there are no issue messages anymore! Still issues? Install the newest drivers for your board and all your hardware. If there are still issues, take a closer look at your hardware! Is your power supply sufficient for your hardware? At least 850 Watts. Is the cooling good? Does something overheat? There are many things you should check before we take deeper looks. Try to upload your dxdiag file (type it in your Windows search bar and after seeing the tool, store all the information and upload the file).

For as long as I can remember, ED has had a problem displaying contrasts in the shadows of objects, and is unable to show enough gray steps. Anyone familiar with analog camera technology knows that high resolution is not necessary to display even the smallest objects at great distances on small monitors. The “trick” is that contrast and shadows/gray steps give objects a specific shape that the human brain recognizes on a 2D monitor and converts into a three-dimensional object. In all videos and images of the original data, at the same distances and despite the compression artifacts caused by uploading, the objects are clearly recognizable as aircraft and vehicles, even in BHOT Wide mode. In close-up view, details can be seen at a distance of 12 miles. You can even recognize what type of aircraft or vehicle it is. In DCS, nothing at all can be seen at the same distance, no matter how much you play with the brightness and contrast controls. DCS simply does not display shadows on the MFDs as they are constantly seen in the original data. You can see all of this perfectly in your images. All you see are 2D blobs because the gray streps are missing to give the objects the necessary depth so that our brain can generate objects from them. I just don't understand how you can't see that! If you look at how blurry and washed out the original images and videos are because this data has obviously been stretched (clearly visible from the fact that the MFD markers are all completely blurry too, like the whole picture, which would not happen), it becomes even clearer that what we see in DCS is significantly worse than what pilots see when they look at their displays. Let's summarize: DCS is unable to render enough gray steps as they appear in the original and attempts to simulate a lower image resolution with blur, which removes any depth and contour from objects, regardless of distance. Unless you explicitly use the digital amplifier in TV mode, all you see are blobs, unlike you can see in the original vids and pictures. Furthermore, ED is unable to provide a preset for the MFDs that delivers a high-contrast image. It is well known that a pilot has to adjust this image slightly, but the fact that the image of the MFDs delivers an inadequate image, regardless of whether it is a hot start or a cold start, is poor. And you can't make it look like in the vids from the Sniper Pod, no matter what you try, because of the missing gray steps! Together with the virtually non-existent shadows in modes other than TV, the current Sniper Pod from DCS does not even come close to what the original shows, even within the poor-quality videos. I would really like to see at least the image quality of the original videos, reduced by processing artifacts, available in DCS. Anyone who believes this to be the case should please provide the images to prove it! The image above show nothing like I can see in the Vids from the original Sniper Pod. Where are all the shadows and the gray steps from the contrasts? Please guys, look at the missing gray steps and shadows in DCS! Where are they? How will one simulate the same picture quality if there are not enough gray steps and nearly no shadows? Since when is an analog camera unable to deliver shadows like in DCS? Please! Look at the original vids and pictures. It's so obvious, that DCS currently doesn't deliver those things!

Hi, thank you, but those are the system settings with Lens Effects enabled. I've asked for the VR settings. You have to disable the Bloom effect, like in my settings, you can see below. null

Wow, since 2021 and still WIP? Yeah.

Wait till the "sudden death" of the D9 engine will catch you up. Yesterday 3 times in a row, out of nothing, without any annoying sound beforehand, the engine dies like it got a headshot. No Enemy ever was shooting at me. First time it was 15 Minutes after the Thunderbolts Fureball Mission. Flying over the airfield, waiting till all Doras has landed. Speed around 300 KM/h. The engine stops without any noise. At first, I thought I was out of gas, but no, 50 % fuel left. The second time, I tried my luck against the AI Mustang UFOs. MW 50 on full speed, >starting< a 30 m/s climb. Speed was 600. Without a noise, the engine stops running after 20 seconds. I do not use any kind of Mod. The D9 is a long story of a sudden death engine bug, lasting more than 6 years, and ED is unable to fix it. The DCS D9 is no secret weapon, but has a secret, that's for sure!

Would you please show us your DCS VR settings? I only saw this if Blooming and/or Lens Flare was enabled with Eye Tracking running. Was a thing long time before QV was a thing.

@Peedee I think it's all about the CPU, if the 5090 can't deliver enough FPS. And I can say that the FPS are different from the AC and the map. Since I have "updated" from a 7950X3D to a 9800X3D, I am completely CPU bound in VR. Even in 2D 99% of the time I am CPU bound. It could have somthing to do with an update, but I am not 100 % sure. I believe the 9800X30 is a very good CPU, but not good enough for DCS. Perhaps I will buy a 9950X3D. Every extra power/MHz will translate in "moar" FPS. My test maps are Afghanistan and Germany (Berlin) and the AC's are the F16 and the AH64-Apache. Try the Apache over Berlin, low level flying or the F16 Cold Start in Afghanistan. Do you always get 72 FPS in those situations? Guys, I think the "Jitter" @Papamiraculi is talking about has something to do with the Headset-tracking and the Room Lightening frequency. @Papamiraculi try to change the frequency. Some old lights flicker. If you enable pass through, and you see a fast flicker, that's the thing that's causing the issue.

Hello together. I want to share where my issue was coming from and how I fixed it. It's all about pressure! It's about the cable loop provided for this purpose on the head strap, the very stiff cable, and the probably too low tolerances of the fan blade covers. All this also explains why the problem mainly affects the left fan. A cable loop is provided to prevent the cable from kinking when the head strap is folded up. This loop has a guide. And this guide ensures that tension or pressure is applied to the cable. This pressure is transmitted via the cable connection to the optical unit. This is enough to cause the fan blades of the left fan to rub against the cover and produce a humming noise. If you remove the cable from the guide, the noise is almost 100% eliminated. I can't say exactly what is happening inside the optical drive without opening it up. But I'm not going to do that. The fact is, I can create or eliminate the problem on my own by changing the pressure on the cable. This is exacerbated if, like me, you have a “small” forehead, which causes the headset to bend even more and thus creates more pressure on the cable connection via the cable. So if anyone experiences a similar problem to mine, please try removing the cable loop from the designated loop to see if that helps.

@Twwhitey I don't have this issue. I had to lower my brightness in DCS to 1.8 and in Pimax Play to 99 %.

@Dawgboy I hope you get a nice and 100 % well working Headset. Maybe I am the unluckiest guy ever, so it should be possible that your Headset will be ok.

Hi everyone, unfortunately, I have to revise my statement after using the headset for three days. Although the left fan was silent when I first connected it, I now heard a humming noise from the left fan when I turned it on. To be honest, I am extremely disappointed that such an expensive headset obviously has a manufacturing defect. You may wonder how I came to this conclusion. Well, I did some research and came across several discussions that address this very issue. Many users with this problem do not report it or keep the headset despite the issue. What is surprising is that mainly the left fan seems to be affected by this problem. The problem seems to be due to insufficient tolerances in the cover and the fans, meaning that even the slightest change in pressure on the housing, temperature, or fan speed can cause this noise, as the fan blades then rub against the edge of the housing. During my research, I found a video that describes this exact problem at 12:44 and also demonstrates the noise. The video also shows how you could fix the problem yourself if you feel confident doing so. However, for 1700 euros or dollars, this is something you shouldn't have to do. I am now certain that I had three completely different headsets and all of them, without exception, had and still have the same problem with the left fan. If I didn't have to drive 40 kilometers (there and back) every time to drop off the packages at the only UPS parcel station in my area, all this effort wouldn't be quite so bad. Unfortunately, there's also the very laborious and time-consuming testing involved in explaining as precisely as possible what isn't working and why it's probably not working. I really like this headset and think it's great, if it weren't for this suspected serial problem. It's probably less than 0.5 millimeters that's causing all these problems. And I would bet that after a few months, many users will still be experiencing this problem. I hope I'm wrong, but my experience so far unfortunately suggests that it's very likely that many other users will also be affected by this problem, even if that's not currently the case. I just can't imagine that I'm the only person who's had the same problem three times in a row with three brand-new headsets. Just to be on the safe side, I'm playing the lottery today. With my “luck,” I'm bound to hit the jackpot!

Hello everyone. Good News (for me ). Thanks to Calvin and Cindy, the new headset arrived today. That was quick. And what can I say, everything is working as I expected so far. The main problems are all gone. The fans are whisper quiet. The displays don't get visibly darker or brighter when I look from bright to dark areas and vice versa, and I no longer have to move the headset to see sharp with my left eye. Thank you also for your support.

No, you don't need a 5090, that's simply not true, not at all! You'll need a 6090! But joke aside. A 4080 or 5070Ti is a good start to have more fun with a Crystal Super as with a Quest Pro.

Yeah, I think that's the problem, but I can't go with the snap rotation. I tried it a few times. It feels completely wrong. That's probably why it makes me feel sick. Not my world.

@Dawgboy Yes, but still not as good as with Necksafer. I have to move my body more to get a good look behind me. Even with the Crystal Super, you get not the big FOV view you have in RL. But now I can see the first part of the wings and the tips of my loadout of my F16 without XrNecksafer and without moving my whole body. Edit: You ordered the Wide FOV version. You will perhaps see the whole wings with only moving your head at the edges of the lenses, but you still have to twist your upper body to get a good look behind you.

Hello everyone, I would like to share with you an important discovery I made regarding micro stutters. It may already be common knowledge, but I couldn't find anything about it in the forum, which is why I'm starting this thread in the PIMAX section. This may be a problem that only occurs in conjunction with the XrNecksafer and the PIMAX software. My OG Crystal kept to start stuttering when I looked to the side, and then stabilized itself, even though the FPS and frame times were consistently high enough to not get any stutter at all. After switching from the 4090 to the 5090 with its better raw performance and significantly higher FPS, I was surprised to find that the slight stuttering in some situations and maps was still exactly the same as before. Until then, I had assumed that it was due to the poor performance of the 4090, so I didn't look into it further. Now, I was sure that it had nothing to do with the GPU. So I tested what was possible, but always with XrNeckSafer enabled. It never occurred to me that this great tool could cause a problem. It never even crossed my mind that it could be due to this tool. Then I've got my Crystal Super and this Crystal Super had a few major problems, and in order to test everything properly and rule out problems with third-party software, I disabled all tools. I was surprised to find that these mini jerks when looking to the side had completely disappeared. And not only that, suddenly the image was still smooth even when I had FPS dips way below 72 FPS. At first, I thought I had reset the setting, but that wasn't the case. So I enabled each tool (Quadviews Companion, OpenXR Toolkit, Quad-Views-Foveated, and XrNewckSafer) individually, and as soon as I enabled XrNeckSafer, the stuttering started again. It seems as if XrNeckSafer prevents the “smoothing” of frame times, which is normally handled by the manufacturer's software. It may be due to how I configured the XrNecksafer (see image below), which is why others may not notice this effect If anyone is using XrNeckSafer and experiencing mini-stuttering when looking to the side, even though the FPS and frame times should be sufficient for smooth display, I recommend trying it without XrNeckSafer. For me personally, it was an eye-opener.

Whenever I see your very rude manner of communication, I find it extremely difficult to believe that you actually work on an F16 yourself. Apart from that, it would be important to know which Army regulation prohibits refueling an external tank unless it contains less than 4,000 pounds of fuel? Why less the 4,000 pounds of fuel and not 3,500 or 4,500 or empty? There should be reason for it! What is it? What happens if a pilot lands with more than 4,000 pounds of fuel in the center tank, the aircraft is rearmed, and he basically needs a full center tank to complete his mission? It may well be as you describe here, but what are the reasons for this, and what measures are or must be taken to ensure that the center tank can be refilled to capacity when it contains 4,100 pounds of fuel instead of 3,999 pounds? Please share your knowledge with us. An essential part of this hobby is knowing why and how to do things so that they work in the end. When you work on the F16, you will be told the reason. At least that's how it is in the Deutsche Luftwaffe. Everyone is told why certain things have to be done in a particular way. I firmly believe there is no difference in the US armed forces. It would be nice if you could help us to understand what are the reasons for all of this. Thank you!

Hello @Calvin.Pimax, thank you for contacting me. I was unable to respond to your private message until today, as I did not have time over the weekend. I have sent you the current ticket number via private message. In my last message to the young lady from the support team, I wrote that I can only accept another replacement if it is actually a headset with a guaranteed new optical unit. This message may be delaying everything! I don't know. I am 99% sure that the last replacement wasn't a new optical unit. The fact that 5 of the 6 previously reported problems are exactly the same again, and that the third point (chromatic aberration, triple vision in 3 different colors) is less pronounced because the brightness of the displays has been reduced, is a pretty big clue for me. However, I did not report the seventh issue because I felt that the other six issues were more than enough. The 7th issue was that the right display occasionally becomes slightly darker or lighter when switching from light to dark and vice versa. In the end, six out of seven problems remained completely unchanged, and one was mitigated. To get "another" one with all those exact issues, that's like winning the jackpot twice in a row with the exact same numbers. I don't think I'm that lucky. And please don't get me wrong, if the repair is done well, I have no problem with it. Unfortunately, the last repair (I think it was one) was more than inadequate, and then there's always this endless process of troubleshooting, documenting, reporting problems, waiting for responses, repackaging, and then waiting again to see if it will be better this time. Like everyone else here, I have to work hard for my money, and I know that mistakes are made or things don't always work like they should. No problem, I can and must live with that. However, I expect a repair to work, especially when the delivery includes a note signed by two people stating that the headset has allegedly passed all tests. I can say with absolute certainty that either what is written on the note is not true, or the tests are not good enough. I notice that I'm getting upset again, so let's stop. If I had the choice, I would prefer to receive a new optical unit and keep the old headset and optical unit. After the arrival of the new optical unit, I would test the new optical unit and send the old one back. That way, I would be sure that I would not end up with "another" unit that had been completely failed to repair. And if PIMAX has problems to deliver the normal 50 PPD optical units, I would even go with a wide FOV 50 PPD unit if this would fasten up the delivery and shorten my waiting. Unfortunately, it currently looks like I won't have a fully functional headset in my hands until the end of September, almost 11 months after I placed my order. That's tough. Nevertheless, thank you for your attention and with best regards

Yea, but it's inside the Headset. I've got the answer from PIMAX. They want to send me another replacement (in 3-5 weeks) and then extend the test period by or to 7 days. It's probably because of the language barrier that I don't quite understand what that means. Quote: To address this, we'd like to arrange another replacement for you. We will extend a 7-day return window, starting from the date the new replacement unit is delivered. This gives you ample time to test the unit thoroughly. To me, it reads more like the trial period will be shortened next time, even though the word “extended” is used. Very “artfully” worded. It's being shortened, but they use the word “extended.” Just my kind of humor. At least I'll get a 3-month warranty extension if I decide to keep the device after that. So far, I haven't been asked to pack up the old headset and send it back. At least, that's how it was last time. Last time, the “new” headset was only sent to me, or rather the replacement process was initiated, after PIMAX had confirmation that the old headset had been received. That alone took more than a week. I'm curious to see how long it will take this time. But I'd also like to take this opportunity to stick up for the support team that's helping me. The guys and girls are doing a great job.

@Dawgboy Thank you That would be the best way for me. I've got a message from the support team, they will contact me tomorrow, with a clear update and proposed plan. And that's how the Fan of the Super Sounds: The first file is from the old one, the second file is from the "new" one. Sound Super first HS.m4a Pimax Headset Bee Sound new HS.m4a

Hello @Peedee and @Panzerlang, thank you both for the response. On one side, I am happy you both have "super" Supers ( ) and it gives me a little bit of a hope, on the other side I am really frustrated that "2" Headsets I've got are so bad. And thank you for taking the time to provide information about the offset settings. I may test this over the weekend, but at the moment I am frustrated when I put on the headset and see the excellent image quality, knowing that I will have to return the headset because my previous headset already had all these issues, which I reported extensively (photos, sound files), and then I get a headset back with almost all the same flaws, and on top of that there's a note signed by two people saying that the headset passed all the tests. Are they blind and deaf? I don't know how the testing is done, but delivering something like this to the customer with almost all the faults still present shows either a great sense of humor or simply incompetence. The worst thing is that, no matter how frustrated I am, I will have to wait months and will probably receive the same device again. @Calvin.Pimax Should I give this device back to be sure not to get this device again and order another one?

Hello everyone. I had problems with my first Crystal Super and received a replacement device. The problem is that the replacement device has almost the same problems as the previous device, which is why I almost hope that it is not a replacement device, because otherwise I am incredibly “lucky” with the devices or PIMAX has a huge problem with the quality of the devices. I would like to ask here whether I am just unlucky or whether you are also familiar with these problems. I have the following problems with both devices: 1. Chromatic aberration in the sweet spot. With the first device, it was so severe that all the illuminated buttons in the F16 cockpit turned white and I saw all the numbers three times in different colors. With the second device, I “only” see this in the pause/start image on the buttons. There is no sign of it in the F16 cockpit. 2. The left fan (when I put on the headset) sounds like a bee, so even with noise-canceling headphones, I can hear this buzzing noise when it's quiet in the game. Playing with the DMAS headphones is not possible this way, at least if you value the background noise in the game. 3. The right display gets brighter or darker depending on whether I'm looking at a light or dark area. This doesn't happen all the time, but it does happen occasionally and manifests itself as a very slow flickering. 4. To achieve the sweet spot in the left display, I have to push the headset up about 3-5 mm on the left side and move it slightly to the left so that my eye moves further down and to the right to see everything clearly with my left eye. This wasn't quite as extreme with the first Crystal Super. When aligning the HMD with the HUD, I see two lines on the large cross. On the right eye, the line runs vertically from top to bottom. On my left eye, I have a second line, as if I were squinting. This line drifts down to the left. I didn't have this with the first headset. Due to all these almost identical errors with both headsets, I almost suspect that an attempt was made to repair the old headset and that the headset was given a new SN so that the 14-day trial period could be controlled by the system again. However, if it is indeed a new headset and so many problems are identical on both headsets, I wanted to ask you if you are experiencing similar issues? I am an owner of the OG Crystal and have not a single issue with it. Greetings

Da ich mein Quest 3 verkauft habe, bin ich mir nicht zu 100 % sicher, aber es wird auf der linken Seite angezeigt, dass du eine Latenz von 45 ms hast, richtig? Und die Latenz ist wie festgenagelt. Keinerlei Varianz. Wenn dem so ist, wirst natürlich immer ein Stottern haben. Warum ist die BIT-Rate bei dir os niedrig? 200 Mbps scheint mir viel zu niedrig zu sein. Ultra Einstellungen und nur 200 Mbps und dann niedrige Latenzen? Ich glaube nicht, dass das so etwas wird. Da müssten 500 Mbps her. Wie ich schon schrieb, ist es lange her, dass ich die Quest mal aufhatte, aber ich bin mir sicher, dass 200 Mbps viel zu niedrig für ULTRA-Settings ist, wenn es um Latenzen geht. Mal einen anderen Codec ausprobiert? 10 Bit ist ein gewaltiger Sprung gegenüber den 8 Bit der anderen Codecs.

At first, thank you @Dangerzone for this thread! Many good points one can start with to discuss. To cut a long story short, there are seven points that have personally helped me reduce stuttering: 1. Enable hardware acceleration in W11 and in the BIOS REBAR. 2. Disable all unnecessary programs running in the background. 3. Have at least 64 GB of system RAM installed. 4. Install DCS and the disk cache on the fastest SSD drive. 5. Set the latency to Ultra and vertical synchronization to off in nVidia CPL. 6. Use a CPU with the lowest possible latency (definitely not INTEL). 7. The most important point is to adjust DCS to the minimum FPS the graphics card can deliver so it always achieved and ensures smooth gameplay. Regarding the RAM optimization shown in the video presented in the thread: I believe that it may be helpful for people who have less than 64 GB of RAM and only slow hard drives. What you see in the video is not a bug in DCS World or Win11, it's the opposite. You can see how Win11 makes optimal use of RAM, because RAM is always faster than a hard drive. Why wouldn't you want to use your RAM as much and high as you can? My own tests show that Win11 does everything right, and when files are no longer needed and others need to move up, the area that is no longer needed is immediately cleared. As I write this, I am on the Germany map. I pushed up to 55 GB RAM (the highest reading I could get) by pressing F11 and after that I stayed at one place. And now only 32 GB are occupied. This is how it should be. You don't have to use any extra tools, if your settings are optimized for your Hardware ( VR differs here a bit ;))! Many “problems” are simply based on believing what is specified as the minimum requirements for DCS World is enough to play the game with all the great graphics. This makes DCS World playable, but far from optimal. For me, the biggest FPS hogs are, in order of importance, the following, if FPS fluctuates: 1. Terrain shadows = Flat (biggest impact) 2. Clutter = 0 (big impact) 2. Trees = 0.5 (big impact) 3. Water = Low (medium impact) This is what I was able to test for myself. First optimize the hardware, then optimize DCS World for the hardware! There are no magic settings that can turn poor/unoptimized hardware and software into a miracle cure!