Rather than necro-bump a thread that was already ignored I decided to attempt creating a thread where this issue can discussed in full. For reference, the visual artifacts in question can viewed here. A major thanks to @Pimel for taking the time to capture the problem!
Despite many allusions to “tearing” the only thread documenting a specific issue with footage has been completely overlooked. I hope it’s reasonable to assume that this is what most users have been referring to when describing “tearing.” Why hasn’t Pimax addressed this phenomenon by attempting a technical explanation? @PimaxUSA Failing that, let’s see if the community can figure this out. PiTool is going open source soon right? Maybe the answer lies down that route. Any and all feedback would be tremendously appreciated!
Finally, @Pimel, do you continue to have this issue?
I have seen a screen tear exactly once, a couple of months ago. I fixed it by powering off my 8K and rebooting my system. (I didn’t want to diagnose the problem; I just wanted the problem to go away.)
It sounds like you have a hardware issue. If you haven’t requested a replacement, you should.
I’m sure it’s a coincidence, but it was also the right-side panel which had the tearing.
Thank you very much for your reply. To clarify, I don’t experience this problem non-stop but there is no rhyme or reason to when I experience it. I backed the Pimax knowing full well that it would require tinkering but I believe there to be a limit to what the end user can be reasonable expected to try to rectify.
I don’t want to sound ungrateful, I love my Pimax, but having a nebulous term like “tearing” being bandied about when a video exists of a known problem is counter-productive. That’s why I conceived of “one thread to rule them all” as a way to pose the question to the community “Is this what you mean when you say “tearing?””
Problems like this shouldn’t continue to exist at this stage in the game. The product is too mature and is in the hands of more than a relatively small group of enthusiast Kickstarter backers. I confess, I hadn’t even considered RMAing it. Maybe I am confident a software solution is all that’s necessary or maybe I’m not confident that the new one I receive will be any better.
Lastly, my unit is a 5k+ if that makes any difference.
Looks to me like a displayport hardware malfunction or the cable losing signal due to transmission degradation, have you tried to move and twist along all the cable to see if the problem worsen out or more spikes appear ?
I have had a Teamviewer session with Pimax support for an hour to try to find the cause. We couldn’t completely pin down the issue and after some time it was decided to replace my unit.
Sorry for getting back to you so late @Pimel, but Im glad you got instant help through Teamviewer!
To me this looks like something the GPU ís messing up, or maybe the DisplayPort connector.
Have you tried it with another GPU maybe?
Anyhow, hopefully a replacement headset will solve this!
@Lillo I will give that a try, thank you for the suggestion. I received a new cable not long ago to address the pixel storm but it didn’t correct this issue which I experienced with both cables.
@Pimel It’s encouraging that they took the time to work with you on the issue. I just wish they had attempted to create a dialogue around this specific problem.
@SweViver Wow! Martin I know you’re really active on the forum but I didn’t necessarily expect to see you turn up here, although I’m glad you did. I have always want to tell you how much I appreciated your hard work during the M1 testing phase. You’re the reason I pledged for a Pimax on Kickstarter in the first place!
If you were in my shoes would you RMA the unit or would you wait a bit longer until the open source drops?
Coincidentally, around this time last year I befriended a group of Swedes that I fly DCS with and have been teaching myself Swedish. So once more: tack för allt du gör!
As Pimel has been a long time member here during the p4k. The Teamviewer has been a first class support they have offered. Some members they have spent time helping folks is something bigger companies could learn from.
I am indeed a long member and was surprised they put in the time they did. But this was also some time ago when the problem first started to appear. So maybe they have better solutions by now.
Our technical support team is updating FAQ by collecting solutions from forum and service desk now. i followed the process for a while, and this situation going to be changed.
Do you mean that you have been following the screen tearing issue? I need to know what the next step is. Do you recommend that I RMA the unit? Is the screen tearing something Pimax is trying to fix via software? @PimaxUSA Kevin, would you be willing to weigh in here?
The screen tearing issue is cause by bugs in old version pitool, but it has been fixed for a while. You can download the latest pitool in our official website.
Thanks very much Martin but I am actually on v1.0.0.129 By the way, did you see my post to you above? If not, thanks again for all your hard work!
@anon74848233 As I mentioned to Sweviver I am on v1.0.0.129. Did you perhaps mean the latest “stable” release? v1.0.0.129 still says “Beta test release” in the thread title.
I will give this v1.0.1.132 at try. Thanks everyone! If I’m still having problems I will report back.
I have a similar problem when i turn up all the settings on a program.
I tested just now on steam home. turn up steamvr video to 500% and pi tool render to 2 : no problems. Turn up app video settings to 500%: screen tearing. turn down frame-rate in pitool: tearing goes away.
My guess is its band with issues
For example in skyrimVR I have screen tearing in the towns but often no screen tearing outside or in buildings.
I do have a a 2080ti so maybe most cards would just crash in stead of having screen tearing, so maybe this i a very unique issue.
Changing all the settings individually may produce no screen tearing with out any loss of quality but i have no specific idea what setting does what.
By the way, did you see my post to you above? If not, thanks again for all your hard work!