en:games:star_trek_armada_1:known_problems
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:games:star_trek_armada_1:known_problems [2022-04-06-15-49] – [Too High Resolutions Crash the Game] 7saturn | en:games:star_trek_armada_1:known_problems [2022-07-09-20-52] (current) – [The Auto-Assimilator Soundeffect does not Cease] 7saturn | ||
---|---|---|---|
Line 46: | Line 46: | ||
++++ | ++++ | ||
===== Too Long System PATH Variable Crashes the Game on Startup ===== | ===== Too Long System PATH Variable Crashes the Game on Startup ===== | ||
- | When using the unaltered CD version on a modern system, it is very likely, that the game will never start. One of the reasons is a too long //PATH// variable of your Windows system. On modern Windows this is very common. On old Win9x or ME installations this was hardly ever any issue. You could of course try and remove unneeded parts of the //PATH// variable, but it is actually not necessary to alter your system settings. Simply use the GOG version | + | When using the unaltered CD version on a modern system, it is very likely, that the game will never start. One of the reasons is a too long //PATH// variable of your Windows system. On modern Windows this is very common. On old Win9x or ME installations this was hardly ever any issue. You could of course try and remove unneeded parts of the //PATH// variable, but it is actually not necessary to alter your system settings. Simply use the GOG version |
+ | ===== Too Much RAM Crashes the Game on Startup ===== | ||
+ | Similar to the above problem with the system' | ||
===== Game is Visible But Cannot be Joined ===== | ===== Game is Visible But Cannot be Joined ===== | ||
This problem presents itself in the following way: One player opens a match on his computer. Another waits for the game to show up, which it eventually does (it may take a moment to find it). But when actually trying to access the match, the game claims, that the match has gone in the meantime (>> | This problem presents itself in the following way: One player opens a match on his computer. Another waits for the game to show up, which it eventually does (it may take a moment to find it). But when actually trying to access the match, the game claims, that the match has gone in the meantime (>> | ||
===== The Auto-Assimilator Soundeffect does not Cease ===== | ===== The Auto-Assimilator Soundeffect does not Cease ===== | ||
- | It happens (rather often) that the [[auto-assimilator|special weapon of the Assimilator]] unit of the Borg is used, but once it is not active any more, its sound effect still continues indefinitely. This can easily be stopped by shortly opening the game's menus ('' | + | It happens (rather often) that the [[auto-assimilator|special weapon of the Assimilator]] unit of the Borg is used, but once it is not active any more, its sound effect still continues indefinitely. This can easily be stopped by shortly opening the game's menus ('' |
===== Mouse Pointer Stays in the Center of the Screen ===== | ===== Mouse Pointer Stays in the Center of the Screen ===== | ||
It happens from time to time, that the Windows mouse pointer is visible at the center of the screen and won't go away on its own. This can also be solved by opening the menus for a moment ('' | It happens from time to time, that the Windows mouse pointer is visible at the center of the screen and won't go away on its own. This can also be solved by opening the menus for a moment ('' | ||
+ | ===== Game Ends the Vendetta Mission with a Loss for For No Reason ===== | ||
+ | Reaching the last wormhole in mission 3 of the [[factions# | ||
{{page> | {{page> |
en/games/star_trek_armada_1/known_problems.1649260199.txt.gz · Last modified: 2022-04-06-15-49 by 7saturn