POST
|
Hi Erwin long time no see : ) I recommend to experiment with the following functionalities: Menu -> Graph -> Fit Widths to Shapes (calculates the width of segments so that they touch the lots nearby. Assigning the street rules in the Esri.lib to dynamic shapes (=from segments). This shows the texture coordinate possibilities. In the Inspector, you can click on the small icon left to the entry field of each parameter/attribute to link values to attributes from other layers. Once done, select the layer in the Scene Editor, and then look at the Inspector. There you can see the code for linking the attribute. If needed, you could change this code (e.g. for formulas etc)... Hope that helps Pascal
... View more
03-20-2015
03:28 AM
|
1
|
0
|
222
|
POST
|
Sounds like a workspace problem (that I have not yet heard of). Maybe try this: Rename the folder .CityEngine (in your home directory) as well as your workspace folder (CityEngine?) Start CE (it should ask to create a new workspace, do it) Start the CityWizard afterwards. Export the models >>> please let me know if this works If so, import your project from the old renamed workspace folder Open your scene and try to export again >>> please let me know if this works Our apologies for the caused troubles. PS: On what OS are you?
... View more
12-18-2014
02:25 PM
|
0
|
0
|
734
|
POST
|
Hello You can export all models (buildings, streets etc) into one Collada file. However the terrain is exported trough another route. Therefore you will need two separate exports (the WebScene Exporter is the only exporter that combines terrain and models). With the Python interface in CE Advanced you also could script the exports. We have not tested our Collada export on the Collada importer of Lumion3D. Theoretically that should be no problem, but Collada is famous for its incompatibilities... Please let us know if you encounter any issues. Best P
... View more
09-05-2014
07:58 AM
|
0
|
4
|
693
|
POST
|
Hi Ben Do you get the message when importing data in an new/empty scene? Thanks P
... View more
09-05-2014
07:47 AM
|
0
|
1
|
1226
|
POST
|
As mentioned below, you cannot hide specific attributes. However what you can do, is to export only the reports without the attributes. To do this, set the export parameter "Metadata" to "Reports" instead of "All". You can do this per layer.
... View more
09-05-2014
07:21 AM
|
1
|
1
|
1293
|
POST
|
Apologies for the late response. Unfortunately there will be no new CityEngine VUE (for evil administrative reasons), means VUE users need to continue to purchase CityEngine Basic via Esri. However, our friends from E-On will soon release something amazing in regards to CE (hint: LumenRT - Home) Best Pascal
... View more
08-21-2014
11:09 AM
|
0
|
0
|
471
|
POST
|
This depends very much on the rules and use cases. Some ideas: One thing to try is using the innerRect operation or inserting (and component splitting) a builtin:cube in case you work rectangular shapes. Then work with the index. Or in case you know the direction (but not the index) you could scale it into the wanted direction (to make it long), apply the roofGable operation and scale it back. Means s('10,'1,'1) roofGable(angle,overhangX*10,overhangY) s('0.1,'1,'1).
... View more
08-21-2014
10:50 AM
|
0
|
0
|
397
|
POST
|
Hi Dennis Unfortunately, we cannot comment on release dates. To solve your problem now, I would fix the dae file in the KML. Simplest solution might be via a text editor looking for the transparency parameters and changing them. Best Pascal
... View more
08-21-2014
10:10 AM
|
0
|
0
|
723
|
POST
|
select two layers, then "merge layers" via right-mouse button menu or as an alternative, you can also select the object in the viewport, then press ctrl-x (cut), select the layer in the scene editor and press ctrl-c (copy). Means you can use copy-cut-paste to move objects between layers.
... View more
08-21-2014
10:03 AM
|
0
|
0
|
301
|
POST
|
Hi Nathan The problem is that the roofGable tries to be smart and creates the cable along the longest side. We are aware of this problem. However there is already a solution that works in some use cases: You can use the full-fledge roofGable operation: roofGable(angle, overhangX, overhangY, even, index) The last parameter index defines to which edge the ridge should be parallel. Thus, as long as the edge indexes stay constant in your models, this solution will work. I hope this helps. Best Pascal
... View more
08-21-2014
09:56 AM
|
0
|
2
|
397
|
POST
|
Hi Joe Yes, VOB is still supported (and the format will get even more love in the near future). Best Pascal
... View more
08-13-2014
08:10 AM
|
0
|
2
|
471
|
POST
|
Hello Petr Thanks for the response. I try to summarize: Currently, CE uses the existing/nearest settings when you draw/split a new block - if this is not the case, then it would be a bug. However, you do not like this "smart" behavior and would prefer that each new block has always the same default parameters, correct? If so, I'd recommend to make a small Python script that takes the selected block and sets your preferred values. You can attach the scripts in the GUI in the menu bar. Kind regards Pascal
... View more
08-12-2014
08:22 AM
|
1
|
2
|
856
|
POST
|
Hi Petr Impressive setup. Which version of CE are you using? Thanks Pascal
... View more
08-10-2014
09:32 AM
|
0
|
4
|
856
|
Title | Kudos | Posted |
---|---|---|
1 | 08-12-2014 08:22 AM | |
1 | 03-20-2015 03:28 AM | |
1 | 09-05-2014 07:21 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|