Open garfieldnate opened 1 year ago
Okay, it turns out that I had not set up the x86 version of Python on my machine correctly. When an ARM64 Python calls executables, they run in ARM64 mode, and ai2thor is only available in x86_64.
Now that I have Python set up correctly, the scene renders. The Unity window is unresponsive and the cursor is always the beachball of death, but I can still control it from Python.
So there are two issues here, which ideally would be fixed but a note in the documentation about known issues/constraints would also be helpful:
The Unity window is also unresponsive in Ubuntu. Have you solved it?
@Penguin963 The window is unresponsive on all platforms, and I've learned to live with it 🤷 You can control what happens inside of it using the API, so it is usable. The unresponsiveness just makes it a bit clumsier to work with (mostly focus issues).
I installed ai2thor with
pip3 install ai2thor
. Then I ran the example from https://ai2thor.allenai.org/ithor/documentation/initialization:The console showed me that the ai2thor binaries and assets were downloaded:
However, when I created the
Controller
instance, the Unity window that is opened is blank and completely unresponsive (frozen, with the cursor being the beachball of death):I thought it was curious that the downloaded zip said
OSXIntel64
, considering I'm using an ARM64, but switching to X86_64 emulation mode did not fix the issue. Downgrading ai2thor from 5.0.0 to 4.3.0 did not fix the issue either.The really weird thing to me is that I can run the ai2thor application directly (not from Python):
The above command opens a responsive AI2Thor window: