[Please take no offence from anything in this message that seems 'snarky', I love you all - just treat it as coming from someone with poor social skills, thank you 😉]
As a developer, I frequently need to access the quest 3 file system for my deployed app, to view logs, etc. Every time I wish to do so, I am currently forced to have to put the headset on, and DISCONNECT & RECONNECT the USB cable, (because the USB notification message only appears for a tiny amount of time and is not subsequently accessible anywhere, such as the notification list) and then click the message - which is also often difficult, because when you initially put the headset on and pick up the controllers, it takes several seconds for the controllers to be correctly initialized and allow correct selection.
PLEASE, PLEASE, PLEASE, Provide one of the following: - A method so I can click a 'allow USB connection' ONCE and tick a checkbox or something to say 'ALWAYS ALLOW USB MTP'
- A 'File Manager' inside MQDH which is actually useful*, because what is there right now is not much use.
*For a useful file manager, you will need: - The ability to multiple select files and choose to delete them all with a single choice (not being forced to individually select each file, click delete, then confirm that deletion.... again, and again, and again - The ability to see more than just 'media' (pictures/videos) - give options to see the apps you installed and their files and folders (sure, don't allow deletions, but let us see the files in there.) - The option to select individual files, groups of files, or folders, and 'transfer to pc' (to a destination selectable by the developer - DONT keep putting files on my C: drive please, no developer likes that)
Thank you in advance for reading this, and also if you know more than I do and already know ways of achieving what I ask, by all means I would love you to comment and tell me what I should be doing. (Unless you are gonna tell me to keep picking up the headset and putting it on every time I need to access files on the computer, in which case, I'm not interested in your advice 😀)
It kind of has it. Their dialog is busted. At the verry-verry bottom is the top of letters (at least on my 3), when it pops up. It is an always allow text. It takes a few tries, but you can click it.
Their dialog is too short for their message. Seems another way the never try the tools in 'user' mode before releasing.
It kind of has it. Their dialog is busted. At the verry-verry bottom is the top of letters (at least on my 3), when it pops up. It is an always allow text. It takes a few tries, but you can click it.
Their dialog is too short for their message. Seems another way the never try the tools in 'user' mode before releasing.
There is NOTHING I can see on mine to indicate the top of letters or whatever... But, having said that, I TRIED to kinda click at the bottom, near the bottom, around the bottom. (Yes, sadly I spent a lot of time at the 'bottom') And I was getting annoyed with pulling out the cable from the headset, and reinserting it while I frustratingly tried to click on the message, which was made even harder because the fibre optic cable I am using causes the quest to ALWAYS display a stupid message saying that it is not charging at the fastest speed - and of course that message appears where the USB notification should be etc... Anyhow, I dunno if I somehow managed to hit the the thing which you say is there that i cannot see... But the message isn't coming up anymore, and the USB seems to be working!
Little Note To @meta: Not so much love in your direction, I am afraid. I am a long time dev, I have coded on so many different platforms, with so many APIs, etc. If you really want *your* platform to emerge as *THE* place for AR/VR, you need to make the development experience so good that no one wants to ever develop for anything else. Right now we have a number of projects being worked on, and customers who come to us, and depend on our opinions to architect solutions. Initially Quest 3 seemed like good platform to architect various solutions around - competitively priced, standalone capable, and acceptable levels of hardware. Oh but the development pain! Anyone who thought developing for quest standalone was going to be similar to a PCVR OpenXR experience has a harsh lesson coming their way. I realize that to a certain extent it is still early days with many of these things. And I applaud some of the advances Meta has made. But it is still not enough 😊
When someone architecting an AR/VR solution is presented with a decision as to which platform they want to base it on... it is YOUR job to make sure that choosing anything else other than Meta/Quest would be a choice they don't want to make. You do that, not by having a development experience which is 'meh', or, 'ok', but by having one which is 'superlative' - in every possible way you (and the developer audience) can think of.
