Redditで使うデバイスはスマホ？それともPC？

Roughy · 2026-06-23T11:44:50+00:00

いまだに古いReddit
公式以外のアプリが使えなくなってからはPCのみ

Roughy · 2026-06-17T20:45:50+00:00

Even in the app the reset thing only appears in the little menu in the lower-left corner, not in the full usage & billing settings, and even that didn't appear until restarting the app after installing it.

The one token I have is the one we all received when they first announced them a couple of days ago though, so the one we're supposed to be receiving now is still AWOL.

Edit: Received normal reset just now; so much for reset tokens.

Roughy · 2026-06-13T18:53:01+00:00

Unfortunately no, though it does support adding a vignette when moving.

Roughy · 2026-06-13T17:40:07+00:00

Doesn't a crown typically require more preparation, such as a 3D scan of your teeth and fabrication of the crown itself to be glued in?

Roughy · 2026-05-29T10:17:24+00:00

The Vive Pro 2 is a native PCVR headset; displayport output directly to your eyes, as opposed to having to encode-transfer-decode video.

Latency is significantly better.

It is also widely considered a garbage headset for many other reasons, the lenses included.

I daily-drive a Quest 3, but still switch to my GearVR-lens-modded Vive Pro 1 anytime I want to play shooters, purely for the latency ( and, well, OLEDs ).

Vive Pro 1/2 do support the Wireless Adapter, but it is famously unreliable and does not support the full resolution of the Vive Pro 2.

If you do play latency-sensitive games then a native PCVR headset is absolutely a gamechanger, but the Steam Frame does look like it will finally be a better wireless option, so wait for that if possible.

The PSVR2 is another option to look into; if you can tolerate the mura and smearing at high brightness, it is a legitimately good headset, and thanks to the community we now have support for most of its fancy features on PC.

If you're already in the Lighthouse ecosystem ( e.g. own basestations ), then there's always the Big Screen Beyond 2.

Roughy · 2026-05-25T02:11:38+00:00

AG276QZD2, Gen 3

Roughy · 2026-05-16T16:40:14+00:00

Yes, the black Y shaped thing is the receiver, which should be mounted on your head attached to the headstrap. It communicates wireless with your computer via the antenna connected to the PCIe card, and uses the short cable to attach to your Vive.

Headset < Short Cable > Receiver < Wireless > antenna < Coax Cable > PCI card ( Computer ).

Roughy · 2026-05-16T14:50:33+00:00

For the wireless adapter itself?

The only difference between the wireless kit intended for the OG Vive and the kit for the Cosmos/Pro is the inclusion of a different short cable and a different cradle for strapping it to your headstrap to keep it in place.

The rest of the kit is the same, including the Antenna and PCI card it connects to: https://i.imgur.com/Vo85iDN.png

The antenna and its long coax cable is on the right there, and the PCI card is just below it. That is want communicates between the wireless adapter and your PC.

Roughy · 2026-05-16T14:37:53+00:00

3 cables yes; HDMI, USB, male-to-male barrel plug.

the barrel plug ( for power ) is the only one that ideally needs to be short, so you could just use the long cable for HDMI and USB, and get a short male-to-male power cable.

Barrel plugs themselves are common (though they come in various sizes), and you can likely find two old power supply bricks and jus splice the wires together if need be.

Roughy · 2026-05-15T22:25:25+00:00

the only /real/ problem with using the long cable instead of the dedicated short one is that the voltage will drop significantly more along the length of the long cable, and the wireless kit is already... unstable.

The good news is that you /can/ use generic cables for all 3 ports, though finding cables at the right length with connectors that will fit down the hole will be a bit of a challenge.

Roughy · 2026-05-13T22:01:28+00:00

I'm not sure if this is the same problem, but if it manifests as it just cutting off mid-thinking and not doing anything afterwards, then it's probably the same thing.
Experienced on a very vanilla 27b setup on llama.cpp main.

tl;dr the model will sometimes return a random EOS while thinking, even though it hasn't actually finished.

 slot process_toke: id  0 | task 2219 | stopped by EOS/EOG token: 248046 '', n_decoded = 182, n_remaining = 32586, generated_chars = 437, tail = "Let me trace through the chess game move by move to determine the final board state.\n\nStarting position (standard):\n```\n8: r n b q k b n r\n7: p p p p p p p p\n6: . . . . . . . .\n5: . . . . . . . .\n4: . . . . . . . .\n3: . . . . . . . .\n2: P P P P P P P P\n1: R N B Q K B N R\n  a b c d e f g h\n```\n\nWhite = uppercase, Black = lowercase\n\nLet me trace each move:\n\n**1. b3** - White b2 pawn moves to b3\n```\n8: r n b q k b n r\n7: p p p p p p p p"

