Currently it is not possible to save generated geometry. For some applications it might make sense to "cook" (save the generated geometry) the VitruvioActors so that they don't have to be procedurally generated anymore (eg before relasing a packaged build where no interaction with the VitruvioActor is necssary). This could save performance in such cases and also allow for proper collision mesh setup.

Tasks:

• Add additional context menu entry to "Cook Vitruvio Actors"
• This should generate static mesh for the generated geometry as well as instances
• Also consider instance and material reusing
• Add option to also immediatly replace the procedural VitruvioActors with the cooked geometry
  • Maybe it would also make sense to support the reverse (eg convert the cooked geometry back to a procedural VitruvioActor). This would require to store the attributes which were used for generation to be stored somehow

I am not able to see vitruvio component drop-down list, everything else ios coming except this drop-down folder where it has all the attributes

Hello,

When I try to package the game for windows I get the following error, is this error known to you and do you know how I can fix this?
UATHelper: Packaging (Windows): ERROR: Expecting to find a type to be declared in a module rules named 'Vitruvio' in UE5Rules, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null. This type must derive from the 'ModuleRules' type defined by Unreal Build Tool. PackagingResults: Error: Expecting to find a type to be declared in a module rules named 'Vitruvio' in UE5Rules, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null. This type must derive from the 'ModuleRules' type defined by Unreal Build Tool.

When I add the Vitruvio plugin to the plugin folder of the project I get the following error upon creating the package:

PackagingResults: Error: System.ArgumentException: An item with the same key has already been added. Key: Vitruvio

The description of Vitruvio says "..for the generation of procedural buildings in the Unreal Editor or at runtime". I've seen examples of how to export from CityEngine to the Unreal Editor using Datasmith, but I haven't been able to find any examples of how to generate a city at runtime (outside the editor, after the game has been built). I'm assuming this is what is meant by "runtime"? I've seen the Python & C++ plugins so I'm assuming it has something to do with that? The jupyter notebooks with pyprt seem close - import the rule package and then generate the 3D building / tree / city.
https://github.com/Esri/pyprt-examples/blob/master/ex7_building_modeling_optimization.ipynb
This example does it in the web:
https://www.esri.com/arcgis-blog/products/city-engine/3d-gis/converting-3d-geometry-formats-made-simple-using-pyprt/
But I haven't seen an example of doing it within an Unreal game.

Specifically, I want to be able to do everything in code - so have a rule package file and then use that plus user input in the game to generate a tree or building or entire city dynamically (rather than pre-built). Is this possible and if so, is there a tutorial for the code to do this? Thanks!

Currently the name of the HierarchicalInstanceComponents looks like this.

Tasks:

• Use the actual instance name as the Component name (eg. FlightHelmetInstanceComponent)

Hi, when the UE5.3 version will be released?

Currently holes are not handled correctly when using a static mesh (with holes) as an initial shape.

Tasks:

• Improve static mesh to initial shape conversion algorithm to also detect holes
• Properly pass initial shape (with hole information) to PRT

Currently reimporting an RPK asset does not work (for example dragging an RPK which already exists into the content browser). If an updated RPK is needed the user has to import it with a different name and update all the references.

Tasks:

• Support reimporting Assets (via drag and drop or context menu)
  • The VitruvioComponents should automatically replace the RPK reference
  • The attributes should be kept

Currently only scalar attributes from PRT are supported.

Tasks:

• Add support for loading array attributes from PRT
• Implement details customization which supports array types

I know it just came out but i really need motion matching and this plugin at the same time.

Currently it is not possible to export initial shapes from CityEngine together with attributes. This could be useful if buildings should be generated exactly as they were in CityEngine. Currently we always use the default attributes which results possibly in a different generation.

Tasks

• Support initial shape attribute
  • There might be different ways this could be solved
  • Use Datasmith together with "Asset Metadata"
  • Use Shapefiles (would also preserve edge ordering which is not possible with Datasmith)

Hi,
I can import RPK file, but it's not procedurally generating the city.
RPK exported with CGA from CityEngine 2019.
I'm on the Paris Base project.

Can be some clarifications about the procedure?

Currently if there is an error during generation (eg mismatching CGA versions) zhe errors are only displayed in the log. This can be a bit confusing as some users might not have the log open by default.

Tasks

• If an error happens during generation, display a popup (same as "Generating models ...") with a text notifying the user that an error occurred during generation and a link to the log for more information

Currently all UV sets are encoded from PRT which can lead to issues as Unreal only supports 7 UV sets at most and CGA materials potentially can have up to 10. Also the default Vitruvio material currently only uses the first UV set.

Tasks:

• Limit the number of UV sets from PRT by excluding unnecessary UV sets (candidates are bump-map, specular-map and dirt-map uvs)
• Add support for multiple UV sets to the default Vitruvio material (currently only the first UV set is used in the material)

Tasks

• Update the build system to download/install PRT 2.4
• Fix issues regarding USD encoder
• Adapt to any API changes

Unpacking RPKs can take a long time currently. As we only need images from the RPK in Unreal we can read them through PRT directly from the RPK instead. This would also solve our issue that we can not load TIF images from Unreal.

Tasks:

• Load images from RPK through PRT
  • This would most likely also help us to get rid of the workaround for the "number of image channel detection" we currently use

It would be great if static meshes keep their scaling when they are converted to vitruvio actor using the context menu.
Right now the shape is generated for the mesh at (1,1,1) scale even if the static mesh had a different scale before conversion. The issue is that the if the CGA rule generates different shapes based on the size of the footprint, the generated geometry will not have the right shape. Scaling the vitruvio actor doesn't solve the problem as it only scales the generated geometry but doesn't recreate it.

It can happen that the generated building is upside down, when applying a RPK to a concave shape and changing from static mesh to splines for further processing.

Tasks:

• Compute the polygon orientation using a more sophisticated algorithm (There might already be something implemented in Unreal like for example in PolygonTriangulation::ComputePolygonPlane)
• Use the orientation to properly order the vertices of the polygon

Improvement

Currently any change to a VitruvioActor cannot be reversed. This functionality would be very helpful when accidentally breaking anything and trying to get back to its initial stage.

Currently we do caching at various places (RPKs, Materials, Textures). Each cache is implemented in a similar way to support async access etc. We could extract some code into a base cache structure and reuse it for all cases.

Tasks:

• Check what code is shared between the caches
• Extract shared code

If a rule without "generated geometry" (for example only an insert eg R --> i("someModel.fbx")) is run, or the generation result is empty because the generation did not run through (eg because there was an error during generation because of mismatching CGA versions) Vitruvio crashes.

I get an unexpected error on v 1.4 when I try to extract it. I DL'd 1.3 and several of the other packages with no issues, and I turned my AV off. Seems like it must be something specific in 1.4.

This is not the only file that throws the error. Let me know if you need more info.

Thanks!

EDIT: I was able to DL the source and compile it with the prompt. No luck on the packaged file though.

Currently material values > 1 are not working correctly. Eg. CGA code with

set(material.color.r, 1.5)
set(material.emissive.g, 50)

don't work properly.

Tasks:

• Make sure that the color attributes are clamped properly
• Support values > 1 for other color attributes (eg. emissive > 50)

Can we expect a release of of Vitruvio that supports Unreal Engine 5?

Echoing a question that was put in UE Marketplace here.

Thanks!

Currently attributes are not sorted according to their order (metadata from PRT attribute annotations).

Tasks:

• Correctly order the attributes in the Vitruvio details panel (see also https://github.com/Esri/serlio/blob/master/src/serlio/modifiers/RuleAttributes.cpp#L146)