32 replies to this topic

[jeannot]

Wumpus, on 02 April 2012 - 05:44 AM, said:

You are justifiably annoyed, but for the time being you'll have to jump hoops to play the game until something can be done about this. I'm going to ask Edwin next time I see him online and see what he says.

I don't think the fullscreen mode is going to change. This is the recommended mode since Snow Leopard. It allows cmd-tab and facilitate the use of non-native resolution. I, for one, like that fullscreen mode since it doesn't disable mission control (mapped to a function key). Maybe Feral could add an option to disable mission control in the startup dialog, if that can indeed be done via a simple script.

[Eric5h5]

jeannot, on 03 April 2012 - 03:15 AM, said:

This is the recommended mode since Snow Leopard. It allows cmd-tab and facilitate the use of non-native resolution.

Um...the previous full-screen mode in Snow Leopard works fine with cmd-tab and any particular resolution.  I was just playing an older Feral game last week (I'm on 10.6.8) with the "correct", non-annoying full-screen mode, and there weren't any issues.

--Eric

[edddeduck]

Wumpus, on 02 April 2012 - 05:44 AM, said:

You are justifiably annoyed, but for the time being you'll have to jump hoops to play the game until something can be done about this. I'm going to ask Edwin next time I see him online and see what he says.

We had to update our windowing code for Lion/AppStore and the result is we have a few annoyances for some peoples setup as our window mode now can be effected by spaces etc. We are looking at solutions but the solutions have to be officially sanctioned Apple don't like it if we start using undocumented or private API's in AppStore titles.

In other news, people with Nvidia cards and BioShock 2 might want to install this driver update from Nvidia.

It contains updated graphics drivers for Nvidia cards that will speed up many games and applications. If you have an Nvidia card and want a bit more performance in games I would give these drivers a whirl.

Edwin

[edddeduck]

Janichsan, on 02 April 2012 - 05:00 AM, said:

Sorry, but "simply do this" or "simply do that" simply won't do. I don't see why I should jump through hoops because some programmer chose to integrate some fundamental design flaws.

Maybe it's just me but making assumptions like "some programmer chose to integrate some fundamental design flaws" is flawed as you are basing it on absolutely no evidence. Perhaps they still exist because of something else? Like rules on how you have to do things in the AppStore and not being able to override OS functions or use private APIs?

Using AppleScript / AppleEvents is unlikely to be allowed (the solution provided in the thread) as sandboxing (in Mountain Lion) prevents applications from being able to use AppleScript or AppleEvents as this is a security issue so is banned. This also means features like iChat status, iTunes pausing etc might also have to be removed as they also rely on AppleEvents to work. This is all in flux but hopefully will show this is a lot more complex than your rant about "fundamental design flaws". Remember for every hour you play a Feral game we likely play for 10 hours at the very least so if it annoying for you then think about us...

And no before you ask I can't give any more details but we do see your issue (and find it annoying ourselves) and we are looking at solutions but there needs to be a way to do this and respect all Apple's rules. When we find it we will implement it you can be sure of that!

Edwin

[the Battle Cat]

Send me to Apple.  I will bang some heads together and even bring you back a T-shirt.

[edddeduck]

the Battle Cat, on 11 April 2012 - 10:09 AM, said:

Send me to Apple.  I will bang some heads together and even bring you back a T-shirt.

Reminds me of a student version of myself, lots of beer, the Apple campus WWDC drinks party, the head of Quicktime and some forceful points made about codec support.

Ah to be young and fearless

Edwin

[Janichsan]

edddeduck, on 11 April 2012 - 05:01 AM, said:

We had to update our windowing code for Lion/AppStore and the result is we have a few annoyances for some peoples setup as our window mode now can be effected by spaces etc.

WTF – seriously? Does Apple enforce this crap arbitrarily?* I have a couple of games from the MAS that don't even support cmd+tab (e.g. Limbo or Galaxy on Fire 2).

(* I don't expect you to be able to answer that rather rhetorical question – unless you know how Apple decides...)

Quote

We are looking at solutions but the solutions have to be officially sanctioned Apple don't like it if we start using undocumented or private API's in AppStore titles.

Just out of curiosity: what's wrong with the fully documented kiosk mode?

edddeduck, on 11 April 2012 - 05:15 AM, said:

Maybe it's just me but making assumptions like "some programmer chose to integrate some fundamental design flaws" is flawed as you are basing it on absolutely no evidence.

That changes were to put the blame, but not that this integration of a fullscreen mode is fundamentally flawed.

[Eric5h5]

edddeduck, on 11 April 2012 - 05:15 AM, said:

This also means features like iChat status, iTunes pausing etc might also have to be removed as they also rely on AppleEvents to work.

It sounds like Apple distribution is becoming too restrictive, and that it's probably time to make a separate version for the App Store.  No sense making things worse for everyone just because of one distribution channel, even if it is an important one.  I suspect that maintaining a separate version is not high up on your list of "things I really wanna do", but submitting to the App Store requires separate work anyway, and other companies have done this with even bigger changes (like Aspyr's App Store version of Civ IV).

--Eric

[edddeduck]

Janichsan, on 11 April 2012 - 11:29 AM, said:

Just out of curiosity: what's wrong with the fully documented kiosk mode?

That is a really good suggestion, thank you for making it. Feel free to PM me more if you have any I am not sure if we can use it as the option to disable some of the expose settings also disables CMD + Tab which is a more popular feature than hot corners etc. I also see the documentation written in 2009 and never updated... Always a good sign

Cheers!

Edwin

[Janichsan]

edddeduck, on 12 April 2012 - 03:21 AM, said:

That is a really good suggestion, thank you for making it.

Not bad for someone who utterly failed to produce anything workable with Xcode, eh?

[Smoke_Tetsu]

Last time I tried Bioshock 2 multiplayer cmd+tab was disabled and that was a pain because there's no in-game chat that I know of.

[edddeduck]

Janichsan, on 12 April 2012 - 03:56 AM, said:

Not bad for someone who utterly failed to produce anything workable with Xcode, eh?

Sadly it looks like Kiosk mode is not very useful for our goals. You can disable Expose (mission control is not mentioned as the documentation is very old now) but it means you also have to ban cmd+tab which is a popular feature. I think this is likely why our dev team have not used it in the past as we get more flack for the lack of cmd+tab (see below) than we do for 3 and 4 mouse button uses.

Smoke_Tetsu, on 12 April 2012 - 04:09 AM, said:

Last time I tried Bioshock 2 multiplayer cmd+tab was disabled and that was a pain because there's no in-game chat that I know of.

Command Tab is disabled due to tabbing out in GameRanger games will automatically quit the application. This is a GameRanger "feature".
For approval reasons we had to ban cmd+tab in the MP to avoid that situation.

In game chat for now has to be run through a third party system.

Edwin

[Wumpus]

I have to say I'd definitely rather have cmd-tab and deal with hot corners. I use that feature all the time and I hate it when games don't have it.