Open andytriboletti opened 5 days ago
Well I have two things to say here.
1- Where does this script originate from? AFAIK that's not how things work, or I have missed some greater code changes, since I haven't been active for a while.
You cannot simply throw random data against the server and then hope for the best. If you want to know what should be in the JSON data, take a look at plugins/1_mhapi/JsonCall.py and plugins/8_server_socket. The xxxops.py files show the available functions (aka commands in your code).
2- The issue in the application is that arbitrary JSON data leads to a KeyError and a consecutive SIGABRT (on my system), shutting down the application, probably because the code is running async. This absolutely should not happen and is a serious bug. On the other hand the intention of the code is mainly to communicate with Blender over localhost by our plugins. Chances a rare it will ever see unexpected JSON data, except it is used outside its intended specifications. Therefore the issue has low priority.
The script is from a combination of claude, chatgpt, gemini. I want to use makehuman from a game so I am using socket. Could you provide sample code documenting makehuman socket code in the readme?
On Sat, Jun 29, 2024, 12:23 PM Aranuvir @.***> wrote:
Well I have two things to say here.
1- Where does this script originate from? AFAIK that's not how things work, or I have missed some greater code changes, since I haven't been active for a while.
You cannot simply throw random data against the server and then hope for the best. If you want to know what should be in the JSON data, take a look at plugins/1_mhapi/JsonCall.py and plugins/8_server_socket. The xxxops.py files show the available functions (aka commands in your code).
2- The issue in the application is that arbitrary JSON data leads to a KeyError and a consecutive SIGABRT (on my system), shutting down the application, probably because the code is running async. This absolutely should not happen and is a serious bug. On the other hand the intention of the code is mainly to communicate with Blender over localhost by our plugins. Chances a rare it will ever see unexpected JSON data, except it is used outside its intended specifications. Therefore the issue has low priority.
— Reply to this email directly, view it on GitHub https://github.com/makehumancommunity/makehuman/issues/246#issuecomment-2198251528, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAATIBBVDVLIPFBZL6FDD4TZJ3NO3AVCNFSM6AAAAABKCKJSCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGI2TCNJSHA . You are receiving this because you authored the thread.Message ID: @.***>
afaik it is not a documented open API. Why did neither chatgpt, nor claude, nor gemini mention it?
And yes, each socket works like this. The secret is in export_command which might be 3 lines or 3000 lines. When it becomes interesting, AI usually starts to create a lot of fantasy XD
To use the API:
check the commands in 8_server_socket ... it will be like 3000 lines ... meshops.py will get meshes, or proxies, skeleton etc. Furthermore you need to understand the meaning of positions, UV coordinates, proxies ... and when all that will work, we might change the socket because WE need a different functionality.
A non-documented API for internal purposes is not really meant for this.
An open API or one just calling the file-exporter we don't have. Btw.: mhx2 is also an internal format which is only known to blender + makehuman.
And it will not be implemented in the old version.
At least it could be an idea for the new one, which unfortunately needs some time to be usable ;)
In that case, I guess I should add both, a remote trigger to export a file via e.g. gltf + a classical open API, where people need to understand the complete logic.
Thank you for answering, I appreciate it.
I downloaded the windows app and synchronized the database. Then I ran a python script to connect to the server.