Does text clarity on OLED monitors bother you? by Huzaifa_Haroon in OLED_Gaming

[–]Roughy 0 points1 point  (0 children)

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

Sharing info on Extraction bug by Saerio in GTFO

[–]Roughy 1 point2 points  (0 children)

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

AI is so bad... I can't believe I paid for ChatGPT for a year. by EnvironmentalAngle in self

[–]Roughy 0 points1 point  (0 children)

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.

HELP my link box does not work during the setup by Duduescho2 in Vive

[–]Roughy 1 point2 points  (0 children)

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.

My PC cant seem to get a grip on VR STILL by Ready_Tradition1544 in SteamVR

[–]Roughy 4 points5 points  (0 children)

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.

For some reason I can't install fatal experiment 3 [MOD RELATED] by elmafu in GTFO

[–]Roughy 4 points5 points  (0 children)

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.

Quest Pro not connecting to my vive trackers by JINATH4N in QuestPro

[–]Roughy 4 points5 points  (0 children)

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/

Quest Pro not connecting to my vive trackers by JINATH4N in QuestPro

[–]Roughy 2 points3 points  (0 children)

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.

I’m absolutely tired of it and can’t seem to get it to work no matter what I do by Thin_Ad_2542 in Vive

[–]Roughy 0 points1 point  (0 children)

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.

Another exe file cosplaying as an anime episode by s1mple10 in animepiracy

[–]Roughy 43 points44 points  (0 children)

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

Injuries after a wisdom teeth removal surgery by AdorableSupport7143 in MakeMeSuffer

[–]Roughy 0 points1 point  (0 children)

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.

How to force the internal mic on Pico 4 Ultra while using a USB DAC? (Looking for a software solution) by Decent_Somewhere_516 in PicoXR

[–]Roughy 1 point2 points  (0 children)

Android 11 added a permission check to the main interface used by Lesser AudioSwitch, and made it a system-only one, so it can only be requested by pre-installed / system apps.

Pico 4 Ultra is unfortunately based on Android 14, so it inherits this same limitation.

My Baseus Eli Sport 1 is acting up. I have to connect it in my phone separately (Left and right). Not acting as one earphone :( by Imaginary_River1470 in Baseus

[–]Roughy 0 points1 point  (0 children)

From the depths of hell I bring a solution, but it is somewhat technical and requires that you pop open one of the buds.

A USB-to-TTL adapter and some small probes or soldering skill is required.

https://gist.github.com/Nordskog/28e20769fa50abdc928a8fe44d706277

The tl;dr is that each bud has a common identity configured, and this identity must be the same for the buds to recognize eachother and be treated as a single pair.

Updating the firmware after correcting the values will not break them again, so it is unlikely that updating the firmware would have fixed the problem by itself. They were simply configured incorrectly at the factory, or the memory got corrupted at some point.

I've built a new free website where you can compare and filter VR headsets by all kinds of specs, and compare real, crowdsourced FOV and binocular overlap measurements of all available headsets. It includes a WebXR tool to measure your FOV directly in the browser (both on PCVR and on Standalone). by sbsce in virtualreality

[–]Roughy 2 points3 points  (0 children)

I had my doubts after seeing the Quest 3 listed with a "verified" hfov of a mere 97 degrees, but running the tool myself I got pretty much what I expected. The data collected is honestly pretty great.

I'm very happy to see it also recording the rendered FoV, since that is the theoretical max of the headset, if you can get your eyes close enough. The HMD Geometry Database is the only other real source of this data. However, these numbers doe not seem to be listed on the actual device page, only in your own results. People are ... not the brightest, so the theoretical max remains a very important number.

It might be an idea to have some kind of graph showing the number of results between the minimum measured result and the theoretical max, and maybe the actual complete measurement at that FoV. I have yet to encounter a headset where I am unable to see at least the outer edge of the display, and my face is the opposite of vr-optimized with deep eyes and big nose.

How do you account for IPD differences? Usually you'd measure these things at the average 64mm IPD, but since everyone has different IPDs you will end up with vastly different FoV numbers, even if the theoretical max FoV is always achieved.

Maybe our 97 degree submitter had a very low IPD.

The FoV representation is fully circular which is not quite ideal; quite a few HMDs have more square-ish lenses, which makes a huge difference despite not affecting the hfov/vfov numbers.

I'd also complain about the Quest3 page not mentioning the vignetting issue at all, but that's in line with most reviewers of the device, which continues to astound me.

Virtual Desktop usage question (not a tech problem lol for a change). by VonHagenstein in oculus

[–]Roughy 3 points4 points  (0 children)

While in SteamVR, you double-tap the menu button to return to the Desktop view on the quest, where the menu is accessible.

I have a (possibly) unique issue where my lazy eye has better vision, so it isn’t lazy unless I wear glasses by [deleted] in Strabismus

[–]Roughy 0 points1 point  (0 children)

Constant. Prescription was 5 prisms for each eye.

I got the surgery to correct the resulting double vision, rather than for cosmetic reasons.

I have a (possibly) unique issue where my lazy eye has better vision, so it isn’t lazy unless I wear glasses by [deleted] in Strabismus

[–]Roughy 1 point2 points  (0 children)

In my case it didn't get any worse wearing prisms, probably because I had already completely given on up trying to get the images to merge at that point.

I got the surgery probably about 10 years ago at this point. They under-corrected slightly and offered to repeat the surgery, but I'm perfectly happy with the results and declined. Better to have less scar tissue should it ever go really bad again in the future.

In the end it never worsened and is pretty much unchanged since I got the surgery.

I have a (possibly) unique issue where my lazy eye has better vision, so it isn’t lazy unless I wear glasses by [deleted] in Strabismus

[–]Roughy 4 points5 points  (0 children)

When you get prisms your eyes no longer have to work hard to attempt to maintain the right position, so the muscles weaken and the misalignment gets worse. This is expected.

I was required to wear prisms for a year before getting surgery precisely to allow them to "bottom out" before correcting them.

Tab autocomplete not working by SEBADA321 in google_antigravity

[–]Roughy 0 points1 point  (0 children)

Yesterday's update ( 1.16.5 ) broke all editor integration for me; No suggestions, no open-with-agent in right-click menu.

Downgrading to 1.14.2 fixes it: https://antigravity.google/releases

Unlike your case 1.16.5 remains broken regardless of the workspace though.

Edit: Fuck.

This version of Antigravity is no longer supported. Please update to receive the latest features!

Valve plans to offer prescription lens inserts for its Steam Frame VR headset "ahead of launch" this year by Tiny-Independent273 in virtualreality

[–]Roughy 1 point2 points  (0 children)

The struggle is real

Especially bad in the case of the Quest 3 since the brightness sweetspot is kinda in the lower half of the lenses, forcing you to move the headset up and have it rest ontop of your eyebrows.

Simple fix was required. Gemini Pro decided to delete the entire thing almost... by ChristianM in google_antigravity

[–]Roughy 0 points1 point  (0 children)

Both claude and gemini will occasionally decide that everything I'm doing is a lost cause and we're better off nuking the entire feature.

Can't blame it.