Non programmer trying to set up Mogre

Ttheartist

08-01-2010 22:47:44

Hello there everyone

I looked everywhere to try and find my specific issue with setting up Mogre 1.4.8 on my PC.
Anyways here it goes. I followed the set up guide in tutorial Zero to the letter and I am getting errors.
The errors vary depending if Im using Visual Studio 2010 Beta 2 or Visual C# 2008 Express
Here are the errors:

VS 2010:
When compiling I get a could not load file because file could not be found

VS 2008 Express:
When compiling I get a could not load file or assembly "Mogre" or one of its dependencies...An attempt was made to load a program with an invalid format

Any help would be very much appreciated.

Meharin

09-01-2010 09:44:40

Are you on a 64 bit machine and a 64-bit OS? I am and working with 1.6.4 and I have seen Invalid format errors, as well as broken solution paths. I don't know if this helps you, but I have fixed both of these by making sure I never build in Visual Studio with "Any CPU" build target selected (a combobox in the VS toolbar next to Debug/Release), and always change it to x86 if that's one of the options (needed to do this in the MogreSamples solution, and somewhere else I think. Some solutions only have the "Win32" option though, which I think should be fine.)

Ttheartist

09-01-2010 17:20:06

Currently I am running windows 7 64-bit...I see these tool bars that you are talking about but in both versions they are set to debug in x86 code.

Beauty

13-01-2010 13:22:31

Welcome to the Mogre forum :D

The Mogre version 1.4.8 is outdated.
Please use the 1.6.x version.

Since October we build up a new SDK for Mogre from the scratch.
It should make more easy the life, especially for newcomers.

The download links are in the first post of the thread Mogre 1.6.5:
viewtopic.php?p=64380#p64380

The depencies you can find here:
http://www.ogre3d.org/wiki/index.php/Mo ... pendencies
Alternatively the SDK installer shows you the download links.

The examples of the SDK are for Visual Studio 2008. I suppose you can convert them to VS 2010.


There still can be problems with the SDK.
So we are happy for problem/bug reports and improvement ideas :wink: