Code center > Bugs and fixes

Ties in 2.4

<< < (3/6) > >>

Elite:
Yep PY, you're correct, .tielen .tieang .fixang and .fixlen only work once a tie is hardened, which takes 20 cycles

And the tie fixing commands are noticably different to the tie changing commands, the tie changing commands like .tieang spring back quickly, allowing for wriggling motions

Numsgil:
I think the .tielen1 was an unexpected consequence, and PY really meant them not to work on birth ties.

Elite:
On Tie Lengths and Angles
Replacing .tielen1-4 and .tieang1-4 in 2.4

I've had an idea inspired by Nums' use of commands in his new 2.5 tie paradigm

The problem with re-implementing the tie port commands like .tielen1 into 2.4 is that such a system is unmanagable when there is lots of ties
So how about these four commands to replace the sysvars .tielen1-4 and .tieang1-4

settielen
settieang

tielen
tieang

They affect the tie port on the top of the stack, so:
50 2 settielen
Would permanently set the length of the tie on tie port 2 to 50

And tielen and tieang would temporarily change the length for 'wiggling' motions, like the .tielen and .tieang sysvars

Alternatively, you could have positive numbers specify tie phases (number in .tie) and negative numbers specify tie ports (again, taken directly from Num's new tie paradigm)

What do you think?

PurpleYouko:

--- Quote ---.tieang1-4 act more like .fixang though, and likewise with .tielen1-4 ... I think that what's happening is that they're not getting reset and so are permanently forcing the tie to the value stored in them
--- End quote ---
Yeah .tieang1-4 does change the tie angles permanently as does .tielen1-4
maybe that was bad planning on my part to use this nomenclature instead of using .fixang1-4 but it's a little late to change it now.


--- Quote ---I think the .tielen1 was an unexpected consequence, and PY really meant them not to work on birth ties.
--- End quote ---
Extremely unexpected. I thought I had applied all the safeguards to specifically prevent these controls working on birth ties.

PurpleYouko:

--- Quote ---They affect the tie port on the top of the stack, so:
50 2 settielen
Would permanently set the length of the tie on tie port 2 to 50
--- End quote ---
Numsgil and I actually had a discussion along these lines once before.
The general consensus was that making the system work with two numbers on top of the stack would be detrimental to evolutionary advances since it makes the chances of evolving a specific sequence a lot lower.
I could be wrong though. It was quite a while ago but as far as I remember that was the reason I used the tie controls the way they are now.

I would have no objection to switching them to the method you suggest as long as we can get a consensus decision among DB users.

Very few robots (probably all my own) have really utilized the tieport controls anyway.

Navigation

[0] Message Index

[#] Next page

[*] Previous page