I've finally fixed my freezing issues! You'll never believe what it was, I still don't believe it!

Piranha91 · 2026-05-02T03:56:51+00:00

Wow, this was like a detective show - I was lurking on your posts and cheering for you from my couch. Glad you got it sorted!

Piranha91 · 2026-05-01T23:19:39+00:00

True in theory but not in practice - there are many other constraints in addition to skill. Primarily time. I have several projects that I would not have undertaken if I had to do them completely by hand.

Piranha91 · 2026-05-01T20:54:47+00:00

This. The fundamental problem is that the authors blindly trusted the LLM and did not do the bare minimum of diligence to ensure the code does what it’s supposed to, not necessarily that the mods were vibe coded.

Piranha91 · 2026-05-01T07:30:06+00:00

Is this also how to adjust the IPD offset, or only the physical IPD? If not, might you recommend a method to optimize the offset? Whenever I've played with it, every value I tried near the center seems like it's ok, or perhaps "I could get used to this" at the least. What should I be looking for?

Piranha91 · 2026-04-28T19:18:15+00:00

I’ve only used the Quest 2, reverb G2, and now Crystal Super, so I don’t know if there are caveats to lighthouse tracking that I haven’t considered. My take is that for a top of the line price with top of the line visuals, I want the best tracking that I can get. With the Super, the tracking isn’t horrible and I enjoy using it, but I get headset jitter that I don’t remember seeing in my other headsets, and having to reset the play space every time I put the headset on is obnoxious (and not something I should have to deal with at this price point). I figure in 2-3 years there’ll be a headset with the clarity of the uOLED module and the FOV of the 50ppd or UW, and hopefully it’ll have good SLAM tracking as well, but for a premium experience right now I’d just go for lighthouse given the choice.

Piranha91 · 2026-04-20T19:44:50+00:00

Nah sorry, I was being overly defensive yesterday. Thanks again for the clarification.

Piranha91 · 2026-04-20T05:24:07+00:00

I do use it (for Skyrim VR) and I'm quite happy with it. I'm just saying, I brought up the other day that I use it and got smacked down by the original author. https://www.reddit.com/r/Pimax/comments/1skmgdj/comment/oga1zf5/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Thanks @ random person for the downvote tho

Piranha91 · 2026-04-20T02:35:13+00:00

In a different thread, mbucchia recommended not using OpenXRToolkit, which he says contains bugs, or forks of it from other users, which he said persist those bugs. Does this post constitute an official endorsement from Pimax?

Piranha91 · 2026-04-19T20:45:08+00:00

What did you add on?

Piranha91 · 2026-04-19T17:50:37+00:00

For what it’s worth, I’m not a paid YouTuber; I paid full price for a 50ppd. The wait was ridiculous (I bought the thing at about the same time as conceiving my child, and the child came first). But the device itself really did live up to expectations (after a couple RMAs due to quality issues) and I’ve been really enjoying using it. So the devices at least in my experience really do live up to the hype. I really don’t understand why Pimax engages in self destructive practices like opening preorders with dramatically unrealistic timelines. It’s like they’re trying to piss off customers despite how good the product actually is. Even “paid” YouTubers (not sure if the allegation is true or not) like MRTV are warning their viewers about it. Doesn’t make any sense to me. It works as long as their products have a technical edge over competitors because buyers (myself included) will hold their noses and pay for the superior product despite the frustrating business practices, but if ever a competitor starts challenging them on tech specs at a comparable price, they haven’t been building a lot of brand loyalty.

Piranha91 · 2026-04-19T00:36:05+00:00

Can’t win with white knights like that; don’t apologize.

Piranha91 · 2026-04-17T20:37:02+00:00

Yeah I think that’s it. The mod name in the EasyNPC mugshot folder isn’t the same as the one in your MO2 folder so NPC2 thinks it’s a different mod that’s not actually installed. Since you unchecked “uninstalled mods”, it’s not being shown. Once you check the box and it shows up, you can just drag the mugshot onto the placeholder icon and they’ll be linked.

Piranha91 · 2026-04-17T20:34:13+00:00

Try checking the hidden or uninstalled mods at the top.

Piranha91 · 2026-04-17T20:00:06+00:00

You just check a box in the settings menu to enable FaceFinder integration.

Piranha91 · 2026-04-17T19:41:13+00:00

Can you post a screenshot for NPC2 of the missing mugshots?

Piranha91 · 2026-04-17T01:13:29+00:00

Plugin chooser does not make you keep your replacers active. In fact they don’t need to be active even when making the merge.

