DllNotFoundException

You probably saw my post as well on another thread. Here's my specs, and a recent list of changes/potential causes:

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828-1532)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: X58A-UD5
Processor: Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz (8 CPUs), ~3.1GHz
DirectX Version: DirectX 11
Card name: NVIDIA GeForce GTX 650

Unity Version 4.3.3f1

Recent changes:
- Adding and removing/hiding/reactivating Rift and Non-Rift cameras
- Added binaural audio package (removed it, no difference)
- Changing from deferred to forward rendering and back again

Thanks,
Jay

I started getting these too when I updated the Microsoft Visual C++ packages. Seems like I downloaded the wrong version (x86 or x64, don't remember which) and when I uninstalled it and downloaded the other everything started to work again.
http://www.microsoft.com/en-us/download/details.aspx?id=40784

Edit: Seems like the C++ packages aren't the problem (or the only problem). It's also about the new Binaural audio integration which JayExbleative mentioned too.

With x86 and x86_64 folders in Plugins folder, the binaural audio seems to work but Rift (and Sixense Hydras) won't. The x86 folder contained only the 3Dception binaural audio DLL, and after deleting that whole folder the Rift and Hydra DLL works (but seems like the audio doesn't).

With x86 and x86_64 folders in Plugins folder, the binaural audio seems to work but Rift (and Sixense Hydras) won't. The x86 folder contained only the 3Dception binaural audio DLL, and after deleting that whole folder the Rift and Hydra DLL works (but seems like the audio doesn't).

Sweeeeeet, thanks, that fixed it for me. I thought I'd deleted it all, but once I removed it from the x86/64 folders everything is working again.

Hi folks,

Varun from Two Big Ears here (3Dception binaural plugin). Are you still having issues getting the Oculus plugin + 3Dception to work? It seems ok on multiple test systems here. Let me know if you are still having an issue and I can help troubleshoot. You could even email support@twobigears.com with details, and we can post a response back here if there's an issue that needs fixing.

Let me know!

"cybereality" wrote:
Hey guys, I am going to have someone look into this since it has seemed to effect more people.

Can you please list your PC specs (especially video card), operating system, and version of Unity?

Thanks,

Andres

3.6 GHz i7, 64bit Win7, Gigabyte X58-USB3, AMD Radeon HD 7870
Unity 4.3.2f1

Interesting. I will see if this helps pinpoint the problem.

Update:

I created a new Project + scene, and everything was working. Perhaps there is a bug that can occur when compiling during import?

Edit:

Created yet another project (actually, working an old project file), and got the DLL not found exception again. In the other thread I found the "fix", copy the OculusPlugin.dll file into C:\Program Files(x86)\Unity\Editor

------------------
System Information
------------------
Time of this report: 3/14/2014, 23:14:40
Machine name: ******
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828-1532)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 08/26/10 17:43:02 Ver: 08.00.15
Processor: Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz (8 CPUs), ~3.1GHz
Memory: 12288MB RAM
Available OS Memory: 12280MB RAM
Page File: 4049MB used, 20506MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Sound Tab 3: No problems found.
Input Tab: No problems found.

-------------
Unity Version Info
-------------
Unity Pro (demo) 4.3.4f1

Hey guys, I came across this a few months ago and was able to solve it by changing the resolution size of the Game window in the editor. I'm not at my workstation so I can't check it to be sure but if I remember correctly that was the "fix" that worked for me. Hope that helps!

Hi all,

I was able to reconstruct this problem and have fixed it in the recent version of 3Dception. It *might* be related to what some of you face:

Unity by default seems to have a slightly undefined behaviour when loading plugins on 32 bit Windows/Linux. If the DLL is placed directly in the 'Assets/Plugins' folder it will pick it up with no problems reported. On the other hand, if a user places the DLL in 'Assets/Plugins/x86', it will search for the 32 bit plugins in that folder and NOT the parent 'Plugins' folder.

With 3Dception we had created the x86 folder with our DLL placed in it. On running Unity on a 32 bit computer (or the Unity Editor on a 64 bit computer) it would therefore find the 3Dception DLL and not the Oculus dll. We've fixed this by removing the x86 folder. Some plugin developers use the x86 folder so it might be worth looking into if you face this issue.

Hope this makes sense? If not, I'd be happy to elaborate.

"ntkeep" wrote:
Hi all,

I was able to reconstruct this problem and have fixed it in the recent version of 3Dception. It *might* be related to what some of you face:

Unity by default seems to have a slightly undefined behaviour when loading plugins on 32 bit Windows/Linux. If the DLL is placed directly in the 'Assets/Plugins' folder it will pick it up with no problems reported. On the other hand, if a user places the DLL in 'Assets/Plugins/x86', it will search for the 32 bit plugins in that folder and NOT the parent 'Plugins' folder.

With 3Dception we had created the x86 folder with our DLL placed in it. On running Unity on a 32 bit computer (or the Unity Editor on a 64 bit computer) it would therefore find the 3Dception DLL and not the Oculus dll. We've fixed this by removing the x86 folder. Some plugin developers use the x86 folder so it might be worth looking into if you face this issue.

Hope this makes sense? If not, I'd be happy to elaborate.

Ahhh - cool! Thanks mate, this just repaired my build. In my case it was adding the current Leap Motion Beta. :)