Driving the Original Oculus Quest from an ASUS VivoBook S15 Ultrabook with an eGPU (RTX 3060 Ti)

February 17, 2021September 5, 2026

ASUS lent me an ASUS VivoBook S15 — a compact laptop built around the concept of “Move forward, your way."

This configuration runs an 11th-gen Intel Core CPU and comes with a Thunderbolt 4 port. Can you connect an eGPU enclosure over that Thunderbolt 4 port and actually enjoy the original Oculus Quest? Let’s find out.

The Test Setup: ASUS VivoBook S15 S533EA (S533EA-BQ032TS)

Here’s the spec sheet for the unit I borrowed. This is the configuration I’m testing throughout this article.

Model	ASUS VivoBook S15 S533EA S533EA-BQ032TS
CPU	Core i7-1165G7 4 cores / 8 threads, 2.8GHz (Turbo Boost 4.7GHz)
GPU	Integrated GPU (Iris Xe Graphics)
Memory	16GB
SSD	1024GB
HDD	None
Power adapter	65W
OS	Windows 10 Home 64-bit

What I Used: Razer Core X

Item	Razer Core X
Manufacturer	Razer
Size (H x W x D) (mm)	230x168x374
Internal dimensions (mm)	160x57x330
Built-in power supply	650W

This eGPU enclosure has a fairly beefy 650W built-in power supply. I’m testing it here with an RTX 3060 Ti installed.

The Razer Core X doesn’t come with a Thunderbolt cable, so I used a separate one for this test.

GIGABYTE GV-N306TGAMING OC-8GD

This is a GIGABYTE-made RTX 3060 Ti — one of the more modest, lower-mid-tier models in GIGABYTE’s lineup.

Getting the Oculus Quest Running

Now let’s connect the Oculus Quest and see how much performance this setup delivers. As a benchmark, I’ll use the frame rate the PC is able to render.

In the Oculus app’s graphics settings, I changed the rendering resolution to its minimum value of “0.8x," its default of “1.0x," and its maximum of “1.3x," and recorded the frame rate at each setting.

Connecting the Oculus Quest: The Cabling

The ASUS VivoBook S15 has a single Thunderbolt 4 port on its left side.

This is where I connect the eGPU enclosure. That leaves the USB Type-C port occupied, so connecting the Oculus Quest means falling back on a USB Type-A port instead. On the ASUS VivoBook S15, the left-side USB port supports USB 3.2, while the right-side one is USB 2.0 — ideally you’d want to use the left one.

You’ll need either a USB Type-A-to-Type-C cable, or a similar Type-A-to-Type-C adapter.

The ASUS VivoBook S15 has three USB Type-A ports in total, and all of them supply only around 2.5W of power.

While Oculus Link is running, the Oculus Quest’s battery gradually drains. If you’re planning a long session, it’s worth starting from a full charge.

As an Amazon Associate we earn from qualifying purchases.

Frame Rate in Beat Saber

As a classic example of a lightweight VR app, I’m testing Beat Saber.

The frame rate comes in above 200fps — there’s plenty of headroom to spare.

Frame Rate in Half-Life: Alyx

As an app with much richer visuals, I’m running Half-Life: Alyx.

Low Quality Setting

At the low quality setting, no frame drops occur. That said, if you push the rendering resolution up to 1.3x, textures can occasionally fail to load in time, leaving flat, undetailed surfaces. In practice, a resolution around 1.0x is the safer bet.

Maximum Quality Setting

The pattern holds at the maximum quality setting too. There are no frame drops, but at 1.3x resolution textures can again fail to keep up.

Frame Rate in SteamVR Home

This is the home screen you land on when you launch SteamVR. Since you’ll see it every time you start SteamVR, if it doesn’t run comfortably here, that friction adds up fast.

The frame rate holds above 90fps here — comfortable.

Frame Rate in Asgard’s Wrath

This is the big-budget RPG announced alongside Oculus Link itself — a classic example of a heavy VR app.

Asgard’s Wrath’s recommended CPU is an Intel Core i7-7700 or better. Here’s how the CPU benchmark app Cinebench R20 compares:

The ASUS VivoBook S15’s CPU doesn’t reach Asgard’s Wrath’s recommended performance level. With that in mind, let’s check the frame rate.

Quality Setting: “Easy"

It plays without any frame drops. At a rendering resolution of 1.0x there’s still headroom to spare — plenty playable.

Quality Setting: “High"

At the Oculus Quest’s lowest rendering resolution setting of “0.8x," the frame rate holds at 72fps, but as soon as the CPU picks up any other work, things get choppy — I can’t recommend running it this way.

You’re better off sticking with the “Easy" quality setting in the app.

Frame Rate Results Across Rendering Resolutions

Here’s how the results break down by rendering resolution setting. Because the Oculus Quest’s display has a noticeable screen-door effect (visible gaps between pixels), raising the rendering resolution doesn’t make as much visible difference as you might expect.

In practice, as long as the default setting doesn’t drop frames, you can consider the setup good enough to use.

Standard Setting (4128 x 2272)

With the PC-side Oculus app’s rendering resolution left at the middle “1.0x" setting (resolution: 4128 x 2272), I measured the frame rate for each app.

Frame drops occur only with Asgard’s Wrath at the “High" quality setting. CPU performance is the bottleneck when it comes to pushing apps to higher quality.

Frame-Rate-Priority Setting (3104 x 1712)

I set the PC-side Oculus app’s rendering resolution to its minimum “0.8x" (resolution: 3104 x 1712), the setting that gives the highest possible frame rate. At this setting, the image looks a bit soft and compressed, like a heavily compressed video, but performance is rock solid.

Every app runs with plenty of margin here. Even with each app’s quality setting maxed out, no frame drops occur.

Quality-Priority Setting (5408 x 2976)

I set the PC-side Oculus app’s rendering resolution to its maximum “1.3x" (resolution: 5408 x 2976), the setting that produces the highest possible image quality, and measured the frame rate.

Frame drops only show up with Asgard’s Wrath at the “High" quality setting. Half-Life: Alyx can also occasionally show flat, undetailed textures that fail to load in time, so I can’t recommend running at this resolution.

Realistically, there’s no need to push the rendering resolution this high.

What I Could Not Verify

This is a single review unit lent by ASUS, so I can’t say how much these numbers would vary between individual units. I only tested with the specific Thunderbolt cable, Razer Core X enclosure, and GIGABYTE RTX 3060 Ti listed above — a different cable, eGPU enclosure, or card model could shift the numbers. I also stuck to four apps here; a heavier or more CPU-bound title than Asgard’s Wrath could behave differently.

In Summary: Yes, With the CPU as the Ceiling

Can the ASUS VivoBook S15 + RTX 3060 Ti drive the original Oculus Quest?

Yes — the ASUS VivoBook S15 paired with an RTX 3060 Ti handles the Oculus Quest comfortably.

That said, the CPU can become the bottleneck at times.

Even raising the rendering resolution doesn’t do much for the Oculus Quest, since its display already has a fairly pronounced screen-door effect. There’s no need to push the rendering resolution higher than necessary.

The ASUS VivoBook S15 is a mobile ultrabook built around an 11th-gen CPU. CPU performance in mobile ultrabooks keeps climbing generation over generation, and once you fix the graphics bottleneck by adding an RTX 3060 Ti, it turns out VR is enjoyable to this degree.

The CPU doesn’t have much headroom to spare, so if you’re running a heavy app, you’ll get the most out of VR by making sure nothing else is competing for CPU time in the background.