Simon.Anderson Posted March 17, 2017 Share Posted March 17, 2017 Hi, I'm currently trying to load the AppVive plugin but am getting the following error: ---- Plugins ----Loading "AppVive_x64d.dll"...EnginePlugins::addPlugin(): can't load "AppVive_x64d.dll" library 126 - I'm loading via these lines in the config: <item name="render_stereo" type="int">5</item> <item name="extern_plugin" type="string">Interface</item><item name="extern_plugin" type="string">AppVive</item> - The interface plugin loads fine - I have the dll in the appropriate place - I don't have problems loading other plugins Is there something obvious I'm missing here? Thanks, Simon Link to comment
Simon.Anderson Posted March 17, 2017 Author Share Posted March 17, 2017 Ok other plugins seem to be having the same problem - could be looking in the wrong location? The plugin dlls are sitting in the same directory as the exe Link to comment
silent Posted March 17, 2017 Share Posted March 17, 2017 Hi Simon, It seems that some dlls are missing that are required to launch AppVive dll. You can use dependency walker to find out which ones. Probably, you just need to install SteamVR first. How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
Simon.Anderson Posted March 20, 2017 Author Share Posted March 20, 2017 Hi, I've Installed Steam and SteamVR, the unigine sample is working fine - just not my app. I copied all the Unigine lib dependencies into my exe directory and the error message has changed: ---- Plugins ----Loading "AppVive_x64d.dll"...EnginePlugins::addPlugin(): can't load "AppVive_x64d.dll" library 193Loading "Interface_x64d.dll"... The key here seems to be "library 193". These number don't mean much to me - without trouncing through the unigine source is there any way I can find out what this dependency is? I've looked at dependency walker but it's not trivial to figure out which dlls are missing. Thanks Link to comment
silent Posted March 20, 2017 Share Posted March 20, 2017 Hi Simon, 193 error usually means that you are trying to load wrong library (for example, msvcp120.dll is 32 bit inside bin directory instead of x64). If everything is working in our application, there is probably just some kind of mess with dlls in your application directory. Unfortunately, there is no really easy way to find out what happens here without Dependency walker help. How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
Recommended Posts