Code center > Bug reports

Large fields bugs

(1/3) > >>

Testlund:
Here's another run-time 6 overflow.

CODE:
a = rob(n).mutarray(t)

HOVERING INFO:
a = 0

rob(n).mutarray(t) = 75000

The above crash appeared when I ran in the safe setting (see topic 'Settings that makes 2.37.4 stable) with the difference that I increased the field size to width 40000 and height 30000, and increased veggie population to 400. It only took a few minutes for the crash to appear.

Testlund:

--- Quote ---I don't use pond mode ...
just nontorodial ...
--- End quote ---
Then I don't get it. Have you tried my safe settings file? I don't use torodial either. Now I've been running a simulation for 12 hours with no crash, nontorodial and no pond mode. Boyancy on. Field size is width 32000 and height 24000. Max veggies set to 300, but I only have around 10-30 veggies on the screen. The bots are very quick to eat them. Maybe that's why it hasn't crashed, because there are so few veggies.

PurpleYouko:
There are a number of issues with large field sizes.

One of which is that the bot's internal X,Y,Depth readbacks get screwed when you run a sim with a width or depth greater than 32,000.

One fix is to change ALL variables in the program to "longs".

This is on my to-do list but will have to wait till the next round of fixes.

Numsgil:
I strongly disagree with changing the robot memory array to longs.  For reasons that aren't immediatly apparent to me at the moment...

PurpleYouko:
Yeah I never did figure out what your problem with that was.

Seems to me that it will give many many benefits and absolutely no problems.

* VB runs faster with 32 bit variables.
* All the overflow crashes will disappear.
* X,Y and depth will work for all sim sizes. Means that ant-bots can run in larger sims.I do not propose to allow the use of larger numbers as it would be rather silly to have bots wandering around with millions of energy and/or body points. They will still be limited to 32000 (or possibly rounded to 40,000 or 50,000)

I don't see what other issues there are with this proposed change.

Please let me know your specific objections as soon as you can figure out exactly what they are.  :P

Navigation

[0] Message Index

[#] Next page

Go to full version