Gun Jam

I had the G2 and the VR1 and just now switched to the super. If you want really bad eye tracking use the VR1. With the super i've found eye tracking to be 100% spot on (although using DFR sometimes i feel like it needs to be faster but that could just be less than ideal DFR settings as well) Text looks clear but Ive also noticed the sweet spot on the super is not that good its actually pretty small and does require you get a good fit with the HMD but once fit correctly its quite nice. My big issue is Ive not be able to get the super to run stable and as such a 100% of my time has gone to troubleshooting why it keeps crashing rather than getting to fine tune it for best experience. I did just submit a ticket. did you have any issues with the OG? DId you ever use the G2? Is there a VR headset that does look good to you? what are your computer specs? I have the 13900k and a 4090 I don't have eye prescriptions and still have good eyesight. The super is by far the best looking VR headset ive ever used and Im not noticing any of the issues you've brought up. The grid and text issue is quite surprising to hear. 1) if you close one eye is is better? 2) if the answer to 1 is no then you should be able to photograph this issue with a ph cam or something if you do that can you post the photo? I would like to see this.

Can you run any type of fixed foveated rendering with the crystal light? there isnt a lot of room for improvement i see in your specs without going to a 5090

Im still testing this. I dont use necksafer. Ive had no crashes with HL Alyx or DCS after totally removing all pimax software then putting the PC in safemode and deleting all the leftover pimax folders (I couldnt delete one because it said a file was still in use so thats why safemode) I installed 4.42.1 and made no changes everything stock settings in pimax and as much as possible in DCS. So far I have about 3 flights with about 3 hrs no issues at all with crashing. Ill try to make changes slowly over time and see if any problems pop back up.

cool Thanks for your input!

quick question. I'm not actively looking upgrade anytime soon but the AMD stuff is looking pretty neat. Regarding this post it was suggested that the 9800X3D is faster than 14900K. Which source did you use to arrive at this conclusion and about how much faster do you believe it would perform in DCS VR VS the 14900k? Im also aware that your recommendation is also considering the issues some have reported with the intel CPU vs heat and degradation. Thanks

I'll try starting a ticket

This isnt a dcs problem. I cant get it run half life alyx for more than 10 min at a time. it crashes back to steam vr home. Alyx is probably the most refined, optimize and stable vr game ever developed its an S tier VR experience that run great on a 2080 and a G2. If it wont run stable this seem like maybe a hardware issue. is there a pimax log I can look at? is there a way to figure this out other than letting friend try it on their system?

Until just now I always thought this was a quadviews issue. its not. Even with quadviews off it still crashes. it might run just a bit longer on average but I guess its not a QV issue. I bet its not even a dcs issue any more. Will check some more stuff and let you know what I figure out. I had to extend my trial period so I hope I can figure it out now for reals lol

That was my first starting point. a hint might be that I could get almost non of the suggestions to work. The 8k shadows did work but broke integrity check I did successfully create the autoexe file to keep hud and mfd away from dlss (but that got wiped out when I removed the dcs folder for trouble shooting... I see no difference) I did add the dcs exe to pimax play no problem I did setup pimax play no problem 1) Dcs doesnt show up in DLSS swapper main page I tried to add it but not sure if its even working 2)Nvidia profile inspector doesnt have DCS.exe. I use Digital combat simulator black shark from the list which in my case has no "DLSS overrides" as shown in the video and no options with SR listed that I can find 3)Mbuccas quadviews did work but would crash just as often if not more. 4) I did not try the open xr layers in the API tool kit 5) In nvidia control panel 3d settings using sharping would not initially work but a reinstall to the latest driver did solve this Some notable lines from the crash file as follows 2025-09-03 03:16:47.037 INFO VISUALIZER (Main): [20:16:47.822][Info ] OpenXR: System Eye Gaze Interaction Properties: Name=Pimax Crystal Super VendorId=13476 is not supported! 2025-09-03 03:40:28.448 INFO VISUALIZER (Main): [20:40:29.232][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_FOCUSED->XR_SESSION_STATE_VISIBLE session=1 time=253321681100 2025-09-03 03:18:42.315 ERROR EDCORE (37296): Can't open file: /textures/!cracksmask.lua. 2025-09-03 03:18:42.315 ERROR EDTERRAINGRAPHICS41 (37296): Failed to open array "!cracksmask.lua" 2025-09-03 03:18:42.325 ERROR EDCORE (37296): Can't open file: /textures/!cracksmask.lua. 2025-09-03 03:18:42.325 ERROR EDTERRAINGRAPHICS41 (37296): Failed to open array "!cracksmask.lua" 2025-09-03 03:19:20.523 ERROR EDCORE (37296): Can't open file: /textures/!cracksmask.lua. 2025-09-03 03:35:00.280 ERROR NGMODEL (27652): Can't load lod ptb-800-mig21-collision.edm of model ptb-800-mig21. Reason: More distant lod must not have more arguments than closer! 0 < 1 in ptb-800-mig21-collision.edm ptb-800-mig21

@Calvin.Pimax Hello Ive spent my trial period attempting to get stability from the super in dcs. After several weeks I think I have figured out a pattern that causes the crash. 1) If I go to saved games and delete the DCS folder I appear to get one good run from DCS it will run at least 30 to 40 min and have no issues during that play period (at least within that time frame as far as I can tell) 2) On the next attempt after Ive shut off pimax play I will relaunch pimax play and pick DCS from my assets and launch as normal 3) quad views will not run and FPS will be low. restarting does not appear to solve the problem. 4) I can get quad views to work again in several ways I can make edits to it in the dcs game settings and I think it will work on the next launch. I can enable it global and it will work on the next launch. I can go to games / dcs and pick "Start" from the bottom of the dcs settings window. 5) In all cases dcs will now crash with in 10 to 20 min. This appears to get worse with continued attempts (maybe) To use again repeat steps 1. steps 2-5 seem to follow as described each time. I believe i notice visual anomalies before the crash for example it feels like tracking maybe degrade just enough for a second or two that it makes you ask "was that slowed down or just me being real smooth and not moving much" I can see a flicker when looking down and back up this flicker is actually the image appearing twice but off set slightly for a frame or two. My pilots position in the cockpit may change just a bit you notice when you press the recenter button. ALL of this was occurring and I was like yep this is gonna crash in like a minute... and it did. Any ideas 4090, 13900k, 64mb ram Ive not really tested the super much outside of DCS. I have Alyx but cant get it to load I get a purple grid in the preview window I read this is a resolution issue and can be fixed with a console command... did not have time to F with that. Test HMD runs fine but I havent tried running it for 20 min either. Thanks!

