Homeworld 2: BugsReference

Most recent edit on 2007-03-06 22:11:37 by MiKail

Additions:
- The function "SobGroup_FillSubstract" is mispelled.

Edited on 2007-02-15 17:07:39 by MiKail

Additions:
- Ships will only use one (the first) launch path, even when several exist.

Deletions:
- Ships will only utilize one dock path when docking to another ship, regardless of the number of paths that are available.This is not true: if a dock path is busy then the next docking ship uses another path if available. -SunTzu

- Ships will only use one (the first) launch path, even when several exist. Either this item, or the one above, is incorrect. Can't remember which one... -Mikail
  
  Edited on 2007-02-15 04:39:18 by SunTzu
  
  Additions:
  - Ships will only utilize one dock path when docking to another ship, regardless of the number of paths that are available.This is not true: if a dock path is busy then the next docking ship uses another path if available. -SunTzu
  
  Deletions:
  - Ships will only utilize one dock path when docking to another ship, regardless of the number of paths that are available.This is not true: if the a dock path is busy then the next docking ship uses another path if available. -SunTzu
  
  Edited on 2007-02-15 04:38:50 by SunTzu
  
  Additions:
  - Ships will only utilize one dock path when docking to another ship, regardless of the number of paths that are available.This is not true: if the a dock path is busy then the next docking ship uses another path if available. -SunTzu
  
  Deletions:
  - Ships will only utilize one dock path when docking to another ship, regardless of the number of paths that are available.
  
  Edited on 2007-02-12 05:42:13 by SunTzu
  
  Additions:
  - AI never uses command corvettes.This can be changed in the AI building script. However the RDN docs say that AI cannot properly use the command corvettes when they build them.
  
  Deletions:
  - AI never uses command corvettes.'This can be changed in the AI building script. However the RDN docs say that AI cannot properly use the command corvettes when they build them.'
  
  Edited on 2007-02-12 05:41:29 by SunTzu
  
  Additions:
  - AI never uses command corvettes.'This can be changed in the AI building script. However the RDN docs say that AI cannot properly use the command corvettes when they build them.'
  
  Deletions:
  - AI never uses command corvettes.
  
  Edited on 2007-02-10 21:59:07 by MiKail
  
  Additions:
  - Players still drop and game desync all too frequently for other reasons.
Game Loading
- Games often freeze in multiplayer when initially loading.
  
  Edited on 2007-02-10 21:57:52 by MiKail
  
  Additions:
  - The kick player dialog steals focus from the chat window. This is really annoying.
Players Dropping
- I suspect I've noticed that players drop frequently when I do very rapid zooms using the mouse wheel.
  
  Edited on 2007-02-10 21:23:05 by MiKail
  
  Additions:
  - AI never uses command corvettes.
Tech Sharing
- If you've researched, say, Battlecruisers or Destroyers and you transfer a ship with a Capital Module, your teammate benifits from your research and is able to build those ships.
Badge Glitch
- (Not sure exactly how this works.) If you're in the GS lobby and a player has applied a badge you haven't downloaded yet, a different badge is displayed in its place.
  
  Edited on 2006-07-03 01:31:16 by MiKail
  
  Additions:
  - A greater number of ships may temporarily dock with a target ship than is specified for the target ship's shiphold size.
  
  Edited on 2006-06-22 22:56:27 by MiKail
  
  Additions:
  - Custom campaigns cannot be selected from within the default UI. They can only be loaded via the command-line switch.
