Its not only GFX card. Its complete GFX system (include CPU, RAM speed etc). U just dont understand what i talking about. If u measure GFX system parameters with high load (target fps=40 for example) u can avoid stutter.
I never had a stutter cause my every component top and overclocked. almost 4ghz ram, 5.2 cpu with 5ghz cache etc. 253 version just need automatically adjustable delay dependent on system parameters.
Probably for my system its can even do things faster than 253 version doing.
Ignorance. Multiple members here have high end intel cpus and 2080tis with 32gb of ram and stuttered. you have an 8k which is why you can’t comprehend the situation, it applies to 5k+ users nearly exclusively.
When i have 5ms frametimes and stutter, you’re not going to convince me its my system.
https://community.openmr.ai/t/tracking-issues-april-2020/26759/109 look at peoples system configs. You will not be able to trendline that we all use bad hardware.
Not true. We have an at least 1 8k member that has reported studdetr. 5k+ only has a larger number due to more of them out there.
It would be more interesting to have folks like yourself test an 8k as you’d likely still experience studder.
There are 5k+ members with lower end cpus without studder as well.
That’s right… i knew of the one 8k user with judder, but most people did opt for a 5k+ and that may be why it seems one sided.
Pimax did admit this was piserver.exe issues, but I have no idea what the scope of that file is. I’d love to try an 8k or 8k+, really any other HMD to see if it occurs on my two setups. Probably the only pimax user in Rochester/Buffalo NY though 
I don’t mean to sound negative btw, it’s just easy to blame people’s setups when you have a nice rig. ‘USB issues’ is another common one haha. Between index controller issues, tracking issues etc its clear the solutions aren’t always so easy.
Sometimes the nicer rigs can have a component that has flaws.
Os2 was a great OS but due to how it handled memory more thoroughly it would find faulty memory vs Windows and Dos.
Pimax headsets likely challenge the hardware more than regular headsets
wow, I remember os2 WARP (to be exact, warp, lol)
It came with my first PC which was a pentium 60. (btw the only rig I bought pre-assembled) was a c64 kid before.
But, especially for a kid that wanted to play, the os was pretty bad. just like linux 
but anything else ran indeed quite smooth and faster than on the Dos/Win Os.
Os2 Warp could work quite well with the Windows extensions. But tbh Windows sucked eggs at games.
Windows for Workgroups just didn’t cut it. Even once W95 was released it majority of the time rebooted into DOS mode to run games and then rebooted and loaded windows.
It was just DOS 7 auto loading Windowd v4.x
Os2 Warp and later Wizard suffered poor Marketing. Bill Gates was part of the Os2 Warp team and was quoted once that he had no plans to dev windows further as you’d just have OS2. Then of course he left the team and released W95.
Poor marketing and ahead if it’s time was core issues.
yes, we shared and battled autoexec.bat files (and there was another file, forgot the name) at school. like „try this, it will make everything better“ Took those discs home like some holy grail, till somebody came back with an even better config.
Windows became with Win10 actually a great and super stable OS. And improving with little handy stuff like, call me noob but I think it’s kinda new „feature“, win+g. (sound devices overlay + other useful stuff) None of my friends did know that it was implemented, so some here might not know as well.
Hated to alt+tab out of games.
Config.sys and Autoexec.bat. used to be manual edits in an Art form to free up enough base memory to run games (640k) loading drivers and such into hi memory the first meg of Ram above 640k
Memory in excess of 1meg was XMS and you could load a device driver to make it ems. Using Driver Emm386.sys
Quarterdeck had a memory manager (Qemm386.sys) that could do this itself with better results than Microsoft’s Memmaker released if mem serves in MSDOS 6 0. Microsoft was sued after copying Stacker’s Drive doubling software. MS’ was called Doublespace; they removed it in DOS 6.21 and later were able to re release it as Drvspace.
Windows OS started to become more than a gui on top of DOS I believe with Windows 2000. Prior to that Win98 Second Edition was decent and Windows ME was meh.
Windows 10 really is imho when it has started to become much better with actually giving more accurate install estimates.
Quarterdeck also had a text based Multi Tasking enviroment. Deskview if memory serves(much better than Windows 3.1x for workgroups).
Pimax headsets may well “challenge the hardware” and I am somewhat sympathetic that USB chipsets are a poorly specced dog’s breakfast, but HMDs need to run properly on a wide variety of hardware. Lower framerates are acceptable on lower end GPUs, but weird effects like stutter should never be an issue. Likewise, a version of the headset software that only allows a GPU to run at 70% is plainly buggy software. You can’t blame mysterious problems “with people’s rigs” for that.
I think the Pimax hardware has a lot of potential, hopefully they can figure out the software side of things.
Check out a recent post on W10 june updates maybe causing crashes. Plus a recent user posted using a new w10 feature to boost gpu utilization.
Yes pimax needs to help find a solution to to a variety of issues that maybe related to compatibility. But don’t knock the fact that GPU models and other hardware software could also be creating issues as well.
At least on the Nvidia side, these are becoming quite rare and simply put, other headsets work and don’t have utilization issues (barring any other system bottlenecks). There’s literally a noteable amount of free performance to unlock in a Pimax that’s being held back by poor software. They clearly tried to address this with the undocumented GPU Catalyst feature but that brings a host of other issues. If/when the Pimax software improves, it won’t be the video drivers that did it.
In my opinion, Pimax is outsourcing the coding of its software for an unnexperienced company/group. There´s clearly a lack of transparency, like the lack of informations in log list, lack of a road map and lack of listening for community feedback. The retract of these issues quoted above is the lack of a 64hz button after the 258 Pitools design changing. We´ve reported this easy fix issue many times in this forum and apparently it didn´t reach to Pimax programmers (or they didn´t care about it).
i have “snow” effect on dark backgrounds with 261 version. Not much snow but quite noticeable.
randomly occurring and disappearing white pixels across the screen. They are clearly visible on a black background. This happens exclusively in version 261.
FPS: 55-57 vs 70fps in 253 …
it’s not even funny. Is it really impossible to use the method of version 253 for those who have no problems with the output of frames?
Updated to 261 from 260 on my 5k+ last night.
During the update it came up with an error that i couldn’t delete certainly file. I told it abort after a few retry attempts and assumed it rolled back. It didn’t. Instead it showed 261
I then rebooted (as I always do) and then tuned on the check which gave me a FW update for 144hz. I enabled 144hz with it’s max FoV setting and played Assetto Corsa. There is certainly a notable jump in smoothness of the image when driving. Less blur, better sense of speed and depth compared to 90/large so I will continue to run 144hz.
My PC can handle it fine so no issues there. Overall, outside of the weird installation issue, nothing bad to report and 144hz for racing sims is certainly appreciated. I have to say the loss of FoV was not perceptible at all even in close side by side racing.
Hi Robert. I imagine it might have been a file in use. Sometimes best to stop/kill piservices.
That was the plan thus I hit abort. Pitools had different ideas…
Hello !
Just in case, i own an Artisan for a week now, using 5700xt nitro+ with Radeon software 20.4.2 and i have no issue so far with Pitool 260, i have no warning neither.
Do you have other issues beside this warning ?
Seems there is a new AMD driver (20.7.1), don’t know if i should update or not…
I’ve only had my 5K+ for a few week so the first pitool I used was 261. The pitool has crashed a couple of times but have not had any in game crashes or drop outs. Performance has been good with no stuttering in any games I’ve tried.
But after reading this thread I decided to try 253 and have been using that for the last couple of days with no issue.
I run at 120hz with normal FOV, pitool at 1 and steam SS at 100 %
with these setting steam was reporting a resolution of 2276x2104 using 261
however with same settings on 253 steam was reporting 2844x2632 which is quite a significant difference.
Yet despite running at a higher resolution 253 has about 10% better frame rates than 261 in all the games I’ve tried. GPU usage went up from 75/80% to about 96% in 253
So it would be nice if they could work out how to get back that performance in the newer pitool.
This is an unfortunate reality of pimax software. Poorly documented, barely tested and the community feedback is barely acknowledged.
It’s been months and @SweViver was going explain and expand on GPU calatyst with performance results. As usual, all talk, no walk.
I’m sure there will be some BS about how there’s a much broader piece he’s working on that’s totally worth the wait! But that’s the pimax experience in a nutshell. Waiting for the next big thing that will be under delivered with a host of caveats followed by confrontational attitude to Feedback.