Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

GreenTeaBD

3
Posts
1
Topics
A member registered Nov 22, 2021

Recent community posts

(1 edit)

I think you should read my post more closely, it seems like you missed what the issue is and most of what I said. I understand why it requires ADB, but it only seems to support ADB over wifi. ADB, just generally, works over USB too (but not here, not in this software) I mean that's what it was originally made to do. I did read the FAQ, and all the other pages, nothing I found seems to address this issue at all.

The problem is with the fact that following the instructions and installing/running it, always allowing ADB over wifi, while the quest is also connected to a pc by USB puts the Quest into a state where it is trapped in Quest Link.

The problem isn't that it can or cant work with Quest Link too, the problem is that it cant get out of Quest Link after installing and following these instructions while also connected to the PC by USB except by removing the USB cable. And then, if the USB cable is reinserted, it goes right back to being trapped in Quest Link. That situations makes the software impossible to actually use while connected over USB because you cannot run Quest native games from Quest Link.

(1 edit)

Why does this even require wireless ADB? I have my headset plugged in all the time, when I enable wireless ADB (why? It's literally wired. Why is it even necessary?) it makes it get into a loop crashing trying to get out of Oculus Link. The only way it works is to disconnect my Quest 3 from my PC by USB entirely.


It says it no longer requires a PC, but the app seems to give a warning and not work without wireless ADB so....

It's unusable for me because of this, and I don't understand why it demands this when wired ADB is right there. Not everyone uses their Quest wirelessly.

On top of that this has caused a problem now where every time I try to use it it automatically tries to connect over wireless ADB which sends my Quest into Quest Link if it's plugged in, which cant be exited without unplugging the Quest. So, that's great.

Following the instructions you gave has made my Quest unable to not be in Quest Link when plugged into my computer. So, thanks for the malware, best ten bucks I ever paid.

Hey everyone,

So, looking at modern profiles (that all seem to work, though I haven't tested much out) they look to be just text files.

I checked out the V1 profiles that were converted to V2 profiles, the ones here https://itch.io/t/208946/converted-v1-profiles and they are definitely not text files. They also don't seem to work in 3DSenVR 0.9.4.4. By not work I mean, if they go in the CustomProfiles directory they don't actually appear in 3DSen.

I checked out a normal V1 profile, they're not text files either. But I don't have any way to compare them beyond that.

So has the format changed past V2? And does that mean V2 profiles aren't compatible anymore? Is there a way to convert them to V3 or whatever we're on? Just trying to check out the old EB0 and RCR profiles.

Thanks