When adding cicrle move from URCAP in czech language, all via points are same. Also all end points are same. URCAP works fine when language is english or when english programming is chosen.
Affected Version(s):
polyscope 5.17.2
It works on CB3 robots
Problem here in script from e-series robot is visible - all via point share same variable and all end point share same variable
real_e-series.script (2.8 KB)
real_CB3.script (9.1 KB)
We are encountering the same problem. It needs to be resolved very quickly. We are currently unable to program circular movements. The issue likely lies in the translation into Czech. Please provide an urgent solution.
Hello @honza.jelwa & @vaclav.ponocny
Thank you for pointing this issue out!
I was able to reproduce the behavior, forwarded the topic internally and we will keep you in the loop on its status.
In the meantime I would recommend to use the “English Programming” setting as a workaround.
/Stefan
I am reporting the same issue as previously mentioned. This situation is absolutely unacceptable, and I require an immediate resolution. We have been waiting far too long for a fix to what should be a simple issue. It is unacceptable that you are avoiding solving it by merely switching the programming to English. We demand to know a specific date when this issue will be resolved. Thank you.
No reason to get upset over it. It has been reported, and UR has acknowledged it as a bug.
It is not a critical bug in any way, since you can use English programming until a fix is made in a future software update.
It is a long process to make software changes with regards to identifying the issue, implementing the changes, testing the new software, making documentation and then releasing it.
I am 100% sure that UR will fix the issue in an update, but it’s not done overnight. 
1 Like
Hello, Oh, that’s just fantastic that it’s not a critical bug, even though it complicates users’ work every single day! Three months have passed, and still nothing? That’s an absolutely incredible pace—how does software development even work if just identifying the issue takes a quarter of a year? Not to mention, using English programming isn’t a solution; it’s a workaround that costs users time, nerves, and efficiency.
Documentation, testing, and releasing? Those are standard processes for any software company, so why does it suddenly seem like climbing Mount Everest? And what about communication? Where are the regular updates to show progress, so people don’t feel like they’re being ignored?
So, thanks for the “ 
” update from three months ago, but now it’s time for less talk and more action.
A happy holidays to you, Roman.
A quick note; I am not associated with Universal Robots. Just a regular user as you are. So do not get upset over them based on my replies.
Oh, great, so I’ve been barking up the wrong tree this whole time! My bad, Efn—thanks for the clarification. And happy holidays to you too. I’ll save my frustration for UR directly; they’ve definitely earned it.