+- FsPassengers Forums (http://www.fspassengers.com/forum)
+-- Forum: FsPassengers (http://www.fspassengers.com/forum/forumdisplay.php?fid=3)
+--- Forum: FsPassengers Support (http://www.fspassengers.com/forum/forumdisplay.php?fid=5)
+--- Thread: Keyboard entry bug? (/showthread.php?tid=5046)
Keyboard entry bug? - GoonBird - 15-08-2005
I can't seem to get the keyboard entry system to work with the Wilco/Feelthere crj-700. It works fine with all my other planes - is there
anything I can do to fix it? Re-inst. didn't do anything... It overwrote the fs9 gps*.dll's which I had to get from the cab-file, but that was
fixable - is this? Or is fsp just not compatible with that particular plane?
Fred
Re: Keyboard entry bug? - SWAFO - 15-08-2005
Keyboard entry system? Do you mean the co-pilot commands for tuning the radio's, etc.? Please be more specific.
Re: Keyboard entry bug? - GoonBird - 15-08-2005
Yep, that's it. A great feature, when it works. It's probably not even in fsp, but a conflicting file from one or more of my many addons,
maybe?
Thanks for the quick reply... : )
Re: Keyboard entry bug? - SWAFO - 15-08-2005
It is in FSP. It should work but only when FSP is running. Start an FSP flight, and press "C"... does the co-pilot say "COM"?
Re: Keyboard entry bug? - DanSteph - 15-08-2005
may be a conflict as well, some add-on "eat" keyboard entry even before it come to Fs2004
don't forget you can redefine FsP's keyboard key using the "setup keyboard" option.
Dan
Re: Keyboard entry bug? - GoonBird - 16-08-2005
Quote:SWAFO wrote:
It is in FSP. It should work but only when FSP is running. Start an FSP flight, and press "C"... does the co-pilot say
"COM"?
Yes, it does say "com" and "nav" - and the radio settings work. It also says "speed" and "altitude" - but it doesn't have any effect on the
settings. It's like the input is acknowlegded by fsp, but it doesn't pass it on to the autopilot - both when it is on and off (the autopilot). Since
the autopilot is specific to this plane (and the 900, of course) and I haven't encountered the problem with other planes or autopilots, it
seems to me to be a conflict between fsp and this specific autopilot.
Quote:DanSteph wrote:
may be a conflict as well, some add-on "eat" keyboard entry even before it come to Fs2004
don't forget you can redefine FsP's keyboard key using the "setup keyboard" option.
Dan
Since fsp "gets" the input,(and the radio setting by keyboard works fine) I'm thinking it's in the "output" from fsp to the autopilot. Does that
make sense?
I hope there is a solution to it - but if not, it's still the greatest addon ever. (Been hoping for something like this since FS 5.1) I've never
flown this much before... And thank you both again not just for finding the time to help me, but also for the great support and the unique
tone of these forums!!
- Fred
Re: Keyboard entry bug? - SWAFO - 16-08-2005
You are pressing numbers after pressing the appropriate keys, aren't you? For example, press "C" followed by 11800. I'm just trying to
see if there's an easy solution.
Re: Keyboard entry bug? - eazy - 16-08-2005
Quote:GoonBird wrote:This happens with some complex add-on panels/gauges. Same thing with the F1 ATR, it accepts course setting but no altitude or heading, although
it does say "com" and "nav" - and the radio settings work. It also says "speed" and "altitude" - but it
doesn't have any effect on the settings
there's no other function on the A and H keys. Maybe some panel functions are modeled in a different way thus not responding to standard inputs
Re: Keyboard entry bug? - DanSteph - 16-08-2005
Ah I see, those "custom" autopilot use private value and don't use at all Fs2004 value
so it's impossible for an external program to grab value or set value for those autopilots.
Dan
Re: Keyboard entry bug? - GoonBird - 17-08-2005
Quote:DanSteph wrote:
Ah I see, those "custom" autopilot use private value and don't use at all Fs2004 value
so it's impossible for an external program to grab value or set value for those autopilots.
Dan
I thought it was something along those lines.... pity.... (I guess I get the feature back when I can afford to buy my first 737
)Thanks for clearing it up, I will stop fiddling with the *.cfg's now...
- Fred