-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add support for instancing #26
Comments
I started redesigning parts of the mtoh plugin to support instances; the current state can be found in the feature/instances branch. Also, from now on big features should happen in a separate branch to avoid breaking the master branch too often. There are a couple of challenges (besides figuring out what's the best way to use the instancer) associated with this task. Mostly regarding callbacks. We'll need to create a large number of extra callbacks to track visibility and update transformation values for each instance, including a smart caching of the data. Instancers work via re-creating transformation matrices for each instance via translate / rotate / scale, and for now, they seem to be the only option to support instances. Same goes for tracking visibilities. Deleting instanced nodes are not trivial either, especially when we delete the master and Maya makes the next instance the master. That'll probably require a full rebuild of instancer / source mesh. Also, I'm not sure how can we assign separate materials to each instance. |
Pushed back an initial implementation (and merged it to master) to features/instances that support static instances (movement updates are not applied, deleting instances doesn't work either etc). |
Updates, hiding / unhiding and deleting instances (except the first instance) works well now. There are a few problems left:
|
Solved several issues with the latest commits in feature/instances.
The code is just thrown together and needlessly overcomplicated at this point now; I'm going to take a look at simplifying the changes before focusing on the other problems. There are some unresolved issues left:
|
Note: once #28 is closed, handling instances will be much more streamlined. |
I'm creating tickets for the remaining issues, so fixing those could happen after the initial release. |
No description provided.
The text was updated successfully, but these errors were encountered: