Latest Contributions by MatthiasBuehler1

Hi ! Since CityEngine is still such a young product, the content is still limited. Also, there's currently no platform on which users share their rules or cities. Though we're very aware of the fact that users, as yourself, are much more keen on actually just using rules as templates instead of creating the rules themselves. Scripting is complex, thus we're researching in this field and work hard to make things easier for the end user. Especially the direction of making template rules more accessible is one of the main focuses of the development. Nevertheless, try to learn CGA scripting. I'm here to help and I'm sure you'll progress fast ! Urban planning is a logic process, as is creating rules for CityEngine ! m. ... View more

hi ! yes, you can check the asset in 2010.3 : if you select the asset in the Navigator (obj or dae), click on the little magnifying glass icon in the Navigator. this will open the file PREVIEW (you can tumble in this little preview.) mtl files are evaluated in there. does that work for you ? matt ... View more

hey ! the attr streetWidth is not inherited to the shapes as opposed to e.g. the connectionEnd Object Attributes. (the graph segments inherit some attributes down to their shapes). if you select a street shape and have a look at it's Object Attributes, you see that they're inherited since they're written in italic (inherited = updates of the graph segment widths will be reflected in the shapes's OA). If you create a new Object Attr on this shape via RMB in the OA tab, you see that the new OA is written normal (not italic). I know, it's tricky. 🙂 * * * NOW. since there's no attr called streetWidth on Street Shapes, you can of course create one manually, but the trick is to map 'scope.sz' to this new attr since it represents the actual width of the shape. The initial scope orientation of Street Shapes is always that scope.sx is 'along' the street and scope.sz is it's width. Example : attr myStreetShapeWidth = 0 # initialize the new attr @StartRule Street -->     set(myStreetShapeWidth, scope.sz)     PrinterRule PrinterRule -->     print (myStreetShapeWidth)     Done. ok ? ... View more

hi ! yes, this is possible ! the easiest way to do this is to use the 'scatter' operation (check the CGA docs in the F1 Help Menu). next to this, you can also use the split() operation to split e.g. a plane in the 2 dimensions into smaller shapes on which you insert assets. let me know if this helps you further... [I guess you'd like an example, right ? 😉 ] matt ... View more

hi ! can you post a screenshot which shows the before/after states ? are you getting any errors in the export.log ? let me know .. ... View more

Hi ! Indeed that would be handy. It's been asked before : https://c.na1.visual.force.com/apex/ideaList?c=09a300000004xET&category=Esri+CityEngine Feel free to post new wishes there ! 🙂 Kind greetings ! matt ... View more

- using   you asset, when choosing incorrect edges the asset was split, but no new faces were created! Why? For example, on the screen I chose edge number 4 and the asset was split from the back. Shouldn't I have just to be clear, you actually meant using 'my (André's) own' asset, right ? ... View more

Hi Stephanie I just move this thread to the correct place (I hope). You posted it in the CityEngine Python section. Hope you get help here .. ! Good luck ! matt ... View more

Hi ! Since the CityEngine creates models based on polygons, CityEngine was not designed to work with point clouds. Thus what you'd need to do is use the tools ArcGIS provides to first convert the LIDAR data to (flat) shapes as a base for the footprints. I know there exists some tools like this, I just do not know them. This process may involve something like converting first to raster, then creating shapes from those raster files. But once you have the shapes, you're good to go in CE. I hope this helps further .. ... View more

hi ! it depends on the file type .. what file is it ? let me know .. ... View more

hi ! yep, sure ! 🙂 ... View more

hi .. I'm not sure about the collada error .. you may want to check with Esri Support for this .. did you try kml/kmz ? you could also try to import with the 'kml to layer' tool. hope this helps you further ! ... View more

hi ! just put the whole project folder onto a server/network drive, then import it into the CityEngine workspace from there on each user's machine. that's great also to back it up since it's only located in one spot... I hope this helps ! ... View more

hi. there's no msi installer available. Hope you make it happen with the exe installer too.. ... View more

best is to use the export presets at the very top of the exporter window, there's an arcMap and google Earth compatibility preset which automatically makes things correct for the two target platforms. only the gods know why, but the two apps treat models differently, that's why we had to include that option. [weird, we know.] does this help ? ... View more