More Mac OSX problems

[Chimpman]

Nope, thought I could figure it out, but I'm totally lost. If anyone can tell me how to set the switch on a mac app I'd really appreciate it.

[Chimpman]

Nope, thought I could figure it out, but I'm totally lost. If anyone can tell me how to set the switch on a mac app I'd really appreciate it.

[Kristoffer O]

Start a terminal window and write something like this.

$ cd Desktop
$ dominions2.app/contents/MacOS/dom2 -w

This assumes you have put dominions2 on your desktop.

[Etaoin Shrdlu]

Originally posted by Chimpman:
I got the game to work just fine on my PC, but I'm having trouble getting it to work on my mac. I searched through other Posts in this forum and followed the instructions for installing SDL and the 2.08 patch. Here is the error message that I get in the console log:

mkdir: No such file or directory
SDL_SetVideoMode failed: Failed creating OpenGL pixel format
NÂgot gick fel!
Failed to init OpenGL
NÂgot gick fel!
Failed to init OpenGL

Does anyone have any ideas. I am primarily a PC user, but my mac is an ibook. I'm looking forward to playing Dom2 wherever I might go ;D.

Thanks in advance for any help you can give.

See the Last handful of Posts in the thread I started... when I got it to work, I felt like the cat that had extracted a mouse that was hiding in his own ear... at the same time so clever for looking there and so dense for not noticing the unbalanced weight on his head.
Command-click on the dominions2.app file, then control-click. You will see the "Show package contents" prompt. This was the part I was missing the whole time. Go through the Contents/Resources line. Anything in the patch that has an Older Version in the original? Replace from the patch. It'll ask for your user password at least once.
Now for the key move. Contents/MacOS. There will be a Unix executable. Take the Unix executable from the patch and dump that in replacing the original again. Poof. Done. Just don't play Jotunheim Utgard.

[Chimpman]

Thanks Kristoffer, that did the trick. See below for more details though.

Etaoin: I read those threads and they were very helpful, but I think we are having slightly different problems. If I understand this right my ibook has a res of 800 600, and dom2 has a default res of something else (something incompatible). So when I tried to run on my ibook the sdl barfs.

I am seeing some funny things:
If I use this command line
dominions2.app/Contents/MacOS/dominions2 -w

the app starts up ok and I get the entry screen (after having already put in my key). However if I mouse over the "Create a new God" option, the "Quit" option highlights. If I mouse over "Create a new Game" then "Map Editor" highlights. It's like the x coordinates are flipped. I have to click "Quit" in order to "Create a new God"
I haven't actually gotten into the game yet, but all of the selection boxes are working like this (with the x-axis flipped in some way). This is very strange.

If anyone has seen this or has any idea of what's going on, please let me know. I can provide more information if needed.

[st.patrik]

Originally posted by Chimpman:
Thanks Kristoffer, that did the trick. See below for more details though.

Etaoin: I read those threads and they were very helpful, but I think we are having slightly different problems. If I understand this right my ibook has a res of 800 600, and dom2 has a default res of something else (something incompatible). So when I tried to run on my ibook the sdl barfs.

I am seeing some funny things:
If I use this command line
dominions2.app/Contents/MacOS/dominions2 -w

the app starts up ok and I get the entry screen (after having already put in my key). However if I mouse over the "Create a new God" option, the "Quit" option highlights. If I mouse over "Create a new Game" then "Map Editor" highlights. It's like the x coordinates are flipped. I have to click "Quit" in order to "Create a new God"
I haven't actually gotten into the game yet, but all of the selection boxes are working like this (with the x-axis flipped in some way). This is very strange.

If anyone has seen this or has any idea of what's going on, please let me know. I can provide more information if needed.

This happens in windowed mode for me (iMac user). But not in full screen. I did report the bug - it seems it is a bug since you also have experienced it.

[Chimpman]

This happens in windowed mode for me (iMac user). But not in full screen. I did report the bug - it seems it is a bug since you also have experienced it.

That's unfortunate for me, since I can't seem to get this thing to run in full screen mode. Darn. It's a little frustrating.