Hi, there was during Halloween sale ;-)
Anagan79
Creator of
Recent community posts
Hi there your simply are faceing the Meta bug from v62, v63 and v64. Meta fixed the issue in v65 🤘👌
Anyway here are the explanations https://anagan79.itch.io/quest-games-optimizer/devlog/668007/known-issues-bugs
What do you see on the top left corner of sidequest when your headset is plugged ? Could you show me ? You should try another USB cable and be sure its an OTG cable.
I asked yyou for the developer mode because ome people imagine this is the developers options in the headset and didn't check their smartphone app.
Anyway you have plenty other solutions to enable ADB here : https://anagan79.itch.io/quest-games-optimizer/devlog/360229/enabled-adb-wifi-vi...
Hi, I understand what you mean but here is my answer :
- motion sickness is in majority due to virtual locomotion, and virtual world apprehension, not only because of frame rate. Yes a higher frame rate can help in some dynamic games, but dynamic games are not really recommended for beginners. Anyway, today and by default, 90-95% of the games run at 72hz which is still the basis refresh rate even on very popular games. More and more developers tends to implement 90Hz but almost only on Quest 3. But beginners also play on Q2 for example. So if the motion sickness was very impacted by refresh rate, you could imagine that meta would have forbidden 90% of the games.
- each games are different, that is why I can spend hours and days to optimize one game. And even many low quality or low res or low poly games can't handle 120fps because it is too heavy to handle by the Quest 3. So, with a "Enable 120Hz mode for beginner" button, it will not be a magic solution and instead of having smoothness games you will end up with laggy games and that will be a very bad idea and experience for beginners. If a game run at 120Hz but the headset is not capable to render 120 images per seconds, even with boosted CPU and GPU, you will end up with lags. So, this is a good idea but it's not feasible unfortunately.
I hope you are okay with that :-)
Hi, could we write in english ? :-)
For the moment, nobody reported me problems on v65 and I don't have problems myself on my 3 devices.
When you says : ADB is yellow, you mean, you see the bolt icon ? If you see the bolt icon this means you see ADB green icon, this means all is fine.
But if you see ADB red and the red banner, this means ADB is disabled. A fix is to enable ADB wifi via sidequest like when installing QGO.
But in your case, you reinstalled the app and if you don't see the debug prompts, this is because ADB wifi is not set. Yous must click on sidequest to enable ADB wifi like in my video.
Also, check if the dev mode is enable in your mobile app. Some users lost developer mode in v64 because of Meta update.
Hi, I understand what you mean but here is my answer :
- motion sickness is in majority due to virtual locomotion, and virtual world apprehension, not only because of frame rate. Yes a higher frame rate can help in some dynamic games, but dynamic games are not really recommended for beginners. Anyway, today and by default, 90-95% of the games run at 72hz which is still the basis refresh rate even on very popular games. More and more developers tends to implement 90Hz but almost only on Quest 3. But beginners also play on Q2 for example. So if the motion sickness was very impacted by refresh rate, you could imagine that meta would have forbidden 90% of the games.
- each games are different, that is why I can spend hours and days to optimize one game. And even many low quality or low res or low poly games can't handle 120fps because it is too heavy to handle by the Quest 3. So, with a "Enable 120Hz mode for beginner" button, it will not be a magic solution and instead of having smoothness games you will end up with laggy games and that will be a very bad idea and experience for beginners. If a game run at 120Hz but the headset is not capable to render 120 images per seconds, even with boosted CPU and GPU, you will end up with lags.
So, this is a good idea but it's not feasible unfortunately.
I hope you are okay with that :-)
Hi, thank you ! 🤘
2 solutions 😉
- You can purchase another QGO license to support me 😜
- Or don't pay again and just use your QGO account on your new device 😉. 1 QGO license = 1 user. So, you can have a Q2 and Q3 and use the QGO license you already bought 👍
Anyway if you love the app, don't forget to rate it 🙃
Hi, QGO can't be in the home pinned in the universal menu. You can't do that with an app that is not from the official store. But since the v62 or v63, QGO icon sometimes appears in this universal menu as a recently launched app. This is nice of Meta doing that :-).
Concerning the QGO shortcut feature. What did you put in the shortcut text field ?
Hi,
Did you accepted the 4 debug prompt like in my video by clicking ALWAYS ALLOW ON THIS NETWORK/COMPUTER. You must not click on the simple ALLOW button.
If yes and if you only lost ADB, you should plug your Quest to the PC and enable ADB Wifi via sidequest again, this should do the trick ;-) It is explained in the red banner you should get.
Hi, QGO can't alter height nor controller calibration, it only change the refresh rate, cpu level, gpu level, ffr level , etc..., and all the modification QGO do are reset to default when shuting down/rebooting the device. So you risk nothing 😉
Nobody reported this issue since QGO was born and don't have the problem myself on my 3 headsets.
Anyway did you try to reboot the Quest ? Did you try to redo your guardian virtual boundary, did you try to clean your guardian virtual boundary and redo your guardian ? Did you try to reboot your controllers ? Are you playing in a dark room ?
All these things could help.
And yes this v64 have some problem but I don't have this one.
EDIT : you can also try to disable Lying down feature
SBS = Side By Side (both eyes). This is the video record section on the Meta Quest Developer Hub : https://developer.oculus.com/downloads/package/oculus-developer-hub-win/
They clearly mention that in some case you can't get audio/(mic) to work.
Hi, mic have issues since a long time on the Meta Quest, but yes, it sometimes appears if you run ADB commands to tweak the recording settings, it "break" the mic... I didn't find any solutions. In my side, I don't care about mic as the games I record I solo games, but yeah this is sometimes a problem. But sometimes it works without any issues... What are the settings you apply for video recording ?
Hi, I can't proceed to refund myself, you must ask Itch.io support but what I can see is you used 3 different emails ;-)
And because your premium extension purchase is not the same as the one when purchasing QGO official app, you can't activate premium extension. I can link your premium extension to your email used for QGO if you want.
Salut, je ne sais pas à quoi elle sert cette pastille bleue ni comment la virer, mais entre nous, ce n'est pas un problème, ignore ce truc et tout ira bien ;-)
J'ai remarqué que ça le fait aussi sur pas mal d'autres applications pourtant à jour. En général cette pastille est pour signaler qu'une mise à jour de l'application est disponible sur le store. QGO ne faisant pas partie du store officiel, je n'ai pas de réponse, mais toujours est-il que ça ne nuit pas à l'utilisation de l'app :-)
Salut, quelle version de QGO as-tu ?
Ça ne marche pas quand tu fais cette manip dans ma video à 6 : 04 ?
Nope, as I can't know if you disabled proximity sensor or guardian via the meta quest developer hub or via the Quest settings or via side quest or any ADB commands. So the result could be a wrong value. Turned ON in QGO (QGO remember it is green), but you then disable the setting via the meta quest developer hub, but QGO will still display the green value ;-)
I did that in the past but too many people reported me the value was wrong and the reason was the changed the state from another way and QGO wasn't informed of this new state ;-)
Haha ;-)
I mentioned that it could be possible that playing time could be reset after a Meta update. It was the case in the past but I updated the way I retrieve the playing time to avoid as possible that to reproduce. So, this is a good thing to read this feedback :-)
Regarding the color indicator, I don't understand (sorry I'm french), what did you mean ?