Am I correct in assuming that the issues with the “Pick Point”-node when using it with Dynamo Player are still present in 2025.2?
Picking a point on “integer values” (eg. X = 5, Y = 5) does work with dynamo player but picking non-integer values (eg. X = 5.25, Y = 5.25) results in
X = 12618200205442804.0000
Y = 14268423939782906.0000
Is there a way to pick a point using dynamo player?
Hi @pumpaij,
There should not be any issues using the node in Dynamo Player. In fact, the “Hatch Areas Table” sample that comes with the product uses the Pick Point node for the table insertion point, and it has a point already selected:
That’s really weird - for me, there are issues and not only in 2025.2.1 but also in 2026.
The coordinates are recognized correctly when you pick a point within dynamo player but once you hit “run”, they are transformed into gibberish.
This is my testing script:
The point is displayed correctly when you pick it in dynamo player:
But once you hit “Run”, it’s turned into:
The provided “Hatch Areas”-script also fails but for some strange reason in a different order of magnitude.
Picking point:
This is true for 2025.2.1 and for 2026 (all examples are done in 2026).
My initial thought was that the “Country and Region”-settings of Windows might be the cause of this issue as our decimal-seperator is a point and not a comma but it also fails when I set it to a comma.
So yeah, the “Pick point”-node would be really nice but I think it still doesn’t work in an Dynamo-Player-environment.
Civil3d-version:
Dynamo version:
Dynamo Player version:
Thanks. Is it only an issue in Dynamo Player?
I tested Pick Point node for selecting center points for creating circles both on 2025 and 2026 and node works perfect. Also picked coordinates are displayed the same in Dynamo Player after running script.
Maybe some add-on or Country-Kit is causing this strange behaviour?
Thank you for all your replies!
Is it only an issue in Dynamo Player?
It’s only in Dynamo Player, using standard Dynamo everything works normally.
(Of course it would be neat if it worked in Dynamo Player since people are more afraid to open up scripts/have to know what they are doing.)
Maybe some add-on or Country-Kit is causing this strange behaviour?
I’ve installed Civil3d 2026 just for testing if this behaviour is still present so it’s a vanilla-install without any add-ons or country kits. I’ve furthermore tested on three different machines and I could always reproduce this behaviour.
One guess is that it might have something to do with the geman version I’m using?
The Dynamo-example e.g. has “Surface” selected in the “Choose object type”-node so it fails if I don’t change that to “Hatches”.
But I’m just grasping at straws here.
Update (and only tested with 2025.2, as this is the version installed on this machine):
Okay, this is wild - after some testing while writing this post, I think I’ve narrowed it down a bit:
It does work correctly, if the script is open in Dynamo while I run the script in Dynamo Player. No issues.
If I close Dynamo and only launch Dynamo Player, the output always reverts to the value that was prepicked in Dynamo BUT it messes up the inputs in the same fashion as this issue.
So if I prepick [0.5|0.5] in Dynamo, close Dynamo and launch Dynamo player, the prepicked point is turned into [5.0|5.0]. I can now pick any point using Dynamo Player, the output will always be [5.0|5.0], regardless of which point I picked.
As in my initial script I had prepicked a point with large coordinates, the output was always this point being messed up, regardless of which point I picked.
(If I prepick the point [1999.999|1999.999] and launch Dynamo player, the input is converted to [1999999.000|1999999.000])
Edit:
If I don’t prepick a point in the Dynamo Script, save, exit Dynamo and launch Dynamo Player, I don’t get a point at all as an output because it always reverts to the script, where no point is selected.
I will test in 2026 later.
My solution for now has been to draw a point and select that point using “Select Object”. I havn’t run into issues using that approach:
Absolutely! I’m just trying to isolate the problem at this stage.
This is a known issue with dropdown nodes in non-English versions of Civil 3D that we recently fixed (will be in the next update).
This is helpful - thank you for the details.
