[NURBS Curve Direction Arrows]

Before you use the loft tool, select your NURBS curves and check 'show direction' in the OIP, then when you use the loft tool and cycle through your curves, the direction will display.

[Worksheet nodes]

Currently the worksheet nodes don't ship with the software, the only ones are the ones available on the forum. I'm traveling now, but hopefully @JimWcan link you to the appropriate resource. 

[How to move visible objects (not on the active layer)]

Glad to help!

[How to move visible objects (not on the active layer)]

I think if you change the "ForEachObjectInLayer" line to 

 

ForEachObjectInLayer(Fnm,2,0,1);

 

then it should do the trick?

 

I'm only assuming based on the devwiki's description.

http://developer.vectorworks.net/index.php/VS:ForEachObjectInLayer

 

 

EDIT: I just tested, and it appears to work.

[Multiple records in 1 marionette script]

Hi Nico!

 

I'm going to do my best to explain this to you. I've attached a file with a modified version of your original Marionette object.

What I did:

Instead of using the Parent PIO node, I used the resulting object from your Linear Extrude nodes as the 'obj' input to all of the record nodes. This will allow the record to attach only to the extruded rectangles rather than the entire Marionette object.

In order to create a report that shows these records, it's very important that in the "Create Report" dialog box that you select "Options..." and check "Search in plug-in objects." The report will not see those objects otherwise.

 

I increased the lineweight on the nodes that I changed connections on.

 

I hope this helps! Please let me know if I need to clarify anything further.

RecordsAndMarionette_MFarrell.vwx

[Multiple records in 1 marionette script]

16 hours ago, Nico Vindevogel said:

 Is there a way to associate a record to each piece in the script? It is not necessary to see the records in the oip , if its possible to get the data in a regular worksheet it would be perfect.

 

Hi Nico!

Can you clarify for me, are you hoping to have each of the extruded rectangles have different record data, or are you trying to attach the record data to the entirety of the Marionette object?

Both are possible, I just want to make sure we're on the same page before I take things in an entirely different direction than you're looking for.

 

Also, if Alan's example helped at all, then that's great as well  

 

Marissa (aka MFarrell I wrote those nodes.)

[Help with Simple Script]

Okay here's an updated version with OIP controls that allow the changing of both circle radius and font size.

CenterTextOnObject_MFarrell_v2017_v02.vwx

[Help with Simple Script]

Hi Scott -

 

Here's a post that has an example similar to what you're looking for.

 

Take a look at this and see if it helps you, if you need a little more guidance, let me know and I'll do my best to quickly help you!

[IF Node performing a Mix2 at the same time?]

Most nodes will repeat the last item of the shortest list when they are run, which is what you are seeing here. Deleting duplicates would be a good way to fix those errors, as long as there aren't any others that would have the same value that you would need.

 

Another way to handle this would be to return the first x number of items in the list, with x respective to the length of the shortest list. You could probably use the 'Split List' node to do that.

[output drawing order]

10 minutes ago, Chris Brough said:

 

The thread links go to the old forum. is there a way to easily find these threads again?

 

I updated that post to use the correct links!

Hope this helps!

[Marionette Monday Webinar Questions]

@Alan Woodwell and @DSA, are you referring to the file attached at the very beginning of this thread, or somewhere else? Because I am having no issue running the infographics file from the earlier post.

 

I'm attaching the 2017 version here, in case this can help remedy your problems...

 

Infographics_v2017.vwx

[Marionette in 2017]

It appears that the same issue is happening to both of your files when updating to 2017.

 

@Alan Woodwell- in your 2017 file, for some reason the output from your 'add' node is also being wired to your x port on your lower 'Point 2D'

If you remove that wire, your network works fine.

 

@willofmaineAlthough you only attached your 2017 file, it appears that you may also have an extra wire. If you go into your network, I'm assuming the '2Run' node should not also be wired to that top 'Point2D'

 

I don't know why this is happening, but I will file a report on them and see if someone with more knowledge of the backend can figure things out.

[Slider Control With Input Ports?]

I will follow up with this idea though - you could use the slider node to define a percentage of a range of values, or even a factor, it just would not directly reflect in the OIP.

