Have you tested it on other games t se if it is ESO specific? There was a bug in 10.9.2 for second monitors linked in the other thread linked by @xhunter.
I have asked the question to development team and will post a response as and when I get one.
I posted an update to this on the other thread with more posts about this here.Have you tested it on other games t se if it is ESO specific? There was a bug in 10.9.2 for second monitors linked in the other thread linked by @xhunter.
I have asked the question to development team and will post a response as and when I get one.
It's not 10.9 or other games, this drop out of full screen is ESO, and was not in the last beta either.
I would like them to take over all displays, even if they only show black or some game related subtle textures on the un used displays.
CoolRickDangerous42 wrote: »As of 1.0.5 the fullscreen mode works PERFECTLY for me. AWESOME!
Isn't that what this is for? Controls > Key Bindings > Toggle In-Game Cursorchristerb16_ESO2 wrote: »With the revert, full screen behaviour is slightly better. For me, however, it's still unusable due to the fact that the game steals keyboard focus. I can see applications on other screens just fine and also so things like scrolling a browser window with the mouse wheel. Any keyboard input is sent to the game regardless of what I do.
This sort of makes the full screen mode unusable for me as I require the ability to type into applications outside of the game.
Isn't that what this is for? Controls > Key Bindings > Toggle In-Game Cursor
It's what I use the type in other apps etc.
In other games like WoW I believe it does the same and it's just the way Apple handle the multiple monitor behaviour. It is complicated by the fact that each OS X version does things differently. 10.7.x has real issues with multiple monitors from forums.RickDangerous42 wrote: »FWIW, I have the same behaviour as @christerb16_ESO2 but I don't really mind. Whenever I need to type outside ESO I switch fullscreen mode by using cmd-F, do the outside typing, and then cmd-F back. Current behaviour is at least better than the non-working one we had before.