Dominions II: Technical/Hardware Issues

[Grymnyr]

Stunning. I tried it the hard way. The patch ran successfully, thanks.
Now, about adding MODS and MAPS...can this only be done via terminal as the "finder" doesn't allow viewing beneath the dominions2.app itself?

[Johan K]

Again, right clicking should give you that option.

[Zweiblumen]

Dominions 2.16
Mac OS X
Powerbook laptop (not sure the video card)
SDL version that shipped with the game.

In windowed mode my mouse y coordinates seem to be inverted. Is this an SDL or Dominions issue, and is it going to be addressed? Windowed mode is unplayable like this.

Thanks

[Alneyan]

One command switch seems to address this issue (from the relevant text file in /doc):
" --badmouse Inverts y-coords in windowed mode. Cures SDL bug on Mac OS X"

[djo]

What version of OS X are you using?

If you're not comfortable poking around in application packages, implementing that fix is a bit of a pain.

[Zweiblumen]

I'm running 10.3

I'm comfortable enough with technical things, but I'm not sure how to add command switches to the launch path...can someone describe how to do that?

[djo]

10.3, odd. I wonder if it's also hardware linked.

OK: I don't have time today to go into great detail, and I'm not in front of my Mac to check things, but here goes:

- if you right-click or control-click on an application, most will give you a "show package contents" option which lets you see into the application's guts

- (I think you need to install custom maps this way in dom2 as well--I forget)

- once you're inside the dom2 app, you can see the actual executable application and figure out its full path

- then, from the Terminal application, you can run the app by typing the full path to the executable (just like in Linux); at this point you can add command-line options

- if it works, you can then (if you are ambitious) write an Applescript to start the game with the switches, and you can save the Applescript as a double-clickable application itself

One still wonders why you'd see this issue, though...I would have thought that if you're running 2.16, it would be far behind you.