[Slider Control With Input Ports?]

Unfortunately at this time, this isn't possible. There's no way to define an OIP control dynamically.

 

It's definitely on our list of things to try to improve, but we so far haven't made any headway. OIP controls must be statically defined.

[Splitting Zipped Lists]

Okay, I modified the node I created last year... This appears to solve the issue, at least on my end. It does still have some limitations that will require some more handling, but I think it should work for what you're trying to do right now.

 

Let me know if you run into any issues.

SplitList_NEW_MFarrell.vwx

[Splitting Zipped Lists]

This doesn't look right to me.

I'll try to take some time today to see what's going on.

[Access panels?]

Pat beat me to it - here was my example.

 

This is using a 3D Wall Hole Component that matched the extrude exactly.

 

 

EDIT:

with a proper Hybrid object, Top/Plan could look like this:

 

 

[Access panels?]

15 minutes ago, Tom Klaber said:

The wall does not heal itself around the symbol object.  I do not believe the wall whole component fixes this.   You could build in the missing piece of the wall as part of the symbol, but the symbol only work with walls of that thickness.

 

Without actually testing this - I think there is a way to query if the object is inserted in a wall, which would allow us to get the parameters (i.e. thickness) of the wall and take it into consideration when building in that missing piece. Food for thought. I will look into it as soon as I have more free time.

 

EDIT:

I'm actually 90 percent sure that we can just define how far into the wall the object will cut. Will update when I verify this.

[Access panels?]

2 minutes ago, Kevin McAllister said:

But unfortunately the file was a victim of the forum transfer. @MarissaFis there any chance of reposting the file?

 

I updated the first post in that thread with Robert's original files. Let me know if there are any others you need.  

[Access panels?]

1 minute ago, Kevin McAllister said:

 

Can I ask what the challenges are with an object that's inserted into wall but doesn't go all the way through?

 

This would be a cool use of a parametric Marionette Object. I wonder if its possible or on the road map - a marionette objects that generates a 2d component, a 3d component and a wall hole component that can be inserted into walls.... I don't think there's any way of doing this now but @MarissaFmight know if its been talked about. It would be a cool wishlist item for Marionette.

 

Kevin

I actually believe this is already possible. Robert Anderson has a skylight example that will insert into roofs, if I remember correctly.

[voronoi familiar colorful cubes]

22 minutes ago, hans@mnpro.no said:

I would like to try the voronoiObj.vwx file, but when I press the link I get  an error message: We could not locate the item you are trying to view. Could you perhaps upload it again?

This should be the one!

VoronoiObj.vwx

 

Also - I updated the first two posts in this thread to have their original attachments. You will find, though, that this/these files may require external python libraries. In 2017, this is easy to remedy, but 2016 is significantly harder - I never even got it to work.

 

EDIT:

Here's the same file working in 2017 on Windows. I'll work on updating it to be cross platform soon.

 

VoronoiObj_v2017.vwx

[Marionette in Walkthrough Mode]

I can't say that I'm surprised that this fails!

It's probably similar to how some objects don't draw in the right places when you're in a 3D view and change something.

[Sorting list in OIP]

@Stephan Moenninghoff

 

I believe we've been holding off on documenting it because in some cases we've encountered it not being very reliable.

I'm sure if we keep seeing it not fail that we can get it into documentation - it's more of a 'hidden bonus feature' currently.

[Parametric Books]

Just now, Stephan Moenninghoff said:

Thanks, @MarissaF :-).  Marionette is highly addictive. I had a couple of hours to spare today (a rare occurrence) and I had to make a decision what to do. Of course I ended up wiring a spike for textured, parametric box, my next pet project ("anything you can put on a shelf"). I wish I could do more Python sometimes to be more flexible.  Having said that - what we can do just with nodes is already very good. I hope, Marionette will get regular updates with new features. 

 

This is really fun to watch.

[Parametric Books]

@Stephan Moenninghoff - this file is really impressing QA here, just thought you should know

 

I got a message this morning from a coworker 'You have to see this!' and I went over there, and of course it was your file. (Of course I already knew about it, but they all love it.)