Community Crystal Troubleshooting

Planet Pimax!
1

This topic will be used to collect troubleshooting topic links and solutions

2

Community Solutions for Connecting Issues.

  • Try connecting pimax hmd with only mouse & keyboard connected to USB.
  • See link: u/apprenhensive_sir1653 on Reddit(r/pimax) discovered there was a conflict with his wireless keyboard & mouse(Corsair).

:reddit: r/pimax Source

3

[Help] Pimax Crystal Light not recognized by Pimax Play – Need Advice!

  • Posted by: u/Fewrelionship193 - on :reddit:

Hi everyone,

I’m having a frustrating issue with my Pimax Crystal Light headset, and I’m hoping someone here might be able to help. Here’s what’s going on:

  1. The headset is not being recognized by the “Pimax Play” application.
  2. The app launches without any error messages, but it just seems to idle indefinitely without doing anything noticeable.
  3. If I close Pimax Play and reopen it within 5 seconds, the headset is recognized most of the time, but not always.
  4. I’ve tried completely uninstalling Pimax Play, including clearing all leftover files in AppData and other user profile subfolders. After reinstalling, the app works once and recognizes the headset, but then the same issue starts again.
  5. I’ve also reinstalled drivers and let the system (Windows 10, fully updated) detect the headset again, but no improvement.
  6. Power cycling the headset doesn’t seem to make any difference either.

I’ve also unplugged and reconnected all USB and DisplayPort connections, but that didn’t solve the problem either.

This problem started suddenly, and I didn’t make any changes to my system or install new software beforehand. The only workaround I’ve found so far is to open Pimax Play, close it, and reopen it within 5 seconds—but that’s super inconvenient and unreliable.

Has anyone experienced this issue before? If so, how did you solve it?

I’d really appreciate any help, advice, or ideas!

Thanks in advance!##

SOLUTION

  • Posted by: u/Fewrelionship193 - on :reddit:

Hi everyone,

I just wanted to update this post in case someone else runs into the same issue. I managed to solve the problem! :tada:

The issue was related to old or duplicate devices lingering in the system. Here’s what I did:

  1. I used a tool called DeviceCleanup to remove all devices that were no longer physically present on my computer.
  2. Among these, I found some unknown devices and a duplicate of a Pimax audio device, which I deleted.
  3. After cleaning up all the unnecessary devices, the Pimax devices were recognized again by the system as if it were the first installation, and the Pimax Play app started working perfectly.

If anyone else is having similar problems, I highly recommend checking for leftover devices with DeviceCleanup—it might save you a lot of frustration.

Thanks to everyone who took the time to read and help!

:reddit: r/pimax

1 Like
4

2 posts were split to a new topic: Pimax Play Manual WiP

5

Let’s troubleshoot your Pimax Crystal Light. A structured approach covering common issues. Always consult the official Pimax support website and forums for the most up-to-date and specific guidance.

1. Basic Checks:

  • Power: Is the Crystal Light properly plugged in? Check the power adapter at both the wall and the headset connection. Try a different outlet.
  • Connections: Ensure all cables are securely connected to both the headset and your PC (USB, DisplayPort/HDMI, power). Reseat the cables at both ends. Try different ports on your PC if possible.
  • PC Restart: A simple PC restart often resolves driver or software conflicts.
  • Pimax Play: Make sure you have the latest version of Pimax Play installed. Reinstalling it can sometimes fix corrupted files.

2. Display Issues:

  • No Image:
    • Check Connections (Again!): Seriously, double-check them. A loose connection is the most common culprit.
    • Display Driver: Ensure your graphics card drivers are up to date. Download the latest drivers from the NVIDIA or AMD website (depending on your card). Consider a “clean install” of the drivers (an option during installation).
    • Direct Mode: In Pimax Play, check if “Direct Mode” is enabled. Sometimes toggling it can help.
    • Headset Firmware: Check for firmware updates for the Crystal Light through Pimax Play. Outdated firmware can cause display problems.
    • Other Displays: If you have multiple monitors, try disconnecting them temporarily to see if there’s a conflict.
  • Distorted Image/Artifacts:
    • Cable Quality: Try a different DisplayPort/HDMI cable. A faulty cable can cause image distortions.
    • Overheating: Is the headset overheating? Ensure adequate ventilation.
    • Graphics Settings: Lower your in-game graphics settings to see if it helps. This can rule out GPU overload.
  • Black Screen/Flickering:
    • Refresh Rate: Try lowering the refresh rate in Pimax Play.
    • Background Processes: Close any unnecessary applications running in the background.
    • Windows Updates: Make sure Windows is fully updated.

