Shift+z dropped off my FS9.cfg, can someone please provide the .cfg line for it (under [Keyboard Main] I reckon. Not sure exactly what the mapping title is, but Shift+Z provides present position data plus frame rates.Thanks!Rich Perry

Shift+z dropped off my FS9.cfg, can someone please provide the .cfg line for it (under [Keyboard Main] I reckon. Not sure exactly what the mapping title is, but Shift+Z provides present position data plus frame rates.Thanks!Rich Perry

I am not at all sure that is where the "command" is -I suspect you would be wise to rename your present FS9.cfg file (FS9.cfg.BAK) and allow it to be rebuilt new when you start up FS once again.If Shift Z then works, you can copy and paste any special tweaks you had from the disabled copy into the fresh new one.Keep us posted.

Perhaps an easier way to restore your Shift Z function is to use the Assignments dialogue.

Perhaps an easier way to restore your Shift Z function is to use the Assignments dialogue.

OpaThanks...when I tried to map "shift+z" to a joystick key, it still wouldn't work. I've done the, delete FS9.cfg and let it rebuild a fresh one, it works for a while, then it seems as I fly other aircraft, other than saved C172, certain mappings go away. It used to happen with joystick as well, but then someone recommended adding LOCKED=1 to joystick main and joystick slew...so I may add that line to KEYBOARD MAIN in FS9.cfg, once I get the settings figured out.I'm using Vista Ultimate 64 bit...while FS9 smokes on my system, strange little things occur without any input from me, like the dropping of keyboard mapping. I suppose there's some minor gliches given 32 bit meets 64 bit O/S to be expected.THanks!Rich

I don't have Vista 64 bit (the only version I would ever try/use) but have you tried right clicking the FS9 Icon, then use 'Compatability' option, and pick to run FS9 in 'XP' mode? Might work, since it would run as 32 bit? Perhaps. That is what I would try before doing complicated tweaks that might just make things worse. I believe Vista 64 uses different memory offset assignments and the conflict results in 'lost keyboard mapping' (only a guesstimation).Chuck BNapamule