fleahead
-
Posts
13 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by fleahead
-
-
The Manual says I can select microphone on the ACP in the VC screen only, but I can not push any buttons on the ACP. None of the buttons are lit. My FS9 ATC menu allows me to tune various frequencys but I can not communicate. Am I missing something?
fleahead of ohio
-
No, that's the problem, Pete. They use some standard controls, but not all. As you probably know, Airbus has several push/pull knobs which controls flybywire or managed flight. Feelthere uses left/right mouse clicks to input the controls. But, some functions work via AP controls, such as LOC HOLD & APPR HOLD, but others don't.
I have the demo version of Key2Mouse and it appears I can make it do what I need, then let FSUIP translate the KEY entries to BUTTONS. I just have a concern that it will effect FPS.
Thanks for the answer.
Jim M
-
Is there a way to find FS control assignments that correlate to mouse clicks of various knobs and buttons? For example, in the Feelthere Airbus series, I want to use buttons to increase/decrease the altitude knob. I have tried all the Ap possibilities and every other FS control that has anything to do with altitude, but nothing works. I did manage to control the heading and speed with standard FS controls, but there are several panel buttons and knobs I can't get assignments for.
Is this something I can see via LOGGING? I know that when I mouse click a knob, that has to translate into some number that has to translate to a control.
I've been looking into the Mouse2Key program, which appears to be able to do what I want, but I really don't want to load another addon to bog down the system any further.
Jim M
-
Hi guys... I'm on XP SP2 and everything is up to date. I leave all USB devices connected and seldom have to reboot, but it doesn't matter if I reboot or not. I see the assignments in FS9.cfg after I have removed them, then a reload, so I can only presume some other file is loading them in the cfg during reload. Actually, I didn't check the cfg after closing FS9, so it could be getting wrote during shutdown. I'll check.
There must be something to the assignment being stored in another place since I loaded a default Cessna this morning and I had a multitude of various buttons and axis assigned on the four control devices I have attached. Everything is stable in good old FSUIP.
-
I know this has nothing to do with FSUIP, but I thought maybe Pete or someone would be able to shed some light on this problem.
I have CH pedals and have RUDDER and LEFT/RIGHT BRAKE assigned through FSUIP. I remove the assignments in FS9 controls, but everytime I reload FS9 the assignments are back. I removed the assignments on my yoke, and throttle assignments, and they stay eliminated. I have even tried directly editing fs9.cfg but they still get reassigned on the next reload.
Jim M
-
OK Pete. 373.1 did the trick. I now see the KEY save registered in the ini file. I also verified the AXIS, BUTTON, and CALIBRATION is still OK. Thanks so much :lol:
-
Yep... just as you confirmed... it appears to be only the KEYS that I see no aircraft specific header line created. I made an AXIS, BUTTON, and KEY aircraft specific entry for both a PSS 777 and the Feelthere Airbus, and only the KEY change did not create an entry in the ini file. I saw the AXIS and BUTTON change registered OK.
-
Hi Pete...
I downloaded 371 back in December and had no problems. I don't regularly check for new version releases, but after I noticed this problem, that's when I downloaded 373. I don't want to mislead you, but 371 was working at one time because I have the following lines in an older ini file:
[buttons.PSS Boeing 777-300ER QANTAS No VC]
0=P0,26,K90,14
1=P0,27,K88,14
[Monitor]
Display=1
Like I say, I just noticed this in 371 a few weeks ago. But like you are asking, I have only noticed this saving KEYS, so I'll go try a few specific aircraft buttons and axis changes, and get back in a few minutes...
Jim
-
Thanks for the rapid response, Pete. I noticed this a few weeks ago in 3.7.1. I downloaded 3.7.3 yesterday, and I get the same problem. I have removed FSUIP.ini once to start a new one. Same results. I was assigning to Feelthere A319, but also tried assigning to PMDG 737 with no saving there either. Here is the last ini file I have tried. As you can see, it does record the buttons and keys of unspecified aircraft.
[Keys.]
1=80,8,66483,0
2=75,8,65733,0
3=80,8,66483,0
4=80,8,66483,0
5=107,9,65879,0
6=107,9,65879,0
7=107,10,65896,0
8=109,9,65880,0
10=107,10,65896,0
12=109,10,65897,0
14=45,8,66299,0
16=45,10,66298,0
[Axes]
0=0X,256,F,66387,0,0,0
1=0Y,256,F,66388,0,0,0
2=0Z,256,F,65764,0,0,0
3=1X,256,D,22,0,0,0
4=1Y,256
5=1Y,U,-4161,16383,66079,0
6=1Y,D,-16384,-9362,66080,0
7=1V,256,D,23,0,0,0
8=2X,256,F,65763,0,0,0
9=2Y,256,F,65762,0,0,0
10=2Z,256,F,65763,0,0,0
11=3X,256,F,65763,0,0,0
12=3Y,256,F,65762,0,0,0
13=3Z,256,F,65762,0,0,0
[General]
WindSmoothing=Yes
AutoTaxiWind=Yes
PropTaxiWind=No
TimeSetMode=Partial
WhiteMessages=No
ThrottleSyncAll=No
GraduatedVisibility=No
LowerVisAltitude=0
UpperVisAltitude=25000
UpperVisibility=6000
GenerateCirrus=Yes
WindShearSharp=No
UpperWindGusts=Yes
ExtendMetarMaxVis=Yes
PatchSimApAlt=Yes
DisconnTrimForAP=No
ZeroElevForAPAlt=No
AutoClearWeather=Yes
ExtendTopWind=Yes
WindSmoothness=5
SmoothPressure=Yes
PressureSmoothness=5
SmoothVisibility=No
VisibilitySmoothness=2
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
MinimumVisibility=0
MaximumVisibilityFewClouds=0
MaximumVisibility=0
MaximumVisibilityOvercast=0
MaximumVisibilityRainy=0
OneCloudLayer=No
ThinClouds=No
ThinThunderClouds=No
CloudThinness=1000
ThunderCloudThinness=10000
CloudTurbulence=No
CloudIcing=No
WindTurbulence=Yes
SuppressAllGusts=No
ExternalOptionControl=Yes
AutoTuneADF=No
KeepFS98CloudCover=No
ShowPMcontrols=No
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
StopAutoFuel=No
TrapUserInterrupt=Yes
NavFreq50KHz=No
ClockSync=No
SmoothIAS=Yes
SetVisUpperAlt=No
VisUpperAltLimit=6000
MaxIce=3
MinIce=-1
WindSmoothingDelay=0
WindSmoothAirborneOnly=No
LimitWindVariance=No
VisSmoothingDelay=0
VisSmoothAirborneOnly=No
TrafficControlDirect=Yes
SuppressCloudTurbulence=No
SuppressWindTurbulence=No
SpoilerIncrement=512
ShortAircraftNameOk=No
TCASid=Flight
TCASrange=40
TrafficScanPerFrame=10
AxisCalibration=No
CentredDialogue=Yes
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
ClearWeatherDynamics=No
OwnWeatherChanges=No
FixWindows=No
FixControlAccel=No
WeatherReadInterval=4
MoveBGLvariables=Yes
TimeForSelect=4
WeatherReadsFast=No
MainMenu=&Modules
SubMenu=&FSUIPC ...
History=4INIUJB4PZDEK813B6ZJ3
[JoystickCalibration]
ExclThrottleSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=0
RudderTrimControl=0
CowlFlaps1Control=0
CowlFlaps2Control=0
CowlFlaps3Control=0
CowlFlaps4Control=0
MaxSteerSpeed=60
Aileron=-16384,0,0,16256
SlopeAileron=4
Elevator=-16253,0,0,16128
SlopeElevator=3
Rudder=-16384,0,0,16128/8
SlopeRudder=15
LeftBrake=-16384,16256/16
RightBrake=-16384,16256/16
Spoilers=-16384,16383/16
Flaps=-16384,16383/16
[buttons]
1=R1,4,K107,8
2=R1,5,K109,8
3=R1,0,K107,10
4=R1,1,K109,10
5=R1,2,K107,9
6=R1,3,K109,9
7=R1,6,K107,12
8=R1,7,K109,12
[Keys]
2=79,8,66389,0
Jim
-
I have with problem with 3.7.1 and 3.7.3 (registered). If I make key or button assignments with Aircraft Specific checked, nothing is saved in the fsuip.ini file. It is saving the general axis assignments. I also see misc changes such as wind smoothing being saved in the .ini file. I have no duplicate dll files in the modules folder.
jm
LNAV VNAV Keys
in FSUIPC Support Pete Dowson Modules
Posted
Using Wilco 777, what are the fs9 cammands to assign VNAV/LNAV to keystrokes. I don't recognize any of the ap_ commands that would be for that.
Jim