Reassigning Pause not working

[pdavit]

Friends,

 

I'm using a Microsoft Arc Keyboard that seems not to have a Pause button.

 

So I enter FC2 control configuration and change Pause to key P.

 

When the game start and prompts to press Pause it seems that letter P is not assigned and I cannot start the game.

 

No other key seems to work also for Pause.

 

How can I resolve this? I cannot start playing FC2.

 

Thank you.

[mvsgas]

Make sure that "P" is not being use on another function. IIRC, "P" is normally used for drag chute. In the game it might be assign to both. Try changing one of them to control+P, see if that works.

Normally the games warn you if you got a key assign to something else.

[pdavit]

Make sure that "P" is not being use on another function. IIRC, "P" is normally used for drag chute. In the game it might be assign to both. Try changing one of them to control+P, see if that works.

Normally the games warn you if you got a key assign to something else.

 

Yes, that was what I thought initially was the problem of my reassignment and I did actually attempted to setup Ctrl+P without success also. :-(

[ivanwfr]

maybe useful info: Pause == Break

[EtherealN]

Unfortunately ivanwfr, that keyboard does not have the button.

 

[ivanwfr]

Yea, I was looking for technical details from MS ... wrong idea -- I mean technical is irrelevant here ;) -- at last, found a mistake I didn't do!

 

Here is the -- not simple -- solution : http://www.autohotkey.com/

Edited May 22, 2011 by ivanwfr
Autohotkey

[pdavit]

Yea, I was looking for technical details from MS ... wrong idea -- I mean technical is irrelevant here ;) -- at last, found a mistake I didn't do!

 

Here is the -- not simple -- solution : http://www.autohotkey.com/

 

What simpler than reassigning another key? Now the topic is why this doesn't work also. It seems that FC2 forces to use only the Pause/Break button even if you have changed this. :-(

[ivanwfr]

It looks like FC2, and DCS A-10C as well, do not listen to keyboard events. Instead, they sense each key state the same way they do for DX Input switches and in this case, AutoHotkey won't help... Now, you're looking for a real keyboard ;)

[EtherealN]

No, changing key should work. MacBook Pro's don't have that key either and everyone I know that uses them have no issue reassigning, so there should be something else in play here.

[pdavit]

No, changing key should work. MacBook Pro's don't have that key either and everyone I know that uses them have no issue reassigning, so there should be something else in play here.

 

Installed latest patch but still no success. :-(

[pdavit]

I opened an official support ticket for this issue. Below is the reply I received:

 

There are several possible solutions:

 

1. If you are running NewView, this is probably the source of the problem. You need to either Alt-Tab out and back into the sim or rename the NewView folder prior to starting the sim.

 

2. If you have Windows Vista or 7 and have installed an earlier version of StarForce (eg. 3.x), it may be the cause. Please try removing old StarForce drivers with SFREMOVE utility (item "Versions before 5.5"): http://www.star-force.com/support/drivers/

 

3. Reset keyboard settings. Navigate to <FC2_installation>\Config\Input\Aircrafts\A-10C\keyboard\ and delete or move away file Keyboard.lua. Then repeat for other aircrafts.

 

4. Reinstall sim from scratch into empty folder (notice that uninstallation leaves settings intact and they should be removed manually).

 

 

None of the solutions above have helped though. I haven't tried option 4 since this was a fresh installation already.

 

Option 1: I'm running the game in full screen mode. I tried to Alt-Tab without solving my problem. I tried also to set the game in Window mode and this didn't help either. Support team has also instructed to rename the NewView folder. Where is this folder located and rename it to what is not mentioned and I have asked for further clarifications.

 

Option 2: Yes, I'm running Win7 Ultimate 64bit with SP1 installed. When I run the removal utility I got a message that no driver is installed.

 

Option 3: Deleted all keyboard.lua files from all aircraft folders without any luck also.

 

I'm stuck to the cockpit screen all the time with the message to press Pause/Break and no key reassignment is also accepted by the game.

 

This bug must be fixed in a future patch. Maybe an easy workaround for the developers could be to choose another default key for pausing other than the Break key. And maybe key reassignment should work as well too. ;-)

[ivanwfr]

You can also try a G700 programmable mouse button.

[pdavit]

You can also try a G700 programmable mouse button.

 

I'm not going to be buying new hardware for every software bug out there that's for sure.

 

If this is not addressed by the developers my game will have to be returned unfortunately.

[cichlidfan]

I'm not going to be buying new hardware for every software bug out there that's for sure.

 

If this is not addressed by the developers my game will have to be returned unfortunately.

 

I did not have a handy installation of Lock-on to test but since I do have the ARC keyboard, rarely use it though. I went ahead and tested it with DCS A-10 and was able to reassign Pause to the Backspace key. Worked just fine.

 

There are so many similarities between FC2 and other DCS titles I thought it was worth trying since not everybody has one of those keyboards lying around.:huh:

[pdavit]

I did not have a handy installation of Lock-on to test but since I do have the ARC keyboard, rarely use it though. I went ahead and tested it with DCS A-10 and was able to reassign Pause to the Backspace key. Worked just fine.

 

There are so many similarities between FC2 and other DCS titles I thought it was worth trying since not everybody has one of those keyboards lying around.:huh:

 

The reassignment "works" at least it's visible inside the controls configuration. It seems this is not reflected inside the game though.

 

I will give a try to Backspace as well when back home.

 

But of course if other factors like the OS installed or drivers etc take part in this then our reproduction conditions are different (letting aside a different game even though by the same developers and same architecture).

 

Anyhow, I will keep attempting since this game is great. I've read in another forum that someone with a similar issue resolved this by editing manually the default keyboard file. It looked as if FC2 enforced to use the default one instead of the used defined one.

 

The quest goes on!...

[cichlidfan]

I did that on an ASUS G60 laptop, Nvidia 360m, Win7-64 Pro. If I have time today I will try it on another machine, Win 7 Home Premium, that does have a vanilla install of LockOn FC2.

[pdavit]

I did that on an ASUS G60 laptop, Nvidia 360m, Win7-64 Pro. If I have time today I will try it on another machine, Win 7 Home Premium, that does have a vanilla install of LockOn FC2.

 

I'll be waiting for your findings since Backspace didn't work either. There's no issue with the keyboard since the radio communication menus do appear when I press the corresponding button.

[cichlidfan]

I'll be waiting for your findings since Backspace didn't work either. There's no issue with the keyboard since the radio communication menus do appear when I press the corresponding button.

 

OK.:cry:

 

I have found the root of the problem. I did not dig into the entire file structure but the basic problem is that there are multiple keyboard profiles. DCS A-10 is the same way but there is only game or sim mode. If you set a key under the A-10 menu and then fly a mission for a different plane your changes will not be there.

 

To do what you wish to do you need to modify the pause key for every single configuration.

 

When you are in the Option>Controls window there is a pulldown that says Aircraft next to it. That pulldown contains ten options (each plane plus Free Camera). Each of these selections maintains its own keyboard.lua (did not look for where). You will need to modify Pause for each and every one of the pulldown selections one at a time.

 

I did not test this to completion but if I mod the Pause under Free Camera and then start an A-10 mission I get exactly what you did. However, I did have a second keyboard connected that allowed me to confirm that the original Pause key still worked. Once I modified the Pause for the A-10 selection in the pulldown everything worked just fine.

 

This should hold true regardless of OS or any other variables...if the game installs and runs that is.:thumbup:

 

Hope this gets you going. I may have to give FC 2 a spin. I have never played it before aside from making sure the install functioned.

 

Somebody in tech support owes me a nickel!!!

[pdavit]

Somebody in tech support owes me a nickel!!!

 

Certainly!!! ;-)

 

Your resolution sounds correct and I'll check that when back home and report here.

 

I did notice different keyboard files (per aircraft type plus a default and user defined files inside the game's folders), and there was also a step by the support team I included in a previous post that instructed me to remove the user defined one but I never noticed that the controls panel had this option also. It only makes sense otherwise having a global configuration couldn't have resulted in different keyboard files. ;-)

 

Thank you so much for this...

[cichlidfan]

Certainly!!! ;-)

 

Your resolution sounds correct and I'll check that when back home and report here

 

It was not that big of a deal once I saw how much FC2 looked like DCS A-10.

 

