-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Unity environment freezing on launch #13
Comments
The small window is expected as it's set in the scene to train at that window size (128x72). Likely to make performance better while it's crunching the PPO. I have noticed on my system that it seems to freeze, while still actually crunching away. Check Tensorflow to see if it continues to update, also Jupyter updates the mean reward below the training code chunk as it progresses. Also, if it turns out to be resource related, maybe remove some of those balls/platforms from the scene and then rebuild. Overall, this demo is pretty intensive and I'm guessing that watching the game window while it's crunching probably isn't feasible unless you're on a decent rig (I have 8GB RAM I7 and still can barely watch the game window during this specific PPO), but even then watching it is just wasting resources :/ |
Same problem but am able to launch Unity Environments successfully by launching the python scripts directly. Following the wiki Balance Balls walkthrough, launching the environments from the Basics or PPO Jupyter Notebooks, Unity Environment will launch, display the Built by Unity logo and then hang with a black screen. Mono path[0] = 'C:/Documents/Unity/ml-agents/python/test2_Data/Managed'
Input initialized. Initialized touch support. UnloadTime: 1.216441 ms Once you force quit the program, the log is filled with cascading socket exceptions: SocketException: An established connection was aborted by the software in your host machine. I was able to successfully launch the environment running the python script directly with "python ppo.py <env_name> --train". |
Thanks for trying this out, everyone. It is indeed the case that running in a small window, and low frame-rate are expected behavior. This is in order to allow the game to run at 100x speed, and provide as much training data as possible. If this is creating issues on your device, I would recommend trying to decrease the The black screen hang that you are experiencing @JZito might be due to the environment not resetting yet. Try running a block of code in |
Hmm. I slowed down the time scale to 5 for debugging purpose, and I could see it going. But after a second or two the pixels on screen stopped moving and it froze. I was watching it in jupyter notebook, and it was showing new rewards until the freeze, at which point it stopped. Which leads me to think this is an actual crash, and not just unresponsive UI. (For reference, I'm running this on a 64-bit i5 4595, without CUDA/gpu support for the time being) |
Nevermind, I'm an idiot, I needed to increase the number of episodes. Thanks for your help! |
Glad you were able to get things working! |
@awjuliani Can you please tell me how to reduce the time scale ? |
Hi, |
Hi there, |
Hi all. To have the simulation proceeds from python, you must call |
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. |
I've got to the point that I can successfully launch the 3D ball example. However, when I run the jupyter notebook file and the app starts automatically, it starts a tiny window and then freezes, and has to be process killed (see image below). Jupyter notebook doesn't show any errors, so I'm not entirely sure what's up. Any ideas as to how to fix this?
Thank you!
The text was updated successfully, but these errors were encountered: