tag:blogger.com,1999:blog-7582438520651320420.post4974639192293538868..comments2019-02-13T10:00:37.422-08:00Comments on Oculus Rift in Action: Setting up the Rift on a MacBook ProAlex Bentonhttp://www.blogger.com/profile/12907188510267549004noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7582438520651320420.post-43622243745543202262014-12-25T16:02:33.617-08:002014-12-25T16:02:33.617-08:00use Command F1 to switch between primary and exten...use Command F1 to switch between primary and extended<br /><br />use Command F to go full-screen or<br />Command M to minimize when it glitches!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7582438520651320420.post-84225190494621302522013-12-10T14:06:01.817-08:002013-12-10T14:06:01.817-08:00I concur that for development purposes, windowed m...I concur that for development purposes, windowed modes are the way to go. It likely imposes a performance penalty but it's way less of a pain to access the debugger. Of course another alternative for more pro shops or those with higher budgets is remote debugging, but that's anything but trivial.Bradley Austin Davishttps://www.blogger.com/profile/16387001483589908239noreply@blogger.comtag:blogger.com,1999:blog-7582438520651320420.post-31814705589029612862013-12-10T11:45:47.607-08:002013-12-10T11:45:47.607-08:00I've found that mirrored and extended are each...I've found that mirrored and extended are each a pain for their own reasons. :) One alternate approach you might try is to mirror and run your Rift app in windowed mode. It might not be performance optimal, but you can simply maximize the window and it works well enough in the Rift(for me anyway, YMMV). This way it's much quicker to switch over to other apps(like your IDE) without incurring a lengthy mode switch.Anonymousnoreply@blogger.com