While I was working on this bug report, I discovered that ruckig has an offline trajectory mode which solves all my problems in life. Still, I think this is a bug and tracking it down will make the world a better place.
I want to piece together several trajectories but there were always jumps in the transition points. I attached an example. Sorry the code is so redundant but this was the easiest way to generate the problem from my cpp source.
I noticed that it's always just one parameter that has a problem. I suspect that it's the critical one that determines the duration and you just forgot to slow this one down to the next biggest multiple of dt.
While I was working on this bug report, I discovered that ruckig has an offline trajectory mode which solves all my problems in life. Still, I think this is a bug and tracking it down will make the world a better place.
I want to piece together several trajectories but there were always jumps in the transition points. I attached an example. Sorry the code is so redundant but this was the easiest way to generate the problem from my cpp source.
I noticed that it's always just one parameter that has a problem. I suspect that it's the critical one that determines the duration and you just forgot to slow this one down to the next biggest multiple of dt.