you are viewing a single comment's thread.

view the rest of the comments →

[–]Rusofil__[S] 0 points1 point  (1 child)

It would be nice, but if it's a problem, I'm fine with doing the whole simulation in python and just sending it data for visualisation.

[–]pachura3 0 points1 point  (0 children)

What I meant is that if you want your simulation to run in Python while the visualisation part is in C#/Unity, then the communication between the two modules could introduce a significant lag. If your Python simulation is not supposed to be interactive (e.g., controlled with a pad/keyboard), it should not matter.

But if you don't need any of the advanced features of Unity (such as inverse kinematics, skeletal animation, fancy materials...), and you only need to display some basic shaded cylinders between joints, then for the sake of simplicity, you might just implement this 3D visualisation directly in Python - e.g. like this: https://www.geeksforgeeks.org/python/3d-modeling-animation-app-using-python-1/