@Trouffman As mentioned in Discord, this "feature" is a little silly and never worked in NDI5 and somehow we survived.

Options:

1. Use this PR's code as written when sends a working metadata when Allow hardware acceleration is checked and send a fake non-working metadata when it is unchecked.
   Sending fake metadata to turn off hardware acceleration is effectively no worse than not sending any metadata.
   If NewTek ever fixes/adds this ability then we either magically start working or just need to make a simple change the the metadata.
2. Change this PR's code to only send the working documented metadata only when the Allow hardware acceleration is checked (ie: don't send a fake non-working metadata).
3. Not have any UI option and just always send a request to enable hardware acceleration.

I think an option is best.
I could see some users wanting to legitimately reserve all of their GPU compute for gaming/whatever and never want NDI to always automatically use their GPU.

Option 2.

I considered turning this on by default, but I do not think that we should because there is no way to directly turn this off for someone who does not want this enabled.

The only way I can think of to turn this off is to maybe reset the receiver, which is not intuitive how to do.
We could make it so that any settings change stops and restarts the receiver.

One other way is to require the user to close and reopen OBS! 😦

"Forcing" a receiver reset on a settings change could be the way, this is already the case for some of them.

"Forcing" a receiver reset on a settings change could be the way, this is already the case for some of them.

I have a solution for that in another PR, so I will go ahead and merge this relatively tiny PR.