This is a tricky one. Thanks for your help. Ill look into this. Openxr is now supported natively within the pimax software. running open xr independent also didn't seem to help any.

I was able to get though a whole flight the other day with no issues. I tried the same thing again now and this time it did crash. Both the screen and DCS. It also informed me of a crash log being generated. Which I attached. I tried to find the line VISUALIZER (Main): [20:16:47.822][Info ] OpenXR: System Eye Gaze Interaction Properties: Name=Pimax Crystal Super VendorId=13476 is not supported! But did not seem to be able to locate it. I did see the cracksmask lua still... not sure what that might be. any ideas from the new log? Thanks dcs.log

Nice! Thank you

I don't believe this is a pimax issue as I noticed it a lot with the G2. I always thought this was an issue mostly caused by the fresnel lens design. It appears that it is not. In lower light conditions there is obvious banding which looks like you would see 20 years ago in a attempt to render a sky that gets darker as you look up each band is a shade darker. Im assuming that this hasn't changed in 20 years and is a dcs thing. I also am willing to bet there is a setting somewhere that can reduce or eliminate this. With the higher resolution of the super its more of an issue now vs the G2. where should I look to help reduce this?? Thanks!

what is the new version number? How did you get this update I dont see it on the website... is it only available via direct download from within PP? Thanks

well a lot of us have been fine using the G2 so at least that much lol (in other words it far worse in the g2 vs the super)

I would hang onto what you've got now and keep saving up. Nothing in going to really give you much improvement. You will have much better success saving for a while and picking up a used unit later on when they become more available and you have more to spend. A used BSB2 9 months from now might be interesting for you.... perhaps

I do have win 11. I gave online a shot. I tried halfganistan first on TTI but it ran out of time. Then switched to PG TTI. I probably got close to 20 min of up time and then the display froze. DCS was still running and functional on a core level. I could hear all my inputs working and the sim running but the display was frozen then after a bit dropped back to the pimax play home screen was very laggy. But dcs was still running... I killed dcs with end task. It never officially crashed. any clues in this log file? dcs.log

I have. Someone on the crash section of this forum provided me with some tips. Ill let you know if they help. SO far it seems improved....

This is the best its ever run with the super. so far, its exceeding expectations and seems stable. this maybe dialed in now from a "this is a solid starting point" Ill let you know if it stays fixed. Thanks

Interesting I thought I unparked the cores. Ill look into all this. Thanks!

Here is the latest Log file. I looked though it but can tell what item might be related to the crash. Thanks! dcs.log

So SSAO on VS off looks the same to you? And yes it is 100% a QV issue. However I'm quite surprised that SSAO "on" made no change on your end.

In my case it significantly reduced the issue. but I can still see it. Turn SSAO on and see if its worse.

@Calvin.Pimax Ive been doing what I can to get pimaxplay 1.41.2 to run DCS with quadviews. I have multiple issues with DCS crashing that appear related to quadviews. Im using only quadviews within PP. I have uninstalled the openrx items. 1) without quadviews I get a pretty soil 35fps and DCS seems crash free. (im using syria instant action f14 takeoff from turkey the night one as a test) 2) with quadviews I get a pretty solid 35 fps or 60fps or 85 fps it just depends on how it feels during that launch I guess I cant find anything related to this not even resolution / global settings vs game settings. More resolution I get maybe 85 fps then i dial it back and I get 35 fps 2) with quadviews running like crap (35 fps) and settings low say 70% render resolution dcs wont crash or wont crash quickly. 3) with quadviews running great like 80-90 fps at 100 or 150% render resolution It usually crashes in a minute to 10 minutes or on final load screen just before you click "fly" or whatever with the background and cockpit visible behind that window. there is no consistency or obvious pattern to which outcome im going to get. Is there anything I can submit or provide you that could help isolate this issue?