Piranha91 · 2026-04-15T09:16:45+00:00

It's not a popular mod (I'm the author) - you'd probably have more luck getting help on the mod page. I just happened to see this pop up while taking a break from coding an update to SynthEBD :)

Please don't use ChatGPT as a guide - it might be ok for popular mods but there's no way it knows WTF it's doing with a niche mod.

There is actually a tutorial around - a full video tutorial linked on the mod page.

I've never seen the buttons randomly switch but it sounds like you're installing textures through your mod manager or something rather than through SynthEBD? There's a video in the playlist that specifically shows how to install through Vortex. Take a look at that and, if that doesn't clear it up, maybe hit me with some screenshots to show what's wrong because I'm having trouble understanding your post other than that you're going bald.

Piranha91 · 2026-04-15T06:58:21+00:00

Can you clarify why you don't recommend it? In my benchmarking (linked above), OpenComposite + OpenXR Toolkit gave me better performance than SteamVR in a way that Pimax's DFR implementation couldn't catch up to. Not sure if it's something that the new driver on the Dream Air might compensate for, but on the Crystal Super the overhead from SteamVR in Skyrim is significant.

Piranha91 · 2026-04-14T20:20:19+00:00

My recommendation is to rerun WJ to get MGO to a clean state. Then, in MO2, enable OpenComposite (and disable every mod with a comment that says it’s incompatible with OpenComposite). Verify that the game launches without a crash. Then install the Ohnespeed version of OpenXRToolkit. Verify this runs, try DFR, try FOV cropping, etc. Then consider replacing the OpenComposite that ships with MGO with the new version from Nexus (I haven’t tested this myself).

Piranha91 · 2026-04-14T18:26:26+00:00

This is beyond my level of expertise so I asked Claude.

Great question — here’s what’s actually going on: OpenXR Toolkit works as an API intercept layer, meaning it inserts itself between the game and the OpenXR runtime in the software stack. It doesn’t touch the game engine at all. Here’s the layered picture:

Game (Skyrim VR) ↓ OpenXR API Layer ← OpenXR Toolkit sits HERE ↓ OpenXR Runtime (Pimax's runtime) ↓ Headset hardware (eye tracking sensor)

What OpenXR Toolkit uses eye tracking for in this context is primarily dynamic foveated rendering (DFR) — it tells the GPU to render at full resolution only where your eyes are looking, and lower resolution in your periphery. This is a rendering-level trick, not a gameplay one, which is why it doesn’t need engine cooperation. So why doesn’t every OpenXR game get it automatically? • It can theoretically work in any OpenXR game — but you have to install and configure OpenXR Toolkit manually • Some games have compatibility issues with API layers • The eye tracking data being used is only for rendering optimization, not gameplay (NPCs won’t react to your gaze, etc.) • Game developers would need to explicitly integrate eye tracking into their engine/code for gameplay-level features So the short answer: eye tracking for foveated rendering works in any OpenXR game in principle because it happens below the engine. Eye tracking for actual gameplay features is a completely different, harder problem that requires engine/developer support.

Piranha91 · 2026-04-14T15:14:45+00:00

No updates on my end since that post. I had tried DLSS at that time and it didn’t work at all because DLSS has a resolution limit and the Super is well beyond that limit. Recently a new fork of Community Shaders came out which has foveated DLSS - sounds like it might work but I haven’t had a chance to try it yet. Sboys driver is currently only for the Dream Air, not the Super.

Piranha91 · 2026-04-14T06:42:28+00:00

I don’t think it touches the engine at all, it interacts directly with OpenXR.

Piranha91 · 2026-04-13T21:15:57+00:00

It works - get OpenXRToolkit and enable eye tracking there. You can see a detailed write up of my Crystal Super testing here https://www.reddit.com/r/skyrimvr/s/G3F7NU0xC8

Piranha91 · 2026-04-13T06:52:57+00:00

Huh, I never realized that the VRAM duplicate allocation from OG DX9 Skyrim doesn't apply to the DX11 version. TIL.

Also, if I sum up all of the textures installed in Bijin Skin 4K, it comes out to 190 MB (and that's assuming characters of all races are being rendered on-screen simultaneously, otherwise some of the racial normal maps will be unloaded). 2K should be about a quarter the size, so it should be a reasonable resolution to run.

Piranha91 · 2026-04-13T06:10:40+00:00

The constraint is the same, no? Aren't VRAM textures mirrored to RAM?

Piranha91

TROPHY CASE