Code center > Bug reports
Bugs in 2.42.5
Elite:
Phantom Shots
How to get the bug:
Start a sim with a combat bot. After it's run for a couple of cycles, enough for the bots to start trying to eat a few vegs, click the "Start new simulation" button. Don't touch any of the settings and start a new sim (but start it paused this time). Cycle through a couple of cycles, keeping the sim paused, and you will see some shots magically appear out of nowhere.
Here's what's happening (or what I think's happening):
If you start a new sim while a new sim is in progress, the shots that are on the field at that time aren't cleared, so when the new sim starts, they are still there.
However, if you remove the bot that fired the original shots, the 'phantom shots' will not appear
EricL:
You are absolutely correct Elite. The Shots array is not getting reset when a new sim is started. Any shots which exist in the previous sim will live out their lives in the new one until their age reaches their range.
Nice find. Fixed in 2.42.6.
Elite:
Bots in a Viscous Medium
How to get the bug:
Set the friction settings to "Thick Fluid" and run a sim. The bots vibrate back and forth insanely. This shouldn't be happening.
What I think is happening:
With fluid dynamics, the friction increases with speed. If the bot sits there not moving, then they stay still. The problem comes if they try to move. It seems that the friction when moving is enough to overpower the bot's forward motion and actually force it backwards. Friction shouldn't be greater than the force that the friction is resisting.
Viscosity Glitch
How to get the bug:
Set the friction settings to "Thick Fluid" and run a sim. The bots should vibrate back and forth. Start a new sim but this time change the friction settings to "Sandpaper" or "Metal" or "Teflon". The viscosity is still the same as "Thick fluid". The bots still vibrate back and forth like they're in a thick fluid.
What I think is happening:
The viscosity isn't getting reset when the friction settings are changed to solid. You can see this if you change the friction settings to custom and look at the viscosity.
Overflow Bug
How to get the bug:
Set the friction settings to "Thick Fluid" and run a sim. The bots should vibrate back and forth. Start a new sim but change the settings to "Custom Physics" and change the viscosity. It goes down to 0.01. A couple of seconds after you hit the "Start sim" button, the program gives an overflow error and exits.
What I think is happening:
I haven't got a clue, but I'll bet it's linked with the above bug.
Zoom Overflow
How to get the bug:
While in a sim, unlock your view so you can see areas outside the field and then zoom out. Keep zooming out, and the program will eventually give an overflow error.
What I think is happening:
This is one of the simpler bugs. The area that you are viewing becomes so big that you get an overflow. I reccomend restricting the maximum possible view.
Shootval Bug - Uh oh - major, major bug here!!!
The number in .shootval is the energy cost for a shot, no matter what kind of shot is being fired. If a bot does this, for example:
.aimdx .shoot store
628 .shootval store
(ie. Icarus)
... then the bot will have to pay a whopping great energy cost of 628!
Bots should only have to pay an energy cost of the number in .shootval when they fire -1 shots and -6 shots, not for any other types of shots.
Viruses
OK, viruses could really do with a debugging
Some of the strange behaviors I've been noticing:
* Rather than be fired forwards viruses fly off at random angles (although I think Nums did this on purpose)
* No matter what number is put into .vshoot, the viruses always have the same range
* Viruses loose their condition when fired (I think Nums did this on purpose too) and are getting themselves inserted into the middle of genes. One of my viruses hit a veg and was inserted directly into the middle of the reproduction gene - directly before the START of the first gene. This resulted in the veg going cancerous.
* Genes cannot make themselves into viruses. If the gene number of the current gene is stored into *.mkvirus (ie. with *.thisgene) then the virus will not appear.'Touch' senses
These don't work at all
Here's what should happen:
These sysvars are supposed to detect collisions with other bots
* If a bot is hit/touched from the front, *.hitup should readback 1
* If a bot is hit/touched from the back, *.hitdn should readback 1
* If a bot is hit/touched from the left, *.hitsx should readback 1
* If a bot is hit/touched from the right, *.hitdx should readback 1Delgene
.delgene doesn't work at all
If you store a gene number into .delgene then that gene should be deleted, but this doesn't happen
.thisgene works fine though, so the problem isn't in the gene numbering as I originally thought
Testlund:
I think there is a little bug with the total veggies counter. If I for instance have 600 veggies it drops down to 245 and then back up to 600 within a cycle. It keeps doing that at irregular intervals. I've checked carefully through the veggies but I can't see that lots are dying out and gets born withing just a cycle.
Another thing I found strange is that when I started a new sim in 2.42.5 I chosed 3 veggies from a previous sim in version 2.42.4, they were at generation 7 and 8. I give them only 1 energy at start and they quickly gain up to 32000 energy. All their offspring though only has around 100 energy at birth and they never gain any energy. They quickly die out. In my previous sim I got a stable population going all the way to generation 8 and they gained energy and grew bigger, but here all offspring dies out. Only generation 0 stays alive until about 60000 cycles when old age is starting to rapidly take away their energy. I've set age cost to 0.1 and to begin at 20000 cycles, and I've checked the box below. This worked nice in my previous sim in 2.42.4. At 3040260 cycles I still had a stable population with tons of veggies. This was my last save in that version. Then I began a new sim in this version. I wonder if there might have been some bugs in 2.42.4 that made the veggies survive where they shouldn't. And now when those bugs have been fixed these veggies have a harder time surviving. Or there might be new bugs in 2.42.5. I could zip up a save if eric or someone whould like to take a look at it.
shvarz:
I tried this version and almost right away I found a bug. Or at least I think I found a bug. Bots get energy from nowhere, probably through some bug in tie-sharing/feeding. I found a group of three bots linked by tie and they had 1, 1, and 3 energy with about the same amount of body and these three bots stayed alive for multiple cycles. Check out the attached sim (change name extension to rar and unpack).
Navigation
[0] Message Index
[#] Next page
Go to full version