Jump to content

MrPilot

Member
  • Posts

    23
  • Joined

  • Last visited

Posts posted by MrPilot

  1. Also, there ideally should be an option to assign (in the roof object or style) different hatches based on roof rotation — e.g. 0-180: hatch I; 180-360: hatch II, or 0-100 HI, 100-200 HII, 200-360 HIII... any number of assignments over any range, plus a fallback. So as to give the user maximum flexibility.

    • Like 2
  2. I got the same issue. To my knowledge, this is a missing feature, or rather: a bug — logic would want the same principle as walls would be followed ("hatch rotates in wall").

     

    Screenshot2023-12-11at14_53_20.png.fb3a8059246cf6b6fc5182241189d558.png

  3. @Antonio Landsberger & especially @DomC many thanks for your responses. Unfortunately I'm not a very frequent user of forums (maybe I could improve in this regard somewhat?) – but appreciate you taking the time to respond. Agreed that too much "idiot-proofing" prevents flexibility, and I'm all about being free to code whatever I want. However it's important that bugs (as @DomC you seem to have confirmed) should still be reported and corrected... if a given functionality is provided as part of a proprietary package (vs open-source), we have to rely on the vendor to make adjustments and corrections. Anyhow, many thanks for reporting, and looking forward to seeing if this node can be updated 🙂

  4. I have the same issue. I have a structural plan of a fairly complex roof, where for manufacturing purposes I have each repeating structural member encapsulated in a symbol. There is a record format attached to that symbol so that things like dimensions, material, cost, etc. are saved at symbol definition level. The problem which I have is that data from the symbol definition isn't accessible in tables, so the only workaround I found is to attach two different record formats: one to the symbol definition, with instance-specific data (e.g. unique ID, finish, timber grade, etc.), and another one to the 3D object within the symbol definition, this time with definition-specific data such as dimensions, which don't change as the symbol is a static resource in this case.

     

    A related issue is that tags don't work in symbols within symbols: i.e. in Layoutebenen (should be something like layout layers, i.e. 2D working drawings), in viewports, I can only attach a tag to the "parent" symbol, whereas I would like to be able to attach it to the child instance, and for the tag to access the data stored in the child instance symbol definition.

  5. Having the option to clip in 3D would be even more fantastic. The expected behaviour would be to retain all original hatches / surfaces, and where a cut occurs, a cut hatch would appear as the resulting surface.

     

    N.B. Such a tool should definitely work on groups, not just single items. Feel free to reach out to me personally to discuss details.

  6. Hello!

     

    I find this to be an absolutely necessary tool! To give a current example:

     

    3D section with added 2D details, e.g. tiles:

     

    image.thumb.png.99115bb3c99d7477cf80ccd29c0e2305.png

     

    Evidently, the tiles should be cut by the pink rectangle for better aesthetics.

     

    This is where a clip option would have been great!

     

    Kindest regards,

     

    Konrad

  7. 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.

     

    Quote

    As far as I know, there is no "regular" way at all to show 3D objects with a Line Style. Extrudes seem to be an exception.

     

    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.

     

    Quote

     I'm not shure, but I think this problem exists since VW 2020.

     

    Meaning solids would also display line types correctly in earlier versions?

  8. 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:

     

    Screenshot 2021-01-13 at 12.40.44.png

  9. 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

     

  10. 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.

    Bildschirmfoto 2020-11-06 um 07.29.18.png

    Bildschirmfoto 2020-11-06 um 07.30.51.png

×
×
  • Create New...