Yogesh Khedar

If a particular mavlink command is unsupported, does PX4 send an error about command not being supported? At least with APM i get this error thrown in the MAVSDK logs...

I would prefer the 1st option since that would allow us to be not waiting for the EOL of PX4 1.10 for which we probably don't have a timeline yet....

> Using the old one first seems less ambiguous: PX4 v1.10+ supports it, and when support is dropped in newer versions of PX4 we can make PX4 return "UNSUPPORTED", just...

Allright, i did a rough implementation of the "try old message first and fallback to new message" idea.

Further broken APIs discovered through running Integration Tests with APM-SITL: - Action ```c++ - takeoff // Results in Error: command unsupported (21). (mavlink_commands.cpp:187) - land // Results in Error: command...

Upon further digging into the source of the plugin, i found that the following function/option give the functionality i am seeking. [Bake Option](https://github.com/sideeffects/HoudiniEngineForUnreal-v2/blob/655a7054323e12e3e7170140936c5f99cf87519b/Source/HoudiniEngineEditor/Private/HoudiniEngineBakeUtils.cpp#L550) Am I right about this and if...

I have tried the following options until now: 1. unreal_split_instances: Added this as a detail attribute. This creates Split Instancers but when I bake to actors, I see only these...

Hi @dpernuit , Thanks for your tip. I was able to get this to work by using the Pack node before merge node. The names of all these meshes so...

I also tried using the "unreal_output_name" and it changes the name of the meshes in the Houdini Outputs dialog but not in the World Outliner.

I required the calculation of Heat Flux on Wall Function meshes for my Studienarbeit last year and found none already implemented in OF. So I wrote one using the formulation...