Why aren't you using 2.42?

[EricL]

Sorry, the DNA parse stuff in 2.4 still drops certain sysvar strings, so I was reading sysvar numbers late at night and confused .readtie and .tienum.

The only change I have made that impacts tmemloc/tmemval is that putting something in .tmemloc now stays there like I think it does in 2.37.6, even when ties come and go or the bot puts something in .tienum.  Before .tmemloc was getting set to 0 if .numties went 0 or .tienum went 0 (or hadn't yet been set).

[Numsgil]

I think memloc stays put, but tmemloc didn't in 2.37.  I could be wrong but I'm pretty certain.

[EricL]

I think memloc stays put, but tmemloc didn't in 2.37.  I could be wrong but I'm pretty certain.

If tmemloc does not stay put in 2.37 then I don't understand how this line in Elite's posted bot can work since it appears (to me at least) to set .tmemloc at age 0 and then never again.  The 2.4 code resets it back to 0 right away since .numties is still 0 :

.numties .tmemloc *.robage -1 mult 1 add sgn mult store

[EricL]

By the way, I now know what is going on with .fixang and perhaps othertie  sysvars that arn't working.  Bascially, there is no code in 2.4 that cares.  The routine named Momenti() in 2.37 which handles fixing tie angles was just never ported over to 2.4.  It's called TieTorque() in 2.4, but is completely commented out and the systax is still 2.37, referencing structures which no longer exist such as the robot node list, etc.  No wonder certain bots that fix tie angles just don;t work in 2.4.  I'll port it over.

Is Software Archeologist a viable profession?  

[Numsgil]

By the way, I now know what is going on with .fixang and perhaps othertie sysvars that arn't working. Bascially, there is no code in 2.4 that cares.

 Oops, hehe.

[Welwordion]

Just a thought but could robage in 2.3 count age like in 2.4? its really annoying if  you try to make bots you want to test in both versions.

[Numsgil]

They don't count age the same way?

How does each version count age?

[Welwordion]

2.37 counts age in steps of 100 cyles, so age 3 means between 300 and 400 cylces
2.4 counts age in single cyles, so age 3 means cycle 3

[Numsgil]

I'm pretty certain that 2.37 also counts single cycles.  The robot info page, however, displays age in 100s of cycles.

[Elite]

I'm pretty certain that 2.37 also counts single cycles

100% certain, otherwise the classic antibirthtie genes would take 100 cycles to cut the cord

cond
*.robage 0 =
start
.tie inc
stop

cond
*.robage 1 =
start
.deltie inc
stop

[EricL]

I'm pretty certain that 2.37 also counts single cycles.  The robot info page, however, displays age in 100s of cycles.

Right.  I changed this in 2.42.2.  The age sysvar works THE SAME in both versions.  It counts single cycles and caps out at 32000.  However, 2.42.2 and beyond now maintain an internal age counter that goes beyond 32000.  It is this that is displayed in the robot properties dialog (in cycles, not 100's of cycles as it was previously) and is also used for a few other things such as the logrythmic per cycle aging cost calculation.  That is, the logrythmic aging cost will continue to increase even after a bot reaches 32000 cycles of age.  See #24 and #25  here.

[Welwordion]

Sorry, somehow I always end up with finding the wrong reasons why certain genes do not work :/.

[Numsgil]

That's alright, it keeps us on our toes.

[EricL]

FYI, I have finished porting over the TieTorque() routine from 2.37.6 to 2.42.3.  Elite's battery bot gene posted earlier in this discussion now runs correctly in 2.42.3.  See #11 here.

[Numsgil]

Yay!