Hey @Enopho thanks for your more kind and informative help. So, regardless of the fact that Ive seen evidence that leads me to believe this isn't a OS or registry specific issue, I wanted to go thru your steps thoroughly to try and rule this out, so far so good, because your instructions dude were really awesome, thank you so much.
You might ask? What leads me to believe that it isn't a OS registry specific issue but something deeper to do with the way the hmd interacts with the software to draw this bar? well..
Before, I was running a dual boot, multiple versions of windows, I used my windows 10 install for VR since I was having some odd issues in windows 7 using the AMD catalyst drivers, and/or nvidia drivers. Back then I also had a 960. But please note I've seen this issue on both my AMD and Nvidia chip, im pretty sure the issue is with something in the 'headset registry' or 'view state' if there is such a thing, is it possible for the firmware to accidentally draw a line accross the view screen of the HMD? I believe it's something specific set in the hmd viewstate causing the software to react this way. I'd managed to fix the bar by fudging around with the older legacy drivers like other people mention, but i think t here were some auto firmware updates in between that is leading my pimax 4k to 'change state' from pimax mode to video mode, but only when changing the render setting under 'devices' for the piplay settings, I am sure this isns't normal behaviour and that I managed to fix it by swithcing between them and playing with the render setting, I am pretty sure this is where the 'fix' I had before lays around, but I can't be certain, I'm really not greatly familiar with the way the thing works or how the firmware and hmd interacts over usb with the piserver api. etc
The reason why I say this is, because I accidentally booted up the old install OS on a seperate disk, and it borked the HMD, so that, when I went into the new OS, the line also shown there too, if that makes sense . Then, I reinstalled, my entire OS, on a seperate NVME, which i now dual boot natively and non natively inside libvirtd, but anyway, I digress a bit, the point is something borks the HMD whatever machine i use it on after this happens with the older legacy drivers ,so it's kind weird and kinda annoying.
Evidently, I went through registry, and deleted all the keys for pimax and piplay like you said, and tried the following versions PiPlay_Setup_22.214.171.124 and PiPlay_Setup_126.96.36.199 and piplay_188.8.131.52 which seems to be the most current and uptodate, sadly alas, same black line. I'm gonna try fudging around because I know playing in 'Devices' on the legacy drivers got rid of the black line before, it's just I was stupid enough to boot into the old OS and fudge up the HMD again, so to clarify, I sincerely believe if I sent this HMD to you or someone else you'd have exactly the same issue, and the weird thing is i've fixed it before just changing settings under devices in piplay.
Weird tho right?
Thanks for the help so far, I'll let you know how I get on. and yes, very happy to play around more with this.
The only thing I haven't done yet is play around with the steamvr compositor settings as you instructed, so I will do that now, sorry I had forgot about that, as installing/deinstalling and clearing the registry each time is a pain !
Thank you again kind sirs,
UPDATE: (BECAUSE CANT ADD ANY MORE POSTS ON MY FIRST DAY!
What is also very curiously interesting to note,which is endemic of the issue I suffer, I believe caused by the way render mode and the pimax/view mode works on the older legacy drivers broke something to cause the hmd to 'insert this line' with ALL drivers and ALL versions of piplay/pimax software.
- uh - long setence - the curiosity is that when i change pimax to video mode, the headset goes into red LED state, and never changes, and it says 'mode switch failed', I believe this relates to the way the HMD has been 'left with instruction' to do something, because the state change in firmware/software didn't end 'properly' and/or something similar to this. It's the only explanation I really have.
Einstein said if you do the same thing again and again and expect different results I am mad, but, actually that is exactly what I see here, I think there are more variables to it, than I realise what with all the registry and such, but the fact of the matter is if a completely fresh install and completely modern driver 2.x piplay version has the same black line, that to me is pointing away from the OS and registry and firmly at the interaction between the firmware of the device an d the software, and/or some setting or variable in the HMD.
At least we're getting closer to alluding to the symptoms being seen - thanks again for all the assist !
My working theory:
I think it's odd that changing the view states in the legacy version got rid of black line first time, and then acidentally booting os with the bad piplay/pimax drivers put it back, and the black bar come back even after fresh os instal and recent drivers, i think because the fix also was changing the state and 'render' from 1x to 1.2x in device settings in the piplay, is very similar to the way the 'mode fails' to transition state in the modern piplay. I'm thinking there has been some pushes to the way the device interacts with the software, and a bug has been introduced that somehow not only leads this black line to be there, but for the device to also unreliably transition states, a resultant and atypical symptom I would expect to see, were the state transition differences in the legacy driver states to also either cause or remove the symptoms of the same.
I really hope I am making sense, I a m really determined to get to the bottom of this because I'm sure it's just a bug in the piplay or the driver, and the headset is in really good condition other than this defect, project cars 2 is making me sad, especially that I have an expensive racing simulator I built just for the thing! AAAAAAAAAAAAAAAAAAAAAAAAAAAH
Interestingly, after the view state fail transition in the piplay 2.x version, and turning headset off, then back on, I get a 'blue led state', and a completely grey screen, with NO BLACK LINE.
however, if i was to reboot, and restart the machine and then look into the headset, it would either by GREY(same grey with a black line), or have the PIMAX writing with the black line).
The black line is always in the same place. AND immediately after view state transition failure, then resetting headset, there is a gray screen with no black line, which I believe is telling about the view state fix i find in the legacy driver to both cause, and if done correctly, fix this HMD black line issue.
Hope this makes sense. Yes, also tried flashing to older firmware, and letting it reflash to the latest, which is by the way 265( the version I had when this problem was starting to begin with), though I believe I have seen the problem in earlier firmwares too, apologies, just looked up close, and the gray screen after c hanging view state this time actually has the black line too, but it's significant to me, because i've seen the transition failure cause a gray screen with white pixel in middle, without any black line, and the black line even ghost fades, like there isnt an issue with the screen itself, but, I'm pretty sure this isn't being caused by the cable, at least,
**WHAT IS REALLY SIGNIFICANT?*** I noticed in the older legacy versions if i changed resolution to 1024x768 the black line disappears, or moves substantially. I think this could actually be the crux of the issue, as it turned out async reprojection already ticked in the steam openvr settings!! When transitioning state with the latest version of piplay 2 i notice for a momentary second the black line is not there!!! then the hmd flickers several times in <1 second and black line is back again. Interesting. I'm getting closer to some working theory, or enough for pimax dev or engineer to have an understanding what is happening with software, perhaps?? I also get 'mode switched succesfully' when seeing the grey screen with a black line, when going from video -> pimax and there is nothing at all and headset is led red, even though device reported as connected and said changed state succesfully, but hmd didn't change state succesfully.
On clean boot, after headset being in RED HMD LED state. after failing to switch views. and having light gray background with black line, after reboot, have BLUE HMD LED state, and NO BLACK LINE whatsoever. Then when i click in piplay to VIDEO mode its LED goes to red again and screen goes black. So then i turn off HMD, turn on HMD. Green LED status bright gray screen with black line.
When enabling 1920x1080 mode in piplay the red hmd led status from mode changes go away, but black line still there continuous, and black pimax screen shows with black line thru it (as above), when not 1920x1080 ticked it transition to gray screen without black line or gray screen with black line, which is why this is significant to mention. (so with 1920x1080 mode disabled pimax logo black screen shows but black line always there, without 1920x1080 ticked in piplay settings the pimax black screen doesnt show and only gray screen but there is no black bar sometimes, running steamvr cannot connect to headset without 1920x1080p, because it always show red hmd status i think. Just checking atm. OK getting pimax black screen logo without 1920x1080 setting enabled now, hmmm, bit inconsistent but def the some significant findings here specifically when pimax black screen doesnt show and view mode/state doesnt change properly on hmd, but i do see a gray background with no whiteline, and a little wihte pixel dot in the middle. I just dont know what this means, AAAAAAH
The consistency of the behaviour is very hit and miss, but this explains why recreating the steps to reproduce are so difficult, with the older legacy drivers, which I believe can remove this black bar somehow by the manner in which they operate, specifically 1.2.97, but possibly 1.2.57 as well. I think in older versions before render can be changed without restarting the headset, some bug can be introduced that paints this black bar, that only the older legacy versions can fix (or create) under specific circumstances that retain in the hmd for older legacy, and for newer piplay versions, but may also interefere with mode change states, which occasionally show the black bar removed when those mode states fail and 'fallback' to the gray screen, either with, or w ithout the black, seemingly proving that I am not imagining it or losing my mind I am fairly sure of this anyay its just reproducing it is awkward and hard but the manner in which the black bars disappear during mode changes in all versions of piplay, and older legacy versions which dont change render in the same way, and i believe the render setting under devices in the older legacy versions of piplay can both cause and fix it, that really is the crux of the problem (sorry it is so much text lol)