elicdavis / polyform

Immutable mesh processing library

Eli C Davis

• Founder of Recolude, a startup that helps game developers record players in-game to provide insight into how their application is used. Follow the progress on twitter or DM me if you have special usecases. Demo here.
• In my free time, I work on a procedural mesh editing and generation library named Polyform. A few utility libraries have spawned from it's undertaking as well that might be useful to others:
  • vector - Immutable vector math library
  • jbtf - GLTF-inspired JSON schema for embedding arbitrary binaries
  • quill - Scheduler of operations on in-memory data
  • sfm - Utilities for interacting with reconstruction data from different SFM programs
  • iter - Iterator and utilities. Some inspiration from ReactiveX
  • bitlib - Utilities for reading and writing binary data

polyform's Issues

Chat Window For Web Socket Connections

Clear all vertex attributes

Binary format for Generator Profile

Profile for a generator needs to be implemented in a binary format to support embedded binary data IE images.

Color grading LUT

Create a function that takes a LUT and a color array and generates a new color array with the LUT applied

https://lettier.github.io/3d-game-shaders-for-beginners/lookup-table.html

OBJ Export Issue When Multiple Materials Share Same Name

Surface Simplification Using Quadric Error Metrics

https://cseweb.ucsd.edu//~ravir/190/2016/garland97.pdf

Bake Texture to Vertex Colors

Luminance of Image to 3D mesh

https://stackoverflow.com/questions/31322052/turn-any-2d-image-into-3d-printable-sculpture-with-code/31339320#31339320

Export OBJ - Support Multiple Meshes

Palette Function

As described here:
https://github.com/donmccurdy/glTF-Transform/blob/main/packages/functions/src/palette.ts

Quad Tree

For Organizing 2D data

Node-based Approach to Generator

Right now, it's hard to define a generator hierarchy that doesn't lead to certain generators doing unneeded repetitive work when certain variables change.

To be as fine-grained as possible to avoid such rework, we need to swap to a node-based approach, where each node explicitly defines its inputs and outputs as pointer references to other nodes. Then changes to one input node can easily be propagated to the rest of the graph.

Also opens up the opportunity for the generator to automatically prune un-used nodes. I think all that would be defined on the app level would be the output nodes, then we'd recurse through their references to get everything needed.

Things to figure out:

• How to define groups and sub groups of variables for sake of web view
  • Or maybe we abandon this and create a new node-view for the web?
• Defining some outputs as debug only
• Defining Dev vs Prod input values

Verify Graph is DAG

At the moment. Nothing stops someone from defining a cyclical graph for a polyform app, which would cause an infinite loop when attempting to run a producer.

Upon the start of a polyform app, we should do a check to ensure the graph is, in fact, acyclic.

Proper Weld

Probably just going to implement this:
https://github.com/donmccurdy/glTF-Transform/blob/main/packages/functions/src/weld.ts

N-dimensional KD Tree

Take care of 4D vectors

Import OBJ - Support Multiple Meshes

Color Node Widget

Binary Tree

For 1D data

Split on Unique Material support Any Topology

New Gizmo: Weighted Point

Menger Sponge

Triangulation

Could look at this for reference:
https://github.com/mattatz/unity-triangulation2D

New Gizmo: AABB

New Gizmo: Line

License ?

Hello, under what license is this project released under ? I would like to study it to learn from it. Thank you.

Laplacian Smoothing constrained to a single Axis

Bonus points if the axis is just any normal vector