Jump to content

Frederic_Vbc

Member
  • Posts

    38
  • Joined

  • Last visited

Reputation

27 Great

Personal Information

  • Occupation
    Landscape Architect
  • Location
    Australia

Recent Profile Visitors

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

  1. The problem remains the same in 2023 sp7 unfortunately. A small thing I wish I discovered way earlier: In the edit site model label position mode, if you click and drag you can select all the handles at the same time, then hit the delete key to start with a blank slate. Then just add the label where desired. I find this a lot less painful than having to click on every duplicate one by one. Also, I discovered that if the 2D style is set to '2D contours (smoothed)' labels' handles are not showing properly. To fix the issue just switch to 2D style '2D contours'
  2. Hi Cav, Do you still need assistance with this?
  3. Thank you Andy, you resolved my issue ! Selecting the All or Any criteria before adding a new one was the key to nest properly.
  4. Could we have to possibility to mix All criteria in this set and Any criteria in this set ? I was trying to make a simple line legend of a particular viewport and wanted to show Any objects that is a line, polyline or polygon but I want to ignore the one on the class none. But is doesn't seems possible. I know I can manualy delete them via Cell visibility and sorting but it seems that it should be possible to parameter. Is my logic incorrect or is it a tool limitation ?
  5. Similar kind of issues are happening with landscape area component and site model component. I experienced this too with hardscape component but that has been solved with SP1.
  6. I guess that it is suppose to display the same way hardscape component does. But for some reason it does not display anything. Can others confirm ?
  7. Yep I confirmed, problem is back ! Weird Looks like a speacial gift from SP1 @administrator Could someone look at it please, the problem exist since 2020 !
  8. The improvements introduced to the Site Modifier are great but there is one detail that makes part of the new feature 'Grade limit / Define by contours' a bit useless : The inability to use a simplification tolerance on the modified contour, making the vertices count going through the roof as soon as a curve is used. Could we plase have a simplification tolerance added to the Contour Edit ? Cheers
  9. Thanks a lot Letti, I will let you know if I make any progress !
  10. Well I can't say that I have experienced (this) issue so far. They have made some critical improvement with the site model and the modifiers ! And the ability to realign contours under Grade limits should fix that.
  11. Wow that's great and impressive Letti ! The result looks to be very close to what I was looking for. Your code is far beyond my scripting level but I will study it and try to learn from it. Thank you for your time !
  12. Thanks Pat, Unfortunately I am not yet familiar with Vectorscript or Python. I have been trying to create a node to decompose a polyline into segment based on the node "Compose" but I am getting an error : NameError ("name 'hPoly' is not defined" I am a bit out of my depth here... @Marionette.NodeDefinition class Params(metaclass = Marionette.OrderedClass): #APPEARANCE #Name this = Marionette.Node( 'Decompose' ) this.SetDescription('Decompose similar to how the Decompose menu command would.') #Input Ports hPoly = Marionette.PortInLists( [],'Poly') hPoly.SetDescription('A poly') #OIP Controls #Output Ports out = Marionette.PortOut('Vertices') out.SetDescription('The resulting vertices') #BEHAVIOR this.SetLinksObjects() def RunNode(self): #functions def Add_Handle(obj): out_list.append(obj) #inputs Poly = self.Params.hPoly.value #script out_list = [] vs.DSelectAll() for h in hPoly: vs.SetSelect(( vs.CreateDuplicateObject(h, vs.Handle(0)) )) vs.Marionette_DisposeObj(h) vs.DoMenuTextByName('Decompose', 0) vs.ForEachObject(Add_Handle,'(VSEL=TRUE)') #outputs self.Params.out.value = out_list
  13. Hi, I would like to create a network that create new polygons based on an existing one and a condition. The idea is to 'highlight' (create a new poly) the portion of the polygon where the area width is less than a given distance (here 1500mm). I can think of two avenues to approach this : One might be to run a polyline offset around the boundary and use the intersecting point as delimitation for the new poly. (which is kind of what I do manually) But then I am stuck with translating the use of the 'bucket' 2D polygon Tool : Inner boundary Mode in marionette ? Another approach I was thinking was to use the proximity test (using part of Sbarrett's wrapper) of a series of 2D points on the poly and filter them with a condition, (and ignore a certain amount of consecutive ones I guess to avoid false positive) Would someone have a better idea or have done something similar ? Thanks Fred
  14. Right now the stake tool required you to click in the elevation box, enter your elevation then place the stake. I know it does not seems like much but going back and forth to the elevation box then the drawing can be strenuous when entering hundreds of points manually. Having the possibility of a pop up box allowing to enter the next elevation after each stake being placed would be a nice and simple addition. Or Just being able to hit the Tab key to enter the elevation box maybe. Just something that give the possibility to skip going to click in that tiny elevation box would be nice. Thank you kind developing team
×
×
  • Create New...