This is a list of functional bugs (bugs that relate to game functionality and not game stability) reported by players in this and other threads. Please feel free in this thread to comment on existing bugs or report more.
Additionally, I have a list of "oversights". These are items that, while not necesarily bugs, are functionality that either doesn't make sense, or is missing.
The color code is as follows:
- The bug exists in the current game version
- The bug existed in a previous version, and it is not yet known if it exists in the current version
- The bug has been corrected in some patch. The patch which corrects the bug will be listed individually.
Please note: this thread is NOT for complaints. It is for dispassionate discussion of game bugs and quirks.
Functionality Bugs
- 'R' list (owned items): If you are on a tab with more than a screen of information, scroll to the bottom of the list, then switch to a tab where there is less than a full screen of items, then the list is scrolled off the top of the screen even though it would all fit without scrolling. Also, the indicator on the right that shows where you are in a scrollable list dissappears, so there is no visual indicator that you are scrolled down. To the eye it just looks like all your bases have dissappeared, for example.
- When the ecliptic projecter is activated while in a turret, the ecliptic is projected wrongly. The ecliptic seems to be projected parallel to the normal of the turret rather than on the actual ecliptic of the sector.
Update: The ecliptic is not projected parallel to the normal of the turret, as I first thought, but is projected as if the turret were facing the direction the ship is pointing.
Update 2: This is listed as fixed in patch 1.2, but is not. The projector works in 1.2 the same as in 1.1 or 1.0
Update 3: The readme for the 1.2 patch was actually mistaken as to what Ecliptic Projector issue was corrected. The issue corrected was not the turret display, but the one listed here as Oversight #1 here (turning off after jumps).
- The Gamma PAC weapon is "lighter" than it's little brother, the Beta PAC. Turrets are supposed to (presumably) turn faster with smaller weapons. However, a turret will turn faster with the larger Gamma PAC than with the smaller Beta PAC. This has been verified with a stop-watch.
- If a new base is deployed by communicating to a TL while you are docked in a base, then there is severe corruption of the base deployment cut-scene. The likely cause is that the cut-scene should switch to a view external to the base, but it doesn't.
Update: This has been fixed as of version 1.1
- When viewing the console of another ship in one of your monitors, the console will show the number and type of missiles that YOUR ship has currently active.
- Turret's point themselves directly at a target who's lead indicator is far away from it. It is as if the turret and the guns in the turret are not together. The turret itself is pointing directly at the ship, while the turret's guns try to lead the target. Because of this, a turret cannot engage a target that is below its horizon, even if the target's lead indicator (where you need to shoot to hit the target) is above its horizon. More info here.
Update: Part of this is intended behavior. The "decoupling" of the gun from the camera is intended. This is actually a feature, since guns of different shot speeds in the same turret will aim themselves independantly, so they all need to be independant of the camera. Part of this is an error in my observations, as objects that are below the horizon will continue to be tracked, and will be shot at if their lead indicator rises above. My apologies to Egosoft for the mistake in my observations.
- Independant from the above bug, a turret will not always shoot towards the lead indicator. The amount of error is dependant on the vectors of the shooter and the target, and is quite pronounced. So much so that turrets without scatter-weapons have a hard time hitting massive (and slow) enemy capital ships or TL's even at close range. The odd thing is that the lead indicator seems to correctly indicate where a turret should shoot, but the turret AI is not shooting in that direction. The turret AI is, therefore, seems to be using different target lead calculations from what the lead indicator is using. More info here.
Update: I've been in talks with Egosoft on this (big thanks go to KlausM for taking the time). There is a bug with a turret's target lead indicator where it doesn't take into account the shource ship's velocity correctly. This is verified by them. However, they are suggesting that this doesn't affect automated firing from that turret. I'm not 100% convinced that there isn't still a problem with turret aiming, but I am setting this to amber for now and will do some in-depth testing to look into it.
- When an M5 undocks from an M6, the M6 loses its autopilot settings and stops.
Reported by scribble and verified.
Update: This is intended behavior, and not a bug.
- *** REMOVED *** This item is now listed as oversight #8.
- Police licenses are destroyable by enemy fire or collision damage. As these are not physical objects, but rather a purchased "authority", they should not be subject to damage.
Update: Listed as fixed in patch 1.2. Fix not yet player-verified.
- In SETA mode when the ship is trying to go through a jump gate, sometimes it will go back and forth through the gate many times as though it is not hitting the "trigger" point to actually jump. In non-SETA mode it will jump fine.
Reported by ironwill96 and verified.
Update: This is not a bug, but caused by SETA set to too high a value for your CPU to handle. Turn down the SETA multiplier in options (SHIFT + O)
- BBS Lottery: Sometimes this item does not display the previous winning number, but instead displays the variable placeholder.
Update: This was reported by Egosoft as fixed as of version 1.1, however, there are also reports by players of this behavior still appearing in 1.1.
Update 2: Egosoft has confirmed that this bug is still in 1.1. The "bugfix had a bug"
. Thanks to BurnIt! for the update.
Update 3: Fixed in version 1.2.
- This is now listed as Oversight #9
- Shields will sometimes be recognized only as a ware, and not as a ship upgrade.
Reported by ShanghaiDilly and verified.
Update: This has been fixed as of version 1.1
- If you are too close to a small asteroid when a mine is deployed there, your ship can end up getting stuck inside the mine model. More info here.
Reported by rslifka and verified.
- Many people are never hearing in-station audio announcements. More info here and here.
Reported by Dutchman and Malex
Update:Fixed in version 1.2
- In some cases, the rank progression "percentage" indicator seems to freeze at 0%. The rank may continue to rise, though it is not displayed on the personal stats screen.
Reported by Scoob and verified.
Update: This has been fixed as of version 1.1
- Transparent menus show guages underneath them, but the guages never update once the menu is in place. The cockpit's "flashy-blinky-lights" update through the transparent menu just fine.
Update: I have determined that it is not a transparency issue as I first thought. It is simply the fact that no in-ship guages are updated when any menu is displayed. This can be determined as in some cockpits, some guages are not "covered" by menus, and they do not update when any menu is displayed.
- If a station you own is under attack, it will flash red on the station list, sector map and, if you are flying a ship in range, on your gravidar. If you destroy that station's attackers, it will cease to flash red on the sector map and station list, but will continue to flash red on the gravidar. It will do this until the sector is left and re-entered, on until you dock (in a non-capital ship) and undock.
Update: Oversight #9, which is similar to this bug, is listed as fixed in version 1.2. Status of this bug is "unknown" until it can be verified if it still exists in 1.2.
- If any factory in the entire X universe produces a resource at or under your maximum "buy" price, then your factory's transports will never buy that resource from any trading station, even if the trading station is closer and cheaper. More info here and here.
- In a multi-monitor setup, a cutscene will span both physical monitors.
Reported by GnatB
- In a multi-monitor setup, on initial load the initial menu is centered between the two physical monitors. Once you select a submenu, it stretches across both physical monitors. Once you exit the menu and come back to it, it is on the primary menu as per oversight #5.
Reported by GnatB
- Respawned capital ships appear in the shipyards and never move from there.
Reported by Azzkicka
- Unarmed ships that are attacked will run when in out-of-sector combat, but not during in-sector combat.
Reported by Azzkicka
- If an enemy ship surrenders and you pick up the astronaut, your ship will continue to flash red in the sector map (and cause the sector to flash red in the galaxy map) until your ship docks.
- If a Xenon ship surrenders, your ship will continue to flash red in the sector map even though Xenon ships don't release an astronaut on surrendering.
- Commanding a ship to attack a station has no effect / Stations appear on the list of automaticly-attackable targets for the "Combat->Attack' command (one or the other is a bug, depending on what was intended by Egosoft)
Reported by Tiberian Commander and verified.
- When configuring multiple ship purchases at once, the game does not correctly calculate how many of each ware is available in the equipment dock. This leads to being able to buy more items than are available, and also to some free money exploits.
Reported by Tiberian Commander and verified.
- Live cargo (slaves) can be transferred to a ship without cargo-bay life support without any ill effects.
- Some missions (namely bounty-hunter missions) do not appear on the BBS for any player who started their game prior to the 1.1 patch and then converted the save-game. They only appear for players who start a new game under 1.1.
Update: Not officially listed as a 1.2 bug fix, but as Egosoft asked for player-supplied game save files prior to 1.2's release, this may have been fixed.
- Free money exploit: Go to a ship-seller where the cheapest ship is not on the top of the list. Make sure you have just enough money for 10 of that ship. Select that ship, and make the purchase quantity 10. Now select the "I" (information) screen, and escape out of it. The ship purchase selection will now be on the ship that is at the top of the list. Purchase the 10 of those more expensive ships, and your cash will be set to zero. You can now re-sell those 10 ships for free money.
Reported by Logan321 and verified.
Update: Fixed in version 1.2
- Some users report music corruption in some song files. Corruption persists despite ensuring the only mp3 codec enabled is the correct Fraunhofer Advanced v1.9. More info here
Reported by CoreInversion
Update: Only appears on one or two machines. Probably not a game-related problem.
- Strange effects occur if a ship docks while you are attempting use a transporter to transport to it. It appears that the ship "docks" inside the player object. More info here
Reported by doctorlucky
- Free commodities exploit: Command a subcraft to dock with its mother ship (M6, TL, M2, M1) and then enter into the "Freight beamer" screen. Select all of one commodity, and when the subcraft docks, that commodity will be duplicated. More info here
Reported by Logan321 and verified.
- Events in a remote sector occur differently if they are observed through the sector map than if they are not observed. More info (including a link to download a save game that illustrates the bug) is in this thread.
Verified by brucebia.
- A nebula which obscures something from the scanners of your ship but not another ship that you own in the same sector will still cause that item to dissappear from the sector map/gravidar. The obscuring code does not allow for the fact that another ship you own might be able to see something, even if you can't. More info here
- The ecliptic projecter is turned "off" after warping. It must be turned on every time you enter a sector. This is annoying and different from XBTF & XT. I can't call this a bug, as it may be intended, but if it is intended, I can think of no reason why it should have been.
Update: This has been "fixed" in the 1.2 patch.
- SETA mode should terminate if a ship you own is attacked. As the majority of actual game-time is in SETA mode, having it not terminate essentially eliminates the possibility of ever going to the aid of one of your ships that is attacked. By the time the notification is given, it may be too late to assist the ship.
- "Navigate->Fly to sector" keeps the autopilot on after you arrive in the destination sector, while "Navigate->Move to position" silently turns off autopilot when it completes. For consistency, when the autopilot reaches the logical end of a program, it should always be left in the same state. Additionally, it would be nice if an "autopilot deactivated" message was played whenever the autopilot turns itself off.
- When a weapon or shield is destroyed, the message played is "<weapon name> has been damaged", whereas with every other type of equipment it uses the word "destroyed". As weapons are not repairable, it should say "destroyed" with them as well so as not to confuse players. More info here.
- In a multi-monitor setup, you cannot select which physical monitor to display a menu on. It is always on the primary monitor.
Reported by GnatB.
- AI/Autopilot only seems to do collision avoidance for obstacles directly in a ship's path (the current vector the ship is pointing at). This is a problem when the AI/Autopilot decides to turn. It doesn't "shoulder check", so to speak, and it turns without checking if its destination vector is clear. This is especially a problem when undocking from large stations and hitting autopilot right away. If the new vector for the autopilot is "behind" the ship, it will take the ship into a radical course change. This can cause the ship to ram the station before the turn is complete, and thus before the autopilot can do collision avoidance. It should be fairly easy to, in combination with the turn speed of the ship, check the destination vector of the ship prior to a turn being executed, and perform "preemptive" collision avoidance.
Reported by Incarna and verified.
- Ships under AI control will never use a jump-drive.
Reported by Azzkicka et al
Update: According to Egosoft, scripting will soon be able to control the jump drive. This means that this issue will be resolved.
- Any time a player takes control of a ship, that ship's "home" setting is lost.
UPDATE:This was originaly Bug #9 on the above bug list. It has been confirmed that this is, in fact, intended behavior with the explanation that a player's ship "doesn't need a home". While this is technically true, it is also annoying for the software to make those decisions for me and delete a player's settings. Rule of thumb for software is that an explicitely set user setting is always more valid than what the program "thinks" is appropriate. When a user takes control of a ship, the setting should be suspended but preserved.
- Stations that have >0 resources, but not enough resources for their next "batch" of product will not flash yellow indicating they are out of resources.
Update: Egosoft has claimed this is intended behavior in this thread. While I would usually accept this, the given explanation does not make sense on two counts. 1) They say that it might not blink yellow if goods are incoming, however a station that has zero resources will blink yellow even if its automated freighters have resources that are incoming. Verified with a solar power plant and crystals. 2) A station that cannot produce due to not having ENOUGH resources will sometimes blink yellow on the Gravidar, but not on the 'R' list or on the sector map. Therefore this indicates intended behavior contrary to the given explanation.
More info here.
Another Update: Mr. Handby continues to insist that this is intended behavior. I still think there must be some misunderstanding somewhere, as I cannot believe this would be intended - in XBTF, it worked the "right" way. But, if they say it's intended, it's intended.
Update 3: I posted another thread about this issue to collate all the observations in one place. Mr. Handby has promised that the issue will be looked at. Thanks!
Update 4: Fixed in version 1.2. Thanks goes out to Egosoft for taking the time to do this.
Reported by reljam and verified.
- The "show as enemy if enemy to me" behavior doesn't make total sense on two counts: 1) It has no "in-character" basis. How can you tell if someone doesn't like you unless they actively target you, or you are otherwise the recipient of weapons fire? 2) It makes it so that non-hostile pirates (those pirates who would otherwise not attack you) are attacked. Thus, the behavior has negative functional and negative in-character effects.
The suggested behavior would be to have the setting cause only ships that actively target and/or fire upon you to show up as an enemy.
28 Dec 2003
- Added bug reports numbers 27, 28, and 29.
- Added bug report number 30.
- Added log so viewers can tell what has changed at each update
- Added ship-buying free-money exploit to the bug list (#31)
- Added "show as enemey if enemy to me" behavior to oversight list. (#10)
- Removed a duplicated bug (ack - a bug in the bug list)
- Updated bug #12 (Teladi Lottery winning number bug) to red.
- Added bug #32
- Cleaned up a few formatting glitches.
- Added an update to oversight #9. Thanks to JonHandby, who has promised the issue will be looked into.
- Removed bug #32 (invisible confirmation dialog for "delete all logbook entries) which was not a bug. It was, in fact, stupidity and perhaps severe myopia on the part of this list's author.
- Added bugs #32, #33, & #34.
- Added bug report #35.
- Added bug report #36. Only 28 more to go and this thread gets in the top 10 active threads. Woo hoo!
- Updated all bugs and oversights reported as fixed in 1.2 (and some that weren't if it made sense) to orange pending verification that they are fixed; except for...
- Bug #2 (Ecliptic projector) updated to reflect that while noted as fixed in 1.2, it was unfortunately not fixed.
- Updated bug #8 to green as it is intended behavior. This change should have been made long ago.
- Updated bug #32 to green, as it occurs in so few machines that it is likely not a game-caused problem.
- Updated bug #2 - turns out the readme was mistaken as to which ecliptic projector issue was fixed.
- Updated Oversight #1 to green. This is the ecliptic projector issue that patch 1.2 fixes. At least we still get to turn something green. Yay.
- Updated Oversight #9 to green. This has been verified fixed. Yay yay!
- Added an update to oversight #7 indicating that Egosoft has promised to fix this. Yay yay yay!
- Updated bug #31 to green as it too is fixed in version 1.2.
- Updated bug #6 to green as it was partially an error in my observation, and partly intended behavior.
- Added updated information to bug #7 (turret missing target). Thanks to KlausM at Egosoft for his time on this.
- Bug #10 (police licenses destroyable) updated to green. Couldn't make this happen since 1.2.
- Bug #12 (incorrect display of previous winning lottery number) updated to green.
![[ external image ]](http://xai-corp.net/files/xai-corp.jpg){kind=link}