Code center > Bugs and fixes
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:
--- Quote from: Numsgil ---I think memloc stays put, but tmemloc didn't in 2.37. I could be wrong but I'm pretty certain.
--- End quote ---
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:
--- Quote from: 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.
--- End quote ---
Oops, hehe.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version