|
Post by caelunniveus on Nov 17, 2011 16:10:39 GMT -6
I downloaded and installed a copy of Starsiege (thankyou Snow), and I do seem to be enjoying the game. The Human campaign and Multiplayer run smoothly, even if it has a small glitch with the toolbar (temporally fixable).
However, the Cybrid campaign is unplayable, in a literal sense. Starting the first level everything seems ok until player control is allowed. At which point, I find my HERC "bouncing" in a way that makes me assume I'm stuck halfway in the ground, I have no sound besides the animal's com-chatter, I cannot move except forward and backward (and even then no walking animation, I only knew I was moving from looking at the map), and it seems that while I could fire my weapons they don't do anything, and vice-versa.
If anyone else has had this problem, what would be the fix?
|
|
Snow
Site Member
Starsiege: Retribution
Posts: 234
|
Post by Snow on Nov 17, 2011 17:20:04 GMT -6
Hrm. Unfortunately I cannot recreate these circumstances. I've heard tell that the first mission can glitch out, though I have never experienced it for myself. Either re-starting the campaign or a series of images/video may help.
As for the toolbar, that should be a mere case of resolution. As I run Vista, I use Basic (instead of the standard Aero), but running Starsiege with the "Disable Desktop Composition" amounts to the same thing.
|
|
|
Post by caelunniveus on Nov 17, 2011 19:14:50 GMT -6
I'll try "rebooting" the mission again. See if that does work.
As for the toolbar, which I didn't explain because it isn't a big deal, Whenever the game switches between gameplay graphics and the menu I get the tool bar at the bottom popping up, and forcing a tad of the top of my screen off. I "fix" this simply by using the auto-hide function on the toolbar, and I could also fix it by pressing the windows key and going back into the game (though the second only fixes it for until it happens again).
|
|
|
Post by Mneme on Nov 17, 2011 19:47:44 GMT -6
This is a pretty consistent problem for me as well; I resolve it by, as DS noted, simply rebooting Starsiege until the damned thing behaves. It should after a few attempts. I'd love to determine the actual cause of this so we can fix it. Anyone with any ideas, let me know. Good luck.
|
|