DynamoDS / Dynamo

Open Source Graphical Programming for Design
https://dynamobim.org
Other
1.74k stars 634 forks source link

"Failed to construct..." warning when trying to create a simple Polygon by points (Dynamo 2.16.1.2727) #13689

Open pantoniadis opened 1 year ago

pantoniadis commented 1 year ago

If this issue is with Dynamo for Revit, please post your issue on the Dynamo for Revit Issues page.

If this issue is not a bug report or improvement request, please check the Dynamo forum, and start a thread there to discuss your issue.

Dynamo version

2.16.1.2727

Operating system

Windows 10

What did you do?

Tried to create a simple polygon by points (see attached picture).

What did you expect to see?

A polygon

What did you see instead?

I got a Failed to construct a Polygon from the input points: ACIS_EXCEPTION_FLT_OVERFLOW – Floating point overflow Note that the same issue appears when writing a simple code block, for example this:

point1=Point.ByCoordinates(0,0,0); point2=Point.ByCoordinates(0,10,0); point3=Point.ByCoordinates(10,10,0); point4=Point.ByCoordinates(10,0,0); t1=[point1, point2, point3, point4]; polygon1=Polygon.ByPoints(t1);

....gets the same failure message.

Note also that:

image
github-actions[bot] commented 1 year ago

Thank you for submitting the issue to us. We are sorry to see you get stuck with your workflow. While waiting for our team member to respond, please feel free to browse our forum at https://forum.dynamobim.com/ for more Dynamo related information.

avidit commented 1 year ago

I wasn't able to reproduce this error. Are there any packages installed?

pantoniadis commented 1 year ago

No, i don't have any packages installed:

image
Amoursol commented 1 year ago

@pantoniadis this is a bug with our geometry kernel that will be fixed at the next Revit hotfix and in the upcoming Revit 2024 global launch release. We sincerely apologize for missing this.

This unfortunately means we cannot resolve it in Dynamo alone, and have to wait for said fix to propagate outwards.

aparajit-pratap commented 1 year ago

It should also be fixed in Revit 2023.1.2.

pantoniadis commented 1 year ago

Thank you!