User Forum of Software BASEMENT

Matteo Facchini

Developer

From: Trento

Registered: 2014-09-05

Posts: 301

No edges found for node string

I report here a post concerning what seems to be a basemesh bug

Cheers
Matteo

EDIT: in my case, it happens for particularly long stringdefs (hundreds of nodes). The work around is to divide the stringdef in shorter segments.

Last edited by Matteo Facchini (2023-04-07 15:38:10)

Lukas Vonwiller

Developer

Registered: 2014-09-04

Posts: 159

Re: No edges found for node string

Ciao Matteo

Nodestrings (NS in the .2dm mesh) are limited to max. 200 nodes. 

Cheers, Lukas

Matthias Bürgler

Developer

From: Zürich

Registered: 2019-04-04

Posts: 178

Re: No edges found for node string

Do I understand the bug report correctly, in that BASEMESH produces meshs with a wrong order of node IDs in the nodestrings?

Matteo Facchini

Developer

From: Trento

Registered: 2014-09-05

Posts: 301

Re: No edges found for node string

Yes, but I guess it is related to what Lukas wrote: my stringdef was defined by more than 200 nodes. The numbering seems to be correct until a certain node.

Do you want me to send you the shape files to reproduce the issue?

Last edited by Matteo Facchini (2023-04-19 15:04:52)

Matteo Facchini

Developer

From: Trento

Registered: 2014-09-05

Posts: 301

Re: No edges found for node string

UPDATE
I think numbering is based mainly on coordinates, so if a stringdef let's say goes from south-west to north-east and then to north-west (triangle shape) something goes wrong in the numbering, because x-coordinates overlap, even though y-coordinates do not.