Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: Azoele on April 28, 2008, 08:19:53 am
-
My quest has not ended yet to play FS2 under the mac :rolleyes:
Everything is smooth... but for the keyboard: at first, I couldn't understand why some in game functions didn't work, and I later realized (by trying to bind keys to functions) that my MacbookPro keyboard is seen in the strangest way by FS2Open.
First, all the numbers aren't recognized as such (only key 3 is seen, but as a ' .1,2,4,5,6,7,8,9,0 don't get grabbed by FS2. After that,the question mark, ì and backspace work.
Plus, the keyboard is also seen as azerty, while it's a italian qwerty (this could be minor, but the fact that the numbers in the top row don't work makes playing almost impossible. Without issuing orders to the wingmen or calling support many missions become incredibly difficoult or unbalanced. I get a communications window opened, and then nothing! ;)
Is there any way I can explain FS2Open what kind of keyboard I have?
Thanks a lot :(
(the tear is there because my friends living with me have been getting sound laughters after me and my "Gosh, they helped me! I can finally play FS2!" and then realizing the next problem... :)
Lory
-
I answer myself.
It seems Freespace here hits some sort of a bug with SDL, which was encountered also by the people of ScummVM.
I am unfamiliar with the exact problem (it seems that SDL reports the wrong keypresses; with an Azerty keyboard it needs a Shift+keys on the top row to get a number; on other keyboards the numbers are simply accessible, and to type symbols like % & / you need to Shift+5,+6,+7)
The solution implies turning the keyboard into a French numerical keyboard in System Preferences.
I added a new layout from the preferences, choosing (by chance... :) French Azerty numerical, and there it goes, Freespace now "sees" the numbers and allows me to use communications.
:)
Lory
-
I've seen a few people report this problem in BtRL. I'll pass this info on next time someone asks.
-
I talked too early... :confused:
It worked just once. It's not working anymore. Incredible as it may seem, Freespace ignores the keyboard setting. Again.
It is very frustrating...
Anyone with a new idea?!
-
Hi, All!
My keyboard does not work at all.
Only F1, F2 and Ctrl wokred.
I'm unable to enter callsign.
If using callsign created on PC and transferred to Mac then I can login but unable to control ship but only fire primary weapon.
Need help!!!
-
This sounds like a Mac specific bug. Try using a 3.6.10 build (if any are available) and see what happens.
-
I'm tried latest build available for Mac. Some Mac-specific problems gone (including right and bottom borders freeze) but keyboard still malfunction.
-
As a person not so familiar with Macs I can't offer any assistance. But it might help those who could, if you provided some specifications on your Mac.
-
Hi i'm noob in Freespace 2 community, and i'm having problem with in-game comm !
I'm having the same issue with my french apple keyboard and my mac.
I would like to know if someone finds a solution. I try to use FSOpen 3.6.9 and 3.6.10 with my keyboard setup as a french numeric and USA numeric.
Can someone help me ?
-
same problem here... but with 10.4 it was all fine >(
-
Yeah I forgot to mention, I use Leopard ^^
I google this issue and found nothing. Not even a clue :confused: !
Help us please
Edit : Is there a way to edit the keyboard layout in a config file ? i didn't find anything related to this ?
-
but, did you try with some other games? I noticed that I have the same problem with AA and Quake 4
-
Since these problems only concern Macs (and seemingly only Leopard), it probably wouldn't hurt to direct a complaint or two at Apple's direction. Or if some coders here know what to do, knock yourselves out.
-
but, did you try with some other games? I noticed that I have the same problem with AA and Quake 4
I notice the problem with Starcraft too, I'm not realy a gamer :p
[...]Or if some coders here know what to do[...]
You mean try to edit directly the FSOpen code ?
-
:nervous: Yes?
But again. People using Leopard encounter the issue. With other games as well. Feedback to Apple would not be wrong.
-
I so want to go back to Tiger :(
Anyway... for me it's fixed now. I bought my laptop in UK (so, with English keyboard) but I had the system in my language. I put also the system in British English and now it works fine. (I didn't had this problem with Tiger anyway).
I hope it helps.