Improper version notation

[iryis]

I use the StreamUP plugin for OBS which includes an update checker which seems to look at a version field with the wrong version.

The following is said window claiming this plugin is version 0.0.1, although the latest available version to me is being used (version 1.0 from releases)

I've messaged with the StreamUP plugin developers- one says "it probably means that the dev doesn't use proper versioning, could be wrong though", another said it will be fixed next patch (It was not for me)

Do you intend on supporting this plugin through OBS version 32.0 and later to possibly fix this version mismatch issue with your plugin on your end? Thank you in advance.

(And thank you github for submitting the issue when I wasn't finished..)

[iryis]

I've built the plugin using the OBS Studio v32 bindings mentioned here and even setting the version in .csproj to 1.0.1.0, the issue seems to still report it as 0.0.1, so It is probably on their side.

In doing this I also found an issue with the NSIS where the ProgramFiles(x86) is the hardcoded install directory, but I'll leave it up to you to fix this

[YorVeX]

It's been a long time since I tried StreamUP, back then it simply didn't support version numbers with only 2 components (it wanted 3), I reported that here and it was closed so I assumed it was completed and would work.
As far as I remember what StreamUP did was simply to read the version message a plugin writes to the OBS log/console, so the important question is: in your setup, does my plugin properly announce itself with its current version (check my screenshot in the issue I linked for reference on how it should look)? If it does, then it's something StreamUP would need to fix. If it doesn't, I need to investigate.
Unfortunately I currently have to rebuild my dev setup because my dev laptop died, so it will take a bit until I will be back in business of checking this stuff.

[iryis]

I'd have to check, but it seemed like it did properly announce itself and the proper version.
I haven't seen it since this most recent StreamUP update (quicker than the previous updates), so I think it's safe to assume it was a problem on their end.