|
|
| (19 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | {{TOC right}}
| + | To view and report bugs, go to http://code.google.com/p/bitfighter/issues/list |
| | | | |
| − | This is list of our current high-priority bugs for Bitfighter.
| |
| | | | |
| − | Not all issues belong on this list -- only those that are a high priority for the next release. Other cases should be added to the [https://code.google.com/p/bitfighter/issues/list Google Code bug tracker].
| + | ==019d== |
| − | | + | 1. Check paths in diagnostics page (press F7 twice, page 2), bad paths and missing level, scripts, bots, editor plugins on mac OS version. |
| − | ===General Bugs=== | + | |
| − | | + | |
| − | # Fix (or kill) /suspend command. ''Removed client-side by raptor'' Do we need to remove the server ability to suspend client?
| + | |
| − | # Figure out how to get ids working properly with walls/polywalls
| + | |
| − | # Fix memory leak with robots/levelgen because of disabling every luaW_hold<T>(L, obj); --> use reference counting to delete proxy when appropriate, and reenable this line
| + | |
| − | #* <del>sam686: repeated /addbots /kickbots kindof leaks memory and won't free memory until after running LuaScriptRunner::shutdown() which is normally run only when quitting. Check if everything is freed when a robot is removed.</del> temporary workarounds in [https://code.google.com/p/bitfighter/source/detail?r=4d6f2a48d2543b95939382c8619686a9ac5e7529 4d6f2a48d254] and [https://code.google.com/p/bitfighter/source/detail?r=01414236b4edcdc510b42ac3e2c1144adf17d249 01414236b4ed]
| + | |
| − | #* Added back luaW_hold and reverted 01414236b4ed by updating to latest LuaW upsteam. See [https://code.google.com/p/bitfighter/source/detail?r=e20c8828f30e1a2b3d55d6e115b4c4b8b045b267 e20c8828f30e] Still need to test if memory leak is there, but crashes don't happen like they used to with earlier LuaW revisions.
| + | |
| − | # Disable fast regen when standing still trying to build something with engineer
| + | |
| − | # Lua API doc fixes:
| + | |
| − | #* event method signatures are not documented
| + | |
| − | #* Check that all the old the Lunar classes mentioned at http://bitfighter.org/wiki/index.php/Scripting_018 are also in the luadocs.
| + | |
| − | #* How to document the global enums 'WeaponInfo' 'ModuleInfo'?
| + | |
| − | # Improve screen for loading levels in editor -- perhaps general keyword search, or options for picking by author/title/file, or perhaps navigating a folder tree
| + | |
| − | # bitfighter.ini [QuickChatMessages] is empty with missing comments after a newer version of Bitfighter is run, when "[Settings] version=" is older. Comments only appears after "[QuickChatMessages]" is removed and bitfighter is run.
| + | |
| − | # in onShipLeftZone/etc. events with 'ship' object, either the ship or the ship:getPlayerInfo() doesn't return the same userdata object each time anymore
| + | |
| − | # Start game with joystick plugged in; remove joystick; go to Options>Input... crash! Can't even get a stack trace in Windows!
| + | |
| − | # Shooting a burst or mine while in commander's map makes the map flicker -- Can reproduce on Windows if I have the sensor in my loadout
| + | |
| − | # Lua ship:getPlayerInfo() is nil with bots?
| + | |
| − | | + | |
| − | | + | |
| − | ====Things to test after next lua rewrite====
| + | |
| − | # Levelgen: Having addItem() in main() may randomly fail on repeated ctrl+R in editor or repeated level restart, showing message "***LEVELGEN ERROR*** Error encountered while attempting to run script's main() function: ***.levelgen:44: attempt to call missing or unknown method 'addItem' (a nil value). Aborting script."
| + | |
| − | #:<code>-- for bug #33 from sam686<br>function main()<br> for x = 0, 20 do<br> for y = 0, 20 do<br> item2 = ResourceItem.new()<br> item2:setGeom(x * 100, y * 100)<br> levelgen:addItem(item2)<br> textitem = TextItem.new()<br> textitem:setText(x .. "," .. y)<br> textitem:setGeom(x * 100, y * 100, x * 100 + 100, y * 100)<br> levelgen:addItem(textitem)<br> end<br> end<br>end</code>
| + | |
1. Check paths in diagnostics page (press F7 twice, page 2), bad paths and missing level, scripts, bots, editor plugins on mac OS version.
