Problem with "F" keys

[zacklaws]

I have a problem with the "F" keys which I cannot resolve, the only one that seems to work correct is F1 for the cockpit. Pressing F2 makes the aircraft become very unstable which is a problem I have had for a while even in DCS A10 but only found out today that it was linked to pressing F2, F3 appears to do nothing, but combined with the left CTRL it speeds up time very rapidly, F6 will give me a rear external view of the aircraft and not weapon view, F10 I get just a ground view of units which I can toggle through but I cannot get a map, and F11, jettisons all stores. I have deleted my Save games directory, but the problem still keeps coming back. I have looked through the key bindings but they are all listed to do what they are supposed to do and no conflicts with anything else. All the other F keys do not seem to do anything with views but I suspect that they also alter something in the cockpit as sometimes I hear a click.

 

I am using the A-10C module (v. 1.2) installed into DCS: World program and no earlier versions installed.

 

I'm now finding that when I try to increase the frequency using the VHF AM 10mhz selector switch by use of the mouse, I'm getting map view, but when I press F1 to get back into the cockpit, the frequency has increased as well. Decreasing the frequency by this switch is as it should be with no side effects. This problem did not exist this morning.

 

Looks like its time to delete the saved games folder again......and again......and again........but it does not solve the problem

Edited August 15, 2012 by zacklaws

[Sarge55]

Could you be using a non-standard keyboard or perhaps a different language keyboard? If you have an english version of DCS but using a german keyboard that maybe the issue.

[EtherealN]

DxDiag might help here, but the main thing of interest, like Sarge says, is to know exactly which keyboard we are talking about here. (DxDiag might also help shed som light on possible conflicts and driver issues though.)

[Corrigan]

It almost sounds like you have a modifier applied. Do other hotkeys work?

[zacklaws]

Its a UK keyboard, with UK language. As for other hotkeys, they all seem to work, those that I have tried that is, most times I select things with the mouse.

 

As for modifiers, I have not tinkered with these as I do not know the foggiest about them.

 

What I might do is completley uninstall, clean the registery etc and remove any traces of DCS world from the hard drive etc and reinstall and go from there

[zacklaws]

I have now cleared the save game folder two more times and no change to the game

 

Completley unistalled DCS world and the A10 module, deleted every trace of both on my hard drive and cleaned my registery, rebooted and cleaned again, rebooted

 

Reinstalled DCS World and got an error message saying that my system has a newer version of Microsoft Visual C++ than the one it is trying to install and cannot continue. So why will it run on a newer version?

 

Cancelled installation and unistalled what had installed.

 

Uninstalled every version of Visuall C++ on my hard drive.

 

Reinstalled DCS World and A10 module with no errors along with its chosen version of Visual C++.

 

Opened up DCS World and ran it, and guess what, it still does not work and keybinds etc flawed and I still have all the same problems, for example, open up the radio menu, press F1 for Wingman, select F2 and the aircraft becomes wildly uncontrollable, press F3 and the problem becomes worse as time is speeded up but no way of reversing it, untill I crash.

 

In 25 years of flight simming, I have never come across a game as bugged and flawed as this one in which I cannot resolve the problems in it or find any answers. I am spending more time getting frustrated with DCS World than enjoying it and am not far off putting my fist through the monitor with my high stress levels. The game itself is excellent but because of the complexity of it, it is just ruined by all these problems with it and to me now, just not worth bothering with and a complete waste of money.

 

I only have to look through the user download files, eg, missions etc and by the lack of them, it is obvious that there has to be a big thumbs down throughout the flight sim fraternity towards this game.

 

Anyway I feel better for that rant now as I have spent all morning trying to get it to work and still no closer apart from getting stressed out with it.

 

Will try it again later when I calm down.

Edited August 17, 2012 by zacklaws

[zacklaws]

Time for a bit of shouting, I think I'm allowed.....HALLELUYA.....HALLELUYA.

 

I've resolved the problem.

 

My keyboard is a Microsoft Digital Pro Keyboard and I have just found that for the keyboard to work properly, I must have the "F LOCK" key engaged. So Anyone else with similar problems with a fancy keyboard, engage the

"F LOCK" key

 

Funny though that I do not have to engage "F Lock" for any other games that use the "F" keys thinking about it now

 

And this is the best game since sliced bread, very enjoyable and well worth the money for the entertainment, but sadly totally the opposite if its not working.

 

Now I just have to figure out the workings of the GBU 38. I always get a direct hit on the bridge in instant action, but I cannot plink a static tank with the second GBU 38. As the GBU always hits exactly the same point every time I try it, I presume it is hitting the steerpoint and not what the TGP is looking at and locked on. I can confirm this by changing steerpoints and watching the release data alter with each change, so that tells me its aiming at the steerpoint and not linked to the TGP. But anyway I shall not digress anyfurther as this is the wrong forum to discuss such.

[Sarge55]

Lol... I just checked my keyboard and low and behold I have an "F" lock key as well.

 

It must be set to "on" in the BIOS like the num lock key because I do not recall ever having to hit it.

[AceKng1]

Now I just have to figure out the workings of the GBU 38. I always get a direct hit on the bridge in instant action, but I cannot plink a static tank with the second GBU 38. As the GBU always hits exactly the same point every time I try it, I presume it is hitting the steerpoint and not what the TGP is looking at and locked on. I can confirm this by changing steerpoints and watching the release data alter with each change, so that tells me its aiming at the steerpoint and not linked to the TGP. But anyway I shall not digress anyfurther as this is the wrong forum to discuss such.

 

GBUs will target your current SPI. Unless you have manually set a SPI, your current SPI will be your target waypoint. To manually set a SPI, use TMS up long. For example: when your TGP is set as your sensor of interest you can use TMS up long to set your SPI as whatever your TGP is targetting. To reset your SPI to your current waypoint, use TMS down long.

[zacklaws]

GBUs will target your current SPI. Unless you have manually set a SPI, your current SPI will be your target waypoint. To manually set a SPI, use TMS up long. For example: when your TGP is set as your sensor of interest you can use TMS up long to set your SPI as whatever your TGP is targetting. To reset your SPI to your current waypoint, use TMS down long.

Oddly enough, that is what I do, but I will look into it further in case something else is amiss, I would sooner my procedures are wrong than having to put up with my keyboard not working giving dodgy commands, but now every thing is sorted, I can sit back and start enjoying the game