Dominions II: Technical/Hardware Issues - Page 7

djo · #61 April 15th, 2006, 12:15 PM

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.

Zweiblumen · #62 April 15th, 2006, 01:14 PM

Hmm, I got that far, but apparently when I run the app the 'normal' way some other switches get enabled in addition to badmouse, because if I try to just run the app from the terminal I get all sorts of errors. I'm having a hard time figuring out what the 'default' switches that get passed when I just do an 'open' on the app are.

Hmm

Zweiblumen · #63 April 15th, 2006, 01:20 PM

A ha! It was a working directory thing. Apparently it won't work to execute ./dominions2 from deep inside the contents. I had to go back up to the parent folder level, and then give it a few directories worth of path, but now I can play in windowed mode. Excellent.

Thanks so much! Now I have to figure out how to stop getting wiped off the map

Daynarr · #64 April 15th, 2006, 01:22 PM

Quote:

Zweiblumen said:
Now I have to figure out how to stop getting wiped off the map

Thats the fun part.

Alneyan · #65 April 15th, 2006, 01:30 PM

Odd that it wouldn't work while in the same directory.

No flags are passed by default, so doing an "Open" just means "Run the application" without any other information. Some programs do pass flags, in a way, as their default behaviour may vary depending on your privileges. It isn't very common, though.

Tuna-Fish · #66 August 4th, 2006, 04:12 AM

I'm running ubuntu linux, and after installing and updating to latest when I try to run dom2 it says Code:

dom2: error while loading shared libraries: libSDL-1.2.so.0: cannot open shared object file: No such file or directory

Even if I have installed sdl, tried reinstalling it too. Can anyone help?

Tuna-Fish · #67 August 5th, 2006, 04:17 PM

Solved that one myself, of course you need to have the 32-bit libs for dom2. Kinda misleading names there when running 64bit system.

shovah · #68 August 28th, 2006, 09:45 AM

I know this shouldnt be a problem with dom3 right round the corner but whenever i start up dominions i have a problem. Recently got windows XP and has happened since i installed it, dom2 loads slowly and once its up, while the mouse works fine, i cant do anything. Can select network/new game ect and the background dosnt move.

As ive said it isnt a big problem with dom3 around the corner but i dont want to have to drop out of my current mp games.

Johan K · #69 August 28th, 2006, 10:48 AM

Try upgrading your graphics driver to the one supplied by your video card manufacturer. This is necessary to get decent OpenGl support for ATI and Nvidia.

Jamie · #70 October 17th, 2006, 01:41 PM

This seems to be related to the above. In order to stop myself playing too much I tend to periodically wipe the game. On the last two reinstalls the game has run *grindingly* slow so as to be unplayable. I'm not talking about the battles, I don't even go there, its on everything. Even the start up screen. Just maximising the window makes the CPU grind away.

I'm running this on a Laptop with SuSE 10.1 that has an ATI Radeon 9000 in it. I have recently installed the new driver in this from ATi which to the best of my knowledge is running fine (e.g. fglrxinfo). It made no difference.

Note also the dom2 has run absolutely perfectly on this machine in the past. Indeed when I had Suse 9.1 on it I managed both states - perfect and grindingly slow without any significant system changes in between.

Hope someone can clarify this or at least give me a systematic way of uncovering the problem.

Jamie