Latest Contributions by MatthiasBuehler1

Hi, did you set the attr source to the object attr ? in the Inspector, check if behind the attr it says (rule) or (object). if it says rule, then change the attr source with the little icon right next to it, a bit left. the icon looks like a little black tringle pointing into a white rectangle. ... View more

Hi ! Then it's most probable that this is the bug which got resolved for 2012. Can you download the 2012 Trial version and test it ? http://www.esri.com/apps/Products/CityEngine2/index.cfm Let me know if this is an option... Matt ... View more

Hi ! Are you using the TRIAL version of CityEngine ? M. ... View more

You can of course also align the terrain to shapes. So you have both options : - align shapes to terrain - aligning terrain to shapes matt ... View more

Hi ! Check the CGA reference about the ther operations. In your case, check especially setback() and shapeL(), shapeO() and shapeU(). Here's some example code : @Group("Ground Level Setbacks",1) attr Front_Yard_Depth = 5 @Group("Ground Level Setbacks") attr Rear_Yard_Depth = 5 @Group("Ground Level Setbacks") attr Side_Yard_Width = 5 @Group("Buildable Volume",2) @Order(1) attr Max_Height = 15 @Group("Buildable Volume") @Order(2) attr Setback_Angle = 60 @Group("Buildable Volume") @Order(3) attr Front_Baseheight = 10 @Group("Buildable Volume") @Order(4) attr Rear_Baseheight = Max_Height+0.1 @Group("Buildable Volume") @Order(5) attr Side_Baseheight = Max_Height+0.1 @Group("Buildable Volume") @Order(6) attr Color = "#ffff00" @Group("Options") @Hidden attr Opacity = 0.5 @Group("Options") @Hidden attr Show_Shell = true @Group("Options") @Hidden attr Floor_Height = 3.7 @Hidden attr lotArea = 0 @Hidden attr bldgArea = 0 Lot --> case !Show_Shell: NIL else:   set(lotArea,geometry.area())   setback(Front_Yard_Depth) { street.front: NIL | remainder:    setback(Rear_Yard_Depth) { street.back: NIL | remainder:      setback(Side_Yard_Width) { street.side: NIL | remainder:      BuildableArea     }    }   }   BuildableArea --> set(bldgArea,geometry.area()) envelope(Max_Height, Front_Baseheight, Setback_Angle, Rear_Baseheight, Setback_Angle, Side_Baseheight, Setback_Angle)   BuildableVolume   BuildableVolume -->   color(Color)   set(material.opacity,Opacity)   report("Lot Area (m2)",lotArea)   report("Max Building Area (m2)",bldgArea)   report("GFA Potential (m2)",geometry.volume/Floor_Height)   report("FAR Potential",geometry.volume/Floor_Height/lotArea)     ... View more

you have to double click the edge of a static shape to select it. then, the set street edges command is available. m. ... View more

Hi ! Your best option is currently to play with the system. You'll find that the only real limitation to do this street layout that CE does not yet have a real on ramp / off ramp crossing type. But with editing some of the street's tangents, you can approximate this. Maybe put this image in CE as a Texture (Map Layer), scale it up and start blocking out the form. Show me a screenshot once you're there, ok ? m. ... View more

Hi, Incoming polylines from a GDB are always used together with the 'Dynamic City Layouts', with the Block generation deactivated. ( No subdivisions ). Incoming polygons are 'Static Shapes' and there is no connection to the 'Dynamic City Layouts' system. Note that when you select a 'Lot' shape, that you have streetWidth() attributes in the Object Attributes. Together with the First Edge, this is defined by the 'DCL' system. Now if you just import Static Shapes, it depends where the First Edge is. The First Edge defines 'FRONT' in CGA. Thus, my 2 scripts 'inform' Static Shapes on 1] where the best position would be for the First Edge and 2] where the Street Edges are. This is calculated for selected GRAPH segments. So since the 'DCL' inform the Dynamic Shapes automatically, we mimic this via Python, to inform Static Shapes. Additionally, the following issue may also occur to your workflow : http://forums.arcgis.com/threads/79729-Origin-of-shapes-imported-from-FGDB-seems-arbitrary NOTE : The streetWidth() attributes are not standard attributes. They're actually an array ( a list ). That list is just displayed in the Object Attributes as if they were separate attributes. That type of array CAN NOT be ported via GDB directly. Assuming you preprocess your Static Shapes in ArcGIS / FME instead of using my scripts, by addressing both the clockwise issue ( other thread ) and the actual position of streetEdges, the best thing you can do is nevertheless write single streetWidth attributes in ArcGIS per edge and then in CityEngine just create a script which takes those attributes, deletes them and writes an attr array, which then is usable in CGA. Read this a couple of times, then let me know if questions remain. 😮 Sadly, there's currently no easier way to port this information. Let me know if you're good in scripting, then I may give you more inputs ! 🙂 Matt ... View more

Hey Robert. Which version of CE are you using ? I know there was a bug in the convert() function in the 2011 version, which was resolved for the 2012 version. I have tested exactly this workflow in December and it worked perfectly. See attached image and other stuff. [ATTACH=CONFIG]22825[/ATTACH] Let me know this first, then we can dig deeper. Matt ... View more

Hi .. Well, then I guess this is a limitation of the data at hand .. 😞 heightmap files are limited in precision and represent terrains only by vertically displacing a grid of points. So either you have a really good detailes heighmap and quality-matching satellite picture for on top of it. Otherwise, I guess you can not really do more. CityEngine only provides the tools to show the data you have, not increase the quality. Sad but true .. Maybe try to get some better raster files for this task.. Ok ? Have a nice day ! Matt ... View more

to visualize this a bit better, activate wireframes with the '7' key and set the 'wireframe alpha' of the terrain layer (same place as the uv-subdivisions) to about 0.4. ... View more

Check the attached image .. Not sure if you see the same .. ... View more

CityEngine software has way to many hoops to jump thru to activate. I went thru the process just to try it and I still get " No  license file found" These types of DRM are the worst for a consumer who is willing to try a demo, and a possible buyer. really disappointed. Hi .. Can you PM me : *phone number *first/last name *email address Let me know. Then I can forward you to tech support. Sorry for the inconvenience ! matt ... View more

Hi .. Just a note as a quick input .. ArcGIS works in XY space with z being the height. CityEngine stores all data yUp, X and Z being the 'ground plane'. Check out the axis jack, which you can toggle with d,a Check out the compass, which you can toggle with d,c Check out the navigation display, which you can toggle with d,n And most important : Check the 'View Coordinate System', which you can set in the viewport display settings. Note that the whole HUD ( Heads Up Display ) adapts to the VCS. Means that the navigation display displays the data depending on the VCS which you have set. 'CityEngine CS' displays all data the way it is stored, in cartesian coordinates. Note how the axis jack switches too ! When working with CGA, you always work in the cartesian system, so the direction of the first edge is along the initial scope.sx. Means you want to try to change your code to '*.ox'. Maybe geometry.angle(azimuth) may help you too ! Check the docs on that one .. Let me know if this changes your findings ! 😮 Matt ... View more