Code center > Bugs and fixes
Things to fix list
PurpleYouko:
Problem: Crashes caused by deleting or changing bot names.
Details:
--- Quote ---Renaming or deleting a Bot used in the current or loaded settings then starting the sim causes the program to ask for the location but doesnt accept it and needs a three finger salute. Fairly serious
--- End quote ---
This happens when the name of a robot DNA file is modified or deleted from a text editor and the settings in the sim are unable to find the DNA file.
level: Serious
Resolution: Under investigation. Problem understood. Waiting in the queue for fixing.
PurpleYouko:
Problem: General save issues.
details
* The species starting position grid doesnt save properly. Sometimes not at all sometimes one of the corners is misplaced causing wierdness. Annoying for ant bots.Level: high
Resolution: Pretty much all sim saves are mostly non funtional in 2.36.2. So much stauff has been changed within the program and is continuing to be changed that fixing save functions has to wait until all major internal changes are done first. Otherwise we will have to do them several times over.
PurpleYouko:
Problem: "Insert a new value" control in the mutations panel not working right.
Details: When a new robot is selected and the mutations panel is opened, all controls except "insert a new value" default to 5000. "Insert a new value" stays at zero.
Level: Annoyance.
Resolution: Fixed!
Problem was due to an incomplete transfer of my code to Numsgil's resulting in missing or incorrect code in the options panel.
PurpleYouko:
Problem: Corpses immune to physics.
Details: When corpses are enabled, they just bounce about and never slow down. It would appear that friction doesn't apply to corpses. They also don't sink to the bottom so there appears to be a problem with bouyancy too
Level: Serious
Resolution: Fixed!
Problem was due to a number of bad peices of code in the physics module. Now works fine.
PurpleYouko:
Problem: Phantom shots
Details: Shots appear to come from invisible robots. They come from a moving source but no robot is visible. Only appears to happen with "Torroidal" disabled such as in pond mode.
Level: Serious
Resolution: Fixed!
Problem was due to somebody messing about with the border collisions routine and thus allowing robots to have x and y values greater than maximum field size and smaller than zero. Problem was in a routine making robots bounce off the sides (or not)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version