Hi Ryan
Its great to hear about your enthusiasm for procedural modelling and that you follow the path of CityEngine since its early stages.
We agree with you, the user experience of CityEngine is not yet where we want it to be. While it is an ongoing initiative to improve usability, - recently we simplified the Inspector for example - "Better UI" is now one of the focus topics for the next release. This will free resources to design and implement improvements, so stay tuned.
Let me comment your feedback in more detail:
1.) The concept of workspaces is not easy to grasp, thats true. On the other hand it helps you organise your content in the long run. It is deeply rooted in CityEngine, therefore we cannot change it without big efforts. One concrete line of attack regarding better UI is the improvement of the first-time user experience.
2.) It is not our intention to prohibit/make it difficult to use your favourite input device in CityEngine. For future CE Basic Versions, we plan to support 3D Mice too.
3.) Working with geo-referenced data is one of the main features of CityEngine and therefore makes it a great fit in GIS workflows. To use Get Map Data in a non-georeferenced scene you can do the following: Download the data into a scene with an appropriate coordinate system. Then create a new scene without coordinate system, therefore select “No Projection, raw data in feet”. Create a Map Layer -> Terrain and use the map files from the previous scene. you find them in the ./maps folder. Next, set X & Z-offset to 0, this places the terrain at the origin of your scene. To move the terrain vertically, use elevation offset in the Inspector.
4.) To import assets into your CE project, go to import… and select the appropriate wizard. By clicking “Browse.." you can import data from your computer. Maybe you missed the button on the top left to expand the file tree.
Again, we are aware of the usability issues and are continuously improving. Thanks for your feedback and hopefully I was able to help.
We are sorry for not answering you earlier, it looks like we lost track of your post.
As a new user of ESRI products (as of this year) and a new GIS guy from a video/ animation and 3D software background, I do notice a lot of the same frustrations that Ryan mentioned in this thread. I am encouraged that it is replied to by you (Christian) with the level of detail that you are willing to try to make it easier to use for people, especially those of us with 3D software knowledge.
I'm not going to beat it down with numerous details or comparisons, which are many. The concept is great and the capabilities (so far) are okay, except for the output quality. I presently have an open case with ESRI support that is being investigated in regards to the output, and how it handles texture images when exporting.
To make this a short post and convey the ideas for improvement, I want to simply get this out there. ESRI products are known for their support and use of Python scripting. Blender 3D is open source, FREE, and highly capable software that rivals the big platforms like Maya, 3DS MAX, etc. The code is also free, and it also leverages Python for customization, game development and plugins. The open-source GNU license for Blender also allows for it to be edited, studied, copied, re-packaged and sold as something else.
Therefor, why not get a copy of the Blender code and use the render engines, animation tools, format import/export capabilities, image editing abilities, and basically build CityEngine over the core of Blender? I'm not a programmer but I do know that there should be something to gain from what's done already. I started another idea thread about integrating animation recording and playback of tours over maps (similar to Google Earth Pro, also FREE) and this is done in Blender as well. Get a copy from Blender.org and try it out.
By the way, someone else also makes a GIS plug-in for Blender but I have yet to figure out how it helps me with ESRI. This could also be used/ leveraged in integrating them together.
Hi Thomas,
Thanks for your input and welcome to the world of GIS and ESRI. We are aware of blender and we like it a lot. Still, switching to the blender core is not part of our roadmap.
With the 2017.0 release we will deliver numerous UI/UX improvements, and we will continue in this direction for future releases.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.