CUBIZEN: Global Mapper, CityEngine & Creative Tech

I'm taking a short break to post again today. This is the second lesson on i(), covering the form that takes two parameters. Sometimes, when you load a file exported from a 3D program into CityEngine, the direction of the height axis is different, so the object ends up placed all wrong. This is because the direction of the height axis differs from program to program. (Programs can be divided into those that use the right-hand rule and those that use the left-hand rule.) If it's a source you made yourself, you can simply export it with the y-axis pointing up, but with files made by other people, you often need to change the direction. In that case, you can place it correctly by changing the second parameter, upAxesOfGeometry. I created a square pyramid in a program like the one shown below. figure 1 If you look at the axis directions of this program, the x-axis is the same as in CityEngine, but the height axis is the z-axis...

Understanding importing and scaling external 3D assets in Esri CityEngine using the CGA i() insert command. This tutorial covers the fundamental syntax and behavior of the CGA i() command in CityEngine, explaining how imported 3D models adapt to point, line, face, and volume scope dimensions across procedural modeling workflows. I am posting this briefly as I have a bit of time during my schedule. I planned to work on CGA coding while looking at building photos, but I realized I missed one critical command. The elements that make up a building—walls, windows, doors, window frames, fences, surrounding ornaments, water tanks, air conditioner outdoor units, signboards, landscape trees, and so on—are far too numerous to list. Implementing all of these directly in CGA??? While not impossible, there is certainly no need to do so. We must use an effective method. Among the various elements of a building, if a component is al...