Exporting to CityEngine Web Scene (3ws)
CityEngine Web Scene (3ws) is a custom, web-optimized format that can be shared on ArcGIS online and viewed with the CityEngine Web Viewer.
Select the content you want to export in the 3D Viewport, and start the exporter.
Specific Export Options for 3ws
In addition to the general export options, the Web Scene export has an additional export page which allows to control settings of individual layers:
Checkboxes denote if a layer's contents are exported. The initial state of this checkbox depends on the 3D viewport selection, before the export dialog is opened.
The layer name, as it is set in the CityEngine scene.
Layers can be combined to layer groups: All layers with the same group name are collected in a Layer Group. In CityEngine Web Viewer, only one layer of a group is visible at a time (exclusive visibility). Furthermore, all layer groups enable Swipe View in CityEngine Web Viewer.
You can name your CityEngine scene layers to automatically have their layer group set by using the pattern GROUPNAME.LAYERNAME.
|Backdrop||Layer will not appear in layer pane, is always visible.|
|Visible||Layer appears in layer pane and can be set visible or hidden. Initial state is visible.|
|Hidden||Layer appears in layer pane and can be set visible or hidden. Initial state is hidden.|
|Scene settings||Use global option set in Object Interaction in first export dialog page.|
|Locked||Objects in this layer will not be selectable. All objects are combined to a single entity. Therefore locked layers contain a way smaller object count than pickable layers, which can often improve performance in the Web Viewer.
As all objects are combined, per-object metadata can not be written (No Metadata option only).
|Pickable||Objects in this layer will be selectable, all objects are exported as single entities (features). High object count in a layer can decrease performance, it is therefore recommended to only set layers to pickable where required.|
|Scene settings||Use global option set in Object Metadata in first export dialog page.|
|All||Write both object attributes and reports to object metadata.|
|Attributes||Write object attributes to object metadata.|
|Reports||Write generated report data to object metadata.|
|None||Do not include object attributes nor report data.|
|Scene settings||Use global option set in Textures in first export dialog page|
|High Quality||Convert all layer RGB textures to JPG with high quality|
|Medium Quality||Convert all layer RGB textures to JPG with medium quality|
|Low Quality||Convert all layer RGB textures to JPG with low quality|
|Half Sized||Resize all layer textures by 50%; RGB textures are written as medium quality JPG|
|Compact||Resize all layer textures to 50% size but with a maximum of 256x256 pixels; RGB textures are written as low quality JPG|
|Original Textures||Use original textures (Note: only JPG and PNG textures are supported in Web Viewer. Other textures formats will appear black)|
|No Textures||Do not include textures in layer objects.|
In all Texture Quality modes except "Original Textures" the texture size will be limited to 2048 pixels.
Other 3ws export features
- Bookmarks defined in a CityEngine scene will be exported directly to a Web Scene, and are available in the bookmarks menu of CityEngine Web Viewer. Note that different camera angles are not supported at the moment, Web Viewer displays all views and view bookmarks with the default CityEngine angle (54 degrees).
- The current camera position and direction before starting the export is stored to the Web Scene and used as initial view in CityEngine Web Viewer.
- The current shadow and ambient occlusion settings of a CityEngine scene are exported to the .3ws file, and are used as initial values in the Web Viewer. Be careful with enabling shadow and ambient occlusion before exporting, as on some machines Web Viewer might not support direct or diffuse shadows, or will get a performance impact.
As initial settings are stored during export, changing options (such as shadow settings) in Web Scene preview will not change the intial configuration of the Web Scene.
Export tricks and tips
- Due to browser limitations and to ensure compatibility on less powerful systems we recommend to keep Web Scene size (size of .3ws file) below 15MB. Reduce your Web Scene size by
- choose a smaller extent for export (select less objects)
- Use a smaller terrain resolution (512x512 or less). Terrain resolution can be set in Inspector pane of Terrain Layer, Layer Attributes, terrain resolution u and v.
- finetune Texture quality export options (use compact or half-sized)
- or manually convert your textures to lower-resolution JPG or PNG and use texture quality Original
- set export option Interaction to locked where pickability is not required
- reduce the geometric complexity of the models (e.g. lower level of detail, less details on streets).
- By default, terrain geometry is simplified during export. This can take a while for complex terrains. To speed up this process,
- use a smaller terrain resolution (recommended 512x512). Terrain resolution can be set in Inspector pane of Terrain Layer, Layer Attributes, terrain resolution u and v.
- disable Simplify Terrain Meshes in Main export options → Optimizations (not recommended, as this will increase .3ws file size)
- When setting Texture quality to Original Textures, make sure the layer only uses JPG and PNG textures. Other formats are not supported by WebGL, and will appear black in the Web Viewer.
- When preparing Web Scenes for a wider audience, keep in mind that a Web Scene might not run as fluent (or not at all) on other, less powerful systems (less memory, less powerful graphics card). Reduce the exported extent and 3ws file size to ensure wider compatibility.
- Export Quick Start: Step-by-step guide
- General Export Reference
- Webscene Workflows
- Export Application Notes
Copyright ©2008-2016 Esri R&D Center Zurich. All rights reserved.