Jump to content

Stephan Moenninghoff

  • Content Count

  • Joined

  • Last visited

Everything posted by Stephan Moenninghoff

  1. Version 1.2


    No need to keep different size TV symbols any more with this handy Marionette. The screen image is adjusted automatically to the size of the screen and standard screen sizes can be chosen from a popup-menu. Features: Generates a TV set at standard sizes or at a user-defined custom size The "Automatic Size" option will fit the maximum available size into the given Box ("Shelf"). Choose from different Images to be shown on screen Add a frame in black gloss or aluminium Option to use surround light (aka "Ambilight") Wall mounted (centre of box) or free standing Can be used inside an interiorcad cabinet and will automatically adjust its size to the available space inside its box
  2. I really like having the Valve but I needs it to be smarter. Could an option be added that portions of networks joining after the Valve are not affected? The Valve currently disables too much and could be used much more often if this was possible: In this case I want the dialog to pop up only if the valve before it has been enabled. Currently, the Valve kills my entire network downstram of it. Is that necessary? Could the Valve please also disable controls in the OIP? If a control comes after a Valve, this would be an elegant way of hiding it. Thank you!
  3. Ah, I like a good modelling challenge. Here's another take. Hope it helps! Knife.mp4
  4. @jtempleton did you extrude open polygons or polylines to make objects? They can cause this.
  5. As for the original topic of this thread: I am still fine. No occurence of black viewports with my workflow. So, definitely better.
  6. @Jim Wilson I think it's gone. I haven't seen it since SP2. Thanks!
  7. Think so. It's been a while. I had a quick look inside the wrapper and it looks like this: Feed the values in according to the node description. You may have to string several of these together.
  8. Use a function perhaps, like x*x*50 or something similar?
  9. @Nuno Antunessee my reply to this thread, it has an object attached with some texture manipulation that should answer all your questions:
  10. @Nuno Antunescheck out my Box objects. I am resizing the texture to fit to the lid for example. Does this help? Box.vwx
  11. I can only comment on the auto-cutout for countertop wish: That is entirely possible with the full version of interiorcad. You can group a routing contour with a sink symbol and have it behave like a window in a wall: Cutout.mp4
  12. Is this the "Custom Cabinet" you are referring to? You can click inside a segment and adjust its size as shown in the screen shot.There are more advanced options in the full-blown version of interiorcad. Some videos here.
  13. Try this. It's not far off, just needs some refinement. Vortex Box.vwx
  14. @Palle You need to supply a list of values to the rect and, subsequently, extrude node. That will take care of everything. The ordered list is not necessary for this kind of thing.
  15. The Books have been converted to run with VWX 2019 and I fixed an error where the 'Hardcover' library needed a shelf depth and height of 2m to produce any books.
  16. Yes but what I am proposing are changes pertaining to the functioning of the UI. That's UX. What I was trying to say was, let's not confuse VWX functions ("How do I change the crop of a viewport") with UI functions ("How do I access the side pane widget while the RM is in a docked state").
  17. Interesting poll about colour in the Archicad UI after it was made all white. Yeah, one needs to be careful, users are fickle... ūüôā
  18. Jim, with the Resource Manager, users were not given a choice though. They *had* to use it. And while it's better than before, the UI does still not allow for the RM to be used in a docked state. I do tech support once a week (because I want to) and whenever I Teamviewer into customers' screens, I see the RM floating and collapsed. Why? Because its options are not visible in a docked and hence narrow state. This is a pure UX thing and I think it needs to be addressed. I have detailed how it could be addressed in my prototype. I am not proposing that my graphics be used (I think they are just next year's old UI and some young, talented designers will do a better job, no doubt) but the way it *behaves* isn't right. It's a usability bug if nothing else.
  19. All good and well but please let's not create the standard excuse for not caring about the aesthetics of the UI here. This thread is and has been about how VWX *looks*. Perhaps also a little bit about how it *feels*. But not about how it *functions*. A modern appearance is completely separate from functionality and what this thread is about is mostly aesthetics. Improving on features has never been a weak part of VWX, in fact I think we must admit that huge progress has been made over the past years. This all has happened while maintaining a dated and clunky UI. That is what this thread is about so please let's not muddy the message by such comments (although I'm sure it is a valid comment in a different thread).
  20. Sending and receiving values from any node is a good idea and other node-based apps have it, too (screen shot from Origami). Any output should be able to be fed into a sender node and received anywhere for input. That would be a welcome new feature for Marionette.
  21. Confirmed. The Resource Manager previews also show the black backgrounds. Once edited on a different machine, they return to normal.
  22. Today everything is back to what it was before. So, again, the user folder must be reset to fix the black renders. I wonder what brings this about. Is there anything the customer might be doing, that provokes this behaviour?


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...