Known Bugs

Q · #1 August 6th, 2005, 03:08 PM

One more intel bug:
Intel sabotage and technological (research) sabotage will destroy randomly projects in the intel/research list.
Because usually you do not divide points but concentrate all points to the first projects in the list, there is a good chance, that a project is destroyed which was not yet started. Therefore the target empire looses nothing at all and the attacker wasted his intel points on the attack. The chance for this is greatest if the target empire fills the list of intel or research to the maximum of 12 projects.

Ed Kolis · #2 August 6th, 2005, 05:32 PM

This is probably a bug in Windows, but you think it might be possible to have the game explicitly hide the log window when a combat replay is displayed? In Windows it works just fine, but in Linux + WINE the log window stays on top, making combat replays almost useless

Oh yeah, and maybe something about the minimize/alt-tab causing the game window to become really tiny when you restore it... again, probably a Windows bug that let the SE4 bug slip through unnoticed, but it does mess things up in Linux

Fyron · #3 August 6th, 2005, 05:57 PM

Wouldn't that be a bug in Wine, not in Windows? Wine isn't properly handling the layering of the windows, it would seem...

Using the Windows GUI API is not a bug... It is different from the Linux GUI API, but this does not make it a bug.

Will · #4 August 6th, 2005, 06:48 PM

And #64. It's a bad one, confirmed with DarkAnt as reproducable.

There is a way to cause the game to partially crash, but not exit. An access violation error is thrown, and the game ends up showing you the empire of the last player on the list. Buttons do not work ("order" buttons are clickable, but do nothing), but you can use F2-F12 to get at the various info screens, can navigate the galaxy map, look at individual ships, etc. As you could imagine, this can quickly kill a multiplayer game.

I'm sending a bug report to Aaron with the specific details on how the crash occured. I think everyone understands my reasons for not publicly posting the details on how to reproduce this. DarkAnt and I hope it's just mod/shipset errors that are causing the problem, and it's not something that is exploitable in general. But it's better to be safe.