Latest Contributions by ThomasFuchs

Hello Micah The color picker has not been removed from The Inspector of CityEngine 2016. It has been moved to the drop down menu. Currently there is only the Hex Code #RRGGBB and no color display. Since there has been a lot of requests to show the selected color instead, it will be added again in the next release. New But CityEngine 2016 requires now Annotations to be set in the CGA rule file. @color attr myColor = "#c0c0c0"‍‍‍‍ Rule attributes that do not use this annotation are treated as string values and no color picker is available. In this case either: add the @color annotation to the rule file or use an external tool to pick a Hex Code #RRGGBB and paste it into the attribute field. For instance here is a web based color picker: RGB Color Codes Chart  ... View more

Hello Reit Sined The map shown in the "Get map data" window is drawn using a web interface. On Windows CityEngine uses the internet explorer installed on the system. Please make sure the program has all permissions to access the web server. ... View more

Hello Sean Yes this is possible. You have to set the parameters for the node locked license accordingly. The default config ( ESRI_CE_SDK_LIC_FEATURE=CityEngAdvFx ) should already give the right configuration for the trail version. esri-cityengine-sdk/README_windows.md at master · Esri/esri-cityengine-sdk · GitHub Locate the directory where you copied the plugin, let's call it PLUGINDIR Locate the Maya.env file in your home, usually its in "My Documents\maya\2016" Edit Maya.env as follows: :: use CityEngAdv for floating license ESRI_CE_SDK_LIC_FEATURE=CityEngAdvFx :: uncomment for floating license :: ESRI_CE_SDK_LIC_HOST=27000@my.flexnet.host :: replace <PLUGINDIR> with the actual path PATH=<PLUGINDIR>\plug-ins;%PATH% MAYA_PLUG_IN_PATH=<PLUGINDIR>\plug-ins MAYA_SCRIPT_PATH=<PLUGINDIR>\scripts ... View more

Thank you for you reply. It looks like the Heightmap and Texture files have been successfully downloaded. But clearly the terrain layers elevation attribute has has not been set. Could you please try to add the Heightmap manually by navigating to maps/Terrain_Satellite4/elevation.tif and right-click to import. As shown below, you can manually set the elevation attribute. I hope this will provide a solution. ... View more

Hello Mohsen Nazemi, This is a quite common question. It is not possible to directly read out the rule-defined attributes. Please also refer the following GeoNet thread: Is it possible to read rule-defined attributes with Python? However there are indirect methods, like exporting a report to get the values. Tutorial 12: Scripted report export—CityEngine Tutorials | ArcGIS for Desktop ... View more

Hello Reit Sined, Thank you for your report. There have been no changes in that section of the Inspector. So you were looking in the right place. For some reason the last part with the layer attributes is missing on your screenshot. Please try to re-open the scene and check again. ... View more

Hello Dmytro Zhyltsov, if the "height" attribute is not present in the open street map data, it is a common practice to set it to a default value greater than zero in CGA. That way, the building gets extruded in any case. ... View more

Hello Jugal, Thank you for you question. CityEngine Web Scenes do not support layer coloring. This is a feature of The Scene Editor to visualize which shapes in the viewport belong to which layer. Looking at the example you provided, I guess you want to color your CGA models by layer. To achieve this, you can set a layer attribute "layerColor" for each layer, then make your CGA rules use this value for the color Operation attr layerColor = "#c0c0c0" Colorize -->     color(layerColor)     ... View more

Hello Thomas, Thank you for the error report. I am unaware of the issue. Can you please provide more detail? Have you been able to install other versions of CityEngine or other Esri products? Thanks for the help. ... View more

Hello L R, there is no public known issues list for CityEngine. However this forum can be used to report issues, share workarounds and updates for bug fixes. It is regularly synced with the development backlog of the software. ... View more

Hello Pedro, Thank you for your question. There is a naming discrepancy for CityEngine web scenes (3ws). What is displayed in the information tab is actually what was entered in the description field. ... View more

Hello L R as the CE help on The Inspector states: City Engine has the following types of object attributes: BOOL  : boolean FLOAT : floating point value (double precision) STR  : character string (UTF-16 encoded) BOOL[ ]  : array of boolean values FLOAT[ ] : array of floating point values STR[ ]  : array of character string The attribute type DATE is unknown to CityEngine and will be converted to STR. I made a quick test with a GDB in ArcGIS Pro and imported it to CityEngine 2016.0 It also showed correctly in python. On export to GDB the dates will be mapped to their original type and show up as DATE in ArcGIS Pro again. Please also refer the CE-Help on Esri FileGeodatabase (FileGDB) Export : Export object attributes: Exports all object attributes as feature class fields. Information about data types and domains will be re-used, if available from an earlier FileGDB import. Array values will be ignored if the next option "Export dataset relationships" is not selected and the attribute is not part of an actual relationship. In short: When working with GDB data types like DATE that are not natively supported in CityEngine, you have to: define the GDB attribute in ArcGIS Pro first. do a GDB import in CityEngine change the attribute according to the formatting convention on GDB export from CityEngine the attribute value will be mapped back to its original type ... View more