Mac OSX demo wont launch! Help

[HJ]

Originally posted by Johan K:
You need to install the SDL lib before running Dominions.

Johan , I sent you a reply through pm.

[Vodalian]

I've finally got the demo running in a window with an amazing frame rate of 1 fps. However, there is one serious problem left. My mouse "cursor" seems to be moving up when I move the mouse down and down when I move the mouse up.

[ October 29, 2003, 18:24: Message edited by: Vodalian ]

[Johan K]

That was weird, unless you hold the mouse upside down at least. If you haven't done so already try to update to the latest Version of SDL. Link three Posts down.

[ October 29, 2003, 20:30: Message edited by: Johan K ]

[Senaca]

Yea, followed the link to the framework, installed it and the game runs fine (for 10 minutes at least) Thanks for the help! Perhaps you should sticky this thread for all Mac Users.

That being said the framework was very small, I don't really see the advantage in leaving it out. I would integrate it into the demo and repost.

Cheers,
Ron

[Johan K]

Ooops, seems like we have missed an important part of the demo installation instructions. The reason SDL isn't included is to make the download smaller and people who have played other SDL games (like dominions I) already has it installed.

You need to install the SDL lib before running Dominions. It can be found here:
http://www.libsdl.org/download-1.2.php
Download runtime for MacOSX.

The dom2demo_osx.tar.gz file should be 73730190 bytes large.

Sorry for the missing instructions!

[ October 29, 2003, 17:23: Message edited by: Johan K ]

[Cameroon]

Originally posted by Senaca:
That being said the framework was very small, I don't really see the advantage in leaving it out. I would integrate it into the demo and repost.

Cheers,
Ron

That's exactly the same thing I was thinking. The download is already 70 megs, the SDL framework is tiny by comparison. I'd much rather have to d/l even a few extra megs to get the demo than to have to go get another piece of software

[Johan K]

Well, I guess we could change it if all the Mac Users prefer to have it bundled inside the application. It might make it harder to upgrade to new SDL Versions though

*Edit: Anyone who knows the magic location of frameworks inside app bundles, please let me in on the secret

[ October 30, 2003, 09:33: Message edited by: Johan K ]

[iRichard]

Hello

1) SDL package : you should not include it INSIDE the app but WITH the archive. (already have several "embedded" app with different SDL Version)

2) magical location : download an "embedded" Version of Battle for Wesnoth from www.libsdl.org and look inside.

3) is there a battle simulator in the full Version of Dom2 ?
(which I pre-ordered)

PS : This is my first post on this board.

[ October 30, 2003, 14:41: Message edited by: iRichard ]

[Cameroon]

Originally posted by iRichard:
Hello

1) SDL package : you should not include it INSIDE the app but WITH the archive. (already have several "embedded" app with different SDL Version)

2) magical location : download an "embedded" Version of Battle for Wesnoth from www.libsdl.org and look inside.

3) is there a battle simulator in the full Version of Dom2 ?
(which a pre-ordered)

PS : This is my first post on this board.

The reason that I prefer to have SDL embedded is so that I know my apps will work no matter what Version of SDL they were built against.

How much would it suck if you had purchased two games, but you had to swap which Version of SDL was installed because one was built against an older Version of SDL and didn't work correctly with the new Version?

It's not that difficult to create an updater that replaces the SDL inside the application bundle. I think it's a great development time-saver, too, because you don't have to worry about "Well, what if the user has a different Version of SDL installed?"

[Sithrandel]

Hello there... I have to say that I am a convert to embedded Mac libraries, for a number of reasons....

1) Mac Users chose a Mac because they are easy to use. They expect to double click a program and it to run. If it doesn't, clearly it is the fault of the programmer. Not theirs because they forgot to install something else. [Even worse is when you suggest they compile something.] I am of the same opinion, I love my Mac because usually I only have to dive beneath the hood when I want to.

2) Because including the SDL framework merely puts a copy into the internal Frameworks folder and embedded can easly be made unembedded if someone wants to make it work with a system copy. The chances are greater that someone who is going to want to do that can understand remove instructions than that a true novice will understand how to add it.

3) The libraries are small compared to data / library files.

4) You can always produce embedded and non-embedded Versions (if you use the Apple dev tools you can easly compile both in a single pbxbuild instruction).

5) When Battle For Wesnoth had only a non-embedded Version there were lots and lots of Queries about "it won't launch". Once there was an embedded Version this vanished. Part of the problem is that the app won't run and say "can't find SDL"... it just won't run.

6) The official distribution can include a copy of SDL which is definitely compatible with the build.

All in all the best option is the dual embedded and non-embedded Versions, with the obvious choice being embedded and instructions in the readme on how to remove the embedded library.

By the way, I would suggest for the same reasons, that a fix is made to the windowed mode on OSX even if the inverted cursor co-ordinates are SDL's fault.

Dominions II is a superb game, so let it shine