Jump to content

Stephan Moenninghoff

Vectorworks, Inc Employee
  • Posts

    1,330
  • Joined

  • Last visited

Everything posted by Stephan Moenninghoff

  1. @JoeStewart I know. I have logged a bug with Vectorworks. This will be fixed. Thanks!
  2. @Niels Timmer I am seeing it, too. Are you saying that using the menu instead of the keystroke will not break undo?
  3. @KingChaos you are still trying to force VWX into something it doesn't do. As I have recommended before, start embracing the wonderful world of Vectorworks and stop looking for Solidworks.
  4. @Urstanner you cannot use interiorcad custom parts to create a parametric cabinet. It may be possible in a future version but as for now, it isn't. That's what we have the cabinet PIO for. Hundreds of thousands of hours have gone into its development. It is not a trivial task to create a PIO as complex as the cabinet. Would you like to explain what you are trying to achieve so we can consider it and perhaps implement it as part of the cabinet PIO?
  5. I explained to you on the German forum that VWX doesn't have the same 3D constraints manager as TopSolid. The answer is still the same. You can do this construction with ease using interiorcad - plus, you will get the complete CNC code from the fittings and millings you assign to the parts or their connections. You need to stop expecting things we do not do and start to embrace the possibilities interiorcad is offering. For example, I know from talking to quite a few customers who have converted from TopSolid that although they cannot achieve a fully parametric construction, the modelling process is much faster in VWX. So, some you lose, some you gain.
  6. interiorcad parts and millings use standard plug-in parameter records. The cabinet tool is too complex for that approach. It needs additional opaque data objects.
  7. @Zeno I just tried and succeeded. Maybe try again in a bit?
  8. Update your custom lights. There was a bug when converting IES-based lights. I think it's fixed but the fix may not be in yet.
  9. Yes, unwrapping is necessary only for debugging. I needed to find out which node was causing the error.
  10. I don't know what exctly is causing this. If I unwrap the object node and run the command I get an error pointing to a divide node. Apparently, the unit conversion is acting up and something is getting divided by zero. If I change units to m and then back to mm and rewrap the network and convert to an object node, everything runs without issue. I didn't write the unit conversion node. It is one I collected off the old forum.
  11. Ah, interesting. I'm on a short break right now. Will look into it shortly. Thanks for the heads up, Bert!
  12. Is this latest discussion slightly off topic? I didn't start this thread so maybe I should keep quiet but it could be useful to have this thread for discussions about the *aesthetics* rather than core functionality.
  13. I take it, you have scripted that node yourself? If that's the case, I'm out of my depth. perhaps someone else can comment.
  14. I haven't tried to do this with Marionette but I think the "Get Record Field" node is going to help.
  15. You can do that easily by creating a Worksheet that lists the Spaces. Right-click a Space's row header and choose "Select object".
  16. You are trying to set a viewport's opacity. That's interesting. A VP cannot have direct opacity. You can give the VP a fill colour and put it into a class and set that class to an opacity. I don't think you can give the whole VP an opacity that will pass that opacity on to everything that is contained within.
  17. I don't think that an odd number makes sense here. The offered solution was for an even number of sides.
  18. Here you go. Good old Marionette. Great for this kind of stuff. Alternating Polygon.vwx
  19. It works with any number of edges, as long as there are always two of each. I'll make you a quick Marionette. After my supper.
×
×
  • Create New...