Siyi Li
Siyi Li
@GoingMyWay I also met this problem with boost 1.65. After I switched back to boost 1.58, the problem disappeared.
@GoingMyWay I installed from source, but it's on a remote centos server. I didn't notice your case is on OS X. But I guess on OS X you can also...
It seems that this is a bug in the previous version, based on my testing results on VizDoom 1.1.1 (Ubuntu 16.04) and VizDoom 1.1.0 (Windows 10). I also noticed that...
I also encountered this problem. How did you fix this? @OrangePear