Latest Contributions by SimonHaegler

‎09-24-2017

hi andreas, if you have C++ development time at your disposal, you could use our SDK to implement a X3D exporter: GitHub - Esri/esri-cityengine-sdk: Develop 3D applications using the procedural geometry engine of Esri CityEngine. this repo contains the binaries and example code to get you started - all you need is a CityEngine license. best, simon

‎06-13-2017

hi which version of CityEngine are you using? we already fixed a number of handle leaks for CE2017.0 and are currently trying to reproduce your issue. in the mean time and if you have the time, you could sign up for the 2017.0 beta and try again: Esri CityEngine best, simon

‎06-13-2017

sorry for the very late reply - have you ever been able to solve this issue?

‎06-13-2017

hi & sorry about the late reply. i just verified with CityEngine 2016.1: if i specify a material called 'red' via CGA set(material.name, 'red') it appears in maya as material "red_mat". CE appends "_mat" to differentiate the object from any geometry called 'red' (required by fbx). which CE version are you using? best, simon

‎06-13-2017

does it work in release mode?

‎05-15-2017

hi, thanks for your interest in the CityEngine SDK. at this point, the CE SDK is purely working on the block and building level, i.e. it takes an input geometry, executes CGA rules (via rule packages) and outputs the generated geometry via one or more encoders. e.g. you can use the "area split" operation in CGA to subdivide a block polygon into parcels. support for terrains or street network generation are unfortunately not part of the SDK at this point. but of course we are always open for suggestions. what is your specific use case? sorry for the mixed news & kind regards, simon

‎09-08-2015

hi behnam sorry to hear about your troubles. which CityEngine version do you use and in which Unity version do you see the problem? best, simon

‎08-04-2015

hi, unfortunately, the shapefile importer in cityengine does not consider the character encoding of the attributes, i.e. all strings are interpreted in the native os encoding. this problem has been logged into our bug database and we hope to fix this problem as soon as possible. apologies for the mixed news & kind regards, simon

‎02-18-2015

Finally we are also able to release the patch for OSX: Esri CityEngine 2014.1 FileGDB and CGA Compiler Patch | Samples and Utilities Apologies for the huge delay. Kind regards, the CityEngine dev team.

‎02-08-2015

hi gaetan this behaviour is (unfortunately) expected and is the result of two things: 1. the FileGeodatabase format is not efficient when multipatches of multiple features reference the same image - the image is stored separately for each feature. put differently, there is no common texture storage per feature class. 2. CityEngine does not do any image/texture cropping - it simply exports texture coordinates and the full image. we recognize that in your case these two things result in pathological gdb sizes. would you be able to pre-segment (or simply subdivide) the orthophoto beforehand to reduce the redundancy? you could use CGA to find and assign the corresponding orthophoto tiles. i'll also reach out to some of our ArcGIS data processing experts, maybe there is a way to "throw away" all pixels which are not referenced by the multipatches, i.e. basically cropping down each texture to its active texture coordinate region. sorry for the mixed answer & kind regards, simon

‎12-07-2014

devin, all i can say is that there is a very high probability that CityEngine 2015.0 will support OSX 10.9/10.10. and we will probably drop 10.7/10.8. merry xmas, simon

‎11-14-2014

hi this is a known issue without any currently known workarounds (let us know!). CityEngine 2014.1 (and older) does not support OSX 10.9 or 10.10. at this moment we only support OSX 10.7 and 10.8. we recognize that 10.7 and 10.8 are fast getting out-of-date and plan to support 10.9 and 10.10 for CityEngine 2015.0. kind regards, the CityEngine dev team

‎11-05-2014

We are happy to announce the availability of a patch for the bug mentioned above: Esri CityEngine 2014.1 FileGDB and CGA Compiler Patch | Samples and Utilities The patch is available for Windows and Linux at this time - OSX will follow shortly. Kind regards, the CityEngine dev team.

‎10-07-2014

Dear CityEngine users, Unfortunately, a bug was introduced in the FileGDB importer of CityEngine 2014.1.1703 which imports short int field data as boolean object attributes instead of number attributes. We take this very seriously and are preparing an update. In the mean time, please use the workaround described in this ArcGIS knowledge base article to create long int values of any short int field data: 34315 - Change the data type for an existing field‌. long int fields will be correctly read by CityEgine 2014.1.1703. Please accept our apologies for the inconveniences caused by this bug. Kind regards, the CityEngine dev team.

‎01-14-2014

Hi everybody Thanks for your interest in the CityEngine SDK. I'll try to answer the questions in this thread so far. The published SDK is currently in a pre-release state (release candidate) while we are finishing things. (1) The official location of the SDK is on github: https://github.com/Esri/esri-cityengine-sdk (2) Direkt link to the releases: https://github.com/Esri/esri-cityengine-sdk/releases (3) Documentation The whitepaper and architecture documentation can be directly downloaded (click on "view raw"): - https://github.com/Esri/esri-cityengine-sdk/blob/win64/doc/esri_prt_architecture.pdf - https://github.com/Esri/esri-cityengine-sdk/blob/win64/doc/esri_prt_whitepaper.pdf - The C++ reference is included in the "doc" subfolder of the release. We will also put it online in the near future. A few general things to note: - The CityEngine SDK is currently only available for 64bit platforms. - A valid CityEngine license is required (floating or node-locked). - CityEngine 2013.1 is required to generate rule packges (rpk) for use with the SDK. - You can choose to either clone the repository (and easily get updates via 'git pull') or just download the zips on the release page. Some technical comments: - The warning about the VueExport.dll is expected and can be ignored. - The message "module machine type x64 conflicts with target machine type x86" means that the SDK has been run on a 32bit machine. This is not supported at the moment. We appreciate any feedback or bug reports via the github issue tracker! Thanks for your patience while we finish and polish the SDK. Kind regards, Simon

Online Status	Offline
Date Last Visited	‎02-17-2026 08:28 AM

My Ideas

Latest Contributions by SimonHaegler

Re: X3D export

Re: No more handles (SWT Error) while batch processing .gdb in python

Re: Sign In to ArcGIS Online Fails

Re: export fbx with GIS attribute object id as shape/model name

Re: Ask for help about prt::FlexLicParams

Re: generate city initial shapes with cityengine sdk?

Re: CityEngine Fbx export texture resolution

Re: Is it possible to change the character encoding of a layer in a scene? Or a file?

Re: Heads-up: FileGDB import bug in CityEngine 2014.1 (short int fields imported as boolean object attributes)

Re: Export textured models to Geodatabase

Re: Cannot Browse Computer Directories

Re: Cannot Browse Computer Directories

Re: Heads-up: FileGDB import bug in CityEngine 2014.1 (short int fields imported as boolean object attributes)

Heads-up: FileGDB import bug in CityEngine 2014.1 (short int fields imported as boolean object attributes)

Re: CityEngine SDK

New release of PyPRT 1.12 with support for ArcGIS ...

New release of ArcGIS CityEngine for Rhino 1.4 for...

New release of ArcGIS CityEngine for Houdini with ...

Omniverse Connector for ArcGIS CityEngine is being...

New release of ArcGIS CityEngine for Houdini with ...