3. Tracking Issues:

  • Lighting: Ensure the room is well-lit but avoid direct sunlight or bright reflections, which can interfere with tracking.
  • Obstacles: Remove any obstacles that might be blocking the tracking sensors.
  • Base Stations (If applicable): If your setup uses base stations, make sure they are properly positioned and powered on. Check their status lights. Try recalibrating them.
  • Controller Tracking: If you’re having issues with controller tracking, make sure they are charged and paired correctly.
  • Firmware (Again!): Firmware updates often include fixes for tracking issues.

4. Audio Issues:

  • Headset Audio: Check the audio settings in Pimax Play and in Windows. Make sure the Crystal Light is selected as the default audio device.
  • External Headphones: If you’re using external headphones, ensure they are properly connected.
  • Microphone: Test the microphone in Pimax Play. Make sure it’s not muted and that the correct input device is selected.

5. Software Conflicts:

  • Other VR Software: If you have other VR software installed (e.g., Oculus, SteamVR), try temporarily disabling them to see if there’s a conflict.
  • Antivirus/Firewall: Temporarily disable your antivirus or firewall to see if it’s blocking Pimax Play.

6. Advanced Troubleshooting:

  • Log Files: Pimax Play might generate log files that can help diagnose the problem. Check the Pimax documentation for the location of these files.
  • Reinstallation: As a last resort, try uninstalling and reinstalling Pimax Play and all related drivers.

7. When to Contact Pimax Support:

If you’ve tried all of these troubleshooting steps and are still experiencing problems, it’s time to contact Pimax support directly. They have access to more advanced diagnostic tools and can provide more personalized assistance. When contacting support, be prepared to provide the following information:

  • Headset Serial Number:
  • Pimax Play Version:
  • Graphics Card Model and Driver Version:
  • Detailed Description of the Problem:
  • Steps You’ve Already Taken:
  • Screenshots or Videos of the Issue (If Possible):

Remember to be patient and provide as much detail as possible to help Pimax support diagnose and resolve the issue quickly.

6

Improving tracking

Improving tracking on the Pimax Crystal Light can be tricky, as it seems to be sensitive to various factors. Here’s a breakdown of potential solutions, combining common advice with specific issues users have reported:

1. Optimize Your Environment:

  • Lighting: This is crucial. Aim for even, bright lighting. Avoid:
    • Direct sunlight or reflections: These can confuse the tracking cameras.
    • Flickering lights: Some bulbs, especially older ones, flicker at 50/60Hz, which can interfere. Try replacing them with stable LEDs.
    • Dark areas: The cameras need sufficient light to track features in your environment.
  • Clutter: A cluttered room can make it harder for the headset to track. Try to clear your play space.
  • Surfaces:
    • Reflective surfaces: Mirrors, shiny monitors, and even glass can cause tracking issues. Cover them if possible.
    • Blank walls: If your walls are completely bare, the headset might struggle to find tracking points. Consider adding posters, shelves, or other decorations.

2. Adjust Headset Settings:

  • Refresh Rate: Some users have found that setting the refresh rate to 90Hz and enabling “Upscale” mode in the Pimax software can improve tracking.
  • Light Frequency(PCL - Only): In Pimax Play, try configuring the light frequency to match your region’s power supply (50Hz or 60Hz). This might help with flickering light issues.

3. Check Your PC:

  • CPU Load: The Crystal Light relies heavily on your CPU for tracking. If your CPU is overloaded, it can lead to tracking issues. Try reducing CPU-intensive tasks while using the headset.
  • USB Ports: Ensure you’re using a USB 3.0 port (usually blue). Try different USB ports on your PC, as some might provide more stable power.
  • Drivers: Make sure you have the latest Nvidia graphics drivers and Pimax software installed.

