Latest Contributions by LR

It's not hard, you just i(nsert) the OBJ. Look here: i Operation  ... View more

Make a bridge rule for one of the buildings and move it into place. Here's a simple example: Lot --> Building Bridge Building --> primitiveCube(50, 50, 50) Bridge --> primitiveCube(10, 10, 20) t(0,10,35)‍‍‍‍‍‍‍‍‍ ... View more

You should be able to fill the gap by extruding the faces of the arc upwards, with a flat top. So extrude(world.up.flatTop, archeight). Haven't tested it, though. You might have to fiddle with the scope. ... View more

Maybe a more thorough uninstall with a deinstaller software (like Revo) would help, who knows what files are left behind. When reinstalling, point CE to fresh folders (install directory + workspace). Does a single-use licence require a licence administrator? Perhaps that's the actual culprit. ... View more

Try changing the workspace. If that fixes it, it's most likely there's something's wrong with either of the .lib folders and/or perhaps those starting with a dot too. Move them elsewhere, CE will create new ones on startup. ... View more

To my knowledge this won't be possible with CGA alone. CGA only goes in one direction, and you'd have to return to a previous state. You can call a previous rule, but it'll be applied to the current state. You have to re-run the rule until the area condition is met. Remove the recursion and run the script until the object is generated. Don't forget to update the seed, or you'll always get the same "random" numbers. You can either do it manually (ugh) or automatically with Python (using reporting to export a variable to check in a loop). ... View more

I don't think you can. What are you trying to do? You can more or less store a shape with Python (getVertices and getAttribute), if that helps. ... View more

You could store attributes in variables, like this: set(initialArea, geometry.area) ... View more

A little update: the second problem fixed itself somehow. Changing the shape is being recognized by the buildings without having to reopen the scene. I can't quite tell how it fixed itself, not even power cycling the machine changed anything before. The first problem persists, however - at least when I update the seed and generate. See attached project. I left some screenshots in the image folder as well. The initial ground shapes were made with CE (rectangle, then subdivided). Everything else is rule-driven. Options were left at default. CLau-esristaff wrote: -> This is because we do not want the default set to be influenced by any other scenario.  For example, we do not want scenario 1 to influence the default shapes.  If this were the case, then, when you look at scenario 2, you would see default shapes that were influenced by scenario 1, and this is not good.  We want each scenario to be independent of the other scenarios, and we want the default shapes to be the same in each scenario.  The default objects should not change depending on what scenario you are looking at. Understandable, but this prevents scenarios that show in what ways different setups would impact the default shapes. I guess they'd have to be instanced for every scenario in that case, though. ... View more

Occlusion query has always been janky at best but I think it's plain broken in 2017.0. As far as I can tell, it only triggers once per scene "session". Try moving your building, save/close the scene and open it again. See also my thread here, which unfortunately went unaddressed: https://community.esri.com/thread/198001-inconsistent-and-non-updating-occlusion-query-results-ce-20170  ... View more

LumenRT might be worth looking into if you have the funds. Unfortunately ever since its acquisition by Bentley, its price dectupled. Also a small hint: the CE screenshot function isn't limited by your screen resolution, you can for example make 4k screenshots on a 1080p monitor. ... View more