Doc-Ok has some great stills for testing.
Just got a call from someone at Pimax making sure everything was working.
It came from a “Private Number”, so anyone else that got an 8kX if you get a weird call be sure to answer it.
Quite impressed by the Pimax response on this launch.
Except that your system might slow to a crawl or crash, if you ever get close to that limit. As a programmer, I assume the purpose of the limit is to remove bad system behavior. It would probably be safer to limit it to a lower number like 8K or maybe 12K.
@SweViver
But if that is so we would never have gone to 16384 or had a benefit of it.
I use it and have not discovered a downside except If I push the render resolution up to like 2.0, the GPU gets a heavy load, since it’s not cut off resolution wise before.
I would guess either we should not touch it at all or at least to some value it does not matter how much we push it, except a different limit is hard code else where or the algorithms or buffers in the back can not handle that size.
I guess we would need to test that by incrementally increasing it and then push the resolution up until we hit the limit and so on, or ask the steam dev team, what could be interesting for pimax…
Edit: and large FOV I guess. We should make a dev club, quite a few in here it seems😀
When I tried it (with no extraordinary PiTool or SteamVR settings) my system slowed down extremely so I immediatelly had to go back to the default value. That was last summer, will check again when my 8KX arrives.
It sounds like your super sampling was too high (either in SteamVR or in-game). That’s the only way the limit should act like that.
Certain games use an extra level of super sampling on top of what’s requested. For example, I can only run Hellblade at PiTool quality 0.5 or it runs at a crawl (or sometimes crashes at start-up).
Ok, that might be worth checking - I use it since about a year (maybe a bit less).
I only get issues if i “use” that resolution - as in large FOV, max out every resolution, SS, etc, and then I can push further the 16384 as with 8192 or 12288 and then of course its not usable anymore in game as FPS are like a slide show. But just the value and default “usage” have not done anything “harmful” as far as I have noticed.
Maybe we should make a thread for this an elaborate on it (in the -> PiTool categories ) ?
Just as a side note, after a driver update I had quite strange issues 2 days ago - my FPS where almost half - I have no Idea what happened - only after “fooling around” in my GPU tool (Power Threshold and OC ) it jumped back to normal - no Idea why - but i did nothing to change the setting for the steam values or in game.
I literally had the exact same thing happen after updating to these latest drivers. Same solution fiddling with my OC settings fixed my performance.
One thing to mention is that 16384 on MaxRecommendedResolution with 8KX should NOT be used with Large FOV in SteamVR Home
It becomes a slide show. The SteamVR Home must be extremely poorly optimized as it can’t handle it, while even VR simulators like Aerofly FS2 can without a problem, at least with framerates on 60-65fps at high settings.
Hey interesting to hear!
I was in AMS2 and ACC a lot and getting “best” values for quality and FPS, so it jumped at me straight away. Something must have happened that reset the GPU Card, as all my OC’s where back to default, no idea if that happened before (Precision software update some time ago) or with the driver update, usually I don’t touch that stuff anymore after initially find a good value, so it was not in my focus, but it seems that triggering the firmware of the card did something.
Sometimes a driver dll doesn’t get unloaded properly. I usually just reboot my system after a driver install, which solves that problem.
How do we resolve that distortion btw? Mine is absolutely terrible, it feels like the edges of my vision are swimming all over the place. No combination of positioning or distance from the eyes seems to resolve it, it’s like the lens warping is flat-out wrong.
Have actually stopped using my 8K because of it, it’s too uncomfortable. If I have to switch to narrow FOV to avoid it then I might as well use my Quest or Rift.
I keep hoping there’ll be some kind of update that fixes it or lets us tweak it but as I understood it’s calibrated/set at the factory for each headset and once it’s left the building that’s that… hope I’m wrong about that…
Have you tried the 8KX, @r00x? Or the Comfort Kit?
Hey @SweViver! No, I’d love to, but I only have access to my 8K backer unit I’m afraid. So far no accessories from the Kickstarter have arrived (and as I understand some won’t arrive, like the eye tracking/hand tracking etc now costs extra money). I am using it with some HTC base stations and old Vive controllers. I have at least attached a Vive DAS to tide me over until the Pimax one (KDMAS, is it?) arrives, as I understand that will ship to backers at some point (August or onwards, I think?).
I’ve been a VR user since 2014 and have owned and/or used a range of headsets since then (Oculus DK2, Vive dev kits & commercial, GearVR units, PSVR, Rift CV1, Rift S, Quest, that sort of thing!), so I’m familiar with the effect getting a headset to sit right can have on the visual experience. I have tried messing with the how the headset sits on my head in all sorts of ways (including closer to or further from eyes, up, down, angled, etc) but the lens warping just seems wrong across the periphery of the display.
It’s quite a shame because the FOV is amazing, it would have made a great headset for Elite:Dangerous but I can’t seem to resolve the warping. Am I right in thinking there’s nothing to be done about it, i.e. no way to change or correct it in software? Could the eye tracking modules be used somehow to calibrate the lens warping model for the user, maybe?
How do we resolve that distortion btw?
Try to check this thread & the message I linked below, the hint is to move your head from left to right & vice versa in the most worst environment (where distortion looks worst) while you keep moving your HMD up/down (vertically, really try to move it in a positional that you consider weird/too high/low) & see what position does the trick, e.g you can do it in steamvr home where frequently played games screen with lot of horizontal lines, when you move you hmd up/down you need to ensure those lines get horizontal.Also once spotted best vertical position try to adjust tilting, also I guess you need to remove face cushion bracket & try to push your eyes closer to hmd, I know you already did it all & had lot of hmd, same for me, but what was my surprising when I moved hmd totally in weird vertical position for myself (where I didn’t expect it to be & it still was comfortable) as I used to wear other HMD that way.
https://community.openmr.ai/t/testing-for-distortion-in-vr/28805/53?u=teigue
Well these are the very rare cases.
Since Windows 10 a reboot is necessary from 1 of maybe max 50 cases, maybe even less unlikely depending what kind of drivers you install.
Running an insane amount of frequently updated peripheral devices I can tell.
But of course, I did bump into issues here and there where a restart fixed it. (Mostly not hardware related drivers though)
Beeing so rare though, I retrained myself over the Win10 years only to reboot after driver install if there are issues or if it was explicitly stated during the installation.
But maybe it is still a time saver to boot 49 times unnecessarily on an m2 drives compared to trouble shoot on 1 issue, finding out that a reboot would have fixed it.
Other headsets e.g. HTC vive, they build each unit and then calibrate the distortion profile to fit the headset. Pimax have 1 distortion profile that they apply to all headsets they build, so they can change this distortion profile via firmware update, bit it means if your headset wasn’t built “to spec” you might never be able to get rid of the distortions. Really that should be an RMA (regardless of warranty period because obviously if its been built wrong it was present when the item was shipped).
Hi !!
the thing that scares me is the 75hz: /
I am not sensitive above 90hz but below I find it not fluid enough: / (pimax in 72hz or quest 72hz)
i do a lot of simracing raceroom, ams2, assetto corsa, dcs, dirt rally 2, xplane 11 the 75hz
suddenly is really visible ?? thank you
On my 5k+ as of 2 nights ago, with PiTool 261 and the included 144hz firmware, I switched from 90hz to 144hz. I only play AC. The difference is very noticeable to me. The image while in motion is a lot cleaner (less blur), better sense of speed and general smoothness of gameplay is a lot better. This all leads to better depth perception also. Spent about 3hrs of actual driving in 144hz and I’ll be sticking to it. My system could handle it which was a nice surprise.
Dude, same thing, my system can only run dcs at 30-60fps depending on which server I’m on, but running in the 120 or 144 hz mode is just butter smooth compared to running in 90hz mode. I can’t make sense out of it, but it is very noticeable.