Pimax 8K rocks in 4.37 - Or how to solve the issues with it!
-
@Korbi Other people might, but I don’t need screenshots, your method works! I should have been clearer about that! I followed it exactly twice and then also double checked each step.
I’m just saying I think the short cut for right now is common settings (or roll with what BMS restore setting do for you): normal FOV, parallel projections checked, because that’s what the restore does to BMS settings and it should be overriding your common ones. But until we have some one else try it, there maybe something else in your “secret recipe” that kicked it into working. But I can’t really confirm on my end without uninstalling PiTool and SteamVR.
Yeah, SteamVR does some weird things with resolutions but also on top of that the second number matters because it will confirm what the aspect ratio is for normal or wide FOV. Interestingly, FOV settings in the Pimax also change aspect ratio.
-
@frachy I think the 200% is a little much, but I’ll test it tonight. I can’t ever recall seeing in other headsets like the Quest 2 have quality improvement over about 150%. For those at least it doesn’t work that way, the PPD/DPI limit is still a thing.
I didn’t try over 100% in the Pimax much because often we are talking a very large amount of pixels that today’s video cards just aren’t designed to pump out. 8k TV’s 33 million bring a lot video cards to their knees in 2d, let alone the per eye effect of VR even with the extra VRam of say a 3090/4090.
Parallel projections checked and wide view is truly an 8k number of pixels even at 100%. Also, I would say 100% resolution with normal FOV, Parallel Projections checked, is somewhat similar to the PP unchecked large FOV resolution that I normally run at, so if 200% resolution quality doesn’t knock my socks off, I’ll probably be ok with that performance level. Like I said, I’ll test here in about 6 hours or so. -
@frachy I have been able adjust the SteamVR slider once I turn “Render resolution” to custom and have for years now. I don’t think that is different from your setting. I’ve 200% and 150% I don’t see much difference personally. also, I always keep it at 72hz because since I prefer large FOV, it was always the most realistic for performance settting. Granted, where I am looking is inside the cockpit at the labels and the MFDs because that’s most what I want the detail improved on.
-
Thank you so much for figuring this out.
This works perfectly for me using the Pimax 5K+.
The only extra thing I had to adjust was setting the Hidden Area Mask to false in the Falcon BMS game settings in PiTool.
Mouse and HUD issues fixed. -
I was hoping U1 with it’s “Improvement to VR resolution casting” would fix the issues with parallel projections and maybe the large FOV. Unfortunately it still seems to be the same Normal field of view with Parallel Projections checked is still the best setting with the other issues as reported with settings other than that.
However, I think I’m noticing more texture shimmering than before. That could also be the new video card drivers and other things. Let me know if you all are seeing this or not, made some big changes to my PC this week so it may not be BMS. Overall, hoping that at least the parallel projections and hopefully the field of view will work someday in BMS VR. It is still early for sure and very happy to have it as an option!
-
@Snake122 Interesting!
Won’t be able to test that before tomorrow.
Please keep reporting what’s your experience Pimax users! -
Note there is this setting now that may help with the parallel projections being unchecked:
- set g_fVRCropOffset -100.0; // adjust VR view offset: default = -100.0(auto mode), recommended manual adjusting ranges: -1.0(opposite of cross eye) to 1.0(cross eye)
Also this in some of the FOV:
- set g_fVRIPDMultiplier 1.0; // adjust world scale, default = 1.0.
So when I RTWT, there is somethings we can still try in U1!
-
Pimax lenses/panels are canted about 10 degrees , will devs know this ? DCS required Paraller projections first but they fixed it so maybe same thing,.
-
@haukka81 said in Pimax 8K rocks in 4.37 - Or how to solve the issues with it!:
Pimax lenses/panels are canted about 10 degrees , will devs know this ? DCS required Paraller projections first but they fixed it so maybe same thing,.
@chihirobelmo Do you know if that has to do with the current “issue” on the pimax headsets? Anyway thank you very much for you intensive reseach and additional work you put into VR for U1.
-
@Snake122 said in Pimax 8K rocks in 4.37 - Or how to solve the issues with it!:
set g_fVRCropOffset -100.0; // adjust VR view offset: default = -100.0(auto mode), recommended manual adjusting ranges: -1.0(opposite of cross eye) to 1.0(cross eye
I absolutely have no clue, what crop offset and cross eye means in regards of VR HMDs
-
EDIT: nope, set g_fVRCropOffset looks to not have enough adjustment if any effect at all on the parallel projections off issue. I tested by looking at the same ICP button and seeing how far the mouse cursor was offset, it may have made a slight difference but not much in large field of view setting.
@haukka81 said in Pimax 8K rocks in 4.37 - Or how to solve the issues with it!:
Pimax lenses/panels are canted about 10 degrees , will devs know this ? DCS required Paraller projections first but they fixed it so maybe same thing,.
Yes, and we may have been given the tool to fix this now with the VRCrop… SEE EDIT at top!
@Korbi said in Pimax 8K rocks in 4.37 - Or how to solve the issues with it!:
@haukka81 said in Pimax 8K rocks in 4.37 - Or how to solve the issues with it!:
Pimax lenses/panels are canted about 10 degrees , will devs know this ? DCS required Paraller projections first but they fixed it so maybe same thing,.
@chihirobelmo Do you know if that has to do with the current “issue” on the pimax headsets? Anyway thank you very much for you intensive reseach and additional work you put into VR for U1.
I don’t believe he has a Pimax headset to test with.
@Korbi it didn’t apparently make it into the 4.37U1 technical manual but I’m assuming that it allows some offset left and right. With Parallel projections unchecked, you get the 2-d overlays, etc. that aren’t lined up in each eye. If you find the right value of this setting we maybe able to run with Parallel Projections unchecked, solving the performance issue of the extra resolution that setting takes.
-
@Snake122 I see Snake!
It seems that option won’t help? Did you also try extreme values, like 10 instead of 1? -
@Snake122 said in Pimax 8K rocks in 4.37 - Or how to solve the issues with it!:
set g_fVRCropOffset
There is a mistake in the changelog
set g_fVRCropOffset
is NOT in the code anymore
the value to use is
set g_bVRManualCropAlignment 1 // on turns on manual cropping.
set g_fVRManualCropFactor 0.0 // how much to move the cropped area, -1 totally outward, 0 centered, 1 totally inward. (float value)
-
@Korbi I did. Just not that extreme though, I believe 5, no noticable effect.
@Mav-jp said in Pimax 8K rocks in 4.37 - Or how to solve the issues with it!:
@Snake122 said in Pimax 8K rocks in 4.37 - Or how to solve the issues with it!:
set g_fVRCropOffset
There is a mistake in the changelog
set g_fVRCropOffset
is NOT in the code anymore
the value to use is
set g_bVRManualCropAlignment 1 // on turns on manual cropping.
set g_fVRManualCropFactor 0 // how much to move the cropped area, -1 totally outward, 0 centered, 1 totally inward.
Ok, will give this a try in a few!
EDIT: This is totally doing something. However, if we can find a setting that works, I’m unsure. At low values of under ~.5/-.5 (assuming .xx is the percent of crop factor), it seems to help the offset but then I get my left eye’s cockpit scaled much differently than my right.
-
what do yall think of the pimax headsets so far? im currently using the quest 2 and may upgrade in the near future.
-
@AR_Parker As a long time triple monitor user, I really like the wide view. The largest isn’t available right now in BMS, but even the normal view is quite bigger than most VR headsets. It is clearer than my Quest 2 with a higher PPD level.
However, with BMS I’ve been using my Reverb G2 much more than my 8k X. This is partly due to the issues listed in this and the parallel projections thread, also the bulk/weight, needing to turn on the base stations, and the G2 being clearer. But there are times I notice the G2 not having some of the field of view I would get in the 8K X. Also it takes a pretty high level video card to drive the 8k X.
-
@Snake122 wait for it
Guys, I really don’t know why, but update 1 solved it for me.
HUD is where it’s supposed to be WITHOUT PARALLEL PROJECTIONS!The only irregular behaviour I have left is double vision in orbit view, but thats not used anytime by me and a double rendered frame counter, which I also do not use in normal operations.
AWESOME!
-
and now believe it or don’t
I CAN USE THE FULLL FOV OF THIS FREAKING PIMAX IN BMS 4.37.1
-
@Korbi what about your mouse cursor?
-
@Snake122 it works just fine.