|
POST
|
To get Chris's exact file, you can download the attachment he attached. Here is the link to the same example for 2015.2: http://www.arcgis.com/home/item.html?id=4b928739ca7c4effa11ee29530419057 and for 2016.0: http://www.arcgis.com/home/item.html?id=f4011b7c5d86407c9737733371ca01a6 This example is also available through the download dialog within CityEngine (Help -> Download Tutorials and Examples).
... View more
07-05-2016
02:49 AM
|
0
|
0
|
1039
|
|
POST
|
I would suggest writing a rule to make the parking space lines. First, enable shape creation (Street Parameters in Inspector -> set shapeCreation = Enabled). Then, apply rule to Street shape that sets the line's color.
... View more
07-05-2016
02:25 AM
|
0
|
0
|
978
|
|
POST
|
Maybe you are looking for Shapes -> Convert Model to Shapes
... View more
07-05-2016
02:17 AM
|
0
|
4
|
3908
|
|
POST
|
CityEngine supports importing of data from a variety of different file types including OSM and GDB. Importing Data If you save your work in Maya as an OBJ, then you can import this into CityEngine as well. Maybe your other question is better suited for someone at the USGS.
... View more
06-07-2016
12:51 AM
|
0
|
0
|
1060
|
|
POST
|
Thanks for the suggestion. We will try to incorporate this into the next version of the help.
... View more
06-06-2016
04:36 AM
|
0
|
0
|
1571
|
|
POST
|
Yes, and to support Z R's answer, here's the reference page for scope.sx, scope.sy, and scope.sz: scope Shape Attribute
... View more
06-03-2016
04:43 AM
|
2
|
0
|
1571
|
|
POST
|
There is another option to use a 3D mouse to navigate smoothly in the CityEngine viewport and take a screen capture video. But, really, Thomas's suggestion to export your scene and do the animation in another software is the recommended workflow.
... View more
06-03-2016
04:36 AM
|
0
|
0
|
590
|
|
POST
|
Yes, you can insert the obj file using the i command first and then use the comp split to get the faces. The comp split reference page describes the vertical, aslant, and horizontal selectors with angle ranges and examples: Component Split Operation
... View more
05-31-2016
12:17 AM
|
0
|
0
|
1060
|
|
POST
|
The code looks fine. It looks like the attributes called end and path are linked to Object Attributes. This means that they are trying to get their values from the Object Attributes on the shape. The attribute gid is also linked and has the value 627334 which it got from the linked Object Attribute. The Object Attribute values for end and path are empty, so that's why they look empty in the screenshot. I think this might be why the texture are not found. To link these attributes (end and path) back to the rules, you can click on the icon with the square and black arrow and set them to rule attributes. You could also try to diagnose the problem by printing the texture file to the console before the texture call in the rules using print(path+"White_01_m"+end). Then, open the console (Window -> Show Console) to see the output.
... View more
05-30-2016
07:01 AM
|
0
|
0
|
890
|
|
POST
|
Is the texture file specified in the cga code or does it come from an object attribute on your shape? Could you please include the cga code that determines where to get the texture?
... View more
05-27-2016
03:06 AM
|
0
|
0
|
890
|
|
POST
|
I'm not sure I understand your questions, but here's a guess. Are you trying to import an object with multiple faces (like a building that has sides and a roof) and then apply a rule to it which distinguishes between the facades and roof? Yes, this can be done with a CGA rule. Check out the rule Esri.lib/rules/Buildings/Building_Mass_Texturizer.cga. In the Generate rule, a comp split on the faces is used to separate out the Facade faces (vertical faces) from the Roof faces (aslant and horizontal faces). comp(f){ vertical : Facade | aslant : RoofPlane | horizontal : RoofPlane } Are you wondering what files you can import into CityEngine? Here is a list: Importing Data
... View more
05-27-2016
02:55 AM
|
0
|
2
|
1060
|
|
POST
|
You can get and set the values of attributes in imported cga files if the attributes are user-set. ce.setAttribute(shape, '/ce/rule/X.h', 8) ce.setAttributeSource(shape, '/ce/rule/X.h', 'USER') print(ce.getAttribute(shape, '/ce/rule/X.h')) Just a note: I don't think there is a need to import the same cga file twice. You only have to import it once, then you can re-use the X.Lot rule. Lot --> split(x){~5:X.Lot|~5:X.Lot}
... View more
05-25-2016
01:41 AM
|
0
|
1
|
3998
|
|
POST
|
The street and intersection parameters cannot be changed through CGA rules. You cannot change the underlying shapes, but you can create models that don't have sidewalks, for example, by making the following rule: Sidewalk --> NIL. But, this is probably not what you want to do since it would be harder to deal with the minArcRadius in the rules. You can change some default settings used when drawing streets by going to Graph -> Street Creation Settings. You can set values for sidewalk widths, but unfortunately, the intersection parameters are missing, so you cannot set a value for minArcRadius. (We hope to improve this in the future.) To set the minArcRadius, you'll have to draw all of your streets first, select them all, and then manually set the value of minArcRadius to 0 in the Inspector. Or, you can use a Python script to set the values of sidewalkWidthLeft, sidewalkWidthRight, and minArcRadius for all of the streets in your scene. Here is some code that does this: # get graph segments and nodes segments = ce.getObjectsFrom(ce.scene, ce.isGraphSegment) nodes = ce.getObjectsFrom(ce.scene, ce.isGraphNode) # set sidewalk widths to 0 ce.setAttribute(segments, '/ce/street/sidewalkWidthLeft', 0) ce.setAttributeSource(segments, '/ce/street/sidewalkWidthLeft', 'USER') ce.setAttribute(segments, '/ce/street/sidewalkWidthRight', 0) ce.setAttributeSource(segments, '/ce/street/sidewalkWidthRight', 'USER') # set minArcRadius to 0 ce.setAttribute(nodes, '/ce/crossing/minArcRadius', 0) ce.setAttributeSource(nodes, '/ce/crossing/minArcRadius', 'USER')
... View more
05-24-2016
08:28 AM
|
2
|
0
|
1004
|
|
POST
|
There is an example that you can download from within CityEngine. Help -> Download Tutorials and Examples -> Example Zoning and Land Use.
... View more
05-24-2016
12:52 AM
|
0
|
0
|
452
|
|
POST
|
The Python ce.getVertices() method returns the vertices of the initial shape, the shape onto which the rule is applied. Thus, the vertices seen in the Inspector are the same vertices that are returned by this Python call. The CGA rule that is applied to this shape does not affect the vertices returned by this method. It seems like you want the vertices of the model created by a CGA rule. Unfortunately, this cannot be done in Python. Exporting the model would be a way to get the vertices.
... View more
05-23-2016
09:30 AM
|
2
|
0
|
754
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 12-14-2022 07:18 AM | |
| 1 | 06-22-2020 04:54 AM | |
| 1 | 02-17-2020 03:10 AM | |
| 1 | 07-03-2023 03:37 AM | |
| 1 | 06-07-2023 05:26 AM |
| Online Status |
Offline
|
| Date Last Visited |
10-19-2023
12:40 PM
|