-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple Unity instances stops #4194
Comments
This isn't a valid combination of commandline parameters: you either need to omit We need to validate the arguments better and raise a clearer error message in this case. Note that |
Yes, it wasn't clear to me that I needed the executable from the training docs (I should've thought of it though).
I know, I only went the multiple instance way after the problems I was facing with multiple training areas as I noted in my post |
I logged the --num-envs bug as MLA-1145 in our internal tracker. If you're still having problems with multiple areas, can you post it on the ML-Agents forum (https://forum.unity.com/forums/ml-agents.453/) ? That's a better venue for that type of questions. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Unity environment worker stops almost immediately after running when using num-envs > 1.
Note:
Slightly unrelated issue, but I can't make a separate post about it since it only happens on my custom environment. When I created multiple training areas and start training, my agent won't move after pressing play. I am using a separate controller script instead of heuristics mode, and I can manually control with that. In my original scene with only one copy, the opposite is true: I can train but not manually control. When I press play the position moves, but it is not moving in editor and I can't control. Not sure why this is, but I suspect somehow it is still being controlled by ml-agents.
To Reproduce
Steps to reproduce the behavior:
mlagents-learn config/ppo/WallJump.yaml --run-id=WallJumper --num-envs=2
Console logs / stack traces
Environment:
The text was updated successfully, but these errors were encountered: