Marissa Farrell

Kevin, The issue you're finding with Alan's example is due to changing your profile in a 3D view (I assume) If you change in Top/Plan, the path shouldn't bounce around. This is due to the Convert to NURBS command in Marionette, we're working on identifying the best fix, because apparently we didn't fix it the way we fix most other "object jumping" issues.

Alan and I discussed this when he discovered the fix he just shared. For now I am confident that I can at least get the different 2D bounding box locations as options. I'll look further into using insertion points.

I've tried performing math operations on it as well. I'm wondering if including a loci in the symbol might work somehow? Place the loci at an equal but negative distance from the top-right point?

Unfortunately I haven't found a way to do this. The symbol always re-centers itself. I'll let you know if anything changes, though

Tom, If you edit while in Top/Plan, it shouldn't jump around. This is an issue with using converting to NURBS in Marionette and I thought we had it resolved, but it seems we're still missing something. I might try adding some more varied logic and see if any of it makes it a bit cleaner.

Hey Alan, Most (there are some that are iffy) of those functions on the developer wiki can be used in Python by just adding vs.FUNCTIONNAME(Parameter1, Parameter2, etc.). If you follow the syntax of the functions that already have python examples, you should be able to use the rest of the VectorScript functions in python. The wiki just hasn't had all of its python alternative functions updated to reflect that. If you need more help, let me know. You shouldn't have to know Pascal in this case.

Just to follow up - I think the issue with your node is only that you included "SetListAbsorb()". When I took that out, your node ran for me.

Try the node in this file. I think I misunderstood you initially.

Also, the nodes in the "Text" category should already convert the values to strings before creating the text objects, if you plan to use those.

Brendan, You should just be able to use str(self.Params.dim.value)

Hi Alan, Here's a file that will space your windows equally. If you want some help understanding the math let me know. It uses the "Add Sequence" node I shared in this thread.

My primary goal with this is oriented towards 3D printing, so i'm trying to get things as realistic as possible. Images will likely appear more embossed than anything, but it's better than nothing! Kitty silhouette ornaments for the holidays are a close possibility

Here it is with a larger multiplier (I don't remember what I used initially)

For the surface or the rectangles? The surfaces are still very preliminary. As for the rectangles, I expect the results to stagger quite a bit. Right now the multiplier affects the "brightness" of each rectangle's color. I plan to later have it step in a more uniform fashion... remapping the heights to increase uniformly bsaed on the next color in the list. I'll still post an example, if it's the rectangles you're interested in. (Also, I will be incorporating the same logic to the surfaces if it works out okay, but again, those need much more work.)

I'll keep looking! I'm able to return most of the settings of the image, I just don't know how to actually take that image right out of the cell. I'll ask around here and see if I can find the right person to guide me.

I'm still happily indulging in those days

In general, the "worksheet image" is considered the on-drawing worksheet object... I don't know if we can extract the image from a cell. I'm able to return a boolean if the cell has an image in it, but I don't know how to take that image and use it elsewhere, assuming that's your ultimate goal.

Mmmmm. I don't really know. I'll keep looking at it. I think that some of the descriptions of what these functions do are misleading.

Also working on surfaces. Some refinement is needed - I need to find the appropriate interpolation values. They also slow down my machine a lot... But I don't think that falls on me as much Squirtle comes out pretty good, though

And Jim - I 100% believe I can at least match Trace Bitmap. Give me some time. It's been on my mind for a while now.

zoomer, Are you aware of Marionette Objects? In the sense that you can convert your Marionette script into a responsive Parametric Object? Maybe I'm misunderstanding you, but that's what I'm assuming your "live/non linear/dynamic/realtime" question relates to? I think that it's fully conceivable to do full image processing in Vectorworks - the only potential issue I'm thinking is that it could bog down system resources. The image I used here was only 80x80 pixels. It ran reasonably quick, but some of the other images I was querying took significantly longer. (Part of why I'm holding off on sharing the script. I want to see how optimized I can get it...) Marionette will be forever expanding in any direction a user wants to go. I can see all of your proposed ideas being made a reality in time.

I'm currently working on some image processing projects, and hope to share them with you all in the future. I wanted to share a preview now, in hopes of the reminders to finish this project. I think it will be super useful for some concept ideas! Here's my avatar - brought in as rectangles for each pixel and extruded to a height relative to the darkness of the pixel. (They're my cats - Euler and Crona - in case you were curious ) Sorry for not having a .vwx ready for you - it's still in progress! UPDATE: Working files for 2017 Image Processing may be found here:

For now, that's probably your best bet, aside from using the node in the file I posted earlier in this thread Glad it worked. I'll work with the people who work on the back end to see if we can get this to behave better.

Thanks Brendan, What if you add your "#test" line to the last part of the "class Params()" script, before RunNode()?

Here's a file with a node that you can use as an alternative. The downside is that you will have to type in the name of the layer that you want to move your object to in the String node. This will be the most reliable method for the time being. I know why the current version doesn't work, but I'm not sure how we'll be able to dynamically update the layers that show - the only way right now would be to edit the script in that node, as I've stated in my previous post.