Sensors return only zeros about pyrosim

[abernatskiy]

The current version of the Python interface returns all zeros whenever the data from the simulator binary does not reach it. Since you report that simulator performs as it should, there are two possibilities - either the binary crashes at the last time step or there is some kind of communication error. Communication error is more likely, because Python versions handle subprocesses in a slightly different ways and the code has not been thoroughly debugged to run on all versions in the same way. Which version runs on which machine? Start by ensuring that the machine on which the code fails runs the same version of Python as the one on which it works well.

[Alobal123]

So I tried it on all the versions of python I have installed and did not make any difference.
I have python 3.6.5 on both machines and one works and one does not.

[ccappelle]

It is probably an issue with some of the hard-coded constraints in the C++ code. One common one is the length of the directory path is too long. Because drawstuff (ODE's simple rendering library) needs the path to the textures and this is stored in a char array with a hard coded length. However it could be something else so I suggest setting the debug parameter to true when you initialize the simulator.

sim = pyrosim.Simulator(debug=True)

This should give a clearer picture of what is failing.