Meta shipped the Quest v77 replace figuring out it had main bugs, the corporate’s CTO has acknowledged, regardless of his pledge to enhance high quality management.
Final month, Meta CTO Andrew Bosworth mentioned the corporate was “taking significantly” developer complaints of OS efficiency regressions, undocumented misguided adjustments, and bugs. He mentioned Meta was “spending time on” addressing it, and “doing the work” to resolve it.
“We respect the suggestions as at all times, from builders, [and we] take it significantly. It is our duty, these are our errors, and we’re gonna repair them”, Bosworth mentioned on the time.
Meta CTO Responds To Quest Efficiency Regression Points
Meta CTO Andrew Bosworth has responded to developer issues over Quest’s Horizon OS efficiency regression and the puzzling Battery Saver change.
However round three weeks in the past Meta began rolling out v77, and builders have encountered much more bugs on this new launch. To be clear, we’re not referring to bugs within the new Navigator system interface. These bugs are on the core of the OS expertise.
In a thread on X, Digital Desktop’s developer Man Godin publicly decried the choice to roll out v77. He described how points he had reported within the Public Check Channel (PTC) construct like audio crackling, audio slicing out when switching to passthrough, VP8 video decoding not working, and MediaCodec had been nonetheless current within the “steady” construct.
“Good job ignoring all of the reviews throughout PTC and pushing your replace anyway”, Godin complained. A number of different builders inform UploadVR they’re experiencing comparable points.
In an ask-me-anything (AMA) session on his Instagram web page, Bosworth was requested why folks on “the chicken app”, referring to Twitter (now X), had been “mad at” him.
Bosworth responded that it was “for good motive, I am unhappy to say”.
“Our high quality management hasn’t been the place we’d like it to be”, he acknowledged, as he alluded to unspecified causes for having to push an replace with bugs to tens of millions of headsets:
We really noticed these points in PTC. For causes I am unable to get into, we needed to roll in any case.
Folks say “how might you do it!?” Properly, these bugs do not have an effect on an enormous variety of folks. They do have an effect on devs, who I care about so much, and so they do have an effect on a particular set of individuals, who I care about so much.
We’re engaged on the fixes. A few of them require firmware updates from Qualcomm, and so there is a course of that we’re going by there.
We’re working with urgency on this. We’re not glad about it. There is a bunch of causes we needed to proceed in any case, and it is a measured name with some advantages and a few prices. However we should not even be ready to make that decision, as a result of we must always have significantly better high quality management sooner.
It is a course of. We’re engaged on it. My dedication to that hasn’t pale in any respect.
