I have already generated a USD file from SketchUp. Based on a pre-generated example (tokyo.usd), I can replace the CAD layer and edit a USD file which works fine in the USD Composer. However, it cannot be directly used in AODT due to some missing attribute errors:
2024-07-17 14:31:52 [Error] [aerial_sim.configuration.utils] Couldn’t get ‘points’ attribute from
2024-07-17 14:31:52 [Error] [aerial_sim.configuration.worker_manager] [4dee81b8-3f2d-0193-c95c-cc85516193f0] Couldn’t get ‘points’ attribute from
2024-07-17 14:31:52 [Error] [aerial_sim.configuration.utils] Worker failed to open
2024-07-17 14:31:52 [Error] [aerial_sim.configuration.utils]
2024-07-17 14:31:52 [Error] [aerial_sim.configuration.utils] omniverse://public_ip/Users/aerial/plateau/ED8F_v2.usd
As an alternative, I generated a CityGML file from SketchUp and then converted it to a USD file using the Scene Importer (aodt_gis). However, this approach seems somewhat redundant.
Is there any tool to edit or verify the USD file for the AODT project?
@junxian , did your approach of generating CityGML and converting to USD work for you? We understand that it might be redundant, so can you please elaborate on your use case?
Thank you for your reply. The USD file generated from CityGML can be opened in AODT. However, it still has some minor issues, which I have reported in another topic.
In our use case, we hope to apply AODT in an indoor space. As a result, we need to generate the indoor floorplan with 3D CAD models, which can be easily exported to a USD file. Based on my understanding, CityGML is designed for outdoor and city-level CAD models, which is not suitable for our use case.
I think you can try the example of the user guide with the Tokyo CityGML first (Scene Importer - NVIDIA Docs), and make sure the USD can be generated successfully first. I have met a similiar problem when I use a wrong CAD model.
@junxian I met the same problem following user guide.
I was wondering whether you have ever met the error as Resource deadlock avoided
[ERROR] Failed connection, exiting.
terminate called after throwing an instance of 'std::system_error'
what(): Resource deadlock avoided
Aborted (core dumped)
I encountered a core dumped error while attempting to generate a USD file using a self-generated GML file (from CityJSON). I believe the issue may be due to an incorrect format in the GML file, as the error does not occur when using the Tokyo GML files provided in the user guide.
@junxian Hi, I was wondering for aodt_gis, besides the input and output paths, any other settings need to be specified for generating from my gml file?
If the GML files are compatible with AODT_GIS, I believe specifying the input and output paths should be sufficient. However, we’ve encountered an issue where the output USD file needs to be based on the template.usd file; otherwise, the resulting USD will not include the necessary AODT parameters.
We’ve also attempted to modify parameters like EPSG and scaling, but we still don’t have a clear understanding of how these affect the outcome. If you have any relevant testing results or insights, please also share with us. Thank you.
@junxian Sorry for the late reply. Yes, we also discovered that the aodt_gis requires template.usd for the scenario, which leads to the design of scene files requiring cityGML format. Besides, we encountered the issue that the UE mobility zone is constrained to mobility domain.
Could you please show me how to generates a CityGML file from SketchUp?
We consult the co-worker and are told that SU cannot export the cityGML format
