Latest Contributions by MatthiasBuehler1

hi .. I'll have to track this down. since the 'old procedural times', the EULA have changed, so currently I cannot give you an answer. I'll get back to you ! ... View more

hi ! these two screenshots will make you happy ! 😉 please check all the colored details. to drive the block subdivision lotAreMin and lotAreaMax, do not forget to connect them with the Connection Editor. what this example shows is how you can : - drive min max block subdivision areas - drive street widths - define street types based on width - colorize buildings in CGA which are right next to a specific street type (highway) ok ? [ATTACH=CONFIG]12619[/ATTACH] [ATTACH=CONFIG]12618[/ATTACH] ... View more

hi ! there's no setting for this yet and has to do how ArcGIS / CE interpret the point order of shapes. ArcGIS always stores shapes in clockwise order while the CityEngine always interprets the shape normal counterclockwise. thus, after an import, those Lot shapes have an inverted normal. we're aware that this is a case that should be handled better in future, thus you best just manually reverse the normals after importing them. ok ? ... View more

hi Chris ! thanks for that input ! appreciated. I'll have a look at this. matt ... View more

hey ! thanks a lot for that code, it works so far ! to understand what actually happens here is that all features are actually stored as they were in a geometrical grid and then you delete them based on that grid ? is it also possible to just use a for loop and (possibly) delete each object based on a probability ? or are list based structures not possible ? thx again so far ! ... View more

hey ! better randomly, but every nth would already be great. I'm having the issue with actually getting the list from the selection.. ... View more

hi JC ! to be able to create rules in Visual CGA, you need to know the same things as writing CGA, thus I'd recommend to start with the very basics. I am not a programmer either, but I've tried hard and learned a lot ! VCGA still has some issues since it's been implemented quite quickly, thus I prefer to write CGA code always in the text editor and just look at the graph to check whether my code is well-organized [or just a mess]. if you're a starter, you'll find more info here : http://forums.arcgis.com/threads/52242-Learning-CityEngine-Tutorials-and-other-Training good luck ! 😉 ... View more

hi ! so many questions .. 😉 the standard project structure in the CE is as follows : assets   : 3d objects, facade fotos, the basic elements of your 3d city models [ data going out into the 3d models] data      : data such as shape files or FGDB, .. basically street and footprint data [data coming in from GIS] images   : any other images, references, ... maps     : raster maps such as geoTifs or satellite pictures rules      : cga rule files scenes   : cej files scripts   : python scripts (if needed at all) - this is just the default and can be changed, but I'd leave it at this. you can create any number of subfolders, if needed. maybe look at the structure of the Philadelphia Example. - keep file sizes below max 4096x4096 pixels, better 1024x1024 for less important objects. the reason is that the CityEngine processes all these images on the graphics card and not like in ArcGIS, where you only see parts of the data on your screen. Thus, especially satellite pictures should be kept small to work fluently. For high-res visualizations, they still can be swapped for a higher resolution picture at a later time. The CityEngine is a modeling application, not a visualization platform. Please note also that the way the CE works, all textures need to fit in the memory of the graphics card, thus you cannot process GigaBytes of textures. - the CE uses 2 raster files for a terrain : 1 for the actual height information (e.g. 32 bit geoTIF) and 1 for the satellite picture. Note, both pictures must have the SAME extent ! just play a little with different files. - I usually use png or jpg files for other textures since they're using less disk space. - shapeFiles and GDB are supported. any attribute which helps you to define the 3d model is good. E.g. building height, floor height .. a lot is possible ! - as soon as you drop something which is geolocated into the scene, the Scene Coordinate System (SCS) is set to that very projection. Please note that shapes and curve segments can be / are reprojected on import if that data is in a different projection, but raster files are not also reprojected. Thus make sure especially any raster is prepared to match the CityEngine scene's SCS ! * * * sadly, pipeline networks can not yet be visualized directly from network data (e.g. .stm), but we're working on this. plese have a precise look at the latest CityEngine 2011.1 templates posted by Gert van Maren on the last page here (currently page 3): http://www.arcgis.com/home/group.html?owner=CityEngine&title=CityEngine%20templates&content=all&start=21 check out : CityEngine: Philadelphia example CityEngine Philadelphia example tutorials CityEngine to ArcGIS CityEngine: 2D to 3D ok ? 🙂 ... View more

did you also adapt the attr ? attr Stories = "" would be wrong in this context .. attr Stories = 0 ... View more

hi ! afaik, the exported file type which is exported drom osm.org is always png. thus, this should work. maybe you're nor displaying maps (toggle F9) ? after drag n dropping the file into the viewport, is a map layer created ? ... View more

hi ! can it be that Stories is a float value and not a string ? 5 is not "5" maybe try it without the " .. let me know .. ... View more

hi ! this is indeed not very well documented, here's a few inputs : * we read xyz as regular grid with equidistant square grid (point clouds not supported) * data MUST match Scene Coordinate System (SCS) * points must be stored with spaces let me know if this helps. matt ... View more