IDEA
|
When exporting a scene as an image, it is possible to control the size of the output by changing the pixel density (DPI). However, this control the size of the image only, without affecting how the scene is rendered. While this is not an issue for small exports, it presents a problem for large exports because the rendering of raster datasets is not adapted accordingly. The rendering of raster images draped on the terrain seems to be controlled by the observer distance only. It would be nice to be able to enhance the quality of raster rendering (maybe similar to what was possible on ArcScene) when exporting scenes to large images, in order to preserve details. I talked with someone at ESRI but haven't found a workaround to this at the moment. Any advice is of course welcomed! Thank you in advance for the consideration. Best regards Natan
... View more
05-01-2019
05:35 AM
|
2
|
0
|
749
|
POST
|
Hello Nathan, Terrain as OBJ seem to be a lot easier to export to LumenRT, but how can you ensure their geo-referencing? I've tried in many ways with the centering tool but it doesn't seem to work, and it won't let me re-import my terrain as they are now located far away from where I have my georeferenced objects. Thank you in advance, Regards Natan
... View more
06-28-2018
09:09 AM
|
0
|
0
|
559
|
POST
|
Hello, I am trying to export a scene from CityEngine 2016.1 to LumenRT using the Bentley LumenRT Connect Edition exporter. This usually works well, but this time the scene is quite large and I am running in some problems. 1. I read that it is better to convert CE terrains to OBJ and re-import them in CE and export them as models for performances reasons. However, how can I ensure the georeferencing of these OBJ files? The centering does not seem to work (I have multiple terrains because of the size of the scene). 2. Is there any other way to gain performance during the export? I read about setting proxies for trees (I have points features that are modelled as realistic trees) and re-export to the same LumenRT scene (hence splitting the issue), but these seems to be developped more for SketchUp and I couldn't use them. Thank you in advance, Best regards Natan
... View more
06-28-2018
08:56 AM
|
1
|
0
|
563
|
POST
|
Thank you for your answer! I was working on CE 2015.1, which apparently does not have this option. I checked in an instance of CE 2016.1 and I found it. Thank you for your help and best regards, Natan
... View more
02-05-2017
11:49 PM
|
0
|
0
|
637
|
POST
|
Hello, I am trying to automate a workflow where I import data from different file geodatabase in CityEngine and export the generated models. For that I am writing some python scripts, exploiting the CE() functions. The geodatabases have various feature classes in them, and I would like to select which one(s) to import as one can do in the GUI but with python, e.g. with some parameter in the FGDBImportSettings. However, in the available commands I can't find the appropriate parameter to set the names of the feature classes to import. How can it be done? Thank you in advance! Best regards, Natan
... View more
02-02-2017
05:12 AM
|
0
|
2
|
1615
|
POST
|
Ok, thank you very much for your answer! Best wishes
... View more
01-15-2017
11:49 PM
|
0
|
2
|
747
|
POST
|
Thank you very much for your answer, Scott. Strange to hear that Lumen works for 2016.0 but not with 2016.1. I will check with our support to see how to proceed. Best regards, Natan
... View more
01-12-2017
06:01 AM
|
0
|
0
|
445
|
POST
|
Hello, I would like to know if the direct model export from CityEngine 2016.x to LumenRT 2015 is compatible and working as it is from CityEngine 2015.1 to LumenRT 2015. We would like to update our CityEngine version to 2016, but we don't want to lose the awesome possibility to export models directly to LumenRT 2015. Thank you in advance and best wishes Natan
... View more
01-12-2017
02:54 AM
|
0
|
4
|
1910
|
POST
|
Hello everyone, I take the occasion to ask a quick question in this thread, since it is related, but I couldn't get the answer from your discussion. Can anyone please tell me if CityEngine 2016.x can export directly to LumenRT 2015 as CityEngine 2015.1 does or LumenRT 2016 is necessary? Thank you in advance, Best wishes Natan
... View more
01-12-2017
02:40 AM
|
0
|
2
|
445
|
POST
|
Thank you for your answer. My input does have Z value (it is either a polygonZ or a multipatch and I see it in 3D in arcscene), but Dissolve still provides 2D polygons nonetheless, and this despite in the environment settings the Z values being enabled. It seems unable to dissolve touching objects in 3D and goes back to their footprints in 2D. I apologize, but I do not quite understand the second part of your answer. What conditions do you refer to? In my case it does not really matter how geometry are solved at these crossing since the differences are really minimal, what's important is to avoid overlaps of different objects. The data are not unioned (yet), every segment in the 3D polyline is an object, but the network is contiguous (vertex are snapped) and I do have quite some attribute in addition to the street width (e.g. a street class attribute). I still haven't made any progress, I failed at using Difference 3D to solve the problem. Any thoughts / hint? Thank you again Natan
... View more
01-10-2017
03:01 AM
|
0
|
0
|
1945
|
POST
|
Hello everyone, I am looking for a way to "dissolve" touching 3D data without losing the Z information, is that possible? My input data can either be multipatch or polygonZ. Any workaround would help, and avoiding to obtain a single feature in the output would be a great plus. Briefly, what I have is a street network as 3D polyline, with a field indicating the width of every street. I used 3D symbology to create a strip of the right width, and used "3D layer to feature class" to obtain a multipatch. However, this operation naturally cause overlaps at road crossings, which are a) not nice, and b) causing many issues when I process my data further (e.g. flickering "fighting" polygons). I could obtain both multipatch and polygonZ, and extrude the data to ensure touching volumes, but I was not able to eliminate the overlaps. 3D intersect extract all of them, but I don't know how to proceed without losing the 3D information. I also have bridges, hence I really need something that works in 3D for close features. The desired output would looks as in Multipatch_width.jpg (where we do not see the overlaps, but they are there unfortunately). Any help would be greatly appreciated! Thank you in advance, Best wishes Natan
... View more
01-09-2017
08:16 AM
|
0
|
4
|
3458
|
Title | Kudos | Posted |
---|---|---|
2 | 05-01-2019 05:35 AM | |
1 | 06-28-2018 08:56 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|