-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem exporting geometry per vertices #12
Comments
I can't replicate. I would need a Blend file that exhibits this. |
Hi Ryan, Please find attached a blend file. It contains a house structure grouped in 6 rooms. See image below: The issue happens only when |
@rgsouthall did you fix this issue? With the latest git version I am not getting this error anymore. |
I did not fix it per se as it's a geometry problem, but the VI-Suite now reports zero area if the area associated with a vertex cannot be calculated instead of throwing up an error.. |
Ok, but I am a bit puzzled now. Shouldn't this be zero anyways? |
I use an algorithm to calculate a pseudo vertex area from neighbouring
faces.
…On Thu, 29 Oct 2020 at 13:51, ttsesm ***@***.***> wrote:
Ok, but I am a bit puzzled now. Shouldn't this be zero anyways?
How do you specify the area of a point since it is a single point. I mean
for a face you get the area of the shape based on the vertices that
structure the face but for a vertex/point how you do that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOOW4VVWYWL3FGQSMBOEDLSNFXMTANCNFSM4STH4CTQ>
.
|
Ok, I see. Thanks for the clarification. |
I guess this is also addressed in commit 19f4be8 |
Hi Ryan,
I was working with some geometries and I've noticed that exporting the geometry per vertices in the
LiVi Geometry
node for some of them was failing with the following error:The corresponding per faces option seems to work without issues on the other hand.
The text was updated successfully, but these errors were encountered: