OBS-HUD

Free OBS-HUD 1.0.6

Recently made some icons for this and after a windows update corrupted my system files and I lost all my programs, including the icons I made previously. Going to release them here so I can grab them again in the future if needed, and so anyone else can use them if they want. They were made for a 1440p display so they might be too small at some resolutions. Anyone is free to scale these up or down as needed.
 

Attachments

Recently made some icons for this and after a windows update corrupted my system files and I lost all my programs, including the icons I made previously. Going to release them here so I can grab them again in the future if needed, and so anyone else can use them if they want. They were made for a 1440p display so they might be too small at some resolutions. Anyone is free to scale these up or down as needed.
Nice icons! Thanks for sharing.
 
I don't suppose it would be possible to have this launch automatically as an administrator is it? For some games I need OBS to be run as administrator to hook into games properly, but OBS HUD also needs to be running as administrator in order to hook into OBS. The issue is that I can't figure out how to make both of these programs launch at startup in administrator mode. OBS was easy enough to get working using Windows Task Scheduler, but setting up the same process for OBS HUD doesn't work.

If that currently isn't possible it could be a nice future feature to add some time.
 
I don't suppose it would be possible to have this launch automatically as an administrator is it? For some games I need OBS to be run as administrator to hook into games properly, but OBS HUD also needs to be running as administrator in order to hook into OBS. The issue is that I can't figure out how to make both of these programs launch at startup in administrator mode. OBS was easy enough to get working using Windows Task Scheduler, but setting up the same process for OBS HUD doesn't work.

If that currently isn't possible it could be a nice future feature to add some time.
I am surprised that Task Scheduler is not working. I just did a quick test on my system and was able to start OBS-HUD as admin using that method. Do you receive any error messages or other indications about what might be blocking this configuration for you?
 
I am surprised that Task Scheduler is not working. I just did a quick test on my system and was able to start OBS-HUD as admin using that method. Do you receive any error messages or other indications about what might be blocking this configuration for you?
I don't receive an error. It just says the task is ready to run on startup without actually starting. Even when I try to run it manually it doesn't launch the program and I have to do it manually.

Could the issue be that I have the OBS HUD exe in my program files next to my OBS installation? Task scheduler launches OBS just fine from basically the same folder.
 
Could the issue be that I have the OBS HUD exe in my program files next to my OBS installation? Task scheduler launches OBS just fine from basically the same folder.
I just ran a test. Installed OBS-HUD to the standard Program Files directory. Added an entry to Task Scheduler. Selected the "Run with highest privileges" checkbox. Manually choosing the Run option on the task starts it correctly with elevated permissions.

Task is set to start automatically on user login. When I restarted, it did not start. I changed the trigger to add a 30 second delay, rebooted, and then it *did* start correctly.

Try adding a startup delay to your scheduled task and see if that gets it to work correctly. Please let me know the results.


1778525283372.png
 
I just ran a test. Installed OBS-HUD to the standard Program Files directory. Added an entry to Task Scheduler. Selected the "Run with highest privileges" checkbox. Manually choosing the Run option on the task starts it correctly with elevated permissions.

Task is set to start automatically on user login. When I restarted, it did not start. I changed the trigger to add a 30 second delay, rebooted, and then it *did* start correctly.

Try adding a startup delay to your scheduled task and see if that gets it to work correctly. Please let me know the results.


View attachment 119556
I'll give that a try. It's worth noting that even trying to start it manually today didn't work and I had to navigate to the folder to launch the .exe manually. I'll let you know if this solves my issue.
 
I just ran a test. Installed OBS-HUD to the standard Program Files directory. Added an entry to Task Scheduler. Selected the "Run with highest privileges" checkbox. Manually choosing the Run option on the task starts it correctly with elevated permissions.

Task is set to start automatically on user login. When I restarted, it did not start. I changed the trigger to add a 30 second delay, rebooted, and then it *did* start correctly.

Try adding a startup delay to your scheduled task and see if that gets it to work correctly. Please let me know the results.


View attachment 119556
So I made this change and it still isn't working for me. I should also note that I have the exe set to run as administrator in the properties. Does running it with only the highest permissions in Task Scheduler run the program as administrator as well?
 
So I made this change and it still isn't working for me. I should also note that I have the exe set to run as administrator in the properties. Does running it with only the highest permissions in Task Scheduler run the program as administrator as well?
In my test, yes. The application runs as admin when I selected this option in the task:
1779157392368.png


It is strange that you are unable to run the task manually or automatically. Task Scheduler has a run history option that you can enable from the Actions menu:
1779157488088.png


Once enabled, it will log events to the History tab:
1779157629690.png


Perhaps this can help diagnose the issue. If you decide to try it, please let me know the results.
 
In my test, yes. The application runs as admin when I selected this option in the task:
View attachment 119632

It is strange that you are unable to run the task manually or automatically. Task Scheduler has a run history option that you can enable from the Actions menu:
View attachment 119633

Once enabled, it will log events to the History tab:
View attachment 119634

Perhaps this can help diagnose the issue. If you decide to try it, please let me know the results.
Yeah I've got no idea what I could be doing wrong. It says the task is running, but it doesn't launch the application.

1779198185428.png
1779198199189.png


1779198494624.png


I also decided to disable administrator mode for OBS HUD. Toggling this setting made no difference. I have the trigger set to whenever any user logs on and that works perfectly fine for OBS itself.


1779198351217.png


I added the 30 seconds delay which does at least get the task to start running at log in, but running the task manually doesn't do anything. I'm really not sure what could be going on.
 

Attachments

  • 1779198462891.png
    1779198462891.png
    35.9 KB · Views: 4
Yeah I've got no idea what I could be doing wrong. It says the task is running, but it doesn't launch the application.

View attachment 119637View attachment 119638

View attachment 119641

I also decided to disable administrator mode for OBS HUD. Toggling this setting made no difference. I have the trigger set to whenever any user logs on and that works perfectly fine for OBS itself.


View attachment 119639

I added the 30 seconds delay which does at least get the task to start running at log in, but running the task manually doesn't do anything. I'm really not sure what could be going on.
Okay so looking at your screenshots I noticed that I had it set to run whether user was logged on or not and switched it to only run when logged in. I didn't think it would make a difference but that apparently fixed my issue.
 
Okay so looking at your screenshots I noticed that I had it set to run whether user was logged on or not and switched it to only run when logged in. I didn't think it would make a difference but that apparently fixed my issue.
I'm glad you got it working!

I have no idea why that setting would affect the ability to manually launch a task, especially when the more permissive wording "logged in or not" actually behaves more restrictively. Must be some special Microsoft backend voodoo.
 
Back
Top