-
Posts
1,474 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by Marissa Farrell
-
-
-
I'm going to agree with Kevin's assumption that it's because the profile is a 3D poly instead of a 2D shape.
-
I think you will find that this isn't as easy as you're hoping.
A camera object is considered a plug-in object, and currently I'm not aware of any exposed functions to create one.
I tried using a camera as Control Geometry, but it appears that you can't activate it if you do that.
For now, I hate to say that I can't see a solution to this, but I'll keep it in mind and report back if I find any promising leads.
-
Yeah, the only way that I know of would be to copy/paste into the node.
The top part of a Marionette script is only run when opening/closing the script editor, so there's no way to populate it by running a script unfortunately.
-
Update: I actually did get it to work in Top/Plan just using curves, so that may not be it.
-
-
-
... Just as a quick followup, the Curve node in this file should accept 2D points as input...
-
No problem! We're usually pretty quick on the forums
Let us know if you need any more guidance!
-
Alright, so at a first glance, the most glaring issue I'm seeing is that you're using "Point2" nodes instead of "Point3".
I can work on getting a change in where that won't matter later on, but for now try using Point3 nodes with your Z set to zero (assuming that's what you want), and let me know if that works any better.
-
2 minutes ago, gonzalezj said:
Hello,
How does the Nurbs Curve node work in Marionette? I currently have an ordered list plugged in, a Bool to make the Nurbs Curve tool false so that it interpolates between the provided points, and a Real node with the value of 3 for the curves degrees. When i run the script I get an error with the Nurbs Curve node. Are these the incorrect inputs? Any recommendations welcome.
Thanks!
Can you provide a file, if not, could you provide a screenshot of your error message?
Thanks!
- 1
-
At this point in time the information must be written right into the node. We do not have the ability to create dynamic OIP controls.
-
-
If you need any help with Marionette (including custom nodes) let me or the rest of the Marionette community know and I'm sure we can help you figure it out. It's good practice for us and provides good resources for other users that may have a similar use case.
- 2
-
25 minutes ago, gorrunyo said:
The rotation angle seems to be in radians.
YES!
Good catch. I'll work on a fix for this. For now, there is a node "Degrees to Radians" in Math>Angular Conversion that you can use for converting your values.
-
I've never had good luck texturing with Marionette, so I don't bother anymore...
However I did investigate this, and with a 'value' of 1.57, it appears to rotate the texture to where you want. I have no idea how 1.57 relates to 90 degrees, though.
-
popup
in Marionette
Alan, you're correct that the line of code at the top prevents you from making edits to the node until you alter/remove it (more on altering it later...)
This allows us internally to track changes made to the default content which we could not do before.
-
popup
in Marionette
Attached is a modified Popup List node that does what you would like.
If you need any help understanding this method, please let me know.
- 1
-
What you want to use in this case is the "PIO Handle" node in the Object info category. The "PIO Handle" returns the handle to the resulting Marionette Object and can only be used in Marionette Objects.
The best way to combine these together is with a "pass" node.
I've attached an example. Let me know if you need further clarification.
-
Hi Patrick,
Have you run the "refresh libraries" command from the Resource manager?
If you still don't see them after that, restart vectorworks.
That's been working for me, let me know if it doesn't for you and I'll help you troubleshoot further.
-
I don't believe so. There was new functionality introduced, though I haven't worked with it enough to properly explain it, that will allow users to define parts to be textured within Marionette so that you can modify them with the OIP. I'll hopefully get a handle on that soon and put out a demonstration, and hopefully that will solve some of the issues people are facing.
-
Hey Alan,
It appears that the Get Object Count node is improperly labeled at its ports. The input should actually be a LAYER, as the node will count all of the objects on a specific layer.
I think that for what you're trying to accomplish, you can use "Get List Length" from the Data Flow category.
I'll be sure to update that node to be more user friendly as soon as I can.
Thanks for pointing this out!
- 1
-
Great! Let me know if you run into any further issues with it.
-
I haven't really gotten a final say on what state it is in, but as for the numbering not working past 9, try going through the alphabet instead of 10. so ... 7, 8, 9, A, B, C, ...
Can't promise that will be the solution, but it may be the logic they've used on the back end secret to me.
I still don't bother using it, and although I hate suggesting you don't as well, if you run into things like this the only thing we can do is wait to see if it gets accepted as a bug or not.
Extrude along non planar path NURBS
in General Discussion
Posted
Another method, aside from Jim's, would be with the path object selected, go to Model > 3D Power Pack > Rebuild NURBS...
You can keep the same number of vertices.
Only issue I ran into was when using your profile shape as-is, the orientation is skewed following the path, but this can be remedied by either drawing your rectangle in Top/Plan or editing your Profile position after you've generated your EAP.