Stephan Moenninghoff

There is more than just framed fronts though. You can probably guess what this means:

Hi Kevin, you will need Vectorworks 2021 for interior xs 2021 to run. 2021 actually makes a few things a lot snappier, especially redraw and OpenGL so don't hold back!

Sneak peek... 😁

I have downloaded some very good objects from https://archive3d.net. The vegetables and cookie jar and even the roast turkey was from there IIRC. You need to try them out though. Some are good, others aren't.

Sorry, I forgot that part. Yes, of course you need a none fill and then you set it to filled after the extrusion.

Awesome. Did you model that yourself?

Is that a 3D salad?

Extruding an arc gives you a pie, which you then need to shell to get rid of the sides.

That's possible with the full version of interiorcad and yes, it's an extra plugin. There is an entry-level version, interior xs, which has full capabilities but does not do fittings, parts lists and costing. The 2021 version of interiorcad/interior xs will also feature framed fronts, face frames, openable fronts, awning doors, notched toe kicks and a slew of other features made for users outside of Germany/Austria/Switzerland.

What would you like to do?

@Travis.Designer Here is the help page for creating custom hinges: https://conf.extragroup.de:8443/im/latest/creating-custom-libraries However, for that type of hinge this will not work 100%. I will post a link to a Youtube video here shortly which I have just finished, explaining how to create custom fittings.

As for the file format: you can simply choose "Vectorworks interiorcad" from the list and then copy and paste into your document. This is a Java applet and is slightly temperamental so if it does not work as expected, just choose STEP and download. Then, drag and drop into your document. I will make a short film to explain how to proceed with the hinge from there on. (As soon as I get a chance).

Afk right now. Will explain in a bit.

Ah, you mean the rogue object? Replace the 0 in the 'First Rectangle Width' node with 50. You are creating a dead object so the count for the rotation values is one more than that for objects. You can see it if you go to debug mode:

But that is what it is doing in your example, no?

What is the result you were expecting? Like this?

@Tom Klaber are you on Windows?

Not strictly. Diameters are used to determine which is the largest object participating in the zig-zag array. Objects falling below a certain diameter are assembled in rows, then the remaining space is used to distribute them and as a last step they are shuffled about by a random value. It doesn't matter. Not really. The only limit is that I will stop filling up the shelf once I have finished the last of the distributor modules (because I cannot loop).

They are stacked symbols and symbols outside of the max vertical shelf space get deleted. That's all straightforward . The hard part is: objects get placed randomly. That's kind of the point of the object. You want each shelf with a different set of objects and different placement. So, it's not about the stacking, it's about placement on the horizontal plane in x and y and filling up the shelf in x and y. Does that make sense? I'm posting the object soon anyway. Maybe it becomes clearer then.

A new project. I'm filling up a shelf with plates, bowls, glasses etc. Mainly round or roughly that shape. So I'm doing the math but it is impossible to guess the total length as the filling is not linear, as with the books because I have the shelf depth to take into account. So, I'm looping through the process until I have filled the shelf. I can see no other way.

I wonder if an option could be added to create a loop that will be executed until some condition is met. Think about filling up a shelf until full and then stop. I haven't found a way to do this other than repeating a wrapper n times and using valves to stop the unused wrappers getting executed. Unfortunately, this makes debugging inside of Marionettes very slow because the valve does not seem to start working until the object has been exited. Also, with each repeated wrapper, the compile time gets longer. This makes duplicating the object slow in the document (although I am sure my wiring could be optimised 🙂 ). Any ideas? Could this even be implemented at node level?