Bug Report OBS 21.1 update put files in several wrong places!

TSForrest

TSForrest

New Member
I have OBS Studio 64-bit installed to the default folder that is was originally installed several months ago (C:\Program Files (x86). It seems both the 32bit and 64bit versions are installed under an "obs-studio" folder in this location. I was also accustomed to backing up this folder, and the "obs-studio" folder in the "Users\Username\AppData\Roaming" folder on the drive where Windows is installed. When I ran this update, it seems to have updated a few files in these locations, but put the rest of the files in "bin", "data", and "obs-plugins" folders directly in the "Roaming" folder, instead of in the "obs-studio" folder. It was installing files outside the app's install folders. I tried manually copying these folders to the correct location, but OBS failed to launch, no matter how much I tried to get the files in the right places. Now, I am left with a bunch of "junk" folders with duplicate, but outdated data. When I did get OBS to launch, it was missing major parts of scenes and plugins. I finally just restored a backup that had files from before the update, and that fixed the problem, but I am still using the previous version of OBS Studio. Please check the latest update and make sure it is putting files in the right location. Immediately after the update, here is the very short log file generated during the failed launch:


14:13:43.305: Adapter 1: NVIDIA GeForce GTX 1080
14:13:43.305: Dedicated VRAM: 4176478208
14:13:43.305: Shared VRAM: 4242423808
14:13:43.305: output 1: pos={0, 0}, size={1920, 1080}, attached=true
14:13:43.305: output 2: pos={0, -1080}, size={1920, 1080}, attached=true
14:13:43.305: Adapter 2: Intel(R) HD Graphics 630
14:13:43.305: Dedicated VRAM: 134217728
14:13:43.305: Shared VRAM: 4242423808
14:13:43.307: Loading up D3D11 on adapter NVIDIA GeForce GTX 1080 (0)
14:13:43.347: D3D11 loaded successfully, feature level used: 45056
14:13:43.927: ---------------------------------
14:13:43.927: video settings reset:
14:13:43.927: base resolution: 1920x1080
14:13:43.927: output resolution: 1920x1080
14:13:43.927: downscale filter: Bicubic
14:13:43.927: fps: 30/1
14:13:43.927: format: NV12
14:13:43.927: YUV mode: 601/Partial
14:13:43.930: Audio monitoring device:
14:13:43.930: name: Headset Earphone (Corsair VOID PRO Surround USB Adapter)
14:13:43.930: id: {0.0.0.00000000}.{06d4b869-e6a7-4020-98cc-9e4f3b94b514}
14:13:43.930: ---------------------------------
14:13:43.931: Required module function 'obs_module_load' in module '../../obs-plugins/64bit/chrome_elf.dll' not found, loading of module failed
14:13:43.932: [CoreAudio encoder]: CoreAudio AAC encoder not installed on the system or couldn't be loaded
14:13:43.970: [AMF] AMF Test failed due to one or more errors.
14:13:43.970: Failed to initialize module 'enc-amf.dll'
14:13:43.979: Required module function 'obs_module_load' in module '../../obs-plugins/64bit/libcef.dll' not found, loading of module failed
14:13:43.979: LoadLibrary failed for '../../obs-plugins/64bit/libEGL.dll': The specified procedure could not be found.
14:13:43.979: (127)
14:13:43.979: Module '../../obs-plugins/64bit/libEGL.dll' not loaded
14:13:43.980: Required module function 'obs_module_load' in module '../../obs-plugins/64bit/libGLESv2.dll' not found, loading of module failed
14:13:43.980: [browser_source: 'Version: 1.31.0']
14:13:43.983: NVENC supported
14:13:44.042: [obs-websocket] you can haz websockets (version 4.2.0)
14:13:44.042: [obs-websocket] qt version (compile-time): 5.7.0 ; qt version (run-time): 5.10.1
--------------------END of log--------------------
 

Attachments

  • 2018-03-19 14-17-00.txt
    3.4 KB · Views: 42
TSForrest

TSForrest

New Member
The problem isn't with websockets. That's the last line in the log, but notice that it's not an error. The problem is that the update put the files in the wrong place, so none of the other core plugins, like the browser source plugin, could be found.... they were put in the wrong folder by the update! In fact, it seems that the websockets was the the only plugin that did NOT fail to load, because it was still in the right place, since it was not part of the update!

Don't you see the host of errors long before websockets is loaded?
 
TSForrest

TSForrest

New Member
This has happened to 3 other streamers who ran the update, so please check your facts. I have not talked to a single person who ran this update that hasn't had the same problem, and none of them use websockets.
 
Fenrir

Fenrir

Forum Admin
Well... yes, it is. That error causes the program to forcefully exit, and causes other issues. Please update the websockets plugin, and the issue will go away. OBS has no code that can dump files outside it's own directories, I'm just not sure how this is possible.
 
TSForrest

TSForrest

New Member
Please read the rest of the post. The update put OBS files OUTSIDE the obs-studio install folders in Program Files and my roaming profiles.

it happened. Why would websockets move files for the core OBS install?
 
Fenrir

Fenrir

Forum Admin
First, OBS didn't do that. Something else you have installed is messing with OBS. I have personally tested the update on every version going back to v18.0.0, and none of them cause the files to go outside the program directory. Are you using any kind of antivirus? We see issues all the time with overly aggressive antivirus causing all sorts of bizarre issues like this.

The issue where OBS is not launching properly is due to the websockets plugin, when it tries to load, it just exits with a Qt error and cannot continue the normal initialization. This was confirmed, and fixed, by the developer of the plugin, and we've had hundreds of people who have had this issue so far. Updating fixes it in all cases.

Please, just humor me and update the plugin.
 
O

Osiris

Active Member
TSForrest said:
The problem isn't with websockets. That's the last line in the log, but notice that it's not an error. The problem is that the update put the files in the wrong place, so none of the other core plugins, like the browser source plugin, could be found.... they were put in the wrong folder by the update! In fact, it seems that the websockets was the the only plugin that did NOT fail to load, because it was still in the right place, since it was not part of the update!

Don't you see the host of errors long before websockets is loaded?
Click to expand...

None of the errors before the websocket lines will cause obs to fail to load or fail to load the browser plugin.
 
TSForrest

TSForrest

New Member
OK.. I removed the websockts plugin files... same problem, except the last 2 lines are no longer in the log... how will that plugin explain why the update created the following folders:
C:\Users\user1\AppData\Roaming\bin\64bit
C:\Users\user1\AppData\Roaming\data\obs-studio
C:\Users\user1\AppData\Roaming\obs-plugins

Should't the update be putting the updated files in
C:\Users\user1\AppData\Roaming\obs-studio
C:\Program Files (x86)\obs-studio

???:
 
Fenrir

Fenrir

Forum Admin
Yes, it should. If it's not, something you have installed on your PC is causing the files to be redirected. As mentioned, overly aggressive antivirus is a common cause of these kinds of issues.
 
Fenrir

Fenrir

Forum Admin
I mean, I wish I had an answer for you, I'm not trying to blow you off or dismiss this issue, I'm just not even remotely sure how anything in OBS could cause this, so I'm at a COMPLETE loss where to even begin to check.
 
TSForrest

TSForrest

New Member
Is it possible that I did something wrong to cause the update to put the files in the wrong place? I don't remember any prompts for the install location, but it's possible that I inadvertantly pressed enter and completely missed a prompt or something?
 
TSForrest

TSForrest

New Member
Right now, I am just using the Microsoft Antivirus on my streaming PC. I hope that wouldn't cause problems with the update, or a *lot* of people will be having problems. Anything is possible, I guess. I and not too concerned with what caused it, but rather how to avoid it and how to fix it. I am a big fan of OBS. I'm just a little frustrated, because this has interrupted my channel, stream, and community, and they are all very important to me. I just want to get it fixed, and avoid having this problem in the future. I imagine it is possible that the websockets plug-in could have caused the update to fail in some way. Maybe it was moving files to a new location, and the error happened when it got to the websockets plugin? I don't know. Would you recommend uninstalling all plugins before updating, verifying the update succeeds, then trying to reinstall any additional plugins after the update? I don't want to be stuck using this version and never be able to update. I am now trying to verify which files in which locations are actually being used. I launched the 32-bit version of OBS after the install failed when I was prompted to update when I originally launched the 64-bit version. It prompted me to update a second time, but this was after having trouble with the failed update. Which run of the update put the files in the wrong locaiton is something I am not sure about, but I now have two of all the main files, including the 64-bit main exe's. One in the "C:\Program Files (x86)\obs-studio\bin\64bit" folder, and one in "C:\Users\user1\AppData\Roaming\bin\64bit" folder. I am able to get back to using version 20.1.3, but I don't want to break it by trying to get rid of the duplicate files.
 
D

DrSurround

New Member
I'm seeing what appear to be the same errors after upgrading:

20:34:10.395: Required module function 'obs_module_load' in module '../../obs-plugins/64bit/chrome_elf.dll' not found, loading of module failed
20:34:10.457: [CoreAudio encoder]: CoreAudio AAC encoder not installed on the system or couldn't be loaded
20:34:10.805: [AMF] AMF Test failed due to one or more errors.
20:34:10.805: Failed to initialize module 'enc-amf.dll'
20:34:11.999: Required module function 'obs_module_load' in module '../../obs-plugins/64bit/libcef.dll' not found, loading of module failed
20:34:12.023: LoadLibrary failed for '../../obs-plugins/64bit/libEGL.dll': The specified procedure could not be found.
20:34:12.023: (127)
20:34:12.023: Module '../../obs-plugins/64bit/libEGL.dll' not loaded
20:34:12.138: Required module function 'obs_module_load' in module '../../obs-plugins/64bit/libGLESv2.dll' not found, loading of module failed
20:34:12.353: [browser_source: 'Version: 1.31.0']
20:34:13.558: LoadLibrary failed for 'nvEncodeAPI64.dll': The specified module could not be found.
 
Dantwire

Dantwire

New Member
TSForrest said:
Right now, I am just using the Microsoft Antivirus on my streaming PC. I hope that wouldn't cause problems with the update, or a *lot* of people will be having problems. Anything is possible, I guess. I and not too concerned with what caused it, but rather how to avoid it and how to fix it. I am a big fan of OBS. I'm just a little frustrated, because this has interrupted my channel, stream, and community, and they are all very important to me. I just want to get it fixed, and avoid having this problem in the future. I imagine it is possible that the websockets plug-in could have caused the update to fail in some way. Maybe it was moving files to a new location, and the error happened when it got to the websockets plugin? I don't know. Would you recommend uninstalling all plugins before updating, verifying the update succeeds, then trying to reinstall any additional plugins after the update? I don't want to be stuck using this version and never be able to update. I am now trying to verify which files in which locations are actually being used. I launched the 32-bit version of OBS after the install failed when I was prompted to update when I originally launched the 64-bit version. It prompted me to update a second time, but this was after having trouble with the failed update. Which run of the update put the files in the wrong locaiton is something I am not sure about, but I now have two of all the main files, including the 64-bit main exe's. One in the "C:\Program Files (x86)\obs-studio\bin\64bit" folder, and one in "C:\Users\user1\AppData\Roaming\bin\64bit" folder. I am able to get back to using version 20.1.3, but I don't want to break it by trying to get rid of the duplicate files.
Click to expand...

You can fixed go on %appdata%obs-studio\updates and then run the updater.
 
TSForrest

TSForrest

New Member
I removed the "bin", "data", and "obs-plugins: folder from my "C:\Users\User1\AppData\Roaming" folder, leaving the "obs-studio" folder the only OBS-related folder in that location. I then downloaded the complete insatll for OBS 21.1. After running the install to the same location as my OBS Studio 20.1.3 installation ("C:\Program Files(x86)\obs-studio", for me), I made sure to *uncheck* the "Launch OBS-Studio" checkbox after the install completed. After exiting the successful install. I ran the automated update for the OBS Remote 4.3.3 plug-in, which is NOT compatible with any version of OBS Studio *before* this latest version (OBS Studio v21.1). After running the OBS Remote Update, I was able to launch OBS without any issues. I have no idea what caused the errant OBS Studio folders to be created in my roaming profile folder, but whatever happened, it did not happen this time around. I did not do anying to prepare for this, other than removing the errant folders, and backing up my existing install of OBS Studio 20.1.3. From what I can tell, something caused the errant folders to be created. Then, when I ran the update, it seemed to update some files in the correct locations, but then the other files were updated in these duplicate locations. I determined this by checking file created dates, modified times, and versions in files that have signatures. I still have no clue what caused this. I would think it was an errant folder drag or something like that, if it was one folder, but I had 3 errant folders. It still could have been something stupid that I did to cause it, but regardless, it is working fine now.
 
You must log in or register to reply here.
Top