As I said before, I had never played it (don't ask why it was installed) and I haven't played Black Shark either (have that one too though). DCS A-10, on the other hand, I have been messing with for two months solid one way or another.

 

Your problem, or almost the same thing, happened to people with A-10 as well. It has a Sim Mode or Game Mode choice in the pulldown I described (only one plane but the controls are a bit different in each mode). Change one, play the other...no workee, change one and play that one and all is good. Once I saw that the Controls screen looked just like A-10 I knew what the problem was likely to be.

 

Oh, almost forgot. The Backspace key is used by the A-10 configuration, Target Unlock, I think it was. You may have noticed that when you are in the screen that lets you enter the new key definition, the bottom line will show you what function is already assigned to the key you entered, if there is one. You can still accept and it will make the change and clear the entry for whatever was using the key before.

 

If you decide to start making other changes to the configuration I would strongly suggest saving the new config under a new filename. It will still alway use it but if you need to reinstall you can back them up and keep track of them, especially if you start monkeying with the files for several planes.

 

The same issues will affect joystick, mouse, etc...if you did not notice there are files for each of those as well. You have to save them individually also if you modify the defaults.

 

If you have not looked at it yet, in the <install dir>\Docs directory is a GUI pdf. It has some info on these screens. I did not read it word for word but it appears to cover the subject to some extent.

[pdavit]

We had a success cichlidfan!

 

You are an ace (of the sky or otherwise) :-P

 

Thanx a lot once more!

 

Problem solved.

[cichlidfan]

Cool, have fun!

[Decay]

Yep I'm with you on this one.

except i edited my Wingmancommands.lus file before this started happening.

I've reassigned the pause function to another keuy in all planes.

rebooted still no joy.

[Decay]

Okay Here's my Problem and solution:

I needed to reassigne my radio commands keys see: http://www.lockonfiles.com/index.php/topic/36285-change-radio-commands-keys/

and ended up finding what I needed in:

C:\Program Files (x86)\Eagle Dynamics\LockOn Flaming Cliffs 2\Scripts\Input

WingmenComandPlane.lua

(change F1 to Num1 etc)

But I hadn't checked whether any of the Num1 -Num. had been used in the:

C:\Program Files (x86)\Eagle Dynamics\LockOn Flaming Cliffs 2\Config\Input\Aircrafts\su-25\keyboard

keyboard LUA.

 

Because there was a conflict (in my case Num. assigned where F12 used to be clashing with some of the Padlock views). The game stopped recognising anything but in particular Pause Break.

Simple? - Mental

 

To fix - I went in-game to clear the "Num. " assignments so that nothing would conflict with my edited WingmanCommandsPlane.lua

 

Thanks to everyone who has posted accurate information on this.

 

All the best, - Dave Decay

[Decay]

OKAY HERE'S ANOTHER FIX !!!

 

IN:eg for the SU-25

C:\Program Files (x86)\Eagle Dynamics\LockOn Flaming Cliffs 2\Config\Input\Aircrafts\su-25\keyboard

There is the file keyboard.lua that you are editing when you change keyboard commands in the options page in-game.

This does NOT have the Radio Commands, but you need to know this file, because you will have to check for conflicts later.

 

The file to change the RADIO COMMANDS is in:

C:\Program Files (x86)\Eagle Dynamics\LockOn Flaming Cliffs 2\Scripts\Input

and it's called: WingmenCommandPlane.lua

 

I used Notepad++ to find F1 - F12 and replace those keys to the Num1 - Num0 (F11=Space and F12-Num.)

 

BUT THEN: My game would not get past the "Pause/Break to start" and even though I reassigned the Pause Key in-game it still was not working.

WHAT I FOUND: The "Num." key that I had assigned in WingmenCommand.Plane.lua was conflicting with the default assignments for "Num." that the game was getting from the keyboard.lua in the above directory. I went in-game and cleared the remaining "Num." assignments.

 

The game runs, and I have the RADIO COMMANDS assigned where I need them for my configuration.

 

Super Happy About that one.

Hope this helps others who hate the F1 - F12 thing.

 

Dave Decay

 

"If a job's worth doing - it's worth half doing twice". - Homer Simpson.