Latest Contributions by MatthiasBuehler1

Hmm. the code's missing .. Can you edit the post ? ... View more

hmm.. 'better' is difficult to explain in gemetric terms .. 😉 what's your code so far ? did you try playing with setback() ? ... View more

Hi, check out the i() operaction ( insert ). Spheres can not directly be produced with CGA, but this option lets you to insert premodeled assets. Ok ? m. ... View more

"Hi Larry!"  ( haha, reminds me of http://www.youtube.com/watch?v=JzNSOZ5osOg ) 1] Displaying the 3d data has nothing to do with the actual complexity of the data itself. It's just how the geometries are shown. Yes, CityEngine has a couple of different options, but that's not 'exportable'. I'm not sure if ArcScene has this 'wireframe on shaded' option somehow encoded. Note the 4,5,6,7,8,9 keys in CityEngine ! So I assume the data exported is complete. Which is a good thing. 2] PM = 'Private Message'. See top of the forum page. With PMs, you can send messages directly to some people. Especially good for stuff you don't want to post public, like email-addresses, .. When you click on my user name a new window appears, where you can send PMs. Cheers ! Matt ... View more

Hi, Sorry, not following. 🙂 Can you post a graphic ? Let me know. m. ... View more

hi, for mapping attribute values, use the 'mapping' layer type. to map the elevation, use the 'terrain' layer type. I'd say never use the 'texture' map layer for mapping. plus make sure the attribute in the rule and the one you're mapping have the same name. (it also works by mapping other attributes though, depending on the use case). ok ? ... View more

Hi, 1] What's the details which are lost ? I've stared at the CE/MP image for a minute, but am not sure what's missing.. Can you show the exact details ? The 'wobble' effect you mention in the 3dsMax thread does not remove details, it just messes with all the point coordinates, deleting some decimals. e.g. 1'000'000.012345 meters --> 1'000'000.0 meters ( 8 decimals, 1.2345 cm error.) Though that should NOT be an error when you export to GDB, since that stores vertex coordinate data in double precision. 2] This issue (not transported alpha) is still on the buglist, hopefully fixed soon. ps. You seem to know a thing or two about 3d piping : post "CityEngine for Underground Infrastructure" http://ideas.arcgis.com/ideaList?c=09a300000004xET&category=Esri+CityEngine can you read this and maybe send me a few more inputs on this via PM? Let me know. Matt ... View more

Ok, here's 20 minutes of CGA coding .. 😉 ##################################################################################### # ATTRS ##################################################################################### @Group("BUILDING",0)  @Order(0) attr nFloors    = 15 @Group("BUILDING")   @Order(1) attr groundFloorHeight  = 5.5 @Group("BUILDING")   @Order(2) attr upperFloorHeight  = 3.5 @Group("BUILDING")   @Order(3) attr volumeChange_1_floor = 2 @Group("BUILDING")   @Order(4) attr volumeChange_2_floor = 5 @Group("1",1)    @Order(0)   @Range(0,5)  attr frontSetback_1   = 0 @Group("1")     @Order(1)   @Range(0,5) attr backSetback_1   = 5.9 @Group("1")     @Order(2)   @Range(0,5) attr sideSetback_1   = 0 @Group("2",2)    @Order(0)   @Range(0,5) attr frontSetback_2   = 0 @Group("2")     @Order(1)   @Range(0,5) attr backSetback_2   = 0 @Group("2")     @Order(2)   @Range(0,5) attr sideSetback_2   = 0 @Group("3",3)    @Order(0)   @Range(0,5) attr frontSetback_3   = 5 @Group("3")     @Order(1)   @Range(0,5) attr backSetback_3   = 0 @Group("3")     @Order(2)   @Range(0,5) attr sideSetback_3   = 2 ##################################################################################### # FUNCTIONS ##################################################################################### floorHeightFunction(floorID) = case floorID == 1:   groundFloorHeight else :   upperFloorHeight setbackID (n) = case n >= rint(volumeChange_2_floor) :   3 case n >= rint(volumeChange_1_floor) :   2 else :   1   setbackDimension (n, side) = case setbackID(n) == 3:   case side == "front"  : frontSetback_3   case side == "back"  : backSetback_3   else      : sideSetback_3 case setbackID(n) == 2:   case side == "front"  : frontSetback_2   case side == "back"  : backSetback_2   else      : sideSetback_2 else :   case side == "front"  : frontSetback_1   case side == "back"  : backSetback_1   else      : sideSetback_1 ##################################################################################### # START ##################################################################################### @StartRule Shape --> BuildingRecursion(1) # start with floor '1' = ground floor BuildingRecursion(n) --> case n > rint(nFloors) :   NIL else :   extrude(world.y, floorHeightFunction(n))   FloorVolume(n)   # back to recursion   comp(f) {top : BuildingRecursion(n + 1)} FloorVolume(n) --> comp(f) {bottom:   reverseNormals   alignScopeToAxes(y)   shapeO(setbackDimension (n, "front"),setbackDimension (n, "side"),setbackDimension (n, "back"),setbackDimension (n, "side")) { shape : NIL | remainder :    extrude(world.y, floorHeightFunction(n))    Floor.    }   } ... View more

Hi, There's no limitation per se, but I'd pay attention to : - number of polygons - number of materials - number of groups - number of textures referenced - RAM consumption I'd say it's best you start with light files and add more stuff. m. ... View more

you are absolutely right. it is a PITA that there's no way to do this. this is a very sad, but common problem with 2d data and 3d data. ... View more

OK. please work with obj for now then. We're reworking the exporters, so I'll try to check this in my tests for CE 2013. Thanks for reporting this ! Matt ... View more

Hi, There's no tools in CityEngine to process LIDAR data. You could convert the point clouds to e.g. kml files and bring those in as 'Static Models'. What would you like to do with your specific data ? Let me know. m. ... View more

Hi, Make sure you have enough space between the streets. To actually fill the space in between, you need to close the streets to blocks. --> just create new thin streets connecting all the ends of those streets. so, steps : 1] street left 2] street right 3] street middle 4] raise middle street 5] connect left middle right ends with new streets, on both ends 6] > 2 blocks are created between all segments. 7] change block subdivision to 'no subdivision' or an other type 8] 'grow' your structure until you have the full thingy built. check that you're working with accurate distances and street widths. activate the information display (d,d key) and the navigation display ( d,n ) and check the grid size. note that in this whole process you are 'misusing' the street system to build the geometries you need. using the 'c' key enters the 'edit streets tool', this lets you edit the tangents too. also try Graph Menu > Set tangents smooth. ok ? Matt ... View more

Hi, there's literally hundres of different special 3d file formats out there, sadly we can not support them all. please use a data converter, e.g. FEM or Okino's PolyTrans http://www.okino.com/default.htm ok ? matt ... View more