Nedum

Please Guys, if you want help, then help those who want to help you. Show us your DCS settings. It's strange that those who want to help you post pictures more often and more frequently than those who want this help. Problems are often just symptoms, frequently triggered by multiple settings in the DCS system. Are mods installed? If so, which ones? Do you have the fxo and metashaders2 folders in the game settings section under DCS? If not, do so. Shader problems are not always solved by simply toggling the switches in the DCS settings.

The "PIMAX" settings you talk about are by 100 % the ones from Tally Mouse guide. Even the not necessary "Eye Tracking Switch" is enabled, who only causes issues with XRNeckSafer and does nothing for the Eye Tracking. There is no need for the Nvidia sharpening.

Hi, steht auf Seite 61.

@HOKUM52 Thank your for your report. There is a new Thread for the new PIMAX-Tool. It would be nice, if you would use this Thread to collect all the issues there. The fix could be disabling Bloom in the DCS VR settings section and Flares and Dirt in the System settings. Strange if you have the issue only with the newest PIMAX tool. Cheers

Same.

What you have described is the issue you will get if you enable the Eye Tracking switch in the DCS VR settings. There is !!no!! need to enable this switch for Eye Tracking with a PIMAX OG or Super Headset.

@Dangerzone the line about Hot Plug are not necessary anymore. It works perfect with the buttons in the system tab. You can enable or disable Hot Plug in the game on the fly. With the lines in the autoexec.cfg you are unable to use those buttons, which could cause problems, because most people are unable to remember what they have written in the autoexec.cfg after a few weeks. Or is there a reason to make it the autoexec way?

@MadMonty Thank you for your work! I want to address one thing. The Eye Tracking switch in the DCS VR settings does nothing for a Pimax Headset and causes problems with the XRNeckSafer tool. You should never use this switch if you want to use XRNeckSafer. To date, I am not aware of any Headset that require this switch.

yep, one of my favorite features right now.

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.