4. Advanced Troubleshooting:

  • Covering Cameras: Some users have reported improved tracking by covering the bottom two cameras on the headset. This might indicate an issue with how the headset processes information from those cameras.
  • OpenXR and OpenComposite: Some users have found that using OpenXR and OpenComposite instead of SteamVR can improve tracking.
  • Community Folder (for MSFS): If you’re using the Crystal Light for Microsoft Flight Simulator, make sure your Community folder is empty or contains only essential mods, as some mods can interfere with tracking.

5. Contact Pimax Support:

If you’ve tried all of these steps and are still experiencing tracking issues, it’s best to contact Pimax support for further assistance. They might have specific solutions or be aware of any known issues with the Crystal Light.

Remember that tracking issues can be complex and might require a combination of solutions. Be patient and methodical in your troubleshooting, and hopefully, you’ll be able to improve your tracking experience with the Pimax Crystal Light.

7

SteamVR Tracking

Improving SteamVR tracking can be a bit of a challenge, as it relies on a combination of hardware, software, and your environment. Here’s a comprehensive guide to help you troubleshoot and optimize your SteamVR tracking experience:

1. Optimize Your Environment:

  • Lighting: This is crucial for both inside-out and outside-in tracking.

    • Even, bright lighting: Aim for consistent lighting across your play area. Avoid harsh shadows or overexposed areas.
    • No direct sunlight or reflections: These can confuse the tracking cameras or sensors. Cover windows or reflective surfaces if necessary.
    • Avoid flickering lights: Some bulbs, especially older ones, flicker at 50/60Hz, which can interfere with tracking. Try replacing them with stable LEDs.
    • Sufficient light: Even for inside-out tracking, the headset needs enough light to track features in your environment.

  • Clutter: A cluttered room can make it harder for the tracking system to identify and track objects. Clear your play space of obstacles and unnecessary items.

  • Surfaces:

    • Reflective surfaces: Mirrors, shiny monitors, and even glass can cause tracking issues. Cover them if possible.
    • Blank walls: If your walls are completely bare, the headset might struggle to find tracking points. Consider adding posters, shelves, or other decorations to provide visual landmarks.

2. Hardware Setup and Placement:

  • Base Stations (for outside-in tracking):

    • Placement: Position base stations at least 6.5 feet (2 meters) high, angled down by 30-45 degrees, and no more than 16 feet (5 meters) apart. Ensure they have a clear line of sight to the play area.
    • Stability: Mount base stations on a solid surface that isn’t prone to vibration or movement.
    • Power: Ensure base stations are plugged in and receiving power. Check the status LEDs on the base stations for any errors.

  • Headset and Controllers:

    • Firmware: Make sure your headset and controllers have the latest firmware updates installed.
    • Charging: Ensure your controllers are adequately charged.
    • Connections: Check all connections to your headset and PC, including USB cables and any wireless dongles.

3. Software and Settings:

  • SteamVR Room Setup: Redo the SteamVR room setup to ensure accurate tracking boundaries. Follow the instructions carefully and make sure to cover your entire play space.

  • SteamVR Settings:

    • Beta Branch: Sometimes, the SteamVR beta branch can have tracking improvements. Consider opting into the beta in SteamVR settings.
    • Disable Unnecessary Features: Disable features like “Advanced Home” or any overlays that might be taxing your system.
    • Developer Options: Explore developer options in SteamVR for advanced tracking settings, but be cautious as changing these settings can sometimes worsen tracking.

  • Drivers: Make sure you have the latest graphics drivers and any necessary drivers for your headset and controllers installed.

4. PC Performance:

  • CPU Load: Tracking can be CPU-intensive. If your CPU is overloaded, it can lead to tracking issues. Try reducing CPU-intensive tasks while using VR.
  • USB Ports: Ensure you’re using USB 3.0 ports (usually blue) for your headset and any wireless dongles. Try different USB ports on your PC, as some might provide more stable power.
  • System Resources: Close unnecessary applications running in the background to free up system resources for SteamVR.

