Explore overte#69
Conversation
to something a little more recent; from 2025 rather than 2022.
Slight adjustments to some wording.
* Encourage users to use push-to-talk * Re-arrange settings table to match the order seen in the audio settings tablet window * Add missing audio settings to table * Cyberspace!
…oft support articles
* OpenVR and OpenXR support * Add missing control settings * Update some terminaology
Also correct table issue in vr-controls
* Expand list of files which make up an avatar * Rewrite introduction to emphasise how choosing an avatar empowers the user to express themself * Provide more detail on where to host an avatar, without emphasising individual brands
* Mention all compatible model files * Document grabbing wearables * Document modifying wearables, including that modifications will be saved when favourited * Document favouriting avatars with wearables
* Corrected information about updating apps * Some tweaking to wording and expanded explanation * Removed section on the no-longer-available Text to Speech app
* Include screenshots for the current Places app * cover filtering, bookmarks, portals and home
* Remove erroneous orphaned row of Graphic Settings table
…red rendering performance
* Include context menu button * Use Roboto font to match upcoming UI change
* Change fonts to Roboto to match upcoming UI change
|
I think I'll leave the system requirements alone, and let them be updated/removed in a separate PR. |
JulianGro
left a comment
There was a problem hiding this comment.
I am only half-way done with the review, but I thought I should show what I have already.
Co-authored-by: Julian Groß <julian.g@posteo.de>
* Also remove erroneous step when adjusting volume
JulianGro
left a comment
There was a problem hiding this comment.
Some small things and nitpicks.
As mentioned in the comments, with the American English versus British English differences, I think it makes sense to just stay with American English as to not mix the two of them. American English is probably a better choice for an international audience anyway, because it has easier spelling and fewer exceptions.
Co-authored-by: Julian Groß <julian.g@posteo.de>
Co-authored-by: Julian Groß <julian.g@posteo.de>
Co-authored-by: Julian Groß <julian.g@posteo.de>
…n some contexts. * I have left it as simply "Interface" or "Interface window" where I thought it contextually made sense. * Also made controls instructions generic by removing specific reference to VR controller devices where it wasn't necessary.
* Mono audio input can be spatialised in Overte, where-as stereo cannot be
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
| Using Bluetooth Headsets | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
|
||
| You can use bluetooth headsets, such as AirPods with Overte. However, note that there are limitations to using them, and they may not work in all environments. If using WiFi, ensure you’re using a 5Ghz WiFi connection. On a 2.4Ghz connection, you may experience audio breakup and occasional disconnects. | ||
|
|
||
| Unfortunately, bluetooth audio devices do not currently support stereo input. Therefore, you have two options: | ||
| You have two options: | ||
|
|
||
| * Use the bluetooth headset as an output device only, and use another microphone for input. This allows you to take advantage of the stereo audio. | ||
| * Use the bluetooth headset's built-in microphone. In this case, other users will only experience mono sound coming from you, rather than the normal stereo audio. | ||
| * Use the bluetooth headset as an output device only, and use another microphone for input. This may allow you to use a higher quality microphone than the one built in to your headset. | ||
| * Use the bluetooth headset's built-in microphone. | ||
|
|
There was a problem hiding this comment.
Do we want to just get rid of this entire section?
I never heard about Wi-Fi interfering with Bluetooth. In fact, on pretty much every holiday, I use 2.4GHz Wi-Fi and Bluetooth earbuds at least once and never had audio issues there.
The two microphone options seem like a weird thing to put into the documentation. It turned into an elaborate way of saying "You can choose which microphone you want Overte to use".
There is a legitimate reason for using bluetooth headphones only for audio output and not input, and that is that bluetooth headphones generally need to switch into a really low fidelity mode in such case.
There was a problem hiding this comment.
There is a legitimate reason for using bluetooth headphones only for audio output and not input, and that is that bluetooth headphones generally need to switch into a really low fidelity mode in such case.
You know, the whole "You lose stereo" angle makes a lot more sense if it was supposed to be about Bluetooth's headset profile only supporting mono output, where-as a2dp would support stereo output but no mic input. Perhaps the details got lost along the way somewhere.
That is exactly what happened. I checked the git blame for that line...
Use the bluetooth headset's built-in microphone. In this case, you will only experience mono sound, rather than Vircadia's stereo audio.
Became
Use the bluetooth headset's built-in microphone. In this case, other users will only experience mono sound coming from you, rather than the normal stereo audio.
I think it make sense to warn users they would miss out on stereo/spatialised audio when using bluetooth headsets make sense. I'll try reverting it back to when it made sense.
There was a problem hiding this comment.
With regards to interference, it is possible as they share the 2.4ghz spectrum but having read up on it a little it seems both try to mitigate the problem by trying to detect interference and then avoiding those frequencies for a while (but it's a bit more complicated than that). I would assume interference noticeably impacting Bluetooth connections is possible, and really depends on how much interference/activity is happening.
Perhaps it is less of a problem now, but I'm not sure works on my holiday™ is enough proof it is no longer a problem. I think we should leave that part in for now, unless we do decide to remove the rest of this section.
Updates the Explore section to better reflect the current features and design of Overte.
I do not have access to VR myself, so for much of the VR-specific parts I had to read code, changelogs and interview people who have had experience with it on Overte. I may have gotten something wrong here, so would especially appreciate if someone with access to VR could double-check it works as stated.
Similarly for Windows, I do not have access to Windows but tried to confirm those parts the best I could. If someone with Windows could double check them for me I would appreciate that.