How to solve several common problems in cityengine 3D modeling (2)

Sort out some common cityengine problems without asking for quantity but passing the test.
Question 1:The DEM and Dom with a large data volume in cityengine cannot be displayed after being imported to cityengine.
Solution:This problem is caused by cityengine texture principle. Cityengine uses DEM and Dom as texture processing. The video card limits the resolution of a single texture to 8192*8192 ,. we recommend that you split DEM and Dom into relatively small textures, such as 4096*4096, and then import them into cityengine in blocks.

Question 2:In the cityengine demo rule file, roads automatically generate equal distance Piers Based on the terrain, but they cannot generate more flexible piers, such as non-distance piers. How can this problem be solved?
Solution:Based on the measured pier Position + DEM base height + 3D bridge deck model, the tensile height of the bridge pier is calculated and assigned to the attribute. The cityengine rule is used for stretching. The bridge deck is still automatically generated using cityengine, but the corresponding pier is not automatically generated. For detailed operation steps, see the blog "unequal distance pier generation process. The effect is as follows:

Question 3:Can the export model in cityengine be exported by object instead of merged into a large object?
Solution:For example, you can set the parameter "create one file per shape" When cityengine exports a 3DS file. In this way, the exported data is exported to an independent 3DS model in the unit of footprint. The operation interface is as follows:

Question 4:When a 3DS file is exported in cityengine in batches, the file name is generated randomly. How can we fix the link between the model file and the attributes of the original data?
Solution:For buildings, you can use the ArcGIS toolbox import 3D files tool to convert these 3DS files into a polygon layer in file Geodatabase. This layer has an attribute with the file name of the 3DS file before transfer. After the model is fully translated in ArcGIS, it roughly overlaps with the original footprint position, extracts the center points of each model, and uses spatial connections to link the center points with 3DS file names with the footprint attribute, create a table corresponding to the 3DS file name and footprint, that is, the model and original attributes are mounted. The specific operation steps can be seen in the subsequent "3D model export and GIS property mounting process" blog.
Model exported by cityengine:

ArcGIS import model tool: