Doğan Ulus

Handling large networks would be very valuable for us, so I'm glad it's not an essential limitation. This fix is not urgent, but thank you so much for the fast...

A devcontainer with preinstalled dependencies might be better. Would you be interested in that instead? This is easier to recommend to users.

> It's better for users to learn about dependency management and install prerequisites themselves. As an educator, I fully agree with that statement. But containers is a great tool for...

For the version zenoh-c v0.10.1, I needed to install a specific Rust toolchain (`RUST_TOOLCHAIN=1.72.1-x86_64-unknown-linux-gnu`) to start working with the library. As a non-Rust developer, it took some time for me...

> This asset file must have the same name and be in the same folder as a 3D model file. Is it possible to have a relaxation regarding being the...

As a thought experiment, taking full liberty in implementation, given a catalog reference such that ``` ``` For example, I would search ``` ${ESMINI_ASSETS_PATH}/vehicles//.xoma ${ESMINI_ASSETS_PATH}/models//.osgb ``` I agree that this...

@ClemensLinnhoff can correct me if I am mistaken. I understand the OpenMaterial standard does not dictate 3D model formats, but it is said that three formats are officially supported/endorsed. I...

Yes, I think of a single model (blender) source, and then it is easy to export different formats (`.fbx` and `.gltf`) automatically using Blender API. I am already exporting `.fbx`...

Yes, the original Blender files will be compatible with the XOM. > But since current models are already prepared for rear axle origin, we need either change existing models or...

Here is an initial release that contains a single vehicle (Mini Countryman 2016): - OpenX Assets: https://github.com/bounverif/esmini-assets/releases Here is the current node hierarchy. Is that XOM-compliant? What are your suggestions?...