Create Rectangle - Ctr and Rot

[Benson Shaw]

Starting a new Marionette project, and once again stalled at step 1. Literally! Need to create a rectangle with parametric size, center location and rotation angle about its center point.

 

Create Rectangle node places the rectangle insertion (origin) as the lower left corner.

• I need rectangle to insert at its Center. I could alter insertion by tying to width & height inputs (half ea). not shown. Other ways?
• Create Rectangle has a vRot input, but I cannot find a node for angle in v output.  How is this input controlled?

 

I found @DomC's Enhanced Rectangle mode which is PERFECT! But would also like comment/advice on above questions for the standard rectangle node.

 

I am always a beginner when I start exploring Marionette. It's tantalizing, but so many uncertainties and unexpected results make me reluctant to use it.

 

-B

 

Edited May 30 by Benson Shaw
It's to late to say you're sorry

[the frog]

Hello this is one of the first version of marionette rectangle. I'd rather use Dom.C

rectangle old version.vwx

[Benson Shaw]

Alright. Thanks, @the frog for digging it up.

This old nRectangle node is not in the current defaults library.  It has limitations. . .

 

Nice to see some old kit.

 

Does anyone have a better way to do the rotation with this rectangle node.  I could not find a "v" type (vector) node for angles., only "n" type (numeric).

 

Sticking with @DomC custom node for now.

 

OK, more questions later about setting and adjusting position of EAP path endpoints.

Thanks

 

-B

[Marissa Farrell]

The 'v' prefix is just to let users know they need to supply a tuple. You can either use a Point2/3D node or a Vec2/3D node when you see it. Vectors are 2/3D values.

I'm working on making the library more user-friendly, so I will make a note to look into better ways to handle this.

[Letti R]

Hello,

 

in the attached file you can find 3 ways on how to do it with standard nodes.

I hope you have fun exploring the solutions.

center_rect_rotated.vwx

 

Regards,

Letti

 

[Benson Shaw]

@Letti R  Many thanks for those examples!  I'm guessing that if you need a rectangle in some new network, you have one or more of those saved.  Or do you just make one on the fly each time?

 

@Marissa Farrell Thanks for any efforts to make Marionette more user friendly.  I'm wondering how that Rectangle node was envisioned?   It certainly needs a lot of mods to make it behave similar to the Rectangle tool in vwx basic tool set.  The networks assembled by @Letti R, and the Enhanced Rectangle by @DomC are more user friendly because predictable/familiar in parameter adjustment.  Also, what about that Rotate node description showing rotation parameter in radians, but it behaves as expected with degree input ???  I do understand that the Angle (degrees) node in the image is a Real node, renamed.  But the network by @Letti R responds as expected to angle inputs.

 

-B

 

Edited June 3 by Benson Shaw
How would I know?

[Marissa Farrell]

Many of these nodes were made before my time, and from what I can tell are exact translations of the VectorScript functions that were used. I don't think a lot of "user friendly" thought was put into them.

For example, the Texture nodes have always been a headache for me. 

They haven't gotten the attention they deserve, but since there are so many, I've been tackling them in phases. A few versions ago I reduced the number of nodes by at least 75 since they did similar things to one another, but were named as if they would only work on specific object types. I'm currently going through and looking for gaps in functionality, poor implementation, etc., to get in for next version, but I do think it will be a phase-based process.

If you have other specific nodes that you think deserve a more rapid facelift, please let me know. There are limitations to what can be done in an update vs. a new version.

[Benson Shaw]

@Marissa FarrellSuper! Please carry on with this!

2 hours ago, Marissa Farrell said:

They haven't gotten the attention they deserve

 

2 hours ago, Marissa Farrell said:

If you have other specific nodes that

Seems such requests could be added to a specific thread. Perhaps pinned to top of Marionette forum?

 

One problem is mods to existing nodes can break existing networks. Adding new, improved node (with similar name) to the library would be a possible solution.

 

-B

[Marissa Farrell]

6 minutes ago, Benson Shaw said:

One problem is mods to existing nodes can break existing networks.

This is the caveat which determines whether a change can be made within an update or has to wait for a version.
Currently, when you bring a file from an earlier version into a newer version, the link to the Python file is broken in each node to prevent the concern you have.
Due to this, when a node's functionality needs to be changed, we wait for a new version. Bug fixes and new nodes are the only changes we make during updates.

[the frog]

Hello

Jumping on what you said “For example, the Texture nodes have always been a headache for me.” The textures in Marionette are just a nightmare.

Since the beginning the random texture problem is yet unsolved. Why are the textures changing name as the script is executed? Even when you download the file a new unknown texture can replace the one in the file. For us this is the true limit for using the scripts in our flow. Too much time lost on this matter as the object changes some textures as you try to only change one.

Yes, a new well working node that would allow all the texture parameters in one node would be great. This would be a good way to put the Advil back in the closet.

 

[Letti R]

Hello,

 

@Benson Shaw i unfortunately dont make alot of Marionettes at the Moment. And those that i make are always vastly different from eachother. In the Beginning i tried to make and maintain a collection of wrappers, but i ended up not using them.

 

But please dont think that i just know how to do a Marionette Network from the top of my head. Figuring out how everything works is just part of the fun (for me). By the way, i also fell for the wrong description of the "Rotate" node and converted the angle value to radians.

 

Regards,

Letti