#3D CITYENGINE CODE#
#3D CITYENGINE FREE#
#3D CITYENGINE WINDOWS#

In the campus model, roads and sidewalks could have been created as 3D objects in CityEngine so that they would not be positioned below the terrain. Imported models and CityEngine models on an OSM satellite image in CityEngine Importing 3D Models This clipped raster file was imported into CityEngine and used as a texture overlay for the terrain. The image was exported with the Using Selected Graphics option so only the image contained within the polygon was exported. In ArcMap, the georeferenced image was opened and a polygon drawn using the same coordinates as the border traced in CityEngine. The x,y coordinates of the polygon nodes were recorded. Clip the Georeferenced ImageДЄ polygon was created in CityEngine that traced the border of the terrain file. After the transformation was selected, georeferencing was updated. Depending on the number of points to be georeferenced, first- or second-degree transformation can be used to stretch or bend the raster dataset to better match the target. In ArcGIS, the Georeferencing toolbar was used to place control points first on the raster image and then at the x- and y-target coordinates taken from the OSM data. Geolocated buildings were created in SketchUp using camera images with the Match Picture feature. To georeference the raster dataset in ArcGIS, multiple sets of x- and z-coordinates of OSM vertices around the perimeter of the area (such as road intersections) that are common to both the raster and aligned dataset and easily identified were located and recorded. To overlay a raster image over the target area, it may need to be georeferenced in ArcGIS first if it doesnвЂ™t import correctly into CityEngine. More than one image can serve as background in CityEngineвЂ™s Web Scene if text or other features need to be adjusted for various zoom levels or for visibility reasons.

#3D CITYENGINE FREE#

OSM data matching the extent of the elevation model was exported and converted to an image file with Maperitive 2.0, a free desktop application for drawing maps based on OpenStreetMap and GPS data, and exported as a BMP file at the preferred scale. In this case, OpenStreetMap (OSM) was used as a basis to develop an overlay image.OSM provides a suitable basis to create an abstract representation of the general infrastructure on university campus, but other image overlay options exist. It is advisable to make all edits to the image before draping it on the terrain. CityEngine supports image overlays on terrain data. Once the elevation model is generated, it is usually draped over with an air photo. Trimmed OSM image with x,y control points marked after georeferencing Creating an Overlay Image The TIFF was dragged into CityEngine as a terrain layer. After opening the output raster, it was exported as a TIFF to the CityEngine workspace. The Sampling Distance option used should be a cell size of less than 10 meters, and 3 to 4 meters is preferable. To prepare the TIN for CityEngine, it was opened in ArcMap, and the TIN To Raster tool (in the 3D Analyst toolbox) was used to convert the TIN to a raster. A TIN for Fairfax County was acquired and clipped to the area of George Mason University. A TIN was used for the base elevation data for the campus area, but several other elevation data options would also have worked.

Importing a TIN File into CityEngineДЄ triangular irregular network (TIN) file represents a surface and is often used to visualize terrain information. Finally, buildings were either imported or created, trees imported or generated, and thematic data symbolized. At this point, 3D roads and sidewalks were generated and imported into Esri CityEngine. A labeled raster image file was created so it could be draped over the model.

The first step in the process was the generation of a campus elevation model. This is a C++ project which requires Visual Studio 2017 / 2019 and UE4 requirements (see ).A TIN of the campus was imported into CityEngine.

CityEngine to Unreal Engine workflow documentation:.

Integrated non-VR level with metadata support.

Integrated onboarding experience (tutorial).

Multiple devices are supported for collaborative VR

#3D CITYENGINE WINDOWS#

Supports HTC Vive, Vive Pro, Oculus Rift, Rift S, Windows MR devices.

Streamlined export-import from CityEngine to Unreal Engine with Datasmith.

Integrated VR locomotion and interaction with the city model (panning, zooming, pointing, points of interest, switching scenarios, setting time of day, etc.).

#3D CITYENGINE CODE#

Unreal Engine project containing all necessary materials, blueprints and C++ code to create an interactive VR experience for architecture and urban planning.

3d cityengine