5. Advanced Troubleshooting:

  • Identify the Source: Try to pinpoint the source of the tracking issues. Is it specific to certain areas of your play space? Does it happen with specific controllers?
  • Isolate Variables: If you’re using multiple VR devices, try using them one at a time to see if a specific device is causing the issue.
  • Community Resources: Search online forums and communities for users who have experienced similar tracking issues. You might find solutions or workarounds that are specific to your headset or setup.

6. Contact Support:

If you’ve tried all of these steps and are still experiencing tracking issues, it’s best to contact the support team for your VR headset or SteamVR for further assistance. They might have specific solutions or be aware of any known issues.

Remember that tracking issues can be complex and might require a combination of solutions. Be patient and methodical in your troubleshooting, and hopefully, you’ll be able to improve your SteamVR tracking experience.

8

Tracking & Lighting Warmth

VR Headsets that use Infrared based Tracking should consider using 6000k warm light vs 3000k which emits more ir.

This is for informational purposes only. For medical advice or diagnosis, consult a professional.

Technically, yes, a 3000K lightbulb will emit more infrared light than a 6000K bulb. Here’s why:

  • Color temperature and the electromagnetic spectrum: Color temperature, measured in Kelvin (K), describes the color of light emitted by a light source. Lower color temperatures (like 3000K) correspond to warmer, yellowish light, while higher color temperatures (like 6000K) correspond to cooler, bluish light. Infrared light falls on the electromagnetic spectrum beyond visible red light.

  • Blackbody radiation: Lightbulbs, like most objects, emit light based on their temperature, a phenomenon called blackbody radiation. Warmer objects emit more energy at shorter wavelengths, while cooler objects emit more energy at longer wavelengths.

  • Infrared and visible light: Since infrared light has a longer wavelength than visible light, a lightbulb with a lower color temperature (like 3000K) will emit a higher proportion of its energy as infrared light compared to a bulb with a higher color temperature (like 6000K).

It’s important to note that the amount of infrared light emitted by a typical household lightbulb is relatively small compared to other sources like the sun or specialized infrared lamps.

9

Optimize Graphics

Optimizing graphical settings for the Pimax Crystal Light involves a balancing act between visual fidelity and performance. Here’s a breakdown of settings to tweak, keeping in mind that the ideal configuration will depend on your PC’s capabilities and personal preferences:

1. Pimax Play Settings:

  • Refresh Rate:

    • 120Hz: Ideal for high-end PCs (RTX 4080 and above) aiming for the smoothest experience.
    • 90Hz: A good balance for most systems, offering a smoother experience than 60Hz while being less demanding.
    • Upscale Mode: If you struggle to maintain high frame rates, especially in demanding games, enable this mode. It uses upscaling algorithms to improve performance while maintaining decent visual quality.

  • Render Resolution:

    • Start at 100% (native): This provides the sharpest image.
    • Reduce gradually: If you experience performance issues, lower this in small increments (e.g., 90%, 80%).

  • Fixed Foveated Rendering (FFR):

    • Enabled: This significantly improves performance by rendering the center of your view in higher detail than the periphery. Experiment with the FFR settings (Aggressive, Balanced, Quality) to find the best balance between performance and visual impact.

  • Brightness: Adjust to your preference. Some users prefer a slightly lower brightness for longer sessions.

  • Contrast and Saturation: These are subjective. Adjust them to your liking.

2. In-Game Settings:

  • Resolution: Match the in-game resolution to your Pimax Play render resolution or slightly lower.

  • Graphics Presets: Start with a lower preset (e.g., Medium) and gradually increase individual settings to find the sweet spot between visuals and performance.

  • Anti-Aliasing:

    • TAA (Temporal Anti-Aliasing): Often a good choice for VR, providing decent quality with a reasonable performance cost.
    • DLSS/FSR: If your game and GPU support them, these technologies can provide a significant performance boost with minimal visual impact.

  • Shadows: Shadows are performance-intensive. Consider lowering their quality or disabling them if needed.

  • Texture Quality: High textures can improve visual fidelity but require more VRAM. Adjust based on your GPU’s memory.

  • Effects: Reduce or disable demanding effects like volumetric fog, god rays, and motion blur.

  • View Distance: Lowering the view distance can improve performance, especially in open-world games.