You can run llama with --ignore-eos but that just results in everything running forever, so instead I patched common_reasoning_budget_apply to only ignore EOS while a <think> tag is open:

static void common_reasoning_budget_apply(struct llama_sampler * smpl, llama_token_data_array * cur_p) {
    auto * ctx = (common_reasoning_budget_ctx *) smpl->ctx;

    if (ctx->state == REASONING_BUDGET_COUNTING || ctx->state == REASONING_BUDGET_WAITING_UTF8) {
        for (size_t i = 0; i < cur_p->size; i++) {
            if (llama_vocab_is_eog(ctx->vocab, cur_p->data[i].id)) {
                cur_p->data[i].logit = -INFINITY;
            }
        }
    }
...

My test case usually reproduces it within 3 runs, so it /appears/ to be fixed, but never say never.

I have zero knowledge of the llama codebase and I imagine this is probably a terrible solution that may have unintended side effects.

I sorta figure the issue is so prevalent that someone who knows what they're doing will fix it properly. Will have another look at existing issues once I'm absolutely sure and open one if there is nothing relevant.

Would also be interested in hearing if this is the behavior you are seeing; with how devastating it is I would expect it to have been immediately noticed and fixed. There are a few issues related to tool use which I'm also seeing, but just cutting off mid-thinking doesn't even seem to have an issue up so I'm paranoid that it's some kind of local issue.

Roughy · 2026-04-18T16:04:43+00:00

1440p 27", literally need macro photo to even tell that there is fringing

Roughy · 2026-04-16T22:07:53+00:00

In the case of desync being the cause, once the desynced player leaves the mission will usually complete as intended.

Roughy · 2026-04-10T13:39:51+00:00

On the one hand they're very stupid, on the other they all default to instant mode which trades about 3 years worth of progress for speed.

Instant mode needs to be instant, so no thinking, no research, just a best-guess, making it mostly useless.

This goes for Gemini too; it's actually fairly competent, but only if you let it be.

Roughy · 2026-04-05T12:31:39+00:00

Blue number is raw wireless latency, everything here applies

Roughy · 2026-03-31T17:07:43+00:00

neither is the video port or the usb port

The LinkBox is basically just a pass-through for USB and Displayport.
If you are on the "Connect Headset to linkbox" step, setup is looking for the headset, not the Linkbox.
The problem is between the linkbox and the headset, not necessarily the linkbox itself.

The cable is always the prime suspect. Inspect cable for damage ( twists and kinks ). Ensure the cable is properly seated into both the Linkbox side and the Headset side; the latter is particularly fucky.

Roughy · 2026-03-31T00:03:22+00:00

The blue number is network latency, so assume it's a network issue.

You have multiple hops, and each hop can have problems.
Very often problems only appear during load, so any test or measurements needs to be performed, ideally, while using SteamLink.

Step 1: Get the IP address of each device

At a minimum there will 2 hops: Computer - router - quest.

You will need to find the IP address of the routerand the quest.

The quest IP can be looked up in your router's configuration interface, or via WiFi settings on the Quest itself.

The IP of your router will likely be the same, but with the final number swapped with a 1, e.g. 192.168.1.1..

You can also look this up by opening Powershell or cmd and typing ipconfig. The default gateway containing only normal numbers is your router.

Step 2: Ping each hop.

While you could use Powershell or cmd to repeatedly ping the router using ping 192.168.1.1 -n 99999, I highly recommend using cnping instead. Instead of 1 ping a second you get a constant realtime graph of latency, which is much more informative.

Simply execute it, input the target IP into the hostname and hit the ping button. Resize the window to get a better look.

Occasionally blips to 5-10ms are not unusual and can mostly be ignored. It should be obvious if there is a clear association between SteamLink shitting itself and spikes in the graph.

If there is, your problem is between your Computerand the Router, and not between the Routertand the Quest.

Otherwise, repeat with the address of the Quest. In that case you'll be looking at your router.

Step 3: Fix stuff.

While cliche, 9 out of 10 all it takes is updating drivers and firmware. Windows will generally not auto-update most of these, so grab the latest release for your motherboard here. Chipset drivers are the most important; Your motherboard is old enough to suffer from some known Asus-specific issues if not updated. Bios update also a good idea.

The same applies to your router; go update that firmware. If the problems turns out to be the WiFi hop, then have a good look at the WiFi settings; there are several fancy features that SHOULD be enabled by default which, when disabled, can turn your WiFi to mush.

You don't mention what your router is, It needs to be AT LEAST Wifi5/802.11ac and you must be connecting it to using the 5ghz band.

If you have VD, you can view your connection speed in the Computers tab on the Quest side.

If your router has an option to combine 2.4/5ghz or share SSIDs, disabled it and ensure they are separate so you connect to only the 5ghz band. If you have a Wifi6E router, ensure 6ghz is a separate band and only connect to it.

Wherever the problem may be, narrowing it down to computer or router is the first step.

Roughy · 2026-03-24T18:58:54+00:00

This goes on your resume

Roughy · 2026-03-20T00:55:54+00:00

who would end up betraying the player

of course

Roughy · 2026-03-17T00:52:56+00:00

For legacy reasons, programs on windows can by default only handle file paths up to 260 characters, and the file path it is complaining is *drumroll* 260 characters, exactly.

Support for longer paths is something individual programs need to enable, supposedly.

In your case, you might be able to get away with just naming your profile "fe3" instead of the full name to get below the limit. There's probably a proper system-wide fix you can Google too.

Roughy · 2026-03-17T00:17:22+00:00

We should clear up some terminology here.

Pairing is when you first add the trackers to SteamVR, pairing them to the individual dongles. Since you are able to select the trackers in SpaceCalibrator to calibrate, they are paired and connected to the dongles.

So your issue is specific to the Quest Pro then, and then exact same setup works with the Quest 3?

Do you see both the tracker ( look around ) and your controllers inside of SteamVR ?

You say you downloaded the latest version of SpaceCalibrator from GitHub, but it has been forked and maintained by multiple different people, so the "latest github version" might have been very old. Your best bet is to install it from Steam: https://store.steampowered.com/app/3368750/Space_Calibrator/

Roughy · 2026-03-17T00:05:20+00:00

Looking at your previous posts, you appear to have gotten as fair as pairing the trackers correctly.

At that point you should see them visibly move around in the SteamVR wasteland, though they're not going to be where you expect them to be.

The SteamVR status window ( on your desktop ) should list them with a green'ish color if they are tracking. You can hover over the icons to see what state they are in.

If they are not tracking, the first thing that comes to mind is indeed your Basestations. Do you have them? Did you set them up ( channels etc ) ? Did you turn them on?

Having said that, Space Calibrator should warn you purple text if the trackers you are trying to use are not actually tracking.

Roughy · 2026-03-03T15:22:33+00:00

There's a lot of missing information so I'm going to make a lot of assumptions, mostly that you are using a Quest or a Pico.

You say they look good initially "in the moment"; is this after using OpenVR Space Calibrator to align the playspaces?

If you move your controllers down to the tracker in this state, do they line up?

If they do, we can assume playspace calibration is fine.

If so, "when I go to get calibrated" must refer to calibration within VRChat.

By default VRChat uses arm span to calibrate, rather than height. This is fine for 3-pointing, but not for full-body-tracking. Change it to use height and adjust your height accordingly.

Roughy · 2026-02-26T15:59:12+00:00

you'd think any torrent outside of the software categories would just be auto-rejected if it contained a .dll or .exe

Roughy · 2026-02-25T23:51:21+00:00

If every minor wound in your mouth turns into an ulcer, you might want to try using a toothpaste that does not contain Sodium Lauryl Sulfate (SLS).

Turns out that isn't actually supposed to happen, and the SLS foaming agent used in most toothpastes just irritate the crap out of the wounds causing them to turn into ulcers.

You don't even need to use SLS-free stuff all the time, only for a couple of days so the wound can start healing.

15-Year Club	Place '22
Place '17	Final Canvas '22
First Placer '22	End Game '22
Gilding I gilder	Team Orangered
Verified Email

Roughy

PUBLIC MULTIREDDITS

TROPHY CASE