node to take locators as inputs

[playmesumch00ns]

For the inputs you'll need to use an array of compound attributes. These are just tuples of float attributes that can be grouped together, like a colour, or a position.

For doing the closest face calculation, i'd just do something like you suggested to start off with, to check the rest of the algorithm is working, then worry about optimizing it.

You could theoretically do the screen-space framebuffer thing. But what about faces on the back of the mesh? And what about aliasing?

Much better would be to use a data structure like a kd-tree to optimize your searching.

[mummey]

hmmm... that username tooks familiar... ;)

[jhuangtw]

mummey: wasup brian :P

playmesumch00ns: thanks for your reply, i didnt think about the aliasing/backface problem. i think for now i'll just use the more brute-force-ish approach to get the algorithm working first.

[mummey]

Hi all.
i'm trying to create some sort of a modifier node for polymesh, where it would take the inputs of multiple locators' world space as inputs, and based on them, recompute internal data and refresh the mesh.

i am having trouble trying to understand how to set it up so that the node is constantly watching these locators, and updating when the locators move.

Look up the 'Observer' design pattern for possible ideas. This is an OO structure that refreshes when changes are made.

As for the rest of it, I don't know what Maya provides/restricts. Good luck figuring it out.

-b

[playmesumch00ns]

You don't need to worry about handling updates since Maya's DAG will do that for you automatically.

If i remember correctly, Maya's MFnMesh class provides you with a closestPointOnMesh function, which is essentially what you want to write... beware that closestPointOnMesh is notoriously slow and buggy, but it should be enough to get you started while you get the rest of the plugin written, then you can replace it with your own optimized version later.

To be honest, the hardest part of this is probably going to be setting up and managing the connections between the mesh and you locators. Maya provides all the functionality you need to do that already, but it can be a pain in the arse to use sometimes. I'd concentrate on getting that part bulletproof first, then look at the closesPointOnMesh thing...

[jhuangtw]

hi all, thanks for the suggestions. as suggested i'll look into the closestPointOnMesh function later. for now i'm reading up david gould's book again to try to figure out the array of compound attributes.

the life cycle of the node goes something like this:
- node created, it will modify a output mesh. no locator "hooked on" at this point
- command to create a new locator and the locator is hooked onto the node. the node takes the positions of the newly created locator and recomputes, then modify the output mesh accordingly.
- more locators are added/deleted as the session goes on.

i'm still not exactly sure how to do this yet. can i use MEL to create locators and plug their translate attributes into the node's array attribute, or should i also write a command plugin to create the locators and set up the attribute connections? i was thinking if i could use MEL because i have a mel GUI that would keep a scrolllist of these locators.

this is my first stab at the maya api, this is exciting stuff :) and thanks for all the helps, i really appreciate them.

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.