Gun Jam

additional note. Playing an instant action mission in dcs with the f14 i get temps around 87 to 97 with moments at 100c Playing something normal like KCDII I see temps mostly around 75 to 85c at idle doing this its about 50c Seems normal to me as these are temp limited CPUs if Im not mistaken (if needed just crank it up till it hits tjmax)... Let me know what you think and ill try running the stress test longer

OCCT question. With the 13900k running system stress test and ram test im observing temps holding steady at 100c. TJMax for this cpu is listed at 100c and throttling should occur to maintain this temp. This actually appears to be working as I never see temps over 100c. This is water cooled with a 3 fan 420mm rad. Care was taken when installing the block to the CPU. Im using noctua paste. Im assuming these results are expected and normal but i wanted to ask before I let it run too long. Thanks!

@Calvin.Pimax Awesome thank you. Yes I do have the most recent version. I was flying around online just now and I guess luckily it crashed like it normally does but only about 10 min in so I have small crash log zip from just now. @BIGNEWY might be able to find something of use that could assist me with this. Thanks guys! dcs.log-20250929-033057.zip

They are running xmp and its 2x 32mb. OCCT is new to me ill try it out. I usually run prime 95 and memtest

@Calvin.Pimax The tech got back to me with the following " The DCS process exit codes were 3221225477 and 3221226505. In Windows, these codes indicate a memory exception, which suggests that DCS may have encountered a memory-related issue. Could this be due to in-game settings being too high? I recommend reaching out to the game developers and providing them with these exit codes for further assistance I did post this in the "game crash" section of the forums. Do you know who generally would handle a question like this? I dont notice any memory type issues with normal use and I didnt have any crashing issues before with the G2 or the VR1. I dont think the settings are too high Im still getting a very reliable 90fps out of this now since the last update... That has remained constant and there are now 0 performance issues like I had in the past. It run excellent until it crashes. Thanks

@silverdevil I submitted a ticket to Pimax and their system includes automatically uploading a bunch of logs. I got this reply from the tech. "The DCS process exit codes were 3221225477 and 3221226505. In Windows, these codes indicate a memory exception, which suggests that DCS may have encountered a memory-related issue. Could this be due to in-game settings being too high? I recommend reaching out to the game developers and providing them with these exit codes for further assistance" I have 64gb of ddr5. There is no noted system instability outside of dcs and pimax or pimax and halflife alyx which appeared to crash as well. There was no crashing issues with the G2 beyond the normal DCS issues which were very rare. The pimax tech suggested that perhaps a DCS person would know what to do with the "exit" codes I have no idea who might find that useful if anyone at all. It appears to be of little value but if you know or know anyone who might be able to further isolate an issue let me know I can direct that to them. Thanks

DCS appears to freeze. I dont believe the HMD is disconnecting @Calvin.Pimax Thanks!

@Calvin.Pimax Hey Calvin. I tried again tonight and it ran excellent just like last night but this time it did crash. I was hoping there would be a correlation between good performance vs not as good performance as an indicator if it would crash or not. Seems like not. It did run about 30 min this time before it crapped the bed. Not sure why all of a sudden its running better but I'll take it, but it still seems likley to crash. So I guess I still need supports help. The ticket number is #111697

Since I had the super its pretty much just crashed straight away anytime I try to use it. I found that if I leave DFR off and just dial back the resolution it would sometimes be stable enough to get me though a few missions but its just a heavy G2 at that point I would usually get 60 to 70 fps. The last two times I tried to fly like this it crashed after 10 min and then a 2nd time after 25 min. The next day I turned on DFR globally I figured if it was going to crash it might as well look good. I got 70ish fps out of it using the "quality" preset and at least the center of the image was clear... It crashed 10 min later. Today I saw a patch had been released that mentioned something about vr fix or whatever... I figured I would try it for fun to see what It would do. It didn't seem relevant but whatever. I made no changes and was flying online like the last few times on a pretty busy server and was expecting not much to go my way. The first thing I noticed what fps was locked at 90 sitting on the carrier deck on TTI with 4 other jets starting up. Everything was smooth and all the constant spikes I would see on the frame time graph were gone. It was a smooth flat line with maybe a tiny spike once and a while like no more than 1 every 5 to 10 sec. I have not observed this before that I can recall. Took off and flew around for 30 min then landed pretty much locked to 90fps the entire time I might have seen an 80 for a second or two. This is the first time its ever worked this well or worked as expected based on feedback from other users. I have no Idea if its dumb luck and will never happen again or if the patch had something to do with it. I did open a support ticket before this flight haven't heard back from them yet. Im pretty excited that I finally got to experience what I was hoping was possible. Yeah it's as awesome as they say it is. Maybe just maybe it will work again... who knows.

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)