VREP randomly cannot find remoteApiCommandServer.lua or any related .so libraries
Re: VREP randomly cannot find remoteApiCommandServer.lua or any related .so libraries
It does not crash overnight but as I mentioned before this alternative connection method is unreliable and causes other problems for running parallel instances.
Re: VREP randomly cannot find remoteApiCommandServer.lua or any related .so libraries
Sorry, forgot that you already tried that option.
I have uploaded a new version of the legacy remote API plugin here. Can you try with that one? Make sure to set value of useAlternateSocketRoutines to false again in file remoteApiConnections.txt
Cheers
I have uploaded a new version of the legacy remote API plugin here. Can you try with that one? Make sure to set value of useAlternateSocketRoutines to false again in file remoteApiConnections.txt
Cheers
Re: VREP randomly cannot find remoteApiCommandServer.lua or any related .so libraries
Thanks for the patch,
I've been running with new version of the legacy remote api plugin. It has failed to connect as before, but I want to perform more tests before I say for certain.
If I set useAlternateSocketRoutines to true, does that have exactly the same behaviour as the unupdated plugin?
Thanks
I've been running with new version of the legacy remote api plugin. It has failed to connect as before, but I want to perform more tests before I say for certain.
If I set useAlternateSocketRoutines to true, does that have exactly the same behaviour as the unupdated plugin?
Thanks
Re: VREP randomly cannot find remoteApiCommandServer.lua or any related .so libraries
That's strange. Here it works with the new version of the plugin. The only thing that was changed is to correctly close sockets when disconnecting (thus not causing the memory leak).
Make sure that useAlternateSocketRoutines is false with the new plugin (otherwise it behaves as the old plugin, when useAlternateSocketRoutines is true).
Cheers
Make sure that useAlternateSocketRoutines is false with the new plugin (otherwise it behaves as the old plugin, when useAlternateSocketRoutines is true).
Cheers