severniae Posted June 23, 2012 Report Posted June 23, 2012 Hi, I have a registered version of FSUIPC and have had the throttles set up to workth through FSUIPC and its worked flawlessly for over a week now. I had a FSX crash and now its all gone wrong. FSUIPC wont let the throttles work. When I move the throttle in the sim it stays still. When I set FSX to handle the axis the throttle starts working again but I want to use FSUIPC. Help please! James Walker
Pete Dowson Posted June 23, 2012 Report Posted June 23, 2012 I have a registered version of FSUIPC and have had the throttles set up to workth through FSUIPC and its worked flawlessly for over a week now. I had a FSX crash and now its all gone wrong. FSUIPC wont let the throttles work. When I move the throttle in the sim it stays still. When I set FSX to handle the axis the throttle starts working again but I want to use FSUIPC. I cannot think of anything in FSUIPC or its files which could possibly change just because you had an FSX crash -- unless your FSUIPC4.INI file, the one in the Modules folder where FSUIPC4.DLL is also, was corrupted in the process. That is very unlikely unless the FSX crash occurred whilst you were actually making changes to FSUIPC4 settings. Anyway, I cannot really help at all with no information. I would need to see your FSUIPC4.INI file and the FSUIPC4.LOG file, both from the Modules folder, and also I need to know what you actually are trying to do with the settings. Are you talking only about calibration, for example (when it matters little where or how you assign), or a specific method of assignment? What is your goal, what are you trying to achieve by using FSUIPC for your throttle? You can paste files in a message here. Close FSX down first, though. Pete
severniae Posted June 25, 2012 Author Report Posted June 25, 2012 [General] UpdatedByVersion=4827 History=X2TV4VP0JXUEBAI5DIBW5 MouseWheelMove=No MouseWheelTrim=No 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=-1 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 AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=No WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0 SimConnectUsed=10.0.61259.0 Console=No [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Rudder Pedals 0.GUID={BE1A8FA0-B56D-11E1-8001-444553540000} 1=Saitek Pro Flight Yoke 1.GUID={BE1A8FA0-B56D-11E1-8002-444553540000} [buttons] ButtonRepeat=20,10 1=R1,20,C65966,0 2=U1,20,C65967,0 3=R1,21,C65971,0 4=U1,21,C65972,0 [AutoSave] Next=1 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No [GPSout2] GPSoutEnabled=No [WideServer] WideFSenabled=Yes [sounds] Path=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Sound\ Device1=Primary Sound Driver Device2=AMD HDMI Output (AMD High Definition Audio Device) Device3=Realtek Digital Output (Realtek High Definition Audio) Device4=Realtek Digital Output(Optical) (Realtek High Definition Audio) [Axes] 0=1Z,256,D,9,0,0,0 1=1U,256,D,10,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 Throttle1=-15603,-512,512,16000/40 Throttle2=-15603,-512,512,16000/40
severniae Posted June 25, 2012 Author Report Posted June 25, 2012 ********* FSUIPC4, Version 4.827 by Pete Dowson ********* User Name="********r" User Addr="******@**.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX on Windows 7 Module base=61000000 312 System time = 25/06/2012 21:53:59 312 FLT path = "C:\******\" 343 Trying to connect to SimConnect Acc/SP2 Oct07 ... 343 FS path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\" 593 LogOptions=00000000 00000001 593 Wind smoothing fix is fully installed 593 G3D.DLL fix attempt installed ok 593 SimConnect_Open succeeded: waiting to check version okay 593 Trying to use SimConnect Acc/SP2 Oct07 3073 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 3073 Initialising SimConnect data requests now 3073 FSUIPC Menu entry added 3089 C:***********es\Df1.FLT 3089 C:\*********R 200633 Weather Mode now = Custom 200633 C:\Users\************Roaming\Microsoft\FSX\Previous flight.FLT 210601 System time = 25/06/2012 21:57:29 210601 *** FSUIPC log file being closed Average frame rate for running time of 25 secs = 15.7 fps G3D fix: Passes 18007, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 3 Allocs, 3 Freed ********* FSUIPC Log file closed ***********
severniae Posted June 25, 2012 Author Report Posted June 25, 2012 I have a saitek pro flight yoke. I'm setting the throttles (fist and second levers on the quadrent thing) to be my throttle 1 and 2 - with the reverse part set to reverse. Im doing this for a proper configuration with the Eaglesoft Citation X - Whenever I load the sim if I move the throttle, the throttle in game does not move. This is the same for default aircraft and addon aircraft alike Thanks, James
severniae Posted June 25, 2012 Author Report Posted June 25, 2012 Something strange to note - the throttles work fine if I first load an old default flight I had at EGNX.....
Pete Dowson Posted June 25, 2012 Report Posted June 25, 2012 These are the only relevant parts of the INI file: [Axes] 0=1Z,256,D,9,0,0,0 1=1U,256,D,10,0,0,0 [JoystickCalibration] Throttle1=-15603,-512,512,16000/40 Throttle2=-15603,-512,512,16000/40 There are two questions about this: 1. Why, specifically, are you assigning "Direct to fSUIPC calibration"? I see you are using the throttles with no reverse zone. There are several add-on aircraft which don't like direct assignment. these may not include yours, but it is a consideration. 2. Why are you setting the Filter option on the throttles in the calibration section? Surely your Saiteks are smooth enough. The filter mechanism is very drastic -- I'd recommend you turn that off. It is also odd that you only have throttles assigned and calibrated in FSUIPC. How are you using the other controls? If you are assigning the others in FSX, it would probaby be best to assign the throttles there too. FSX has a habit of reassigning things in any case unless you disable its controllers, in which case you'd need to assign everything in FSUIPC. Apart from these observations I can't see anything actually wrong with the settings. Something is eveidently wrong in fSX, or in the aircraft you wish to fly. the symptoms you mention are normal with the settings you have for some add-on aircraft -- you should probably try changing this parameter to Yes: UseAxisControlsForNRZ=Yes because that makes FSUIPC use the same controls as it would had you assigned in FSX. In your later message: Something strange to note - the throttles work fine if I first load an old default flight I had at EGNX..... Hmm. Certainly sounds like something is corrupt in the normal flight you are loading, then. Perhaps you could ZIP up the one that works and the one which doesn't and send to petedowson@btconnect.com so I can compare them. I'm intrigued. But it certainly points to something screwed up in fSX rather than anything specifically within FSUIPC's control. Why not replace the faulty flights with ones based on the one which works? (After you've sent the the faulty one of course, as i'd still like to understand why). Regards Pete
severniae Posted June 26, 2012 Author Report Posted June 26, 2012 Hi Pete, Many thanks for your prompt responce. In answer to questions 1&2 - Its how the manual for the installation of the Eaglesoft Citation X describes to setup the throttles for their FADEC system to work. And without the 'filter' option set when set to idle the throttles disappear from view in the virtual VC! I'll try some tests tonight to see what reproduces the problem and see if I can send you the relevant files. Many thanks, James
Pete Dowson Posted June 26, 2012 Report Posted June 26, 2012 In answer to questions 1&2 - Its how the manual for the installation of the Eaglesoft Citation X describes to setup the throttles for their FADEC system to work. And without the 'filter' option set when set to idle the throttles disappear from view in the virtual VC! Sounds like your throttle axis is misbehaving. I've never known filtering to fix anything except some jitter on systems with poor power supplies. In fact it was added to help out a chap with computers in some out of the way place in south east Asia. In your case, better than using the filter would be to calibrate a slightly wider idle zone, so that the thrttle stays properly in the idle position. Regards Pete
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