Nuggetz

I am using the updated Pimax Play and QVC only. Pimax XR, QVFR and OPENXRTK have been uninstalled. Sorry, I am not on my PC so can’t send a screen shot of my QVC window, I will try and add it to this thread tomorrow.

I have my resolution set to 100% other settings are similar. Please try 100% I used to use 140%, but don’t regret lowering the value.

I have switched to the new Pimax Play and initial impressions are very favourable. Perhaps 10% increase in FPS. Floating sensation in the headset appears to have stopped Image quality appears cleaner and sharper (no DLSS Selected) Head movement appears smoother and more stable The only negative I have noticed so far is shimmering of text on information table pages but in cockpit and F2 views do not appear affected Additionally the gamma appears brighter and I may need to reduce the setting HTH and useful

I have a little used (6 months) FTW3 RTX 3070, which is available in its original box. Excellent condition. Was replaced by a 3080ti not long after I purchased it in the UK. If you make me a reasonable offer I am happy to sell if you are interested. No pressure whatsoever.

Purchased both on Day 1. I have 2000+ hours in the F16 and 3+ hours in the F18 over almost 4 years. For me the F16 feels more intuitive especially in A2A combat. They both have pros and cons, so it really comes down to which one you like the most is the aircraft you will fly the most.

So looking forward to the F16 radar fixes beyond all else

Firstly thanks for the major update and hotfix. A couple of anomalies appear to exist for me: No landing events recorded in the Pilots log. Unable to refuel/rearm at any blue base with the blue F16 in the Afghan map with unlimited fuel/weapons set in the mission editor. No scores recorded in the multiplayer score table. Not sure if this is just me or have others already reported these issues? Thanks again

An observation from me is that the pilots log does not appear to be recording. Just noticed of the 3 landings done today none of which were recorded. Additionally, flight hours do not appear to be updated. Other data might be missing ie number of kills etc. Worth investigating before too much data is missed. TY

I am not sure if I am understanding the new pilot model in the F16. For example if I switch to F2 view the pilot remains static in VR. However, when moving in the cockpit the head appears to move as does the shadow on the instrument panel and when on the ground on the ground. If I look at other F16 in F2 view that pilot moves randomly. If my view jumps in VR (uncommanded) so that the camera view remains inside the canopy I can see my pilot’s head moving. It is only external views of my F16 where the pilot remains in a fixed position albeit the arms do move ie advancing the throttle. I have found the Left Shift + P command relating to pilot movement but either way no change. Am I missing something or is this how it is intended to work? Many thanks in advance of any help you can offer.

Thank you for the prompt reply

I noticed today that the numeric value linked to the slider for the Afterburner Detent is missing. So when moving the slider you have no idea what the value is?? I have run the full repair on DCS and the numeric value remains missing. Am I doing something wrong or is this a glitch? Thanks in advance.

Not sure if this the correct place to ask this question but I cannot get the pilot’s head to move when seen from outside the cockpit (F2). I have found the control that allows the pilot to be locked and regardless of pressing the keyboard commands nothing changes. I note that both inside and outside the cockpit the pilots arm movements can be seen. It is just the lack of movement of the helmet. It appears the movement of the Pimax Crystal is not being detected despite it working ok in F1. HOTAS movements are detected. Any help or advice would be much appreciated. TY. ps I have run a full slow repair.

I have been having the same type of issues leading to very inconsistent launches of Fox1. No real issues with Fox 2.

After much investigation I have found a work around. if I disable eyetracking and auto IPD the headset no longer goes blank thus crashing DCS 10-60 minutes into a session. Note: eyetracking and and auto IPD work fine right up to the crash so it’s not a calibration failure. Historically I had connected the Pimax Crystal data cable to a USB 2.0 (not USB 3.0) which had worked fine for months but now I use USB 3.0. More testing over the weekend and then an email to Pimax on Monday! UPDATE: Following an exchange of emails with Pimax I have restored eyetracking. The solution was to remove the DP cable from the headset socket and disconnect the short cable from that socket direct into the headset. Then the long DP cable is insert directly into the DP socket under the headset top cover. Thus eliminating the short cable altogether.

I will check next time I log in. Thank you for the suggestion.

I have been hopeful that I might have fixed things but the crashes continue. I attach the latest log which shows a number of errors and warnings but I cannot figure out what is going on. Any suggestions please? dcs.log

Thank you for your suggestion. I don’t use pass through. it is early days but I think the Echo19 Core update may have been the root cause. I have deleted the Core update and at least temporarily deleted the ECHO19 sound module. I ran two long missions last night with no crashes in SP Mode. This morning I plan on doing some MP missions. If that works without crashes I will consider the problem resolved. I shall report back later.

Thank you for your help. I did recently download the ECHO19 Core update to my existing ECHO19 sound mod but I did delete the new Core update just in case it was that causing the problem. I need to uninstall the original ECHO19 files as well and then reinstall the base module only. Fingers cross that fixes it. thanks again.

I have been trying to fix this problem and thought I had made progress when flying two long missions in the Kola map this morning. I attach this mornings logs. I note there are a lot of XR runtime errors and that the trackfile was skipped due to the large size. Any help gratefully received. TY dcs.log dcs.log-20240508-073445.zip

Thanks Bignewy, PSA, TYdcs.log dcs.log-20240507-100112.zip dcs.log-20240507-061550.zip

After playing from 10-60 minutes my headset goes blank and DCS crashes. When I look at the latter entries in the Log there is a warning that the track file is too large. This happens in both SP and MP. I have been using the Crystal for 10 months and this problem has only just started in the last 2-3 weeks. I have done a slow repair on DCS but is still happening. I have also raised a ticket with Pimax but would welcome any help or advice to resolve this issue. Thank You. ps I have approx 1.0 TB of spare memory at this time.

I have noticed with today’s update that: I opened an F16 mission in my missions and moved an aircraft a few miles (air) but when I tried to save DCS would not allow me to do so. I could Save A$. I also noticed that upon landing with a F16 TGP attached and then rearming the TGP stops working but TGP power off/on restarts ok. Not sure if this behaviour is intended?

Although you issue may be different when I had flickering with my 8KX it was down to the main cable. Try connecting your Crystal direct to your PC eliminate hub issues and try again. Check your Device manager to ensure Windows cannot turn off USBs/HIDs. HTH

When you calibrate just have the Pimax software running and only tick the eyetracking box. Do not tick IPD or wearing notification. If you know your IPD that would be good and set it manually. Then retry the calibration hopefully it should work this time. HTH

I would add that unless I power the Crystal on first before any power to the PC the headset/client do not connect. I also have to regularly check the USB/HID trees in Device manager to ensure the box allowing power off to the USB is not enabled. There have also been a number of time the headset disconnects after various time periods causing DCS to crash. I suspect these issues are all related so I hope a fix is provided soon. Thanks.