{"id":3771,"date":"2017-11-06T17:31:45","date_gmt":"2017-11-06T17:31:45","guid":{"rendered":"https:\/\/www.geoplanit.co.uk\/?p=3771"},"modified":"2017-11-07T17:15:01","modified_gmt":"2017-11-07T17:15:01","slug":"cityengine-2017-1-official-release","status":"publish","type":"post","link":"https:\/\/www.geoplanit.co.uk\/?p=3771","title":{"rendered":"CityEngine 2017.1 Official Release"},"content":{"rendered":"
\"\"
This viewshed tool is a great addition to the CityEngine toolset!<\/figcaption><\/figure>\n

So it looks like CityEngine 2017.1 is soon to be released (it gets released for Partners a little earlier!) and wow have the team in Zurich and Redlands been hard at work!\u00a0 Of course there are two headline features<\/p>\n

    \n
  1. The amazing viewshed\/view corridor analysis you can do against your models here (oh and the can be controlled by python too!).\u00a0 Unfortunately for now it looks like you can’t export the analysis, but it is a great tool for understanding building heights and volumes within CityEngine itself.\u00a0 \u00a0I did a small sneak post a couple of weeks back which is here.<\/a><\/li>\n
  2. High-end architectural visualisations with Unreal Engine, basically we have a new exporter function for Unreal Engine based on the Datasmith SDK.\u00a0 \u00a0This seems to replace the FBX workflow and allows a more efficient way of getting your cities into Unreal.\u00a0 \u00a0It looks like its capable of tens of millions of polygons!\u00a0\u00a0<\/li>\n<\/ol>\n
    \"\"
    CityEngine to Unreal Engine… simple.<\/figcaption><\/figure>\n

    It looks like the Esri team are making good on their promise of making CityEngine into a true geodesign tool of great value to Urban Planners.\u00a0 There are a lot of enhancements and bug fixes<\/p>\n

    Among the new CGA functions I think the interesting on of mention is the new annotation attribute @Enum and a change in how @Range works we can also restrict the values (so you can’t as a user override these values in the inspector!).\u00a0 This allows for a more defined set of inputs and makes the inspector much easier to read and interact with. @Angle, @Distance and @Percent do what they say and I think go some way in making people who author rule files (like myself) make easier to use tools!<\/p>\n

    One improvement I’ve noticed is that that the Scene Layer Package export function has been improved to make it what Esri call ‘Smart Mapping-ready’ basically it means attribute information is written to the scene layer package which makes it nice and easy to change colour by values in the online scene viewer.<\/p>\n

    \"\"<\/p>\n

    A big thank you to the Esri engineer who fixed the bug in the FGDB export that meant previously imported feature classes retained memory of their old names when exporting!<\/p>\n

    \"\"<\/p>\n

    Finally a reminder this release CEJ files (CityEngine Scenes) are not backward compatible with 2017.0!\u00a0 Take my advice, use a new workspace directory per CityEngine release and copy old project to the new workspace so you don’t run the risk of damaging your work!!<\/p>\n

    For a full list of what’s been changed you can look at the CityEngine 2017.1 release notes.<\/a><\/p>\n

    Have a view of the CityEngine’s new youtube videos for a bit more on the viewshed and corridors in 2017.1:<\/p>\n