GregH
06-12-2005 10:17:13
I am new to OGRE but even so I see a lot of promise and scope. I have also spent several days (not wanting to bother you folk) in trying to set up a simple VB.Net 2003 project without success. I thought it was my fault at first, but after reading AlbertS's message about creating the DotNet Wrapper (Tortoise & Swig!!) I realise that I could never have guessed my way through the compilation process. In fact I nearly gave up.
And now to the sticking point - no matter which DLL's I reference (downloaded pre-built or home compiled) I cannot access the correct namespaces via Imports in my VB.Net project. The Wiki (I'll figure out what that means one day) says to reference OgreDotNet.dll, OgreDotNet.CeguiRenderer.dll and CeguiNet.dll.
The 7 dll's that I now have available (and don't include some above) are:
CeguiBindings.dll
CeguiDotNet.dll
Math3D.dll
OgreBindings.dll
OgreBindings_Cegui.dll
OgreDotNet.Cegui.dll
OgreDotNet.dll
...and when I import the 3 stated refs I do not get the Ogre namespace...and where is OgreDotNet.CeguiRenderer.dll ??
I was hoping that OGRE would be more user-friendly than raw DirectX, but I'm having a cow of a time getting to an empty launch pad. Can someone please shed some light - once I get past these issues, I will contribute lots. Perhaps you could zip a ready-2-go empty VB.Net project?
Kind regards, Greg.
And now to the sticking point - no matter which DLL's I reference (downloaded pre-built or home compiled) I cannot access the correct namespaces via Imports in my VB.Net project. The Wiki (I'll figure out what that means one day) says to reference OgreDotNet.dll, OgreDotNet.CeguiRenderer.dll and CeguiNet.dll.
The 7 dll's that I now have available (and don't include some above) are:
CeguiBindings.dll
CeguiDotNet.dll
Math3D.dll
OgreBindings.dll
OgreBindings_Cegui.dll
OgreDotNet.Cegui.dll
OgreDotNet.dll
...and when I import the 3 stated refs I do not get the Ogre namespace...and where is OgreDotNet.CeguiRenderer.dll ??
I was hoping that OGRE would be more user-friendly than raw DirectX, but I'm having a cow of a time getting to an empty launch pad. Can someone please shed some light - once I get past these issues, I will contribute lots. Perhaps you could zip a ready-2-go empty VB.Net project?
Kind regards, Greg.