Feature request: Automatically change Oculus Debug Tool settings and create profiles

[ASchneiderBR]

Hello,

Thank you for creating this excellent software. I have been using a few CMD files to set several things before AirLink starts. One of the essential changes I need to make every time is to adjust the FOV settings, especially if Oculus Services restarts.

Besides, I also use a couple of CMD files to launch regular games and Flight Simulator 2020, where I need to crop the FOV extensively.

It would be fantastic if your software could automatically change these settings and create various profiles that alter specific settings on the Debug Tool.

We can modify these settings using the original OculusDebugToolCLI.exe executable by parsing a TXT file. Here are a couple of examples that I use:

CMD file:

"%~dp0\OculusDebugToolCLI.exe" -f odt_fs2020.txt

odt_fs2020.txt:

service set-client-fov-tan-angle-multiplier 0.80 0.70
server:asw.Off
exit

This is my "regular" FOV adjustment:

server:asw.Auto
service set-client-fov-tan-angle-multiplier 0.85 0.84
service set-pixels-per-display-pixel-override 0
exit

Please let me know if you would like any assistance with this idea.

Thank you for your time and effort!

[KrisIsBackAU]

This should be possible to do, depending on a few factors, they can change how it may function.

If I understand it right, you just run the debug tool with the text file as a parameter and it runs the commands ?

Do these commands reset once the link is closed or need to be reset afterwards ?

Thanks.
Kris.

[ASchneiderBR]

Hi there! I appreciate your response.

Yes, FOV and ASW settings are lost whenever Oculus service restarts. I always apply them before launching airlink, but it would be awesome if they could be applied automatically at launch and when airlink starts, just in case.

It would also be cool to have profiles for different sessions, so we can adjust the crop or ASW settings according to our preferences.

This would make this tool perfect for me and I could get rid of my scripts :) (https://github.com/ASchneiderBR/VR-Scripts)

Thank you!

[ASchneiderBR]

Hi again.

I have some ideas for new features: how about automatically switching the default audio device to the Quest when you start the program, and then switching it back to the previous one when you close it?

Another feature that would be useful is the option to automatically run a file, like an .exe, .bat or .cmd. This could help you launch other apps for streaming sessions more easily.

What do you think?

[KrisIsBackAU]

Have you tried OTT (Oculus Tray Tool) ? I feel like it may do what you want with some things, I haven't used it to its full use before so not sure of its features fully.

[ASchneiderBR]

Hello. I believe it has some of those functions but the program is old and I don't think many people still use it, like me. It would be nice to have those features in your software. Cheers!

[KrisIsBackAU]

Hi Antonio,
Added in audio switching, the plugin from NuGet https://github.com/BrettHewitt/AudioPlaybackDevices works well BUT has some issues getting the name sometimes .. might see if there's a different options that's not huge or complicated to use.

But see how the attached version goes with audio switching.
It will once enabled and defined under Settings - Switch to Quest Speaker on launch and Normal Speaker on Exit.
1.0.3.2.zip

[ASchneiderBR]

Hello! I'll take a look and let you know. Thanks!

[ASchneiderBR]

Hello. I did a quick test and found out the devices names are not showing correctly:

Oculus device are being repeated many times and I could not find my default Realtek audio device.

Thanks!

[KrisIsBackAU]

Sometimes it just doesnt get the names right as the nuget package uses a thread that doesnt complete on time to get the names, I did mention its not the best at getting names in my reply with the zip, may try and fix the nuget package when I get some time, ONCE you know which one is which it uses the ID to set it so no worries for future runs, even if it gets the names wrong.

But just close it and run it again and see if it got the names right it feels very 50/50 if it does or not

[KrisIsBackAU]

Give this one a shot - changed what package its using this one seems more reliable and uses a GUID rather then a generated ID
1.0.3.2-SoundNameFix.zip

[ASchneiderBR]

Hey there!

Awesome, the device names are displayed right now. 👍

I've got a couple of suggestions, if that's cool with you:

1 - When I manually switch to the default device, it changes both the default and communication devices. I think it'd be better to change just the default, not the communication one. In my case, I have a separate audio device set as the communication default (for Discord and other apps), so I can split the audio while live streaming with OBS.

2 - I know this is just a test, but maybe a dropdown menu would work better for picking the normal and quest devices.

Thanks a lot!

[KrisIsBackAU]

This should be better, now drop down menu for each type and the setting to change the default speaker only or include communication.
1.0.3.3.zip

[KrisIsBackAU]

1.0.3.4.zip

Added in Program Auto Launch under Settings - Can launch a program on Startup and on Closing.
Currently it can run any file.

I will get your your original request, these are just easy to do in an afternoon on the weekends when I have time.

Oculus Debug Profiles are going to be bit more advanced with a UI and storage and I need to understand them properly.

[ASchneiderBR]

Hi there! I apologize for the late reply. I appreciate your contribution and I will definitely test it out. :)

By the way, I'm excited about this news: https://mixed-news.com/en/meta-quest-v51-brings-a-major-os-update/

The new v51 update will allow us to use Wi-Fi ADB without plugging in the device every time it reboots. This means we can easily adjust the resolution, refresh rate (even 60hz with airlink) and other cool features.

Thanks a lot!

[ASchneiderBR]

Wow! It looks amazing!

I love how the program starts up with a sleek interface and lets you choose when to run it: at launch, at shutdown, or both. One thing that would make it even better is if you could add a delay option. Also, I'm curious how the program executes the tasks: does it do them all at once or in a sequence? I think it would be nice to have a sequential mode, with the possibility of setting a delay between each task.

Thank you for creating this awesome app!