Two small FC 2.0 issues

[Udat]

First: When I started customizing my x52pro profile, i ran into the following "porblem:" Lshift is unbindable on my joystick, so i had to manually change the keypresses for lots of radar commands, and I had to do it over for each flyable aircraft. Is there no way to change a keycommand for all planes at once? If not, could this perhaps be considered for a patch?

 

Second: The limited 6dof head movements is all good when using Tir, but when not, it offsets my cockpitview to the degree of hiding parts of my scope, tews, etc. Any way to make this work like it did in FC 1.12b with my head stationary in the position of my choosing?

 

Thanks in advance!

[EtherealN]

On 1, are you certain? In my profile Lshift shows up as "Shift" and Rshift shows up as "Right Shift", both work as expected.

 

On 2, that's not the 6DOF, that's "natural head movement". That's separate issues - one permitting you to move on purpose (with TIR or mouse/key binds) and the other automatically mimicking the movements your head would make uncousciously when turning. The latter can definitely be shut off, there's a thread somewhere here that I'll try to find for you.

 

EDIT

Here you go: http://forums.eagle.ru/showthread.php?t=51850&highlight=natural+head+movement

[Udat]

Ah, brilliant, thanks so much!

 

And I meant to say Rshift.. And yes I'm certain, my profiler would not let me bind it. I will try updating the SST and see if that helps.

[Udat]

Hmm, still no luck with the Rshift issue, after updating SST drivers. Lshift shows as "skift," not "shift" like for you Ethereal. Is that perchance indicating something about my keyboard or windows version/language? It's set to Norwegian after a friend fixed and formatted my computer.. Please, if anyone could help I'd be eternally greatfull, it's gonna be a huge pain having to change all those keycommands for all those planes every time I reinstall or patch the game :cry:

[Udat]

Desperate bump

[71st_Mastiff]

MMM what version of the game you have Russian? or English sounds like Russian. What patch you use Russian or English? if your keyboard is Norwegian I suggest you change it to English or Russian so you can have the right OS region as this game is only currently released in English and Russian. This would be your issue.

 

 

Hmm, still no luck with the Rshift issue, after updating SST drivers. Lshift shows as "skift," not "shift" like for you Ethereal. Is that perchance indicating something about my keyboard or windows version/language? It's set to Norwegian after a friend fixed and formatted my computer.. Please, if anyone could help I'd be eternally greatfull, it's gonna be a huge pain having to change all those keycommands for all those planes every time I reinstall or patch the game :cry:

Edited May 21, 2010 by Mastiff

[EtherealN]

Hmm, still no luck with the Rshift issue, after updating SST drivers. Lshift shows as "skift," not "shift" like for you Ethereal. Is that perchance indicating something about my keyboard or windows version/language? It's set to Norwegian after a friend fixed and formatted my computer.. Please, if anyone could help I'd be eternally greatfull, it's gonna be a huge pain having to change all those keycommands for all those planes every time I reinstall or patch the game :cry:

 

I should have been more specific: it Lshift does report as "Skift" for me too, I just anglophiled it and wrote as "shift" in here. (My keyboard is swedish, OS edition and language is english). One of the things that can be bit of a bother in this case is that some keys and commands will have other names than in the simulator - so when the simulator wants the semicolon ( ";" ) for something, I actually enter the "ö" key into the SST, since the important thing is which physical key is being pressed and transmitted, not the symbol written on it.

 

(Would be interesting to try make sense of a DVORAK keyboard in this situation...)

 

Udat, I'll move this to the helpdesk. Could you supply a DxDiag output file (see the troubleshooting thread in the helpdesk) just so I can be sure exactly what I'm looking at? A few screens from you working in the Profiler might be useful as well, if you can find and highlight the problems.

 

Mastiff, that does not sound like a russian version, and keyboard language as well as operating system language have absolutely nothing to do with this. Keyboard language specifically was not an issue even when the 1.0.1 patcher cared about region.

[71st_Mastiff]

I should have been more specific: it Lshift does report as "Skift" for me too, I just anglophiled it and wrote as "shift" in here. (My keyboard is swedish, OS edition and language is english). One of the things that can be bit of a bother in this case is that some keys and commands will have other names than in the simulator - so when the simulator wants the semicolon ( ";" ) for something, I actually enter the "ö" key into the SST, since the important thing is which physical key is being pressed and transmitted, not the symbol written on it.

 

(Would be interesting to try make sense of a DVORAK keyboard in this situation...)

 

does and considering its Microsoft I bet you it's an OS regional keyboard issue.

 

(Would be interesting to try make sense of a DVORAK keyboard in this situation...)

 

 

Mastiff, that does not sound like a russian version, and keyboard language as well as operating system language have absolutely nothing to do with this. Keyboard language specifically was not an issue even when the 1.0.1 patcher cared about region.

[EtherealN]

Mastiff, if it was then my computers would be affected. I repeat: what the keys are reported as ("Shift", "Skift", "LShift", "Left Shift", "Elvis Presley") in SST has absolutely no impact on their function in the simulator. It's still that physical key on the keyboard and it is transmitted to both OS and Game as that key, not as the paint applied on top of the key.

 

