Marissa Farrell
-
Posts
1,473 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by Marissa Farrell
-
-
There's also an Color input node that will pass the color of the node as a tuple in the Input category, if you wanted to pursue that option instead.
-
1
-
-
4 hours ago, Benson Shaw said:
@Marissa Farrell I can reliably recreate the problem. I think is result of order of reproduction. My theory is that the nodes manifest first, then the Marionette classes are formed after. The nodes are not connecting to (recognizing? recognized by?) their classes.
Classes do not matter for the purpose of wiring, that shouldn't affect this at all.
I still am unable to reproduce this following the steps you've given me. Which build are you using? I was able to see the error you mention in the file you shared with the error already present, but I cannot get my own copy-paste to have the failure.
This, however, is similar to another issue that was posted on the forum recently, so I don't doubt it's happening, I just need to be able to reproduce it to further investigate.
-
13 hours ago, Benson Shaw said:
But a syntax error results if all elements are copy/paste into a new blank file (also attached).
I didn't run into an issue when copy-pasting to a new file. Let's look into this more. Could you try it again?
10 hours ago, Benson Shaw said:Goal: Run the network. A new object is created and remains selected. Subsequent run commands create new object from the selected object from previous run.
This will be tricky because objects created by Marionette are replaced on each run
10 hours ago, Benson Shaw said:Even worse if the wrapper is converted to Mobject: The Mojbect disappears and relocates to the same layer as the new object from the network.
Marionette Objects are Plug-In Objects. All objects within (created by) a Marionette Object will be on the same layer, just as with every other Plug-In Object.
10 hours ago, Benson Shaw said:also, it's invisible, so, um, where exactly is it?
It's likely there's something within your script that is working incorrectly, or unexpectedly. This will result in an empty Marionette Object (there's an open bug for this)
-
As much as I advocate for Marionette, I will always stand by the opinion that a traditional script is the way to go if it's doable for you! Marionette, to me, is just a way to hold your hand while you learn.
I'd like to suggest you also try recreating this script using Python in Vectorworks, just to introduce you to a different set of syntax that generally is more user-friendly than traditional Vectorscript. It shouldn't be hard to translate 🙂
-
21 minutes ago, Marissa Farrell said:
I was able to recover the object - for now, I've added a locus object so that you can still grab the object when pasting between files, you'll need to update the object in some way after copying it for the object to appear (move it, run the Reset All Plug-Ins command, etc.)
I think I have another idea if the locus isn't suitable for you.
This happens because your object is relying on other resources (your symbol insertion) and my theory is that the objects are being copied over AFTER the Marionette object is created, and since your network calls for them and they aren't yet present, the object fails.
I'd like to correct myself here and provide a better solution.
Your symbol resource that you reference is NOT being carried over when you copy it, I'm actually not sure how it's fixing itself.
The attached file is a better solution. I advise you to place all resources that your network requires within the Marionette script container (you'll notice in this file if you edit your script that there is a group of objects, within that group are symbol instances of the symbols you've referenced in your popup)
-
2
-
-
18 hours ago, Pat Stanford said:
And they look like they were produces on a layer with a very small scale.
Funny you mention this - I've been working within nodes in recent builds to test out some script changes and every node I enter and change resizes when I edit it. I'll have to look into this a little deeper though because I know when we place resources from the RM or tool, they come in correctly. I'm wondering if they're existing within wrappers/objects at an incorrect scale now...
-
17 hours ago, AlistairM said:
It sounds like it could be a similar issue.
I have another file here, in which I isolated a problem node. I suspect that this was to do with copying between files. Maybe this simple example will help identify the issue.
Can you tell me how you got that second node into the file exactly? This node doesn't have the preprocessor command so it's not looking for a script elsewhere (unless you've customized your python scripts in your install) so that shouldn't be the issue.
What version and build were you using when placing that object in the file? Was it two separate installs?
-
I was able to recover the object - for now, I've added a locus object so that you can still grab the object when pasting between files, you'll need to update the object in some way after copying it for the object to appear (move it, run the Reset All Plug-Ins command, etc.)
I think I have another idea if the locus isn't suitable for you.
This happens because your object is relying on other resources (your symbol insertion) and my theory is that the objects are being copied over AFTER the Marionette object is created, and since your network calls for them and they aren't yet present, the object fails.
-
1
-
-
@m.graf - good catch! I hadn't thought of computer localizations.
-
Something is wrong with your network, the value you're getting with the scientific representation means it's not getting the right value...
Can you attach that file?
There's currently not a direct node that converts strings to a number in the default library because there can be different number formats in strings, for example if a user has feet & inches for their document units then the input will need to be treated differently than a user with meters for their units.
-
I've attached a script that doesn't use the worksheet for data, but just queries the individual existing tree objects.
Let me know if this is a suitable solution.
-
It looks like this is due to using a User Origin in the "Wrong" file. Looking into a solution 🙂
-
This should clean that up for you 🙂
You've brought to my attention some shortcomings with the group node, so I'll work on improving that!
-
2
-
-
Which version was this file originally created in, do you know?
-
I don't believe it's possible to export groups as geometry with IFC attached, I think you need to attach the IFC tags directly to the geometry.
Please let me know if I'm misunderstanding. I'm still trying to determine why the Marionette object isn't exporting correctly.
-
1
-
-
Ok, so I'm finding that if I ungroup the Marionette object that I can get it to export to IFC, so I'm digging around inside the network.
I see 4 drawn objects, are you expecting 4 IFC entities to be output? because more IFC properties are being assigned within your script. Just trying to get a handle on things.
-
What viewer are you using? I am able to see Marionette objects exported as IFC when created correctly.
Can you attach the file you're having issues with?
-
Can you attach a sample object so I can get a better understanding?
-
I asked the engineers and unfortunately was given some bad news where there's no simple way to get whether it's assigned to the existing or proposed site model.
I'm going to try a little more digging to see if I can determine another way, but in the meantime I'm going to put in an enhancement request to get that value exposed to the user.
-
1
-
-
Can you be more descriptive as to the end goal? Are you trying to split the object? Are you trying to just find points?
-
Could you attach a small example of a file with a site model and these objects? I'm not very familiar with site models, etc., so having something to work off of will help me to take a look.
-
The easiest way to do this would be to place the line lengths and line objects into a sortable list (which in my example I use a point node to make tuples)
-
2
-
-
1 hour ago, Pat Stanford said:
I am relatively certain that the ability to lock/protect Marionette networks has been asked for but if this is important to you an addition to the Wish List forum would be a good idea.
Correct - this has been asked for in the past. Last time I recall discussing it we wanted to keep Marionette open source.
-
1
-
-
What issue are you running into? I'm still able to successfully make Marionette objects that have separate top/plan and 3D visuals using the current node library.
Set the feature service of a layer with Vectorscript?
in Vectorscript
Posted
I'm not seeing any VS function accessibility for feature layers at this moment in my list, either.
I can throw an enhancement request in for you if you'd like?