3. Nvidia Control Panel (if applicable):

  • Image Sharpening: A subtle amount of sharpening (e.g., 0.25) can improve clarity, especially for distant objects.
  • Power Management Mode: Set to “Prefer Maximum Performance.”
  • Low Latency Mode: Set to “Ultra.”
  • Virtual Reality Pre-rendered Frames: Experiment with values between 1 and 3.

4. Advanced Optimizations:

  • Close Background Applications: Free up system resources by closing unnecessary applications running in the background.
  • Update Drivers: Ensure you have the latest graphics drivers and Pimax software installed.
  • Monitor Performance: Use performance monitoring tools (e.g., FPS counter, GPU/CPU usage) to identify bottlenecks and adjust settings accordingly.
  • Community Resources: Search online forums and communities for game-specific optimization guides for the Pimax Crystal Light.

General Tips:

  • Prioritize Frame Rate: Aim for a consistent frame rate that matches your headset’s refresh rate (or at least above 60 FPS) to minimize motion sickness and improve immersion.
  • Balance Visuals and Performance: Find a balance between visual quality and performance that suits your preferences and hardware capabilities.
  • Experiment and Iterate: Don’t be afraid to experiment with different settings and find what works best for you.

By carefully adjusting these settings, you can optimize your Pimax Crystal Light for a visually stunning and smooth VR experience.

1 Like
10

SLAM Tracking Potential Solution

Might help with SLAM lag: I think the major problem with SLAM on older slower procs might be the fact that Pimax is setting it to affinity core 0 in the first place. Today I removed all affinity on all processes. I did what I’d normally do for gaming with process lasso. I set the only things I need for the game to run high priority but no affinity set to anything. So Pimax was set high priority and high input output. Same with MSFS 2020. It ran better than mucking about with all the affininity I listed above. I’ll do more testing for both day and night use with inside out tracking but it was perfectly solid and my FPS went up to 32 average with much higher low and a higher peak too. Much less game stutters. No lag, no loss of tracking location. To be sure the QR targets are needed too but I think the lagging is because they set the app on core 0 affinity. Just setting most things to normal and setting your game and pimax to high probably would solve the lag for most people. Also seemed like it used less CPU like this was down from 10-12% to 5-10% CPU after removing affinity settings and setting to high. This can be done with free process lasso or with taskmanager each game launch. Not sure if free process lasso remembers settings I use the paid version it’s a great app.

@jaapgrolleman @calvinyau Pimax support please test this yourselves and see if you get similar results? Thanks

Procedure

Here is a video on how to set affinity and priority using both task manager or process lasso.

Im having best results with no affinity set and just bumping pimax and my game to high priority.

I also have very good results setting game and pimax to high priority and affinity of pimax to cores 0-4 and game to cores 5-16.

Here is the support email snip that made me think SLAM was defaulted to core 0:

Could you please try one thing for me to see if it resolves your tracking issue.What we want to do is ensure the VR application you are running is not running on Core 0. The reason for this is that Pimax Play uses core 0 on your CPU to process the tracking, however if a game/application is making heavy use of this core then it can impact the tracking. To do this you can do the following:

  1. Launch your VR app/game as usual.
  2. Open Task Manager:
    • Press Ctrl + Shift + Esc, or
    • Right-click the Taskbar and select Task Manager.
  3. Go to the “Details” tab:
    • In Windows 10/11, click More details if you only see a simplified list.
    • Find the process for the VR app/game i.e FlightSimulator2020.exe.
  4. Right-click the process and choose “Set affinity”.
  5. Uncheck “CPU 0” (and leave the other CPUs checked).
  6. Click OK to apply.

Note: This method only applies for the current session. As soon as you close the game/app and restart it, the process will again default to all CPU cores (including CPU 0). So the above steps will need to be replicated.

Support has been VERY helpful and responsive to me. They even were responsive over the latest holiday.

-michael

Posted on r/pimax by u/neko_Da_cat

1 Like
11

I’m fairly certain that the tracking (SLAM algorithm) is related to the CPU, and the OP’s suggestion could be one possible workaround.

However, to fully address this issue, the focus would primarily be on optimizing the algorithm itself, specifically regarding processing time and power consumption.

12

Does anyone know if the algorithm could moved to GPU to free CPU? Could this tracking calculation be done in CUDA or other GPU calc?

1 Like
13

Unfortunately no, the algorithm can only be done with CPU.

1 Like
14

Well if pimax is playing with cpu affinity they should get feedback from the community that has been playing with this for quite sometime. Prioritizing cpu0 is definitely maybe not the right approach. Move it to another core.

15

Interesting idea. However would avoid Cuds and make it GPU agnostic if parallel processing would work. In theory it might be doable. But not sure if pimax has the needed people to explore it.

16

Arch Linux - Spans USB reconnection

Linux Issue details

Dear Pimax, I know you don’t support Linux with this headset - and I am not trying to use it under Linux (at the moment). It works great for me on windows - I boot that up and can play MSFS just fine. However windows totally sucks and I only use that for MSFS really. Even for other vr (with quest3) I use linux. I would use the PCL under linux if I could - but am realistic about how that will not be happening… However just having the PCL connected to the pc using linux causes a very bad experience. The device constantly tries to connect/reconnect - and causes problems with other usb devices. Obvious the fix is to just disconnect the headset - I will do that. So this is just to let you know that your headset behaves VERY STRANGELY - and should not be doing whatever the hell it does. Please tell your engineers to try this out. The usb reconnects makes my mouse hitch and stuff like that. Some of your users use dualboot and this is a bad user experience. This should be an easy fix for them… Maybe the fix is to create some udev rules for this PCL so we can stop the reconnects. How to reproduce: Boot linux with PCL connected - look at system logs (sudo journalctl -f) Feb 19 13:19:05 archlinux kernel: usb 1-5.4.7: USB disconnect, device number 49 Feb 19 13:19:06 archlinux kernel: usb 1-5.4.7: new full-speed USB device number 50 using xhci_hcd Feb 19 13:19:06 archlinux kernel: usb 1-5.4.7: New USB device found, idVendor=34a4, idProduct=0018, bcdDevice= 1.00 Feb 19 13:19:06 archlinux kernel: usb 1-5.4.7: New USB device strings: Mfr=1, Product=2, SerialNumbe r=3 Feb 19 13:19:06 archlinux kernel: usb 1-5.4.7: Product: Pimax Feb 19 13:19:06 archlinux kernel: usb 1-5.4.7: Manufacturer: Pimax Corporation Feb 19 13:19:06 archlinux kernel: usb 1-5.4.7: SerialNumber: P33000P1174C1000047 Feb 19 13:19:06 archlinux kernel: input: Pimax Corporation Pimax as /devices/pci0000:00/0000:00:02.1 /0000:03:00.0/0000:04:0c.0/0000:0d:00.0/usb1/1-5/1-5.4/1-5.4.7/1-5.4.7:1.0/0003:34A4:0018.2B86/input /input11179 Feb 19 13:19:06 archlinux kernel: hid-generic 0003:34A4:0018.2B86: input,hidraw8: USB HID v1.11 Devi ce [Pimax Corporation Pimax] on usb-0000:0d:00.0-5.4.7/input0 Feb 19 13:19:06 archlinux kernel: input: Pimax Corporation Pimax as /devices/pci0000:00/0000:00:02.1 /0000:03:00.0/0000:04:0c.0/0000:0d:00.0/usb1/1-5/1-5.4/1-5.4.7/1-5.4.7:1.1/0003:34A4:0018.2B87/input /input11180 Feb 19 13:19:06 archlinux kernel: hid-generic 0003:34A4:0018.2B87: input,hidraw11: USB HID v1.11 Dev ice [Pimax Corporation Pimax] on usb-0000:0d:00.0-5.4.7/input1 Feb 19 13:19:06 archlinux kernel: input: Pimax Corporation Pimax as /devices/pci0000:00/0000:00:02.1 /0000:03:00.0/0000:04:0c.0/0000:0d:00.0/usb1/1-5/1-5.4/1-5.4.7/1-5.4.7:1.2/0003:34A4:0018.2B88/input /input11181 Feb 19 13:19:06 archlinux kernel: hid-generic 0003:34A4:0018.2B88: input,hidraw12: USB HID v1.11 Dev ice [Pimax Corporation Pimax] on usb-0000:0d:00.0-5.4.7/input2 Feb 19 13:19:06 archlinux kernel: input: Pimax Corporation Pimax as /devices/pci0000:00/0000:00:02.1 /0000:03:00.0/0000:04:0c.0/0000:0d:00.0/usb1/1-5/1-5.4/1-5.4.7/1-5.4.7:1.3/0003:34A4:0018.2B89/input /input11182 Feb 19 13:19:06 archlinux kernel: hid-generic 0003:34A4:0018.2B89: input,hidraw13: USB HID v1.11 Dev ice [Pimax Corporation Pimax] on usb-0000:0d:00.0-5.4.7/input3 Feb 19 13:19:06 archlinux mtp-probe[161946]: checking bus 1, device 50: “/sys/devices/pci0000:00/000 0:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0d:00.0/usb1/1-5/1-5.4/1-5.4.7” Feb 19 13:19:06 archlinux mtp-probe[161946]: bus: 1, device: 50 was not an MTP device Feb 19 13:19:07 archlinux mtp-probe[161977]: checking bus 1, device 50: “/sys/devices/pci0000:00/000 0:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0d:00.0/usb1/1-5/1-5.4/1-5.4.7” Feb 19 13:19:07 archlinux mtp-probe[161977]: bus: 1, device: 50 was not an MTP device

