KingChaos

Liegt es auch an bauteil 3d? Das wird sicher auch "in einer höheren ebene" geregelt, wie das Ding heisst. Symbole sollten btw meines Erachtens mit Nummern benannt werden, wie es anderswo üblich ist. Leider wissen wir nicht, warum das so ist.

thx i will try

wie kann ich diesen Befehl denn im Script ausfuehren? 🙂 so ganz verstehe ich nicht, was er macht.

Tomorrow

I found some node "get symbols from folder" but it opens a graphic selection for the symbols in a specific folder right as i run the script. for my "project" i need a node which works in the same way as the "get texture" node with a popup/pulldown menu.

Na mein Rechner ist eine HP Z6 G4 Workstation, auch da geht es nicht.

Hey, das war auch vor dem einbauen dieser Node schon nicht umwandelbar, es war nur ein Test was dieser Node macht. Ich brauche den eigentlich nicht, weil ich einen brauche der nicht aufpopt, wenn ich die marionette starte sondern durch ein Pulldown/opoup in der OIP aktiviert wird. Ich war nur froh, dass es sowas gibt und mir DomC diesen gezeigt hat, damit ich das mal ausprobieren kann. gruß KC

Hi, yes the read only attribute of the XG-Cabinets name is at the moment my biggest problem, except the impossibility to convert the network into an object-node. The application of multilevel incides to my parts i do with excel. All the assemblies and parts 3D i use have a database value in the "container" field of this database, because thats is the field where the cabinet name moves in when u dissolve the cabinet. If you read out this assembly name i use (f.E. 01 Hanging Cabinet) the first two characters and after ordering the pieces in the BOM i got multilevel indices. After Cabinet drawing is dissolve the cabinets to find the parts 3D in this BOM spread sheets If there is a new "Baugruppe"-name the count Baugruppe is going +1 and the Zaehler Teil resetted to 1 and column A then -> verketten(Y;Z) and u got a multilevel indices 100 % stable. I did this all because i was not able to marionette a multilevel indices by my own. 🙂 The VWX files will be generated and named by our ERP Software, so all the data is in the file. Ordernumber, Assembly Position, Cabinet position, Pieces Name etc. It would be better, i could look into the cabinet with the spread sheet but that wont work so far :( @Pat Stanford I can name (green) the cabinets yes, but i cant modify the "XG Cabinet.name" field (red) because it is write protected. So i think the cabinets (red symbols) are broken, if i placed more then one of them into my drawing. Only 1 of them then has a connection to the database the rest has not a single value in a single DB. The "naming" is done at a "higher level" and that wont be changed XG told me. 😞 If i have a solution for this i can sketch all interior fully parametrically with automatic indices (with my excel) and i can combine steel parts into my cabinets (with box objects) and add this fake-cabinets (containing only of parametrical steel parts) f.E. this Tego-stuff that would make VW a fully parametrical monster but at the moment the monster has no teeth 🙂 @Pat Stanfordmaybe, you can tell me why the network is not able to be changed into an "object node" BR KC 21058 07 Test Cabinets.vwx

You can do something, IF u can name the objects with marionette and put them onto a Layer "Fertigung" then the measures appear here. Maybe u have u use: =Length instead of =Länge =Width instead of =Breite =Heigth instead of =Höhe in line 3 Test Onink.vwx

hmm, what is the reason for that cabinettool? Do you have the interiorcad? i got no useful application for not interiorcad objects cabinets because we have to cnc them. therefore all stuff i place has to be an interiorcad part 3D or cabinet 3D with 3D-parts. Maybe i misunderstood your english post but i am struggling with naming such cabinets out of the XG generator. This objects are not nameable by marionette, DomC told me. If that is true it is a "death blow" for this solution. 😞

please link your post, i cant find it.

I dont have any extrusion in this file, i only place red symbols made out of XG Cabinets and got problems with the predefined names of these cabinets because the name is not able to be manipulated with set record field.

Why you dont make 3 parametrical marionettes (a square, a circle and hexagon) and select them with radio button?

i get a circle and a square

Thank, you. I thought in a different way -> they dont appear in the OIP if they are not connected to the network. With an if node it seems that they are not connected IF if is not true.

Is it possible, to inhibit that VW will show a variable in the OIP? Maybe i make such similiar situation like your network. Input is a selector, rectangle, circle or hexagon. IF it is a circle, you can input a radius, if rectangle u can input a & b and a hexagon u can input edge count and inner/outer radius? So i dont need a&b in a circle or hexagon, so i am looking for a way that u can "hide" the named input variables which u define as not needed? br KC

Also die POlylinie in eine Gruppe tun und die Gruppe mit Namen versehen geht nicht.

Das ist nur eine polylinie, bei dem andern bauteil geht es genau so

But what for is it? What u have and what u need? I wann know, why u doing such a stuff? U want to detect, what geometry is in the input?

Sry, why Block off input data?

Rounding mistake ist Think

Hi, i used this "Get Texture" Node and i wonder how it has to be modyfied to work with symbols, placed in a specific folder in the ressource manager. I made a few marionettes, but scripting a complete new node i cant do. #COMMAND;READONLYREFFILE;[VWLibDef]/Textures\01. Common\Get Texture.py; #Modified by MF May 2017 #Modified by MF Feb 2019 - provided index for texture @Marionette.NodeDefinition class Params(metaclass = Marionette.OrderedClass): #APPEARANCE #Name this = Marionette.Node( "Get Texture" ) this.SetDescription( 'Returns the selected texture from the dropdown list' ) #Input Ports #OIP Controls selectedTexture = Marionette.OIPControl('Texture', Marionette.WidgetType.PopupTextures, 0) selectedTexture.SetDescription( "A list of the available textures on the document" ) #Output Ports texName = Marionette.PortOut('sTexName') texName.SetDescription( "The selected texture's name" ) texIndex = Marionette.PortOut('iTexRef') texIndex.SetDescription( "The selected texture's index" ) #BEHAVIOR def RunNode(self): #functions def callback(): return 0 #inputs index = self.Params.selectedTexture.value #script # Populate the texture list texNameList = [] texListID, numItems = vs.BuildResourceList(97, 100, '', True) for i in range(1, numItems + 1): texNameList.append(vs.GetNameFromResourceList(texListID, i)) vs.ImportResToCurFileN(texListID, index+1, callback) #outputs self.Params.texName.value = texNameList[index] self.Params.texIndex.value = vs.Name2Index(texNameList[index]) is is possible, to modify this node and get a "Get Symbol" node somehow? Is someone capable to help me with that? I need it for changing symbols in a marionette network which is placing symbols along a polyline. For sure it wont work if i replace all the bold strings into symbol but it is not so far away from this, right? KC

same problem here without "solid boolean". all is working fine, but making "object node" crashes VW Maybe it is something with the naming of the XG-Cabinets. Until now i am not able to modify the Xg-Cabinet-Name, maybe it is read only somehow. I can change the name of the object but the cabinet name is like a phantom. Even if i am sucessfully set the record of "Korpusmöbel - Alle" and read it out afterwards while making a text with this record value it is shown that i modified it, but in the cabinet this change is not seen. br KC Namensinputmit Aktivierung.vwx

@DomCnext problem is, if i place the same symbol-cabinet multiple times, vw wont rename it all cabinets having the same name f.E. "Korpusmöbel-53". That will result, if i ungroup the cabinets, that all the parts 3D have not a single databasenetry. Only the first one placed by marionette has all entries in all databases. the others are not connected to any db. so if i will later on use those parts i HAVE to manipulate the name, or make VW renaming them. 😞 damn, it was such a good plan.