Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] #31

Closed
SirColeslaw opened this issue Feb 3, 2024 · 3 comments
Closed

[BUG] #31

SirColeslaw opened this issue Feb 3, 2024 · 3 comments
Assignees
Labels
wontfix This will not be worked on

Comments

@SirColeslaw
Copy link

SirColeslaw commented Feb 3, 2024

Describe the bug
Installation cancels with error message.

To Reproduce
Steps to reproduce the behavior:

  1. Start installation. <- Even tried to "Start as Administrator"
  2. Define installation path (in my case other than default).
  3. Get error message.
  4. Tried on the other PC also, error stays the same.

Expected behavior
Installation finishes without errors.

Screenshots
If applicable, add screenshots to help explain your problem.
Screenshot 2024-02-03 075907

Screenshot message translated:
"Error overwriting the file: ..."

Logs and details about your system

  • Windows 11 Pro 23H2 <- Using local administrator account
  • OBS 30.0.2 <- In portable mode, not installed in default folder.
  • Beam 1.0.0 <- Installer
@YorVeX YorVeX self-assigned this Feb 3, 2024
@YorVeX
Copy link
Owner

YorVeX commented Feb 3, 2024

The installer isn't intended to be used with a portable mode OBS.

It doesn't really make sense when you think about it, the idea of a portable folder being that you can just throw it anywhere and run it without installation, including through USB stick on a different PC, and then you'd have a plugin inside this folder that registers itself in the system for being installed in this fixed location.

For example, what is supposed to happen if you move the folder (including the plugin inside it) and then try to uninstall the plugin? And if you move the folder to a new PC, you still have the files in there, but no installation anyway, so PC 1 would have the Beam plugin properly installed and registered in the system to be in that folder, but on PC 2 for the same folder structure that's not the case. It goes on, when you use portable mode to be able to easily backup and recover that folder anytime, installation information would also be gone after recovery - or you recover an old folder from before installing it, then you system thinks the plugin is installed but it's not in the folder.
And if you have more than one OBS installed in portable folders on that system where you want to use Beam, which of the folders should the installer register as its install location? From where should it uninstall the files if you choose to uninstall the plugin?

I guess that's just a long way of saying the two concepts "installer" and "portable" don't match 😄

That's what the xObsBeam-win-x64.7z file is meant for, just unpack this into the portable OBS directory. And if you ever need to remove the plugin again, just check what is in that .7z file (it's not much) and delete the files manually.

@YorVeX YorVeX added the wontfix This will not be worked on label Feb 3, 2024
@SirColeslaw
Copy link
Author

Yeah, totally right. Thanks for pointing it out. Seems "bug" was a layer 8 problem ;)

Closed.

@damnedOperator
Copy link

damnedOperator commented May 29, 2024

/reopen, have the same problem with the installer on C:\Program Files\obs-studio. Definitely not a portable installation.

Edit: Opened its own issue for it, as gravedigging this issue maybe isn't the best idea

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants