[Solved] Newbie problem... (can't find DLL)


23-09-2008 03:44:51

Anyone care to make my day :) ?

Trying to setup and run my first MOGRE app and can't seem to get around this problem. I've been following the 0 Tutorial and everything seems peachy, but can't seem to get past this error:

22:38:01: Loading library C:\MogreSDK\bin\Release\RenderSystem_Direct3D9

22:38:01: OGRE EXCEPTION(7:InternalErrorException): Could not load dynamic library C:\MogreSDK\bin\Release\RenderSystem_Direct3D9. System Error: The specified module could not be found.
in DynLib::load at ..\src\OgreDynLib.cpp (line 80)

I've installed the DX SDK... all the other files seem to read in and load, but can never find this one. Any idea why? RenderSystem_Direct3d9 is definately sitting at that path.

Any suggestions/nudges in the right direction would be greatly appreciated, I am eager to play around with this.


*** EDIT:

Sorry, should mention I'm running on XP SP2, using Visual C# 2008 Express Edition... and I cannot get the samples in the Release or Debug folders to work in the MOGRE folder either..


23-09-2008 06:25:34


You must have the plugins.cfg in your app folder and the path in it fix in the good way.

That dll is in the plugins folder.


23-09-2008 14:45:10

Plugins.cfg is definately in the app folder, I know this because it complains when it is not there.

I am pointing the plugins.cfg file to: "C:\MogreSDK\bin\Release\"

That _is_ the correct place... correct? At least that's where the DLL exists as far as I can see...

Any ideas? I've been reading other posts with ALMOST the same problem but they seem to get past the 'cannot find' problems, and land in the 'incorrect configuration' problems. I wish!


23-09-2008 16:41:22

Hi Blackweb,

i think the most suitable way would be to copy the named dll to your bin/debug - bin/release folder. If that wouldnt work, you can use a tool named "process monitor" to find out where your application looks for the dll.

Hope that helps,


23-09-2008 23:20:48

Thank you for all your help everyone.

Turns out a simple mistake (stupidity) was to blame. I had installed the .net SDK, not the DX SDK :)

oh, how I laughed, how I cried.

Lessons learned: not much...