Jump to content

HebHeb

Member
  • Posts

    83
  • Joined

  • Last visited

Reputation

11 Good

Personal Information

  • Location
    Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. when operating with nurbs curves (my go to when creating solids inside marionette) some things to mind: - for closed curves take the first point and use it at last point also (otherwise they are not "closed") - use the "loft surface" node to generate solids (get familiar with the settings (rule, solid, close, ...) - chek the order of the curves and their point direction (with the data flow nodes everything is possible)
  2. In DomC's Node Collection is something that might be interesting? Actually there a a few Nodes/ small example Networks that might help u with your idea! DomC Nodes - Marionette - Nodes - Vectorworks Community Board
  3. Thanks for reaching out! @Letti R was so kind to help me out with a alternative Python script ❤️ this did exactly what i wanted. @Antonio Landsberger But thanks for the version 2 of this node!!! I am 100% sure I will use it later in another script.
  4. i guess this is something basic, but never did this with marionette: i have a list of points that looks something like this (points for each poly) i want to triangulate each poly separately and not the whole polys together... so i need a flattened list for each 'list' and not the whole list flattened. can anyone help me? thanks!
  5. I think there not enough Info to help you. But one Node comes to my Mind that might be wort lookin at: "Get Point On Poly" so you can place and rotate Objects along Polyline shapes.
  6. 1. not very complex, some nested math... squences, ranges, series,... recalculating z-height of polys etc... graphically: no 2. of course only the dedicated gpu active As said: just curious if maybe more "generel problem" acoss other hardware configurations. Might have a chance to test on a system with dedicated gpu only next week...
  7. Hey there, i have some Networks/ and or Marionette Objects that crash my Windows 2024 Update 3 Installation of Vectorworks, on MacOS everything just works fine and as expected. I have already sent a test file to my local Distributor and they said that the issue was now reported to Vectorworks Inc. I also experience much faster response of Marionette on MacOS than on Windows... even my "slow" M1 with 16GB RAM (13" Pro late2020) is oddly faster than my i9-12900H, 64G RAM, RTX 3060 (Laptop GPU) Windows Machine. Wouldn’t expect such huge differences with that hardware. So out of curiosity: Anyone else in this community having similar trouble?
  8. @DomC @Pat Stanford this works perfect! 😍 in this context: is there any acess to the "fixed direction of the profile"? i would literally die for a english Version (or at least the possibility to switch from german to english) Sometimes it is really hard to guess the english terms and get proper search results...
  9. Thank u! I will test it tomorrow and will report my results here 🙂
  10. ty Pat for reaching out! ...and thats exactly the problem: no matter how the profile is moved, after an operation the movement is reset 🙂 if not operated on the result its working, thats exactly what DomC's solution is doing.
  11. had some time to work on this again... Whenever I operate on the resulting "VW-Handletype: 86 Plug-in object" (in this case convert to 3d polys > mesh) the movement of the profile is lost (happens with any operation (also bool) unfortnetly there is no info for 3D Path Plug-in Object (86) on the developer page that might help me to sort it out myself... @DomCHave you any idea how I cloud avoid this behavior? Extrude along Path with Ref point (3D Path Plug-in Object - Handle Type 86).vwx
  12. I can't remember excatly; but could it be possible that this only happes with active plan rotation?
  13. Hey there, is it possible to refresh a marionette object when a given site model is refreshed? thanks in advance, cheers
  14. FYI. Found a working soloution: In some cases (i.e. when using a rectangle as path) i had to ungroup twice to get the 3D poly handle. @Marionette.NodeDefinition class Params(metaclass = Marionette.OrderedClass): #APPEARANCE #Name this = Marionette.Node( 'Send to DTM Surface' ) this.SetDescription( 'sends object to DTM Surface' ) #Input Ports hPath = Marionette.PortIn( vs.Handle(0), 'hPath' ) hPath.SetDescription( 'the input path' ) hLayer = Marionette.PortIn( 0 ) hLayer.SetDescription( 'the layer containing the DTM' ) iTINType = Marionette.PortIn( 0 ) iTINType.SetDescription( 'A number identifying the Site Model surface (0 = existing or 1 = proposed)' ) #OIP Controls #Output Ports hPathOUT = Marionette.PortOut('hPathOUT') hPathOUT.SetDescription( "the resultung elevated path" ) #BEHAVIOR def RunNode(self): #inputs hPath = self.Params.hPath.value hLayer = self.Params.hLayer.value hDTMObject = vs.DTM6_GetDTMObject(hLayer) iTINType = self.Params.iTINType.value #script vs.DTM6_SendToSurface(hDTMObject, hPath, iTINType) vs.Locus(0, 0) # Create a dummy object dummy = vs.LNewObj() hPathOUT = vs.PrevObj(dummy) vs.DelObject(dummy) # Delete the dummy object #outputs self.Params.hPathOUT.value = hPathOUT
  15. Thanks for your reply. Now the Python example makes sense ;D _, _sPIOName, _hPIO, _hPIORecord, _hWall = vs.GetCustomObjectInfo() # Get info from current PIO instance _hPath = vs.GetCustomObjectPath(_hPIO) _hDTM = vs.DTM6_GetDTMObject(vs.GetLayer(_hPIO), False) # Get Site Model on the PIO's layer _hPoly2D = vs.HDuplicate(_hPath, 0, 0) _b = vs.DTM6_SendToSurface(_hDTM, _hPoly2D, 0) vs.Locus(0, 0) # Create a dummy object _h = vs.LNewObj() _hPoly3D = vs.PrevObj(_h) vs.DelObject(_h) # Delete the dummy object I kind of failed like shown above, but with waldo in my mind i'll give it another try 😉 But anyhow, I hope someone can sort it out
×
×
  • Create New...