Jim Supersym Posted January 15, 2013 Report Share Posted January 15, 2013 I only just read this entry. There is no way a new aircraft (one with a different name) can ever be "automatically" added to a profile. It can only be done by user selection. Apart from the profile assigned, if any, to the current aircraft, none of the profile names are even known to FSUIPC until you use the selection facility in the options. I think I have to emphasise what has now been said at least twice. delete the line assigning the aircraft to the cessna profile. I'm afraid FSUIPC does not currently offer an option to do this via the Options tabs -- I thought it an infrequent need and resources better spent elsewhere. Regards, Pete I Apologyze for my bad english, but I hav'nt created manually this line. I've reassign the axis with the fa18 loaded in FSX, but in the profile of cessna... :( fiirst mistake I've done the mistake too, If I'm right, to have assign two time the axis, in general and in the cessna profile. Is is true ? The best I have to do, I think is to delete and recrate the cessna profile with a cessna, and afterthat, if I can crate a profile for the fa18 with the fa 18 loaded, but only with the axins the buttum not already asigned ! Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 15, 2013 Report Share Posted January 15, 2013 I Apologyze for my bad english, but I hav'nt created manually this line. I know. The line is created by assigning the aircraft to that profile via the Options checkbox and selection. When you load a new aircraft (one without a Profile assigned), and click on "Profile Specific", you get a list of the profiles which exist, and an entry to create a new one. You must have simply selected the Cessna one unintentionally. Too quick with the mouse button perhaps? I've reassign the axis with the fa18 loaded in FSX, but in the profile of cessna... :( fiirst mistake After deleting the line for this? So you've repeated the original mistake! The best I have to do, I think is to delete and recrate the cessna profile with a cessna No. If the Cessna profile is okay, just remove the line that Andy and I pointed out, the one assigning your FA18 to the Cessna profile. THEN load FS and load the FA18, and create a new profile with whatever name you like. Do NOT click on "Cessna" again! Regards Pete Link to comment Share on other sites More sharing options...
Jim Supersym Posted January 16, 2013 Report Share Posted January 16, 2013 Thanks a lot for all ! Pete and Andy ! I've done that you tell me so deleting the line about the FA18 in the cessna profile and I've been able to create a new profile with the FA18. It's Ok now. Thanks again ;) Link to comment Share on other sites More sharing options...
Jim Supersym Posted January 16, 2013 Report Share Posted January 16, 2013 Oh ! I'm so desapointed ! It's impossible to assign the brakes left ans right and it's impossible to calibrate : any value changes ! Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 16, 2013 Report Share Posted January 16, 2013 It's impossible to assign the brakes left ans right and it's impossible to calibrate : any value changes ! Sorry, but you'll need to explain a little more. I've no idea what you are talking about. I really can't help unless you say exactrly what you are doing and what you are trying to do, and what you think is not correct. Pete Link to comment Share on other sites More sharing options...
Jim Supersym Posted January 16, 2013 Report Share Posted January 16, 2013 ok I tried to assign in "axis assignment" the axis of the brakes of my saitek rudder. And it's impossible to calibrate any axis : joystick or rudder. Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 16, 2013 Report Share Posted January 16, 2013 I tried to assign in "axis assignment" the axis of the brakes of my saitek rudder. And it's impossible to calibrate any axis : joystick or rudder. So you assigned these items okay? Where, in FS or in FSUIPC? And to which specific controls -- FS controls or Direct to Calibration? What do you really mean by "impossible to calibrate"? Please explain. I cannot see what you see, you must tell me. Did you never have anything assigned and calibrated before? Have you only just got these controls? Pete Link to comment Share on other sites More sharing options...
Jim Supersym Posted January 16, 2013 Report Share Posted January 16, 2013 I assigned the axis in fsuipc in "send to fs as normal axis" In calibration any values don't change when I move the joystic or the rudder, I meet no problem with the cessna or the 747 pmdg. I assigned and calibrated those aircratf with the same options Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 16, 2013 Report Share Posted January 16, 2013 I assigned the axis in fsuipc in "send to fs as normal axis" Okay. That's the same as using FS for assignment. Please tell me the names of the controls you assigned -- there are several variants, each suited to different needs -- and some need different settings. You would generally find it much less confusing and, in fact, more efficient, to assign "direct to fSUIPC calibation" unless you do not want to calibrate for some reason. In calibration any values don't change when I move the joystic or the rudder, Perhaps you need to show me the INI file too. But please concentrate on my comments above first. I meet no problem with the cessna or the 747 pmdg. I assigned and calibrated those aircratf with the same options Since it makes no difference to FSUIPC, this is exactly why I think you are still confusing yourself, as you did before. Let me see the INI file as you have it now. If you only ever assign to FS controls, and use the same controls for every aircraft, you would probably find it much easier to assign in FS itself. You can still calibrate in FSUIPC. I've no idea why you are trying to make things more complex. Do you need different controls for each aircraft? If you use the same controls for each, why are you assigning the axes "profile specific"? You would be better assigning them once and for all, non-specific, don't you think? Pete Link to comment Share on other sites More sharing options...
Jim Supersym Posted January 16, 2013 Report Share Posted January 16, 2013 thank you very much for your attention ! ini file : [General] UpdatedByVersion=4859m History=KQ10C48AOGOLF0IC0E6R1 TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 Console=No DontResetAxes=No AxesWrongRange=No InitDelay=0 GetNearestAirports=Yes LuaRerunDelay=66 MouseWheelMove=No MouseWheelTrim=Yes MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No DeleteVehiclesForAES=Yes AutoScanDevices=Yes VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=No UseProfiles=Yes EnableMouseLook=No InitDelayDevicesToo=No OOMcheck=Yes FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0 SimConnectUsed=10.0.61259.0 [JoyNames] AutoAssignLetters=No 1=Saitek Pro Flight Rudder Pedals 1.GUID={E1D20B50-5A53-11E1-8001-444553540000} 0=USB Game Controllers 0.GUID={88769DC0-EC99-11DE-8004-444553540000} [WideServer] WideFSenabled=Yes [sounds] Path=H:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Sound\ Device1=Périphérique audio principal Device2=Haut-parleurs (2- Realtek High Definition Audio) Device3=Realtek Digital Output (2- Realtek High Definition Audio) Device4=Realtek Digital Output(Optical) (2- Realtek High Definition Audio) [buttons] Buttonrepeat=20,10 1=P0,14,C65752,0 2=P0,16,C66080,0 3=P0,17,C66079,0 4=R0,2,C65607,0 5=R0,3,C65615,0 6=R0,21,C65602,0 7=U0,21,C65604,0 12=P2,8,C66204,0 14=P0,0,C65588,0 16=P2,3,C66204,0 [AutoSave] Next=8 Interval=30 Files=10 SaveOnGround=Yes AutoSaveEnabled=Yes 1=Fri 002138 2=Fri 002208 3=Fri 002238 4=Fri 002307 5=Fri 002337 6=Wed 130603 7=Wed 131411 8=Fri 002010 9=Fri 002039 10=Fri 002109 11=Wed 214523 12=Wed 214533 13=Wed 214542 14=Wed 214552 15=Wed 214601 16=Wed 214611 17=Wed 214620 18=Wed 214630 19=Wed 214640 20=Wed 215227 21=Wed 213421 22=Wed 213430 23=Wed 213440 24=Wed 213449 25=Wed 213518 26=Wed 213527 27=Wed 213537 28=Wed 213546 29=Wed 213731 30=Wed 213741 31=Wed 213750 32=Wed 213800 33=Wed 213809 34=Wed 213819 35=Wed 213828 36=Wed 213838 37=Wed 213847 38=Wed 213857 39=Wed 213906 40=Wed 213916 41=Wed 213925 42=Wed 213935 43=Wed 213944 44=Wed 213954 45=Wed 214003 46=Wed 214013 47=Wed 214022 48=Wed 214032 49=Wed 214042 50=Wed 214051 51=Wed 214101 52=Wed 214110 53=Wed 214120 54=Wed 214129 55=Wed 214139 56=Wed 214148 57=Wed 214158 58=Wed 214207 59=Wed 214217 60=Wed 214227 [GPSout] GPSoutEnabled=No Port=COM0 Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [Axes] 0=0X,256,F,65763,0,0,0 1=0U,256,F,65762,0,0,0 2=0V,256,F,65763,0,0,0 [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 LeftBrake=-16384,16383 RightBrake=-16384,16383 Spoilers=-16256,16384/16 Flaps=-16383,16384/16 Reverser=0,0 Aileron=-16384,0,0,16383 Rudder=-16384,0,0,16191 Throttle=-16384,16192 Mixture=-16380,16380 Elevator=-16384,0,0,16383 MapThr1to234=Yes MapThr12to34=Yes MapThr12to123=Yes PropPitch=-16384,16383 [Profile.cessna152] 1=C152II LIGHTBLUE G.F. 2=C152II Calypso G.F. [Axes.cessna152] 0=0X,1,F,65763,0,0,0 1=0Y,256,F,65762,0,0,0 2=0Z,256,F,65765,0,0,0 3=0V,256,D,23,0,0,0 4=1X,256,F,66387,0,0,0 5=1Y,256,F,66388,0,0,0 6=1R,256,F,65764,0,0,0 7=2X,256,D,4,0,0,0 8=2R,256,D,6,0,0,0 [JoystickCalibration.cessna152] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No MapThr1to234=Yes MapThr12to34=Yes MapThr12to123=Yes FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Aileron=-16380,0,0,16380 Elevator=-16159,0,0,16224 Rudder=-16384,0,0,16255 PropPitch=-16384,16383 Mixture=-16254,16320 LeftBrake=-16383,16384/16 RightBrake=-16383,16384/16 Spoilers=-16383,16384/16 Flaps=-16383,16384/16 Reverser=0,0 SlopeRudder=-1 Throttle=-16380,16380 [Profile.74710] 1=PMDG 747-8i Air France [Axes.74710] 0=0X,256,F,65695,0,0,0 1=0Y,256,F,65694,0,0,0 2=0Z,256,D,22,0,0,0 3=0U,256,D,4,0,0,0 4=0V,256,D,23,0,0,0 5=1X,256,D,7,0,0,0 6=1Y,256,D,8,0,0,0 7=1R,256,F,65696,0,0,0 8=2X,256,F,65697,0,0,0 9=2Y,256,F,65767,0,0,0 10=2R,256,F,65773,0,0,0 [buttons.cessna152] 0=P2,7,C66241,0 1=U2,7,C66241,0 2=P2,6,C66242,0 3=U2,6,C66242,0 4=P2,3,C65571,0 5=U2,3,C65571,0 6=P2,0,C66204,0 7=U2,0,C66204,0 8=P2,8,C66239,0 9=U2,8,C66239,0 [buttons.74710] 0=H2,0,K77,8 1=H2,1,K65,8 2=U2,1,K65,8 3=H2,2,K76,8 4=U2,2,K76,8 5=U2,0,K77,8 6=R0,0,C65588,0 7=R0,21,C65602,0 8=U0,21,C65604,0 [Profile.74710] 1=74710 [Profile.FA18] 1=Flight Test Aircraft E1 [Axes.FA18] 0=0X,256,F,65763,0,0,0 1=0Y,256,F,65762,0,0,0 2=0Z,256,F,65765,0,0,0 3=0U,256,F,65762,0,0,0 4=0V,256,F,65763,0,0,0 5=1R,256,F,65764,0,0,0 [JoystickCalibration.FA18] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No MapThr1to234=Yes MapThr12to34=Yes MapThr12to123=Yes FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Aileron=0,0,512,16380 Elevator=0,0,0,0 Rudder=-16384,0,0,16191 Throttle=-16384,16192 PropPitch=-16384,16383 Mixture=-16380,16380 LeftBrake=-16380,16380 RightBrake=-16384,16383 Spoilers=-16256,16384/16 Flaps=-16383,16384/16 Reverser=0,0 Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 16, 2013 Report Share Posted January 16, 2013 ini file : What about my other points? Have you no replies? [JoyNames] AutoAssignLetters=No 1=Saitek Pro Flight Rudder Pedals 1.GUID={E1D20B50-5A53-11E1-8001-444553540000} 0=USB Game Controllers 0.GUID={88769DC0-EC99-11DE-8004-444553540000} You have these default assignments, to your yoke only by the look of it: [Axes] 0=0X,256,F,65763,0,0,0 Axis ailerons Set 1=0U,256,F,65762,0,0,0 Axis Elevator Set 2=0V,256,F,65763,0,0,0 Axis ailerons Set Why two axes both for ailerons? And you have default calibrations and mappings for those and a lot more. How? [JoystickCalibration] LeftBrake=-16384,16383 RightBrake=-16384,16383 Spoilers=-16256,16384/16 Flaps=-16383,16384/16 Reverser=0,0 Aileron=-16384,0,0,16383 Rudder=-16384,0,0,16191 Throttle=-16384,16192 Mixture=-16380,16380 Elevator=-16384,0,0,16383 MapThr1to234=Yes MapThr12to34=Yes MapThr12to123=Yes PropPitch=-16384,16383 The Cessna assignments seem to be a mixture of FS controls and direct controls. why mixed? Also there are assignments for a non-existent device 2. [Axes.cessna152] 0=0X,1,F,65763,0,0,0 1=0Y,256,F,65762,0,0,0 2=0Z,256,F,65765,0,0,0 3=0V,256,D,23,0,0,0 4=1X,256,F,66387,0,0,0 5=1Y,256,F,66388,0,0,0 6=1R,256,F,65764,0,0,0 7=2X,256,D,4,0,0,0 8=2R,256,D,6,0,0,0 [JoystickCalibration.cessna152] Aileron=-16380,0,0,16380 Elevator=-16159,0,0,16224 Rudder=-16384,0,0,16255 PropPitch=-16384,16383 Mixture=-16254,16320 LeftBrake=-16383,16384/16 RightBrake=-16383,16384/16 Spoilers=-16383,16384/16 Flaps=-16383,16384/16 Reverser=0,0 SlopeRudder=-1 Throttle=-16380,16380 The 747 controls even more so, but with some real oddities: You appear to have selected the older axes not the current "Axis ..." controls. Also it has assignments for a device 2 which doesn't appewar to exist according to the scanned device list! [Axes.74710] 0=0X,256,F,65695,0,0,0 Aileron set (this is the older control, not the current FS "Axis" control) 1=0Y,256,F,65694,0,0,0 elevator set (") 2=0Z,256,D,22,0,0,0 3=0U,256,D,4,0,0,0 4=0V,256,D,23,0,0,0 5=1X,256,D,7,0,0,0 6=1Y,256,D,8,0,0,0 7=1R,256,F,65696,0,0,0 Rudder Set (this is the older control, not the current FS control) 8=2X,256,F,65697,0,0,0 Throttle Set (") 9=2Y,256,F,65767,0,0,0 Prop pitch set (for a 747? Huh?) 10=2R,256,F,65773,0,0,0 Mixture Set (?) The FA18 assignments are all to FS controls: [Axes.FA18] 0=0X,256,F,65763,0,0,0 Ailerons 1=0Y,256,F,65762,0,0,0 Elevator 2=0Z,256,F,65765,0,0,0 Throttle 3=0U,256,F,65762,0,0,0 Elevator 4=0V,256,F,65763,0,0,0 Ailerons 5=1R,256,F,65764,0,0,0 Rudder Seems you have two ailerons and two elevators, but no brakes assigned. I think you've made a bit of a mess, do you see? Without assigning "direct to FSUIPC" you won't be getting FSUIPC to arbitrate between the pairs of controls, so they will conflict. I expect this is your problem. Quite honestly, you seem to be making more and more of a mess. Perhaps you could epxlain what it is you are trying to do. Why all these differing assignments? How many control devices do you have -- only two seem to be connected, so what it the problem with doing basic assignments just the once and use them for all aircraft? In the end I suspect you'd be better off deleting your INI file and starting again. Regards Pete Link to comment Share on other sites More sharing options...
Jim Supersym Posted January 16, 2013 Report Share Posted January 16, 2013 I've one joystick noname and one yoke saitek with a thottle saitek and a throttle propeler mixture saitek and witch are not connected at this moment I will retart properly with a new ini file, it will be better ! The best way is "send to fsuipc calibration" ? Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 16, 2013 Report Share Posted January 16, 2013 I've one joystick noname and one yoke saitek with a thottle saitek and a throttle propeler mixture saitek and witch are not connected at this moment No rudder really then? If you don't leave them all connected, then it will be best, BEFORE assigning anything, to select the joy letter mode of identifying devices -- there's a chapter on this in the User Guide. If you don't do this then things will certainly go wrong at times -- the numbers used are assigned by Windows and are only fixed whilst the device is connected. The best way is "send to fsuipc calibration" ? Yes, it is easier, less confusing, and more efficient. The FS controls are supported because there are some add-on aircraft which need them. Best to make a default set of assignments suited to your devices, and ONLY make profile-specific assignments if really necessary. This is usually when switching from, for example, prop controls (with mixture and prop pitch lervers) to jets (with extra throttle controls or things like steering tiller, reversers and spoiler), or to helicopter controls (completely different) or maybe yoke for Boeing airliners and joystick for Airbus. Set the defaults initially to suit the aircraft type you fly mostly. Regards Pete Link to comment Share on other sites More sharing options...
Jim Supersym Posted January 16, 2013 Report Share Posted January 16, 2013 understood :) Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now