Support per face and per edge custom attributes for PLY import #126339

New Issue

Tolga Yildiz · 2024-08-14T23:33:58+02:00

Tolga Yildiz commented

2024-08-14 23:33:58 +02:00

Currently only the per vertex custom attributes are supported for PLY importer. We can add the functionality to parse the per face and per edge data from the header and construct the geometry with these attributes.

Tolga Yildiz added the

Type

To Do

label 2024-08-14 23:33:58 +02:00

Iliya Katushenock commented

2024-08-14 23:36:20 +02:00

Thanks for the report, but please use other channels for user feedback and feature requests: https://developer.blender.org/docs/handbook/communication/user_feedback/

For more information on why this isn't considered a bug, visit: https://developer.blender.org/docs/handbook/bug_reports/not_a_bug/

Thanks for the report, but please use other channels for user feedback and feature requests: https://developer.blender.org/docs/handbook/communication/user_feedback/ For more information on why this isn't considered a bug, visit: https://developer.blender.org/docs/handbook/bug_reports/not_a_bug/

👍 1

Iliya Katushenock closed this issue

2024-08-14 23:36:24 +02:00

Blender Bot added the

Status

Archived

label 2024-08-14 23:36:27 +02:00

Iliya Katushenock commented

2024-08-14 23:48:21 +02:00

Just to make it clear, geometry nodes have a face corner attribute domain which is used both for corner vertices and edges. In case PLY import support face-corners and node do that, there is nothing to change, everything is as expected.

In case of PLY does not support face corner attributes than it might be an issue on the side of format itself.

Just to make it clear, geometry nodes have a face corner attribute domain which is used both for corner vertices and edges. In case PLY import support face-corners and node do that, there is nothing to change, everything is as expected. In case of PLY does not support face corner attributes than it might be an issue on the side of format itself.

Jesse Yurkovich commented

2024-08-14 23:49:38 +02:00

@bebop_artist Did you intend to work on this yourself? If so, the Pipeline and Assets module would welcome this tracking todo item here and I'll reopen if so.

Tolga Yildiz commented

2024-08-15 00:05:08 +02:00

Yes I will work on this at least on my fork, I was trying to get some data into blender from another python program for viz and debug.

I could have done it in the python API but that requires to install additional stuff to blender's bundled interpreter and the data generation steps are quite long. So instead I just run my python program and generate results with the custom attributes then save them.

I was searching for any kind of visualizer to work with those and so far the MeshLab is the only one, which only reads single per face color. With the current proposition we can have multiple colors/attributes in a single PLY file and determine which one to visualize in the geometry node editor.

Yes I will work on this at least on my fork, I was trying to get some data into blender from another python program for viz and debug. I could have done it in the python API but that requires to install additional stuff to blender's bundled interpreter and the data generation steps are quite long. So instead I just run my python program and generate results with the custom attributes then save them. I was searching for any kind of visualizer to work with those and so far the MeshLab is the only one, which only reads single per face color. With the current proposition we can have multiple colors/attributes in a single PLY file and determine which one to visualize in the geometry node editor.

Iliya Katushenock commented

2024-08-15 00:06:50 +02:00

I do not think you could do anything on a python to change geometry nodes behavior.

Tolga Yildiz commented

2024-08-15 00:12:31 +02:00

With the python API I could have defined the blender mesh with any kind of custom attributes with any kind of data type, I have done it before for another project for various attributes of the procedural generation process(like at which iteration which features are marked etc.), not the geometry nodes of course.

Here is an example

But this allowed me to process the blender mesh in the geometry nodes afterwards by using those custom defined attributes.

With the python API I could have defined the blender mesh with any kind of custom attributes with any kind of data type, I have done it before [for another project ](https://github.com/ComicAddict/gs3d_blender/blob/main/Node%20Structures.py) for various attributes of the procedural generation process(like at which iteration which features are marked etc.), not the geometry nodes of course. Here is an [example](https://blender.stackexchange.com/questions/266991/manually-setting-custom-attributes-per-edge-vertex-etc) But this allowed me to process the blender mesh in the geometry nodes afterwards by using those custom defined attributes.

Jesse Yurkovich commented

2024-08-15 00:29:10 +02:00

I'll reopen. @bebop_artist Feel free to edit your original description to organize and track the work you want to go and do. Once you have a PR you can tag it so that it will "Fix" this TODO.

👍 1

Jesse Yurkovich reopened this issue

2024-08-15 00:29:26 +02:00

Blender Bot added

and removed

labels 2024-08-15 00:29:30 +02:00

Jesse Yurkovich added

Module