Maybe fixed the annoyance by creating udev rules to just disable the headset :slight_smile:

Make udev rules file: /etc/udev/rules.d/99-pimax.rules

Content:

    SUBSYSTEM=="usb", ATTR{idVendor}=="34a4", ATTR{idProduct}=="0018", ATTR{authorized}="0"

Reload rules:

sudo udevadm control --reload-rules
```
```
sudo udevadm trigger
```

Seems to stop my mouse hitching at least.
___
[Posted on :reddit: pimax](https://www.reddit.com/r/Pimax/s/DZiMuSIFNy) - by Confident_Hyena2506
17

Info for pimax play troubleshooting codes

18

PCL Tracking Potential Fix

I fixed the issue (for myself). Saw this on in the ED forums, the PCL cameras operate on a certain hz. If something it sees is also operating on a hz, and the two arent perfectly synced (so always) it completely fvcks you over. LED bulbs are by far the best because they are energy efficient and do not create a chemical hazard when broken, so why would you use anything else? Answer: because LED lights operate on a hz.

I swapped out my LED room light for a normal bulb, turned off my monitors, turned off my keyboard LEDs, and covered my now reflecting monitors with a sheet, and it is night and day different. I can fling my head from side to side so hard the headset feels like its about to fall off, and I get no delay, no stutter, nothing, just butter.

Other solutions that helped me a little:
-Task manager → Details → rclick DCS → set affinity → disable CPU 1 and 2. this (allegedly) reserves a little bit of you cpu for the head tracking, so DCS doesnt use it ALL. Also the post I saw that did this said to also put the USB from the headset into a usb controller (aka the ports on the top of your case).
-Also in details window of task manager, set devicesetting.exe (with the pi logo) to max (realtime) priority.
-Covered a large reflecting poster on the wall with a sheet
-always start playing with window closed and light on, when the room gets dark because the sun goes down you have no idea, and your tracking starts getting worse.

Solutions that did not help me:
-covering the bottom 2 cameras with tape, the headset just absolutely refused to track. It would say “screen on” in pimax play.

upvote and LMK if this helped! the LED bulbs would certainly explain why some people have 0 problems and for others nothing works.

:reddit:f-bounce: r/pimax by img00datr6

@calvinyau team may want to look over this and tear themselves

1 Like
19

Reshade fix for RedBlue shift on Pimax Crystal

This repository contains a chromatic aberration shader that helps fix the “RedBlue shift” experienced on Varjo HMDs (Aero, XR-3, VR-3) and Pimax Crystal.

:warning:f-pulse: Not compatible with Quad Views.

To get ReShade visit https://reshade.me

:reddit: r/pimax - by u/Acinveri