Latest Contributions by CherylLau

Esri.lib, which comes with CityEngine, has some generic building rules that might be useful.  The Building_From_Footprint.cga rule works on 2D footprints as initial shapes, and the Building_Mass_Texturizer.cga rule works on 3D models as initial shapes. ... View more

Thanks for the files, and thanks for the great labeled screenshots.  They really helped us easily understand what you meant. The faces are missing because in CityEngine we do some cleanup that removes zero area faces.  Some of the models you have are small, and this means that the details on the models, like the spikes and tips of decorative elements, are being removed because these faces are considered to be zero area faces.  If you make your models larger in Maya before you export, then they should work. The bridge obj is 0.31m, which means the missing faces on the decorations are really tiny.  (Keyboard shortcut M then D to get the measurement tool, or select it in the toolbar).  In real life, I don't think you'd want a bridge that is only 30cm.  If you scale the bridge up to a more city-scale bridge length, then the decorations should be visible.  CityEngine is made for building-scale and city-scale scenes, so we try to cleanup excess geometry that essentially are "zero-area" faces at these scales.  The collada file is a cube because it is an unknown asset.  Given the error message, I assume that the model is also too small. The tower obj is ok because it is 4m wide, but the collada file is 0.04m wide.  This is why the small decoration elements are missing in the collada file but ok in the obj file.  Try scaling up your model to a larger size. ... View more

No, setting the seedian in this case wouldn't help because the attribute height is initially set to a random number before the rules are executed, and this value for height does not change as you execute the rules unless you use set() to change it. However, you can change height by making it a function rather than an attribute.  This way, a different random number is retrieved every time the function is called.  Then, you don't have to set the attribute value.  You just have to remove the "attr" keyword in front of height, but in this example, I also renamed it to getHeight to make it clear (as an example) that it is going to be executed every time the function is called on line 7 (for each lot). getHeight = rand(1,10) Block -->      split(x) { ~1: Lot }*       Lot -->      extrude(getHeight)‍‍‍‍‍‍‍ You could extend this to work for materials as well. getHeight = rand(1,10) getMaterial =      30%: "wood"      30%: "brick"      else: "concrete" Block -->      split(x) { ~1: Lot }*       Lot -->      extrude(getHeight)      Building(getMaterial)       Building(material) -->      case material=="wood":           color(1,0,0)      case material=="brick":           color(0,1,0)      else:           color(0,0,1)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Either by setting attributes or creating functions, you can achieve what you're looking for.  There are probably other ways too. I don't think you need to set the seedian.  For the initial block shape, one cga rule is executed, and every rand() call within that rule file will return a random number.  Imagine that you have 5 blocks that are initial shapes onto which you apply the rule file.  If the seedian of these 5 blocks were the same, then you would get the same result for each block because each block has the same seedian.  In this case, it makes sense to set the seedian of the initial shapes to something different so that all 5 blocks have different seedian values.  Then, the 5 blocks will have different results.  This case where initial shapes start with the same seedian is not a common case.  As a side note, this rare case can arise when you create static models/initial shapes out of shapes that are stacked vertically (with the same xz values but different y values). ... View more