- New, scripted commands (such as evillejedi's kamikaze command) cause de-syncs in multiplayer. Players affecting deterministic data is not permitted in gamerules.
  
  Deletions:
  - Custom campaigns cannot be selected from within the default UI. They can only be loaded via the command-line switch. Workaround in progress...
- New, scripted commands (such as evillejedi's kamikaze command) cause de-syncs in multiplayer. Enabling the player to affect deterministic data is not permitted in gamerules.
  
  Edited on 2006-06-22 22:40:02 by MiKail [New workarounds listed.]
  
  Additions:
  - Custom campaigns cannot be selected from within the default UI. They can only be loaded via the command-line switch. Workaround in progress...
- Cannot load levels/maps from outside the (largely) hardcoded level-selection screen. Workaround suggested in this post.
- New, scripted commands (such as evillejedi's kamikaze command) cause de-syncs in multiplayer. Enabling the player to affect deterministic data is not permitted in gamerules.
  
  Deletions:
  - Custom campaigns cannot be selected from within the default UI. They can only be loaded via the command-line switch.
- Cannot load levels/maps from outside the (largely) hardcoded level-selection screen.
- New scripted commands cause de-syncs in multiplayer. Enabling the player to affect deterministic data is not permitted in gamerules.
  
  Edited on 2006-05-21 12:10:33 by MiKail
  
  Additions:
  - Level glare set using the setGlareIntensity function doesn't work with all graphics chipsets/drivers. See this thread.
  
  Edited on 2006-05-06 15:02:02 by MiKail
  
  Additions:
  - If you zoom in real close to a ship, the level light source will shine through the model.
  
  Edited on 2006-05-06 14:52:23 by MiKail
  
  Additions:
  Game Exploits
See this thread.

Edited on 2006-05-05 12:00:37 by MiKail

Additions:
- See this thread and this thread.

Deletions:
- See this thread.

Edited on 2006-05-05 11:46:43 by MiKail

Additions:
- Stuff that can only be done in Maya
- See this thread.
  
  Edited on 2006-05-05 11:23:02 by MiKail
  
  Additions:
  - Munitions don't take dustcloud or nebula damage.
- Can't build ships from other races. There have been some workarounds suggested. See this thread.
  
  Deletions:
  - Munitions should take dustcloud and nebula damage, as well.
- Can't build ships from other races. There have been some workarounds suggested. See this thread.
  
  Edited on 2006-05-05 11:20:17 by MiKail
  
  Additions:
  - New scripted commands cause de-syncs in multiplayer. Enabling the player to affect deterministic data is not permitted in gamerules.
  
  Deletions:
  - New scripted commands cause de-syncs in multiplayer. Enabling the player affect deterministic data is not permitted in gamerules.
  
  Oldest known version of this page was edited on 2006-05-05 11:19:39 by MiKail []
  
  Page view:
  HW2 Bugs, Issues, and Workarounds

Data Modding Related Issues

Campaigns
- Custom campaigns cannot be selected from within the default UI. They can only be loaded via the command-line switch.
- Campaign descriptions and level thumbnails should be listed in "*.campaign" files, IMO.
- Cannot load levels/maps from outside the (largely) hardcoded level-selection screen.
- Race is set to 1 (Hiigaran) by default in singleplayer campaigns; and, there does not seem to be any way around except by reversing the order of races in "races.lua". See this thread.
Game Rules
- It would be better if the entrance of the MS out of hyperspace at the beginning of play were done via scripting, since the workaround for delaying/modifying this is ugly.
- Need more functions to handle subsystems.
- Need a function to save persistent data in skirmishes.
- Automatic resource harvesting at the end of missions is really annoying. Auto-harvesting is easily disabled; however, one would still need to provide the player with a means to end the mission manually (e.g., by mapping the function to an unused key).
- Victory conditions based on the number of build-capable ships don't work so well when build capabilities are added to such things as fighters, corvettes and frigates. that is not such a problem; you can easily add another condition to the game ending chunk (like the ships being of capital attack family) - SunTzu
- New scripted commands cause de-syncs in multiplayer. Enabling the player affect deterministic data is not permitted in gamerules.
Weapons
- Weapons with "gimble" setting will not periodically update their targeting assignment even if secondary target engagement and independent scanning is enabled. These will "stick" their target to the one designated either by the player, or the ship's selected target. If no target is selected, then the Gimble weapon will scan once, then "stick" to that regardless of whether it is within field of traverse or not. Use AnimatedTurret if you'd like to have weapons independently selecting and engaging targets without player input. Vagyr and HGN Mothership defense guns function much better as AnimatedTurret setting. Note that this does not require an actual turret model, see Vagyr Battlecruiser's side hull lasers.
- Munitions should take dustcloud and nebula damage, as well.
Ships
- Resource collectors tend go clear across the map in search of ships to deliver their salvage to -- even when a suitable destination is close at hand.
- There should be a scripting method for getting/setting the inclination and azimuth of a ship, relative to the map plane. Currently this can only be done in the .level file.
- Marine frigates will continue their approach, even when their target is no longer visible (or no longer appears in sensors).
- One shouldn't be able to retire ships inside battlecruisers, IMO.
- Can't dock Movers with Battlecruisers.
- Can't retire captured carrier modules, but can retire captured mothership modules.
- Ships will only utilize one dock path when docking to another ship, regardless of the number of paths that are available.
- Ships will only use one (the first) launch path, even when several exist. Either this item, or the one above, is incorrect. Can't remember which one... -Mikail
- Can't build ships from other races. There have been some workarounds suggested. See this thread.
AI
- AI doesn't avoid radioactive nebulae.
- AI doesn't use minelayers.
- AI never repairs its own ships.
- AI never retires ships or subsystems.
- AI doesn't use EMP.
- AI doesn't use Keeper ships. This is easily fixed by editing "data\ai\classdef.lua".
- AI quits playing after it runs out of production/resourcing options.
Starting Fleets
- Starting fleets are per-race, only. Per-player-and-race starting fleets would be better. See this thread.
- Collectors should be listed within the mothership's shiphold in the starting fleet luas rather than being listed seperately (...and having to resort to a crude hack to make them exit the shiphold as a result).
Madstate
- Animations often work better if they start on frame 2 instead of frame 1, for some reason. See this thread. Quote from the RDN docs: "NEVER create keyframes at frame 0! Start at frame 1". Counting beginning with zero, frame 0 is the first frame and frame 1 is the second.
UI
- On large maps, when a ship is past a certain distance from the camera, it cannot be selected using the mouse (even though it can still be seen). It's tactical icon will also disappear when this is the case; so, it's probably due to a setting in the .ship file. See this thread. Change the farClip value in "ui\camera.lua".
- Sometimes the "Edit Profile" menu doesn't leave the screen (e.g., when the host leaves the game setup screen while you're editing your profile). This happens with other menus, too.
- Very laggy! It is often becomes difficult to add/remove ships to/from contol groups using the mouse, or to assign a target to a ship.
- The level name isn't displayed in the game setup screen when joining a game with a custom level.
- Can't use the keyboard to navigate through the front-end menus. This can probably be made to work by modifying "keybidings.lua" (in the "locale\english\scripts\" directory). Can probably even make the bound actions vary depending on the currently-active screen. -Mikail
- It would be nice to be able to view more than one thumbnail per map.
- More substantial text level descriptions would have been nice. One workaround is to add the text to the level thumbnail in a graphics program.
- It would be better if one were able to select levels from more than one directory. This would make it possible to distribute levels made to work with specific mods, while still allowing the player player to play on maps meant for 'vanilla' HW2 when running the mod.
- Clicking on the queue (accessed in game using the 'q' key) a second time should close the build/research window.
- The Diplomacy menu is not available in Skirmish mode. (Arguably, this would give the player an unfair advantage over the CPU.)
Levels
- It should not be possible to add clouds or pebbles to a level from within the DetermChunk portion of a level file, as they do not get saved along with the rest of the map data when saving the game.
- There may be issues, where programmatically creating start positions causes games to de-sync in multiplayer (but not in skirmish). See this thread.
- Can't have "extra" CPU players like you could in HW1. There is a maximum limit of six players in a game; and, all six players are visible in the game-setup screen.
Other
- When added to the HW2 shortcut, the "-GameRule" flag is often ignored (I think).
- As of the 1.1 patch, the randomseed function is ignored. What the devs could have done is created a global variable containing a random seed value. This way map authors would have the choice whether to use a random seed value or a pre-defined seed value.
- Lua tables start with index number 1. Some tables, such as the 'player' table in level files, begin with index number 0. Unfortunately, Lua treats index number 0 like a string index--making iterating through tables difficult.
Missions
- Game-stopping bug in Mission 12. See this thread.
Multiplayer
- Kicking players should be done via a vote, IMO.

Engine Limitations (also, see this thread)

Object Size Limit:
- Objects cannot be larger than somewhere around 25000 units. One solution is to split a model up into several sections and then bind them together. Please update this with the correct info, and a link to a discussion thread, preferably. -Mikail
Object Number Limit:
- Through testing I have found out that you can have 5000 asteroids in a map, but not 10000. I don't know the exact cut-off number, and whether this applies to all objects. -Mikail
Render Distance Limit:
- There is a farClip value in "camera.lua". Objects beyond this distance from the camera are not rendered. This makes creating/playing on large maps difficult.
Very Large Objects (VLOs) & Collision:
- Collision meshes can only take the shape of a rectangular prism. In order to have more complex collision meshes, you'll have to split your model into several smaller objects. See this thread and this thread.
The hyperspace effect is hardcoded.
Performance
- See this thread and this thread.
Game Recordings
- See this thread and this thread.
No. Polygons
- See this thread.
Differences with Mac version
- See this thread.

Bugs/Errors/Typos

The parameter RequiredResearch for PlatformIonWeapons in the Hiigaran "research.lua" is mispelled.
HW2 prints the following error message regarding the 16-bit color-depth setting. "do not show again has not been hooked up properly for this dialog. you must give your message a name" The pop-up window is not supposed to appear after you have checked the box.
"FrigateSpeedUpgrade2" is misnamed for all Vaygr ships.
"Fleet Defense" is mispelled in the description for the Defense Field Frigate.
The description for the Hgn Gun Turret should say "StaticDefense" instead of "StatiMinelayer".
There's a typo in "ShipTuning.xls". The string "RepairAbility" should be "MinelayerAbility" in the Minelayer Ability section.
'data\scripts\scar\scar_util.lua' contains many instances of poorly-formed strings.
The 'vgr_prisonstation' (as well as its special sensors module) is missing an icon in 'shipicons.lua'.

Related Pages

Elite modding taskforce: what needs to be figured out?