Latest Contributions by MatthiasBuehler1

Ok. 🙂 This thread : http://forums.esri.com/CityEngine/forum-44564.html page 2, my last post, script named 'setStreetEdges_v1.0.py'. Check the end of the script, esp. short before : ce.setAttribute(shape, objAttrName, streetWidthAttrValueList) This will show you how to write that list. One thing I've just noticed is that in this line : streetWidthAttrValueList = highestEdgeIndex*[0] -> My coworker made a similar script which states: streetWidthAttrValueList = highestEdgeIndex*[None] So it can be that then, the streetWidth() attributes with the value '0' do not appear in the Obj Attr list in the Inspector, which even may be better. Try playing with this. Concerning the indexing : Note that ArcGIS stores the vertex order clockwise, while CE interprets the vertex order counterclockwise, which messes up the order you have in ArcGIS. But you can fix this by a function which translates between the two worlds. Let me know if some things are unclear ! Matt ... View more

Hi ! All 3D applications use slightly different material systems, so there's sadly no standard concerning this. There's always a headache with this. E.g. if you import those file into an other 3D app, they may look fine.. 😞 Honestly, I'd try to create a script which gets rid of all those transparencies in 1 step after import. Takes some time to develop, but this will also help creating a proper pipeline. Matt ... View more

Hi ! Maybe try the .3ds file format export or .obj .. It may give you better results as a start to track this further down. Let me know .. ... View more

Hi ! Did you see this thread ? http://forums.arcgis.com/threads/57068-Perhaps-I-m-using-it-wrong-my-touches%28%29-rule-seems-to-be-unpredictable [Occlusions are tricky to handle, indeed. I'm usually trying to work around them by using intelligent heuristics or add a few attributes to get around them.] Let me know if you have more questions ! Matt ... View more

hi ! If you guarantee that the base is always square, then I'd use an asset. Much easier than to create the form in CGA. If you want it to work on other shapes, read on .. 🙂 -------- The lower one is quite simple. first, use a roof operation, then directly split that roof volume vertically e.g. roofHip() split(y) {'0.5 : RoofForm. | ~1 : NIL} The first one is a little more complex and can only be created with recursive rules, but using the same concept. There's an example of such a form in the Philadelphia Example, in the 'GIS-Driven Buildings.cga' rule. Track down the VaultRoof / DomeRoof. They're using a certain number of recursions, using that number to determine the new angles at each step. Let me know if you have more questions ! 😮 ... View more

Hi ! You'll have to set this array with Python, this can not be done with CGA. Let me know if you have some experience with scripting (esp. Python), this will be fairly technical .. 🙂 ... View more

Try this code .. 🙂 satelliteImage = "builtin:uvtest.png" #"maps/mySatellitePic.jpg" # user defined image in maps folder satelliteImageData(data) = case data == "SX"   : 1000    # user defined, same as terrain extent. select terrain layer and check Inspector case data == "SZ"   : 1000 case data == "OX"   : 1000 case data == "OZ"   : -1000 else : 1 Roof --> setupProjection(0,world.xz,satelliteImageData("SX"), -satelliteImageData("SZ"), satelliteImageData("OX"), satelliteImageData("OZ")) projectUV(0) texture(satelliteImage) ... View more

Hi ! Looking nice so far, your city. I assume there's an issue with some transparencies which are remapped at the import into MAX. Do you have transparent textures ( with alpha channels ) or are you using set(material.opacity, ..) ? I'd try to first track the material settings alone down in a separate scene until you have a proper pipeline. On a full dataset, it's tricky to track this down. Let me know if you find a specific issue ! Matt ... View more

Hi ! I see. Can you post some screenshots (before - after) or a broken down scene file with rule with which you can reproduce the issue ? I'll need some more inputs to track this down .. Let me know .. ... View more

Hi ! That option is indeed missing currently. 😞 I have forwarded your wish ! M. ... View more

Hi ! In this list : http://forums.arcgis.com/threads/64843-CityEngine-Collection-RESOURCES-FAQ-HELP , go and find the thread on the 'Wobble' effect. This will help you. Let me know if questions remain ! 😉 Cheers ! ... View more

Hi ! Check here : http://resources.arcgis.com/en/help/arcgisonline/010q/010q000000nw000000.htm IE is also supported, but needs the Google Chrome Frame Plugin. Cheers ! Matt ... View more

btw. you will also maybe find some more info on my tutorial videos on shape and street import: vids 4 & 5 here: http://forums.arcgis.com/threads/64843-CityEngine-Collection-RESOURCES-FAQ-HELP ... View more

hi ! coordinates in dxf files are never interpreted as degrees, even though if you import them into a scene which has a defined projection. if you have 48 / -123 degrees approximately, the effective cartesian coordinates you need are much bigger. if you have any GIS data, you can check those values by selecting 1 shape vertex or graph node and then in the Inspector check the vertices tab for the xyz values. note that those values are always cartesian (xz horizontal) and yUp, not as in GIS where you have xy horizontal and zUp. you will find large coordinates such as e.g. 300'000 / -850'000 or so. Thus, you have to move your dxf data to those coordinate positions in your CAD/drawing application. Once your data is at the correct cartesian coordinates, on the CityEngine IMPORT (into the scene), those big values are reprojected using the projection and will land around 48/ -123. I'm currently on holiday. If this helps ok, otherwise, we can check if we find a time to chat. cheers ! matt ... View more