I used a Quest Pro for a few days and the little bit extra FOV was nice. I thought the main menu was smaller because in the G2 it fills almost edge to edge.
I felt a little more confined in the fov going back to the G2. But after a few minutes the feeling went away. I just had too many issues with the Quest Pro and better sharpness on the G2.
For sure. the Crystal has the most Vertical FOV of any headset ive tried. I have to really strain my eyeballs in the vertical axis to get to the end of the FOV . The horizontal FOV seems a bit more than the G2 with an increased FOV gasket on. I can see the vertical ends of the headset âwindowâ so to speak, on both sides of the view. I really dont know why they had to make the Crystal headset so huge. I almost feel like they could have tried to make a smaller form factor to make it lighter. If it had a massive horizontal FOV it would make sense why the headset is so huge, but it does not!
They put it in the 12kâs future case to save money. Makes economic sense but horrible design decision! You get to cosplay a hammerhead shark but without benefitting from the huge FOV the case is ultimately designed for =(
I solved two problems I had with the Crystal today.
Firstly, I had problems with clarity; I could get a really sharp sweet spot with my left eye, but it wasnât in the centre of my vision, while the right eye was not as sharp overall. Iâve had cataract surgery to replace the lenses in my eyes but now have 20/20 vison in my right eye and better than 20/20 in my left. Trouble is I can no longer adapt my eyes for near distances and so need reading glasses. The Crystal lenses have an uncomfortably close focus, 1 metre according to reports, whereas other headsets are around 1.5 metres. As my reading glasses are varifocal, I couldnât really use them to see if they made things better, as they blur things depending on where you look.
So acting on a hunch, I picked up a pair of plain reading glasses from my pharmacist, with a mild +1.0 diopter and tried that. The difference was night and day. Both eyes are now focusing on the screens properly, including the centre of my vison in my left eye. People with presbyopia as they age, who need reading glasses, or have had cataract surgery should really be aware of this issue with the Crystal.
Iâm running the Crystal at 3800 x 4420 and now it all looks fabulous. Super sharp instruments and ground detail. No more searching for a sweet spot, it all looks sharp, except the extreme edges. No wonder others were blown away, whereas I was still struggling to set IPD etc and getting eyestrain.
The other solve was the Apache head-strap, works like a charm and no more wobbling of the headset.
I am currently using the highlight mode. However I noticed that at night it kinda feel that the image is foggy! What are tot using?
I use, âlocal_dimming_black_levelâ : 0.007 in the profile file. Extreme is too foggy, unusable at night and highlight is too washed out. Seems to be a good compromise.
File is located here:
C:\Users"username"\AppData\Local\Pimax\runtime\profile.json
You can edit manually.Make sure to save and Iâd recommend sending a shortcut to desktop to check if the app overrides when wou change something in PimaxPlay. You can reset all Color values to 0 as well, since by default, if you didnât make any changes in the app, it will give you weird values.
currently i have for local dimming black level 0.6 as seen in the screenshot
you have this to 0.007 right? would you mind sharing your configuration also for the colors?
Sure, itâs all at zero for now. I havenât played around with those yet. My main concern was to get rid of that fog:
{
ââ : null,
âPimax P3Bâ : {
âcolor_brightness_0_rgbâ : {
âxâ : 0,
âyâ : 0,
âzâ : 0
},
âcolor_brightness_1_rgbâ : {
âxâ : 0,
âyâ : 0,
âzâ : 0
},
âcolor_contrast_0_rgbâ : {
âxâ : 0,
âyâ : 0,
âzâ : 0
},
âcolor_contrast_1_rgbâ : {
âxâ : 0,
âyâ : 0,
âzâ : 0
},
âdisplay_timing_selectionâ : 1,
âlens_auto_detectâ : 1,
âlocal_dimming_black_levelâ : 0.007
},
âdbg_asw_enableâ : 0,
âdbg_hidden_area_enableâ : 0,
âenable_foveated_renderingâ : 0,
âfoveated_rendering_levelâ : 0,
âipdâ : 0.06234375014901161,
âpixels_per_display_pixel_rateâ : 1,
âsteamvr_use_native_fovâ : 0
}
Also your âpixels_per_display_pixel_rateâ is at 0.75. meaning you have only 75% of the resolution. set this to 1 for full res.
I notice this line reads on your profile.json: "lens_auto_detectâ : 1,
Whereas my line reads: âlens_selectionâ : 2,
Do you perhaps have the plastic lenses? I have the glass ones and am curious about this different setting.
Oh I didnât know that! Maybe it is because I lower the resolution in the Open CR toolkit?
Which setting in the pimax adjust the pixel per display pixel rate?
Mine is also set to 1. How do you know actually if the lense is glass or plastic?
An additional question guys, do you know when pimax will roll out the automatic IPF and Eye tracking? I Stil donât have these options currentlyâŠ
This is a great mystery of Pimax. You need to wait.
Regarding the lenses - you can easily tell glass vs. plastic by touch.
i read in a post that by checking the advance menu, one should see if the headset has glass or pastic
In my settings i can see only one option available i.e. 35 PPD Glass. But if i touch my lenses with my nail, it feel like plastic 
but i cannot really tell for sureâŠ
ok, you mean for the eye tracking and IPD! well lets wait and see when these option would be out for everyone!
The glass lenses have anti-reflective coatings, whereas the plastic lenses, I believe, do not.
Hi Felipe,
I think the "lens_auto_detectâ : 1, is because I have it set on auto, and it detects the Glass lenses by default. They should feel heavy if you take them off.
Iâm also on the latest Public version of PimaxPlay software. Eyetracking is still in Beta.
How did you get version 1.14?
When I download from this site https://pimax.com/de/download-pcvr-crystal/ I get 1.13 and update from inside the app does not provide 1.14
After I downloaded 1.13, at some point it prompted me to update. I didnât do anything special.
But you can try the âcheck for update buttonâ next to the current version in âsettingsâ.
