PTC v57 Release Thread

I have added a "PTC v57" Tag to the longstanding and still very active "PTC v56 - Flashing white/colored pixel artifact problem (introduced around v53)" thread, so that the conversation of the issue can still continue without having to start all over again.

This is important as the thread is linked to in about a half dozen outside forums (virtual desktop, reddit etc) who use it to keep updated about the progress on this issue and potential fixes -  the thread is still used daily with about 8000 current views.

I have checked and this thread does now appear in the search link provided by Ryanality above. I hope the thread issue can continue in this manner.

Ryanality  Thanks mate, I look forward to trying out PTC v57 soon on both my Q2 and QPro (main one I use now).  While I'm not a big fan of this new Blog format I do see your point about posting issues in the Get Help section.  

Just an idea but I think it may be better for you to create a separate PTC v57 Mega thread in the Get Help section to collect and discuss any issues.  I would suggest that users only respond to the Announcements Blog thread when noting PTC updates, including version numbers, so we can keep track of rollouts.  Also, maybe a brief report on how well the PTC is working.

Once v57 goes final I think you should close postings to both PTC v57 threads.  Then the same, open a v57 Final Blog Thread in Announcements (as per normal) and also open a v57 Final Mega thread in Get Help section for general discussions.  I think that this will provide users a more direct way to discuss these updates while also keeping the more user friendly non-blog format.

Anyway, I hope you find some of my suggestions useful and will consider trying some or all of these out.  Thanks mate and cheers.

Edit; Dave200S  I like your idea of tagging ongoing issues that carry on from previous versions.  Thanks mate.

What can we expect in the V57 PTC update?

EveryDay10  When Ryan says that a PTC is rolling out soon (as opposed to rolling out now) I normally see it about 3-6 days later.  I always check this thread to see if any have got it yet.  I usually find that once some get PTC it gets rolled out to others on PTC pretty quickly.  Anyway, when I get ptcv57 I'll post that here.  Cheers mate.

• TomCgcmfc Got it, thanks for telling me 👍 

This is a joke, we have the same problems since v53 where you practically ruined everyones Quest 2 devices for them to ultimately upgrade to the newer device releasing next month.

All the while playing "passive aggressive" with each coming update by completely ignoring all open issue and requesting people to open new threads over the same problem on every new release.

Awesome way to minimize the actual damage you are doing to the FW\Device since this way, you will never have to actually deal with open bugs, as you completely scrub the list on each new update.

NONE! of the issues reported since v53 were fixed. Absolutely 0! yet, you keep pushing more updates to already broken build.

I still want to go back to v52. and the fact that we are already in v57 only comes to show how rushed each update is. as if there is a commitment to push updates every 3-4 weeks, and it doesnt matter if the QA is garbage.

All the while playing "passive aggressive" with each coming update by completely ignoring all open issue and requesting people to open new threads over the same problem on every new release.

pikpukpak  Seems to me you are the one being a little passively aggressive mate, lol!  I've been on PTC with both my Q2 and QPro since about v51 and haven't had any major problems.  The only major issue I've had is with my Q2 battery management (not wanting to charge to 100% or ever get a green full charge light).  This still might just be caused by the 2.5yo battery age and nothing using an external battery doesn't solve.  Other minor issues (I always do bug reports on these) seem to slowly get resolved, for me anyway.

If you are an experienced user than you know by now that you cannot simply rollback to versions older than the current non-ptc.  Continuing to complain about this isn't very useful imho.

Really up to you whether or not you want to participate in the Quest PTC program.  In your case I think it might be a good idea for you to avoid this and just stick to non-ptc.  Again, your choice.

*Bump*

I too have hade the white specs while using airlink sinc v53. A few weeks back, I did however notice they went away while casting at the same time to a chromecast. I stop casting, spots come back, cast again to chromecast, no spots. This is repeatable for me as of right now. Can anyone else verify the aswell, if so, we may be able to point them in the right direction to the solution.

Is there any chance at all that developers will bring back the "Lying Down Mode" that was present in v53 and later removed, within this decade? It's virtually impossible to enjoy 3D VR YouTube content while reclining on a couch, especially when your head is resting on a pillow. This is due to the completely baffling absence of an option to adjust / shift the image center along the vertical axis. It's frustrating that there's no way to comfortably watch VR content while lying down. When will this bug be fixed??!

OK, I got v57ptc earlier today on my Quest Pro and oculus desktop app public beta.  I haven't updated my Q2 yet but I'll do this later.  Anyway, the version #'s are: 

Headset;  57.0.0.191.669

PC app;   57.0.0.192.153

The update included firmware and controller updates.

First BIG news is in the Quest home we now have Legs!  This looks pretty cool and when you shift around a bit they kinda move with you.  I'm not sure they get tracked with the QPro using eye, face, and hand tracking, but I'll try this later.  Pretty cool feature though imho.  The new menu's are nice and you can directly use hand tracking to position and use them.  So, no more direct touch in experimental.  Probably not something I'm going to use much because I mainly am using PCVR wirelessly with Air Link.  Shifting back and forth from standalone to the Rift home void/dashboard menu seems a little more solid. 

I tried a few standalone Quest store, Rift store, Steam store games/sims and everything seems to work fine.  The only problems I found so far is my hands do not show up with the Rift store Toybox app and this makes it impossible to play.  Fortunately it's not something I play very often and just use it to test controller tracking.  I have filed a bug report for that.

Anyway, all I got so far.  Once I get a chance to update my Q2 I'll post those results.  Overall, seems like a nice update.

Edit; Tried with my Q2 and same good results, except the hands not showing up with Toybox.  Also, the washed out colors in Natures Trek Rift store version seems ok now on both headsets.