- Posts: 611
- Thank you received: 114
I think the problem was that the original was the master with Robs stuff added, whereas this is all in his fork of the master
I just cloned Robs fork, checked out the experimantal branch and built it
Please Log in or Create an account to join the conversation.
Rick G wrote:
I think the problem was that the original was the master with Robs stuff added, whereas this is all in his fork of the master
I just cloned Robs fork, checked out the experimantal branch and built it
Should installation instructions be changed?
Rick G
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
That's by design, though it's not optimal. I abort optimization if a
segment is already in progress , to prevent stepping on tp 's toes. Also,
the optimization doesn't run on the last segment in the queue, because that
segment has the potential to be shortened by a future blend arc.
Both of these problems are fixable. I was looking into how to detect "end
if file" in the code, and it seems that the interp_waiting state
corresponds to the interpreter running out of valid moves (rather than just
having a full queue). If this is the case, then a simple check should be
enough to flag the last move. Similarly, I could make blend arc creation
work on the unchanged portion of a segment in progress.
Please Log in or Create an account to join the conversation.
As far as homing - can you give more info? I have not seen constraint violations in quite a while. (homing and otherwise)
Please Log in or Create an account to join the conversation.