Latest Contributions by ThomasFuchs

Good news 😀 @nicolaisteino , @REDSUN , @pinlv  Thank you so much @LionelHenry_EsriFrance for confirming CityEngine 2023 works on Mac with Parallels Desktop. I found this Parallels KB article that also explicitly mentions ArcGIS CityEngine 2023 (and later) can be used: OpenGL versions supported in Parallels Desktop ... View more

Hello, I have an important update for all users of AMD Graphics: If you encounter a black viewport, open the driver settings and ensure the global graphics settings for Anti-Aliasing are set to "Override application settings".    ... View more

Hello @Farhan  Thanks for your question. When creating the RPK please make sure the asset is included in the package. If not, it is possible to manually add the OBJ and its dependencies (.mtl) in the dialog:   ... View more

Hello @jabrett  Thanks for submitting this question. When defining setbacks, it is not necessary to use shapeO(). Please use the setback operation—ArcGIS CityEngine Resources | Documentation instead. To create the T-shape  you also want to use the t operation—ArcGIS CityEngine Resources | Documentation to translate the scope after adjusting it's size. ... View more

Here is where you will find the beta version download on Esri Early Adopter  ... View more

Hello @aogino  here is the documentation on importing basemaps: Get Map Data—ArcGIS CityEngine Resources | Documentation Currently only Esri tile services are supported. ... View more

Hello @aogino  Your CGA code compiles without error. When applying it to a shape, the resulting model is the shape extruded by 10m.   ... View more

Hello @ChanningWang  Thank you for bringing up the OSM boundary information. The OSM importer in CityEngine doesn't need this information. Could you please tell me more about the "subsequent calculations" you want to perform? ... View more

Thanks, @DevinLavigne for reporting this issue. The development team is now looking into it. ... View more

Hello @richiedlon  Thanks for the question. I hope to help you with your interesting project. You can analyze the roof shapes with the geometry functions—ArcGIS CityEngine Resources | Documentation  Use geometry.area() first, then calculate an efficiency factor from geometry.angle(azimuth) and geometry.angle(maxSlope). These values can then be reported: report operation—ArcGIS CityEngine Resources | Documentation ... View more

Hello @biaozeng  Thanks for your question. To export metadata like the attributes, please ensure Mesh Merging is set to either Per Initial Shape or Per Initial Shape by Material. For more information please consult the CityEngine Help on Export DATASMITH (Unreal and Twinmotion)—ArcGIS CityEngine Resources | Documentation ... View more

Thanks for verifying this. With the connection editor, you mapped the Rule Attribute "Eave_Ht" to an Object Attribute named "EaveHeight". This created the following entry in the Layer Attributes of the "Shapes Sample" layer:   attr Eave_Ht = getFloatObjectAttr("EaveHeight")   All Object Attributes of objects in the source layer at the location are getting sampled. In your case the value of the object in the center is returned. The behavior is expected.  To make a direct connection between a Rule Attribute and an Object Attribute, the names must match. Either add an extra (optionally hidden) attribute to your rule   @Hidden attr EaveHeight = 50 attr Eave_Ht = EaveHeight   or edit the name of the object attribute Inspector—ArcGIS CityEngine Resources | Documentation ... View more

Hello @richiedlon  Thank you for your question.  Looking at your screenshots, it seems like you connected the object attribute "Height of the Eave" with your rule attribute "Eave_Ht" via a layer attribute. Have you checked what the values in the Object Attributes section of the Inspector are? Maybe the difference is showing there as well?  Inspector—ArcGIS CityEngine Resources | Documentation ... View more

Hello @Bee-am  Please excuse the late response. I now figured out what is happening: The current version of the Complete Streets Rule does not support bridge occlusion. The overlap/ occlusion queries can cause a rule to generate slowly. The occlusion check on bridge piers was considered an edge case that is not important enough to justify the performance hit. Therefore it was removed in 2018.  If you want to add it back in, edit Complete_Street.cga and replace the "PierCheck" rule with the formerly used code:   PierCheck --> case (Bridge_Display == "On, Show All Piers"): # Occlusion test is disabled, by "On, Show All piers". PierShow case (Bridge_Display == "On, Flag Occlusions"): case overlaps(inter): # This pier hits another model. print("Occlusion true: Bridge pier overlaps another model!") # Flag the pier in red. This is a debugging mode for the piers. color(1,0,0) PierShow else: # No occlusion so show the pier. print("Occlusion false.") PierShow else: # Use standard occlusion method. case overlaps(inter): # Omit piers due to positive occlusion check. # This means the pier would hit a street or other model. NIL else: # No occlusion so show the pier. PierShow     ... View more