You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a bit of background, the servers that communicate between Python and Unity were updated, and this allows all actions to run substantially faster, which is often a preferred trade-off.
But, it is of course useful to view and debug the current frame, so here are a few ways to do that:
Execute a dummy event, that will update the Unity window's frame:
c.step('Pass')
View the Event's image frame in a Python interactive environment with Python's Imaging Library (PIL):
# setup controllerfromai2thor.controllerimportControllerc=Controller()
event=c.step('MoveAhead')
# visualize frame with PILfromPILimportImageImage.fromarray(event.frame)
Plot the image with matplotlib and have it open up in a new window (depending on your environment):
mattdeitke
changed the title
Images from the Unity window lag by 1-step in versions >= 2.4.23
Images from the Unity window lag by 1 step in versions >= 2.4.23
Dec 8, 2020
mattdeitke
changed the title
Images from the Unity window lag by 1 step in versions >= 2.4.23
Images from the Unity window lag by 1 step in versions >= 2.5.0
Dec 8, 2020
When opening a controller and running:
the Unity window that opens in the background is always 1-step behind the action!
However, when viewing the actual returned image from the event, it is up to date:
The text was updated successfully, but these errors were encountered: