Jump to content


  • Posts

  • Joined

  • Last visited


0 Neutral

Personal Information

  • Location
  1. Had a lot of issues with Dropbox, besides their prohibitive pricing (at least last time I looked)... so working with success on NextCloud for a while now. Maybe you should also add OwnCloud to the list (NextCloud is a branch thereof).
  2. I was able to solve this issue by applying a texture to the component which was rendering with black lines, in this instance the glazing in the windows. Window type [1.] does not have a texture assigned to the "glass" component, whereas window type [2.] already does. I hope this helps someone.
  3. Hi halfcoupler, thanks for your reply and checking this on your side! Yes, indeed this worked for me in a shaded / hidden / dashed hidden view... in both examples, the bottom case is the intended result, whereas the top is the incorrectly displayed object after a subtraction has been carried out. Hm, this seems strange. Logically, if the extrude is displayed in a [correct] manner, then so should be other solids, especially that line type selection is available for these objects as well. I thence consider this to be a bug. Meaning solids would also display line types correctly in earlier versions?
  4. Here are some more tests: simple extrusions display properly (here shown in all sides mode), wheareas e.g. a subtraction looses the ability to display line types:
  5. Hi everyone, did any of you manage to assign and display a dashed line on a 3D solid (except for hidden edges)? The line type selection seems to be ignored by 3D solids (working in VW 2021) – in the attached screenshot, both objects have the same attributes; the solid is simply an extrusion of a copy of the rectangle:
  6. +1 from me on this. I use OpenGL for most of my 3D work, so I would see this as a great improvement.
  7. This is my code for a New Group node, which resolved the problem for me (in conjunction with the Loft Surface node): #REFFILE;REFFILE;[VWLibDef]/Operations\Group.py; #Author: ? #Modified on: 2020.11.11 17:00 #Modified by: Konrad Br. @Marionette.NodeDefinition class Params(metaclass = Marionette.OrderedClass): #APPEARANCE #Name this = Marionette.Node( "New Group" ) this.SetDescription( 'This node creates a new group.\n' ) #Input Ports handle = Marionette.PortInLists( vs.Handle(0), 'hObjs' ) handle.SetDescription('The objects to add to the group') #OIP Controls #Output Ports group = Marionette.PortOut('hGroup') group.SetDescription('A new group containing the objects') #BEHAVIOR this.SetLinksObjects() def RunNode(self): #inputs h = self.Params.handle.value #script new_group = vs.BeginGroupN() for i in h: vs.CreateDuplicateObject(i, None) vs.EndGroup() for i in h: vs.Marionette_DisposeObj(i) #outputs self.Params.group.value = new_group
  8. I have a similar issue with this... can't get the Loft node to function, as the Group node always returns an empty set.
  9. Hi Marissa, I'm bumping this topic as I have a similar issue with the "Index Bounds" node – maybe you can give me a tip on what's going wrong here... I am looking to get the index of the first occurrence of item in list. I've also looked at the code inside of the node, and it seems to make sense at first sight for the behavior I'd expect. Many thanks in advance for any help! Konrad Br.
  • Create New...