Our Robot sometimes moves before the cable can spawn correctly, it seems as if its an old state sometimes but we are not sure about that.
Has anyone experienced similar issues when using the evaluation? When we spawn the scene directly its not an issue.
I can confirm that we observed that as well. It only happens every so often and we’ve been just working around it. I hope we’re not expected to train policies that deal with this kind of situation - but since this is may be a timing issue in the toolkit and we can’t change that anyway, my gut feeling would be no.
Yes, I’ve experienced that too, it can even hit something and move the tip.. looks like a vector that is not set back to zero from one task to the other.
Same situation here.
Does this track? Fought this for almost a day through policy side mitigation but the bug is in the engine. Possible engine bug between trials
Our Team has 3 submissions that all ran fine on local simulation, but were penalized on the Intrinsic server for ‘Cable not spawned’ in T1, (resulting in a 1 score in T1) all three times. Is this the same bug?