search

Unity-Technologies / ml-agents

The Unity Machine Learning Agents Toolkit (ML-Agents) is an open-source project that enables games and simulations to serve as environments for training intelligent agents using deep reinforcement learning and imitation learning.
https://unity.com/products/machine-learning-agents
Other
17.19k stars 4.16k forks source link

Error: No Learning Brains set to train found in the Unity Environment - No Brain Type options #1546

Closed dza6549 closed 5 years ago

dza6549 commented 5 years ago

Hi there Win10 - Unity 2018.3.0f2 - ml-agents 0.6

Trying to work through getting-started.ipynb Notebook but get the following error:

INFO:mlagents.envs:
'Ball3DAcademy' started successfully!
Unity Academy name: Ball3DAcademy
        Number of Brains: 1
        Number of Training Brains : 0
        Reset Parameters :

Unity brain name: 3DBallLearning
        Number of Visual Observations (per agent): 0
        Vector Observation space size (per agent): 8
        Number of stacked Vector Observation: 1
        Vector Action space type: continuous
        Vector Action space size (per agent): [2]
        Vector Action descriptions: , 
WARNING:mlagents.envs: No Learning Brains set to train found in the Unity Environment. You will not be able to pass actions to your agent(s).

I see that I cannot change the Brain type to External. In fact I have no options to change Brain type at all - maybe similar to this problem (bug?) like https://github.com/Unity-Technologies/ml-agents/issues/1436

Please let me know if I can provide more info.

nobraintype

dza6549 commented 5 years ago

My fault! Did not have Control ticked in Academy script. Cheers

yangbo commented 4 years ago

My fault! Did not have Control ticked in Academy script. Cheers

Can you show how to tick the Control in Academy script? Thanks.

chriselion commented 4 years ago

@yangbo That checkbox no longer exists since version 0.11.0. Can you please open a new issue explaining your problem?

github-actions[bot] commented 3 years ago

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.