Want to test this?

Find slew commands, one of which is the semicolon ( ; ). On a standard english keyboard that key has the position that houses the "Ö" key on my keyboard. To write a semicolon I press Shift-comma. So we have two alternatives: to get the slew-up function, do I map it to my semicolon (Shift-comma) or to Ö? The answer is: Ö. The simulator does not care about the paint on the keyboard buttons, and it doesn't care about the language windows uses to interpret the signals from the keyboard, it only cares about which key was depressed - and once again I need to emphasize that we are talking about which physical key. Completely ignore the paint on the key.

 

Further, you should note that which language version you have of the game does not impact what the SST software reports a key as. How do you mean it looks like a wrong-version of the simulator when the key reports are from a completely different software package - namely Saitek's profiler software suite?

Edited May 21, 2010 by EtherealN

[Udat]

I'm using English version of both the game and the patch, 100% certain. The problem is that the SST software refuses to acknowledge the existance of Rshift; I press it but nothing registers in the appropriate field. I checked, and everything BUT Rshift registers.

 

Ok there is the Dxdiag and a few screens attached.

 

I'm not sure what I should take a screen of, so I took the first of how it is now (and was in 1.1x, the second of what it looks like after I program

Rshift+.

into the "radar antenna down" square, and the last one after I reprogrammed it to

Lshift+.

. Can't printscreen while inputting, it will register printscreen as a command..

DxDiag.txt

Edited May 22, 2010 by Udat

[EtherealN]

That's very peculiar. Could you open FC2, enter the options screen and find a command that does differentiate between the shifts. I'd suggest starting an F15, initiating your radar (I key), and then trying to flip it between the hi/med pulse modes (Rshift-I). What we want to see here is whether it works in-game on the regular keyboard. If it does not, then the keyboard or keyboard driver might be the issue, if it does work then the SST software is indeed the likely culprit.

[Udat]

I could steer the radar cone with rshift+,.-ø no problems. Not sure what you mean by hi-med mode in the f-15, isn't it automated?

Edit: SST version is 6.2.2.4

Edited May 22, 2010 by Udat

[EtherealN]

F-15 radar in FC2 has three frequency modes: hi, med, and hi/med. The last is the default. (The hi/med mode is best when just scanning, but if you have an idea of target direction, aspect and closure then you are generally better off selecting the appropriate mode for that geometry.)

 

Anyways, that would indicate that it's not a keyboard issue.

A look through my own SST indicates that my SST driver version is 6.2.2.0. Wondering whether they've done something funny (again) in an update...

[Udat]

I just updated it, haven't done that for maybe a year. The problem was there before the update, so might it be my keyboard language or something like that?

 

PS: thanks for staying with me.

Edited May 22, 2010 by Udat
typo

[EtherealN]

It shouldn't be keyboard language, but Saitek does do some funny things. Have you tried setting windows to interpret your keyboard as an english one? If there was a language thing the one thing I'd expect would be something like the language-specific keys being the ones that get the issue, not something as standard as the right shift.

 

Might be a keyboard driver issue though - something between keyboard driver and SST that just doesn't want to co-operate. You could test that out through borrowing a keyboard from a friend (as standard as possible), shutting computer off, then switching KB, then start up. (Reason for doing it powered off being to ensure that windows does reload relevant drivers, if any.)

[Design]

Have you tried the "advanced command"?. Please, take a look at this thread, maybe it's similar to your problem and can help you.

Edited May 22, 2010 by Design
Forgotten question mark :P

[Udat]

@ EtherealN: Sorry I'm pretty unsavvy at computers; how do I update keyboard drivers?

 

@ Design: Tested "advanced command," could still not make the software register Rshift presses..

 

Edit: downloading the 6.6.4.10 beta software.

Edited May 22, 2010 by Udat

[nomdeplume]

What version of the Saitek software are you using? It recognises RShift in 6.6.6.9. You can see the version number using the About dialog from the drop-down menu next to the question mark icon in the top right corner.

[Udat]

6.2.2.4 at the moment. EtherealN is using 6.2.2.0 and it's working for him.

[71st_Mastiff]

well theres your problem.:thumbup:

 

Old computer adage if it ant broke don't fix it doesnt work with computers. "update, update, update"

 

6.2.2.4 at the moment. EtherealN is using 6.2.2.0 and it's working for him.

[Udat]

well theres your problem.:thumbup:

 

Old computer adage if it ant broke don't fix it doesnt work with computers. "update, update, update"

The problem was there before I updated as well.

[Udat]

Yesss, 6.6.4.10 fixed it. Thanks for sticking with me guys!

[71st_Mastiff]

glad you got yours to work as for me my SST is still Bluescreening me I have tried to update or install the SST software many time on this machine and everytime the same. 9.9.9.9, I can not get it to install 6.6.6.9.

 

Even Saitek can't answer this one.

 

Yesss, 6.6.4.10 fixed it. Thanks for sticking with me guys!

[Udat]

That sounds crazy. Maybe you have to format computer :/

[EtherealN]

Mastiff, run DriverSweeper and/or CCleaner to see if you have driver fragments and such causing havoc with your system.