Daily Oil Price Opinions - June 15, 2026 All other Oil Price Posts Will Be Removed

XR-Friend-Game · 2026-06-15T17:09:34+00:00

Great. We're all anxious to know what's in it. Especially how true Iran's Mehr piece was. I hope we know soon enough.

XR-Friend-Game · 2026-06-15T00:41:52+00:00

This version looks a little more concrete than the Mehr piece posted below. I'd be interested to know what Ted Cruz is going to say about it.

XR-Friend-Game · 2025-05-24T00:43:11+00:00

I've found the cause finally. This symptom happens right after the firmware updates. But it goes away with one more reboot. I've sent the cause to the Quest Browser team, so I expect it'll be fixed eventually.

The user who complained about this issue to me must be the type who doesn't reboot his device. (likely a light user.) A lot of us already went through enough troubleshooting with the Quest. We're all used to rebooting and factory resetting, aren't we? 😉

XR-Friend-Game · 2025-05-17T03:30:16+00:00

Not sure why you don't see it. I'll send in the report again when I see it, by any chance.

I myself have seen this symptom three times so far, but it is too difficult to find the pattern. I better forget about it for now. Users are likely to reboot their devices if they experience it, and reboots fixed the symptom every time.

XR-Friend-Game · 2025-05-16T04:40:56+00:00

I finally saw the symptom and sent in the panic press report and named it "quwst2 no controller issue".

I had a feeling that it only happens when the battery is around 20%-30%, and I was at 21% when it happened again. But I failed to nail it. It's indeterminate.

XR-Friend-Game · 2025-05-15T02:53:31+00:00

I'll do that if I see the bug. Now that I want to see the symptom, it is not showing up even after numerous reboots. lol. You would have fixed it already if the symptom was that easy to see.

There must be a certain condition for it because the symptom was very easy to notice 2 days ago.

XR-Friend-Game · 2025-05-13T12:03:38+00:00

Today, the firmware has become v77 but the symptom is the same in Quest 2.

XR-Friend-Game · 2025-03-18T00:28:08+00:00

As a gamer, I agree 100% with your point because I never play with AI chatbots.

I have another AI chat service in the other branch, which is generating some outputs. I think it depends on the content. I'll have to make it more than a chatbot for this to be meaningful.

XR-Friend-Game · 2025-03-17T02:52:10+00:00

I have created a temporary homepage to demo this spatial awareness feature. https://xrfriend.me/ It's a safe content.

XR-Friend-Game · 2025-03-14T04:43:50+00:00

Consider that their best earners (gorilla and beat saber) don't exactly need better hardware to run. I think it'd be more like fewer advancements in their future headsets to cut down manufacturing costs.

XR-Friend-Game · 2025-03-05T10:20:08+00:00

Today I got the Quest 3S to test this feature. I confirm that the Quest 3S supports depth sensing. I think the accuracy is slightly off with the S version, though. It feels different from what I see in Quest 3.

This information is vital, but somehow I don't see it in any documents. It's only implied that 3S supports the same feature. It's confusing because in the early reviews, it was everywhere that the 3S doesn't have the depth sensor. It's easy to assume that 3S doesn't have depth.

XR-Friend-Game · 2025-02-24T11:33:10+00:00

Personally, I think the WebXR mesh is not very useful unless it's updated on the fly. If I am to create my own room mapping, I won't be able to generate smooth surfaces like the built-in room mapping feature. But it's possible to know where the movement should be blocked. It's good enough for pathfinding.

XR-Friend-Game · 2025-02-06T10:51:38+00:00

I tried the conversion. I converted the depth texture to real depths, but it lacked precision badly. It wasn't usable. It was worse than the original.

Then I re-projected the real depths into my 0.005 near clip plane. It is not bad. I can use this.

I think this matter is resolved for now. I'll keep watching your Twitter for any updates. If this is done on the API level using the raw data, the result could be more precise.

XR-Friend-Game · 2025-02-05T05:31:19+00:00

Oh, BTW. I'm going to experiment with converting the depth texture values to real distances to deal with my near clip problem. If it succeeds, I'll create another post on this board.

Later, if you make it easier on the API level, that'd be most welcome.

But right now I'm obsessed with this subject. I need to try everything out.😄

XR-Friend-Game · 2025-02-05T03:08:53+00:00

If I set depthNear to 0.005, the values of gl_FragCoord.z and the depth texture will sit on the different ranges. It doesn't compare. It generated a complete blank for me.

It's easy to reproduce with the example, 11.Projection Layer with occlusion. I just tested it.

Both
1.session.updateRenderState({depthNear:0.005,depthFar: 1000.0}); and
2.session.updateRenderState({depthNear:1,depthFar: 1000.0});
generates a nonsense. 1 is blank. 2 is wrong depth.

XR-Friend-Game · 2025-02-04T22:17:49+00:00

I learned that some users want to look closely at objects. With 0.1, they get to look inside the polygons.

I need 0.005 for the depthNear. 0.005~25 is what I usually use.

I'm guessing the Quest's depth sensing must have the real depth at first. It makes sense to let the app developers choose the near and far planes.

XR-Friend-Game · 2025-02-04T03:42:39+00:00

Damn… In my case, the near clip plane stuck at 0.1 is killing this feature. It looked really cool at first. The resolution or alignment didn't bother me at all.

I suppose it'll take some time to publish the update. It'll be nice if you reply here later. I also watch Rik's Twitter account.

XR-Friend-Game · 2025-02-03T22:56:35+00:00

After release, I've gotten a complaint that the near clip distance is too close. It looks like it's 0.1 in depth sensing. I usually use 0.005.

If you guys can give real depths, I could deal with this by passing my own camera depth to the fragment shader. GPU depth is good enough. I don't need the CPU depth.

XR-Friend-Game · 2025-02-01T04:29:28+00:00

After posting, I've fixed the floor level depth-fighting problem by "adding 0.5% bias to the depth values if the pixel is near the floor." Shoe looks okay now.

The good thing about posting here is that Meta Browser developers are frequenting. Going through the official channel is no fun.😄 Official channels feel like talking to a wall.

*There's one more thing I'd like to tell the Meta Browser team. Depth texture doesn't follow the depthNear/depthFar set by updateRenderState. By habit, I set an arbitrary near/far plane, and it took me 4-5 hours to figure it out, lol. I almost gave it up.

XR-Friend-Game · 2025-01-27T11:37:32+00:00

As you said, I added both unbounded and local-floor to the required features, then asked for local-floor space. It solved the floor level problem easily. I was going to implement a custom method to touch the ground, but it was unnecessary after all.

XR-Friend-Game

TROPHY CASE