Settings that makes 2.37.4 stable!

[Testlund]

I used some other settings and managed to run a simulation for 11 hours, and it's still running. People who doesn't want to search for bugs can use this settings file while they wait for the rest of the functions to work.

After you loaded the settings file, change Waste treshold to 100. That's the only thing that didn't get saved in the settings file this time. Don't know what waste treshold does really.

[Griz]

2.36.4???
or do you mean 2.37.4???

also ...
my rob(o).vy problems come when I am using non-torodial settings ...
ie ... I have some gravity and a 'floor' in the sim.
not sure if PY or Num's uses non-torodial when trying to debug.
with a floor, I do have many more bots down there that have a
zero velocity in the Y axis.
how about you Testlund?
are you also using nontorodial or pond mode when you get
your runtme error 6 ... and it's rob(o).vx or .vy that screws up?

I'm thinking we should toss 2.37 out ...
and go back to the some stable 2.36 version ...
and start there ... and add functions.
2.36 actually works ... but lacks the save/load thing.

[Testlund]

Oh, that was embarrasing.  :redface: I've edit my post above and changed it to 2.37.4 and also changed the name of the attached file.

In the program it says 2.36 though.

And yes, when I kept crashing I had the torodial stuff unchecked, Boyancy checked, pond mode checked, gravity set to .4.

I'm not sure about going over to 2.36 now. As I see it there is only one bug left to fix in 2.37.4; the run-time error 6 overflow.

I think it's the Pondmode or possibly the gravity that isn't working.

[Griz]

it seems to run with  torodial enabled ...
ie ... no edges left or right, top or bottom.
with nontorodial ... it becomes a box ...
and then I have quite a few bots with zero Y axis
velocity at the bottom ...
and it seems this to me is what causes the rob(o).vy overflow.

will have to experiment.

I say go back to the 2.36 because that is still the only one
that doesn't crash on me ... that I can actually run for awhile.
so I'm toying with the idea of starting with it ...
seeing what differences were made in 2.37 ...
and incorporating the features that work ...
and NOT those that screw up.

but I'm tired of fooling with 2.37.4 ...
sorry ... it DOES NOT WORK!!!!
I suspect there are many 'bandaids' that were applied to
problems instead of going back to the source of the problem
to fix it as it should have been fixed ...
and that with each new revision, more bandaids were applied ...
until we now are at a point where the chickens are coming home
to roost, so to speak. ;)

me thinks we should go back and start 'clean'.

so ...
I'll just have to be satisfied with 2.36 for now I guess ...
and see if I can figure out how to add in the features that are missing ...
stealing some of them from 2.37 or even 2.4 ...
things like save/load and the positioning routine ...
maybe can adapt what Bots did.
whatever ...
I'm tired of 2.37.4 ... it's a waste of time.

[PurpleYouko]

I'm tired of 2.37.4 ... it's a waste of time.

I'm just tired of this kind of pointless, defeatist attitude.

If it's such a waste of time then don't bother with it. Just go play with darwinPond or some other program instead of being constructive.  :angry: