Yeah, the error seems totally busted. Or it was a broad disclaimer posing as an error.
Also, I’m sure the overlay works fine for you. But to test what I was explaining properly, you need to overload your vram, and then open it.
Yeah, the error seems totally busted. Or it was a broad disclaimer posing as an error.
Also, I’m sure the overlay works fine for you. But to test what I was explaining properly, you need to overload your vram, and then open it.
I don’t think it was bullshit. When Alyx came out, SteamVR still had substantial issues managing VRAM at times. As a VRChat player, it was very obvious.
This warning may have been partially related to the SteamVR overlay failing when VRAM is full, when it failed the overlay wouldn’t work. And then there were massive perf issues when returning to the app. All centered around managing VRAM.
To this day the overlay will fail to come up if VRAM is maxed out or over burdened. But it seems to recover better. So this issue has improved a lot since Alyx came out. At least in my experience.
Maybe I’m way off. But to sum things up, I don’t think it was bullshit. It was just very cautious and upfront about possible issues.
It is strange that you are still seeing the message on your new config tho. Might just be a bug. — Maybe it’s reading your integrated graphics VRAM in error? Are you using Link with a Quest? Maybe that config causes it to read things wrong?
Sweet. Thanks for the details!
VRChat is still slowly growing in the background.
The metaverse that was the hype you despise isn’t the metaverse people in VRChat want. Mark really destroyed the term.
The releases/changelog have been weird for a little while now on the PWA.
I feared mine would get broken too, but so far I’m ok. I’m on iOS.
Anyone have insight into why the changelog has been weird? And there was a set of updates that seemed to do nothing recently?
Edit: going back and viewing the recent releases in GitHub they don’t look “blank” or weird or duplicate like they were… maybe they were all hand fixed? - I stand by the feeling that recently things have been odd. I had the user vote tracking appear in the PWA multiple updates before it showed up in the changelog.
I would not have guessed that reply guys replying to really popular accounts would ever check if their reply is a duplicate.
I didn’t catch that this is why Alec stopped posting there. I assumed he was just being sensitive to being a public figure in general.
When you make a channel that is filled with “well actually” and “turns out.” You should expect your audience is into doing the same.
And when you don’t have an algorithm filtering these for you… well, then you get the reality of other people’s interactions. Twitter just optionally hides this reality from big accounts. (I’m talking about what they use to label “low quality replies” or something similar.)
The federation issues of replies/boosts/hearts/etc are still a big bummer, though.
They want an algorithm.
As much as people mock it, or know it’s the source of why social media optimizes for outrage and other unhealthy behaviors, the algorithm is what they are missing on Mastodon.
As someone who always used third party Twitter apps, and never directly saw the algorithm in my timeline, mastodon feels like Twitter always did.
I hope they get placed around town in Madison again. But I suspect that’s not going to be part of the deal.
https://lemmy.sdf.org/c/unix_surrealism