You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OBS API is not 100% working API. Particularly obs_frontend_get_current_profile_path() doesn't work at all. Therefore I can't get actually profile path and have to observe possible profile locations manually.
Right now it first seeks portable profile in [obs_location]\config\obs-studio\basic\profiles
If it was not found it will then seek for non-portable profile. In Windows: %appdata%\Roaming\obs-studio\basic\profiles
If you previously used OBS portable mode and later switched it off and the names of portable profile and non-portable profile are same (for ex. default name: Untitled), you can run into a problem that portable profile is used in non-portable OBS.
I blame OBS devs for their API not working correctly. This is rare case, therefore I won't make a workaround for it.
Solution:
Delete or rename "config" folder in OBS location folder.
or
Rename portable profile folder in [obs_location]\config\obs-studio\basic\profiles\ so it doesn't match any profile names in non-portable profile folder.
The text was updated successfully, but these errors were encountered:
OBS API is not 100% working API. Particularly obs_frontend_get_current_profile_path() doesn't work at all. Therefore I can't get actually profile path and have to observe possible profile locations manually.
Right now it first seeks portable profile in [obs_location]\config\obs-studio\basic\profiles
If it was not found it will then seek for non-portable profile. In Windows: %appdata%\Roaming\obs-studio\basic\profiles
If you previously used OBS portable mode and later switched it off and the names of portable profile and non-portable profile are same (for ex. default name: Untitled), you can run into a problem that portable profile is used in non-portable OBS.
I blame OBS devs for their API not working correctly. This is rare case, therefore I won't make a workaround for it.
Solution:
or
The text was updated successfully, but these errors were encountered: