Eike
Eike
Unfortunately not, but I thought about your point: The lib is loaded while creating the handle: `checkCudaErrors(cublasCreate_v2(cublasHandle));` So it might be that the issue is not in loading the lib...
Seems as if it is initializing - but I think it is not the loading of jni but loading the loading of cuda-11.4-8.2-1.5.6-linux-arm64-redist.jar ``` Debug: Loading /home/ecm/.javacpp/cache/cuda-11.4-8.2-1.5.6-linux-arm64.jar/org/bytedeco/cuda/linux-arm64/libjnicublas.so Loading: 48ms elapsed...
Update: Removing cuda-11.4-8.2-1.5.6-linux-arm64-redist.jar from the class path solved the issue. The handle now is created in 1600ms, which is ok when performed on startup.
@dagar: I use jMAVSim just for quick and basic functional tests of [MAVCGL](https://github.com/ecmnet/MAVGCL) or the companion software (e.g. trajectory generation w. offboard) - usually without visualization. For more sophisticated tests,...
Same experience here. Reason: Max data length in ImagePubSubType.java is set to 100 bytes.