rsquared Posted March 24, 2010 Report Posted March 24, 2010 Hi This is a repost of an earlier post , misadvertently placed in Beginners Flight Sim Section ( newbie navigational error) I have currently switched back to FSUIPC after running my CH Pedals and Yoke through the CH Command Centre after my conversion to FSX Acceleration this fall. I am currently using FSUIPC version 4.60 in Windows 7, 64 bit. I have now done three complete reinstalls and each time I have failed. In the first two attempts, there seemed to be interferences in the axes - airplanes impossible to program. I figured I knew what I was doing, having used earlier versions of FSUIPC in FS9 mode but I was beginning to doubt my capability. On the third go, after rereading the manual to see what I might have missed the first two times, I don't think I did anything different but the controls worked as intended. I got about four airplanes installed and each one worked fine - I thought we were done. Wrong! Today when I tried to go flying, there were no assigned axes or buttons - I tried reloading general assignments and profile specific airplanes, nothing. I looked in the fsuipc.cfg file. The profiles are there but they don't seem to be recognized ( see an example of one profile below) One other question. Before I converted to FSUIPC, the button assigned to "Flight Map" worked almost instantly. Now there is a 2-3 second lag and a black screen - is that normal? All help appreciated. Ron [JoystickCalibration.Bellanca Viking 12 Turbo] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No MapThrottle=Yes MapProp=Yes MapMixture=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=-16384,0,512,16383 Elevator=-16384,512,2532,16383 Rudder=-16384,0,512,16256 LeftBrake=-16384,16256/16 SlopeLeftBrake=-5 RightBrake=-16384,16256/16 SlopeRightBrake=-4 Throttle1=-8385,-512,387,387/32 Mixture1=-11868,-7869,0,0 PropPitch1=-14706,-11481,-6837,-6837 SlopePropPitch1=-10 SlopeThrottle1=15 P.S. Added after reposting here - I read the explanations given to fbass in the Topic "Total Frustration" . Just wondering if the USB power management issue might be part of this? I don't know much about this part of the world - any help that you can give me to know what to look for? Thanks
Pete Dowson Posted March 24, 2010 Report Posted March 24, 2010 I have now done three complete reinstalls and each time I have failed. Reinstalls of what? FSX? That's generally not a good idea. Seems to make a right mess of SimConnect more often than not. Today when I tried to go flying, there were no assigned axes or buttons - I tried reloading general assignments and profile specific airplanes, nothing. I looked in the fsuipc.cfg file. The profiles are there but they don't seem to be recognized ( see an example of one profile below) You say "Profiles" but you seem to have just calibrations for the one aircraft, the "Bellanca Viking 12 Turbo". Do you mean you are using "aircraft specific" settings but only for one aircraft? Why do you use the term "profiles"? I really can't tell much from only the one little part of your INI file. A sight of the LOG might help too. It really sounds liker you are not always using the same aircraft, or you have done some messing about in the Profile list and got names all wrong. Best to let FSUIPC take care of all that. One other question. Before I converted to FSUIPC, the button assigned to "Flight Map" worked almost instantly. Now there is a 2-3 second lag and a black screen - is that normal? Doesn't sound like it. But flight map is an FS menu option not a flight mode one. Do you mean "top down" view mode, which is different? If flight map is coming up as a Window, like an FS dialogue, then FS does blank the flight screen. Maybe your map window is appearing behind it? I don't think any of that could be down to anything in FSUIPC. P.S. Added after reposting here - I read the explanations given to fbass in the Topic "Total Frustration" . Just wondering if the USB power management issue might be part of this? Don't know. Depends on your symptoms. If the devices appear off initially it should matter because they'll be seen when they wake up, which they should do after you've waggled them a bit. If you assigned then in FSUIPC (and I can't tell as you posted nothing about any that might tell me) You might need to go into FSUIPC axis assignment options to make it rescan. But you don't lose assignments or calibrations that way. All in all I'm afraid there's simply not enough information. Why withhold so much? Regards Pete
rsquared Posted March 24, 2010 Author Report Posted March 24, 2010 Reinstalls of what? FSX? That's generally not a good idea. Seems to make a right mess of SimConnect more often than not. R.: Since I was posting in the FSUIPC forum, I assumed that I was talking about FSUIPC. Sorry. You say "Profiles" but you seem to have just calibrations for the one aircraft, the "Bellanca Viking 12 Turbo". Do you mean you are using "aircraft specific" settings but only for one aircraft? Why do you use the term "profiles"? R: I use the term "profiles" as defined in page 27 of the manual ( FSUIPC 4.60) I realisze now that my understanding of the term "profile" was synonomous with "specific aircraft" and that appears to have been wrong. You say "Profiles" but you seem to have just calibrations for the one aircraft, the "Bellanca Viking 12 Turbo". Do you mean you are using "aircraft specific" settings but only for one aircraft? Why do you use the term "profiles"? I really can't tell much from only the one little part of your INI file. A sight of the LOG might help too. It really sounds liker you are not always using the same aircraft, or you have done some messing about in the Profile list and got names all wrong. Best to let FSUIPC take care of all that R: I'lll get you the log as soon as I can get back to my own computer but here a few general details. I created a "profile" for each of several GA aircraft that I loaded into FSUIPC. The Bellanca Turbo, another one for Epic LT, Kodiak Quest, etc. After I finished this, I flew a bunch of other airplanes rannging from single engine to twin to jet, no changes were made in FSUIPC, All worked great. I have done no "messing around" with the INI file - everything I did was from the menu screen of FSUIPC. But, even if had only one aircraft in the Bellanca Turbo profile, which happens to be a Bellance Turbo,and if I selected that very same airplane to fly, shouldn't it work? If I go back to fsuipc.cfg and change UseProfile back to NO, would that make things better or not?" Regarding programming button 0 to Flight Map P: Doesn't sound like it. But flight map is an FS menu option not a flight mode one. Do you mean "top down" view mode, which is different? If flight map is coming up as a Window, like an FS dialogue, then FS does blank the flight screen. Maybe your map window is appearing behind it? R. By Flight Map, I meant the screen with the all the A/P's, VOR's, Airways, etc. It does appear after the blank screen it just takes 2-3 seconds. Before I switched, it was almost instantaneous, so I thought I may have been doing something wrong. If the lag is normal, then so be it. All in all I'm afraid there's simply not enough information. Why withhold so much? Ron: I'm not withholding anything. I just don't know what to ask, for or how to ask for it, or so it seems, because what I have given you appears to be indadequate. If I knew, I wouldn't have to ask, so please bear with me. I'll get you the log when I get back to the hangar. Anything else you need? Cheers R.
Pete Dowson Posted March 24, 2010 Report Posted March 24, 2010 R: I'lll get you the log as soon as I can get back to my own computer but here a few general details. Not just the log. I need to see the INI file so I can see what you've done. If you paste them here enclosed in "Code" quotes (see the code button?), they'll not take up a huge abmount of space and be scrolable. Please also try quoting your quotations from my message as else it makes your replies very hard to read correctly. see the "Quote" button? I created a "profile" for each of several GA aircraft that I loaded into FSUIPC. But you actually mean you made different assignments for each specific aircraft. A "profile" would be different, and much easier to use and apply. But, even if had only one aircraft in the Bellanca Turbo profile, which happens to be a Bellance Turbo,and if I selected that very same airplane to fly, shouldn't it work? If you are using aircraft-specific settings rather than profiles, yes, provided the iarcraft had EXACTLY the same name. And i mean EXACTLY. Many aircraft come in several variations. The way you did it the other variations might not work because the names don't match. If I go back to fsuipc.cfg and change UseProfile back to NO, would that make things better or not?" You mean FSUIPC.INI, and now you are telling me you set "UseProfiles=Yes"? Did you do this before or after making aircraft specific settings? If you had UseProfiles=Yes you would have entered profile names of YOUR choosing into the drop down selector. You certainly wouldn't have used complete long unique aircraft names, as that would really defeat the object! R. By Flight Map, I meant the screen with the all the A/P's, VOR's, Airways, etc. It does appear after the blank screen it just takes 2-3 seconds. Before I switched, it was almost instantaneous, so I thought I may have been doing something wrong. If the lag is normal, then so be it. There's nothing in FSUIPC which would induce any lag. Regards Pete
rsquared Posted March 24, 2010 Author Report Posted March 24, 2010 You mean FSUIPC.INI, and now you are telling me you set "UseProfiles=Yes"? Did you do this before or after making aircraft specific settings? If you had UseProfiles=Yes you would have entered profile names of YOUR choosing into the drop down selector. You certainly wouldn't have used complete long unique aircraft names, as that would really defeat the object! I think it is becoming clearer now. In my second attempt, I changed UseProfile to yes but I guess when I tried the third attempt with a new INI file, I must not have entered it because looking at the INI file now, it clearly indicates NO. Rather than try and explain what I did ( or thought I did) , here is the INI file - [General]UpdatedByVersion=4600History=0XWN3ISNB0C53KULM2VG1TCASid=FlightTCASrange=40AxisCalibration=NoDirectAxesToCalibs=NoShowMultilineWindow=YesSuppressSingleline=NoSuppressMultilineFS=NoAxisIntercepts=NoDontResetAxes=NoWeatherReadFactor=2WeatherRewriteSeconds=1CustomWeatherModify=NoSimConnectStallTime=1Console=NoMouseWheelTrim=NoMouseWheelTrimSpeed=1JoystickTimeout=20PollGFTQ6=YesBlankDisplays=NoFixControlAccel=NoFixMachSpeedBug=NoVisibilityOptions=NoOneCloudLayer=NoCloudTurbulence=NoCloudIcing=NoGenerateCirrus=NoSuppressCloudTurbulence=NoMaxIce=3MinIce=-1UpperWindGusts=NoSuppressWindTurbulence=NoSuppressWindVariance=NoWindTurbulence=NoTurbulenceRate=1.0,5.0TurbulenceDivisor=20,20,40,40SuppressAllGusts=NoMaxSurfaceWind=0WindLimitLevel=200WindDiscardLevel=400WindAjustAltitude=NoWindAjustAltitudeBy=2000SmoothBySimTime=NoWindSmoothing=NoWindSmoothness=2WindSmoothAirborneOnly=YesPressureSmoothness=0TemperatureSmoothness=0DisconnTrimForAP=NoZeroElevForAPAlt=NoThrottleSyncAll=NoWhiteMessages=NoShowPMcontrols=NoSpoilerIncrement=512MagicBattery=NoRudderSpikeRemoval=NoElevatorSpikeRemoval=NoAileronSpikeRemoval=NoReversedElevatorTrim=NoClockSync=NoClockSyncMins=5ClearWeatherDynamics=NoOwnWeatherChanges=NoTimeForSelect=4LoadFlightMenu=YesLoadPlanMenu=NoPauseAfterCrash=NoBrakeReleaseThreshold=75SaveDataWithFlights=MenuZapSound=fireworkShortAircraftNameOk=NoUseProfiles=No[JoyNames]AutoAssignLetters=No0=CH Flight Sim Yoke USB0.GUID={E5F89030-94B4-11DE-8004-444553540000}1=CH Pro Pedals USB1.GUID={E5F64640-94B4-11DE-8003-444553540000}[WideServer]WideFSenabled=Yes[Buttons]ButtonRepeat=20,101=P0,0,C66413,02=P0,1,C66432,03=P0,10,C65607,04=P0,11,C65615,05=P0,9,C65567,06=P0,8,C66154,07=P0,32,C65875,08=P0,2,C66276,09=P0,3,C66277,010=P0,5,C66080,011=P0,4,C66079,012=P0,7,C65758,013=P0,6,C65759,014=R0,39,C66416,31515=P0,36,C66416,18016=P0,38,C65671,017=P0,34,C65672,018=P0,33,C66416,4519=P0,37,C66416,22520=P0,35,C66416,135[AutoSave]AutoSaveEnabled=YesInterval=60Files=10SaveOnGround=NoNext=1[GPSout]GPSoutEnabled=NoPort=COM0Speed=4800Interval=2000PosTo6Decimal=NoSentences=[GPSout2]GPSoutEnabled=NoPort=Speed=4800Interval=2000PosTo6Decimal=NoSentences=[Axes]0=0X,256,D,1,0,0,01=0Y,256,D,2,0,0,02=0Z,256,D,4,0,0,03=0R,256,D,5,0,0,04=0V,256,D,6,0,0,05=1X,256,D,7,0,0,06=1Y,256,D,8,0,0,07=1Z,256,D,3,0,0,0[JoystickCalibration]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoUseAxisControlsForNRZ=NoMapThrottle=YesMapProp=YesMapMixture=YesFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60Aileron=-16384,0,512,16383Elevator=-16384,512,2532,16383Rudder=-16384,0,512,16256LeftBrake=-16384,16256/16RightBrake=-16384,16256/16Throttle1=-14835,-11739,-7482,-7482Mixture1=-11868,-7869,0,0PropPitch1=-14706,-11481,-6837,-6837SlopeLeftBrake=-5SlopeRightBrake=-4SlopeThrottle1=-12SlopePropPitch1=-10[JoystickCalibration.Bellanca Viking 12 Turbo]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoUseAxisControlsForNRZ=NoMapThrottle=YesMapProp=YesMapMixture=YesFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60Aileron=-16384,0,512,16383Elevator=-16384,512,2532,16383Rudder=-16384,0,512,16256LeftBrake=-16384,16256/16SlopeLeftBrake=-5RightBrake=-16384,16256/16SlopeRightBrake=-4Throttle1=-8385,-512,387,387/32Mixture1=-11868,-7869,0,0PropPitch1=-14706,-11481,-6837,-6837SlopePropPitch1=-10SlopeThrottle1=15[JoystickCalibration.Kodiak Cargo in Red]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoUseAxisControlsForNRZ=NoMapThrottle=YesMapProp=YesMapMixture=YesFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60Aileron=-16384,0,512,16383Elevator=-16384,512,2532,16383Rudder=-16384,0,512,16256LeftBrake=-16384,16256/16SlopeLeftBrake=-5RightBrake=-16384,16256/16SlopeRightBrake=-4Throttle1=-8385,-3870,1677,7482SlopeThrottle1=7Mixture1=-11868,-7869,0,0PropPitch1=-8772,-903,512,2322[JoystickCalibration.Epic LT Prototype 9]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoUseAxisControlsForNRZ=NoMapThrottle=YesMapProp=YesMapMixture=YesFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60Aileron=-16384,0,512,16383Elevator=-16384,512,2532,16383Rudder=-16384,0,512,16256LeftBrake=-16384,16256/16SlopeLeftBrake=-5RightBrake=-16384,16256/16SlopeRightBrake=-4Throttle1=-14835,-11739,-7482,-7482SlopeThrottle1=-12Mixture1=-11868,-7869,0,0PropPitch1=-14706,-11481,-6837,-6837SlopePropPitch1=-10[Axes.Epic LT Prototype 9]0=0X,256,D,1,0,0,01=0Y,256,D,2,0,0,02=0Z,256,D,4,0,0,03=0R,256,D,5,0,0,04=0V,256,D,6,0,0,05=1X,256,D,7,0,0,06=1Y,256,D,8,0,0,07=1Z,256,D,3,0,0,0 And here is the log FSUIPC4, Version 4.60a by Pete Dowson ********* Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini" Trying to connect to SimConnect Acc/SP2 Oct07 .FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07) Module base=0CE70000 Wind smoothing fix is fully installed DebugStatus=15 78 System time = 23/03/2010 23:13:48 93 FLT UNC path = "\\RSQUARED-PC\Users\rsquared\Documents\Flight Simulator X Files\" 93 FS UNC path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\" 592 LogOptions=00000000 00000001 592 SimConnect_Open succeeded: waiting to check version okay 5023 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 5023 Initialising SimConnect data requests now 5023 FSUIPC Menu entry added 5101 \\RSQUARED-PC\Users\rsquared\documents\flight simulator x files\Carp Dynasty.FLT 5101 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Epic_LT\Epic_LT.AIR 16645 System time = 23/03/2010 23:14:05 16645 *** FSUIPC log file being closed Memory managed: 2 Allocs, 2 Freed ********* FSUIPC Log file closed *********** Appreciate your patience in this as well as in navigation on this forum. This is all a bit new but I'll get the hang of it soon. Cheers R
Pete Dowson Posted March 25, 2010 Report Posted March 25, 2010 I think it is becoming clearer now. In my second attempt, I changed UseProfile to yes but I guess when I tried the third attempt with a new INI file, I must not have entered it because looking at the INI file now, it clearly indicates NO. Rather than try and explain what I did ( or thought I did) , here is the INI file First off, you aren't getting the hang of posting here are you? When you use the Quote or Code buttons you have to select the text you want to so mark FIRST. You are simply putting blobs in. Second, when profiles are being used there's a Profiles section in the INI which lists the aircraft belonging to each profile. You give you own names to profiles, like "Prop", "Turbo", "Helo", "fighter", "Airliner", etc. whatever is applicable to the sort of assignments and calibrations you are making. Then when you load a new aircraft, you simply assign it to one of your profiles, or, if you like, create a new one to suit. FSUIPC takes care of all the arrangements in the INI file. Looking at your profile-less INI file: 1. You only have one Buttons section, so you aren't assigning buttons differently for each of your selected aircraft. That's okay. 2. For some reason you have a generic axis assignment for your 8 axes, and an identical one specific to the Epic LT Prototype 9: [Axes] 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=0Z,256,D,4,0,0,0 3=0R,256,D,5,0,0,0 4=0V,256,D,6,0,0,0 5=1X,256,D,7,0,0,0 6=1Y,256,D,8,0,0,0 7=1Z,256,D,3,0,0,0 [Axes.Epic LT Prototype 9] 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=0Z,256,D,4,0,0,0 3=0R,256,D,5,0,0,0 4=0V,256,D,6,0,0,0 5=1X,256,D,7,0,0,0 6=1Y,256,D,8,0,0,0 7=1Z,256,D,3,0,0,0 You might as well delete that second Axes section. It is pointless and will only serve to confuse. 3. You have separate generic calibrations and specific calibrations just for Bellanca Viking 12 Turbo Kodiak Cargo in Red Epic LT Prototype 9 which is okay, though certainly most of the settings are identical in any case -- especially that first one which only has a very small change in the slope value for one axis and is otherwise identical to the generic settings you have. Unfortunately, the log file you provided shows me nothing because it's for a session lasting less than 17 seconds. In fact it looks like you closed it immediately before SimConnect could even tell me the aircraft name, for me to check. If you want me to spot a problem for you you will need to actually demonstrate it to yourself and show me THAT log, not just load and close FSX and show me a log containing nothing. I am, however, a little puzzled at what you are trying to do here. What is your aim with these tiny changes in calibrations? Normally calibration is a function of the hardware, not of the aircraft -- excepting quite different needs like helicopters version jets versus props versus gliders, say. And then, often, the assignments change too. It isn't that you are necessarily misusing anything, it's just that I'd like to understand what it is you want to do. So far I can't see anything which would stop controls working. But maybe we'll get onto that when I can see a working log with whatever problem it is happening. Then we would investigate further by enabling logging. Regards Pete
rsquared Posted April 20, 2010 Author Report Posted April 20, 2010 First off, you aren't getting the hang of posting here are you? When you use the Quote or Code buttons you have to select the text you want to so mark FIRST. You are simply putting blobs in. Geez, you're not an easy guy to please, are you? :P Forgive us illiterate non technological types but when "quote" appears on the screen as quote/quote surrounded by square brackets , it's pretty easy to take at face value and insert chosen text for the quote after the square brackets. Intuitively I am supposed to that quoted text goes in between them? Ok, whatever Is this better :lol: Unfortunately, the log file you provided shows me nothing because it's for a session lasting less than 17 seconds. In fact it looks like you closed it immediately before SimConnect could even tell me the aircraft name, for me to check. If you want me to spot a problem for you you will need to actually demonstrate it to yourself and show me THAT log, not just load and close FSX and show me a log containing nothing. Ahem, yes, well, simple answer, mea culpa, I didn't know that the INI file rewrote itself every time every time you started FSX so the file I sent you would have come off a start-up of FSX where the joystick axes and buttons did not function so I shut it down as soon as I found out the joysticks did not work. I have since discovered after much trial and error, that if I start FSX after a fresh reboot, everything works as programmed. If I stop FSX, leave the computer running and return to FSX later, the joysticks do not work. When this happens, I have gone to the FSUIPC module and opened the menu - pressed reload all assignments, nothing happens, I have tried to rescan axes but the rescan buttons are greyed out. I have tried to reset buttons but I get no response on the screen when I push any buttons on the joystick, I have then gone to the settings in fSX menu and clicked,unclicked enable joysticks, that does not do anything either. Here is an excerpt of the Ini file when that happens, note that I have deleted many of repetitious lines..... ********* FSUIPC4, Version 4.60a by Pete Dowson ********* Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini" Trying to connect to SimConnect Acc/SP2 Oct07 ... User Name User Addr FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07) Module base=0C580000 Wind smoothing fix is fully installed DebugStatus=15 94 System time = 30/03/2010 22:37:04 109 FLT UNC path = "\\RSQUARED-PC\Users\rsquared\Documents\Flight Simulator X Files\" 109 FS UNC path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\" 593 LogOptions=70000000 00000001 593 SimConnect_Open succeeded: waiting to check version okay 5164 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 5164 Initialising SimConnect data requests now 5164 FSUIPC Menu entry added 5242 \\RSQUARED-PC\Users\rsquared\documents\flight simulator x files\Carp Dynasty.FLT 5242 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Epic_LT\Epic_LT.AIR 11310 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_CLOSE 32760 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 32760 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 32760 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 32760 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 32760 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 34663 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 34710 System time = 30/03/2010 22:37:39, Simulator time = 22:37:11 (03:37Z) 34726 Aircraft="Epic LT Prototype 9" 34741 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 34773 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 35053 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 35053 Advanced Weather Interface Enabled 35100 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 124286 *** Entered Buttons option page *** 128404 Aircraft="Epic LT Prototype 9" 133662 *** Exiting Buttons option page *** 265124 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 265389 Sim stopped: average frame rate for last 35 secs = 96.8 fps 276730 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Bellanca_Viking_Turbo\Bellanca_Viking_Turbo.AIR 276730 Weather Mode now = Theme 276730 \\RSQUARED-PC\Users\rsquared\Documents\Flight Simulator X Files\AutoSave Sun 191512.FLT 277791 Aircraft="Bellanca Viking 10 Turbo" 364886 *** Entered Buttons option page *** 366633 Aircraft="Bellanca Viking 10 Turbo" 372733 *** Exiting Buttons option page *** 392608 KEYDOWN: VK=27, Waiting=0, Repeat=N, Shifts=0 392608 .. Key not programmed -- passed on to FS 399721 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Epic_LT\Epic_LT.AIR 399753 \\RSQUARED-PC\Users\rsquared\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 399784 *** EVENT: Cntrl= 65794 (0x00010102), Param= 0 (0x00000000) PAUSE_ON 401219 Aircraft="Epic LT Prototype 9" 401219 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 401219 *** EVENT: Cntrl= 66064 (0x00010210), Param= 0 (0x00000000) SPOILERS_ON 407646 *** EVENT: Cntrl= 65732 (0x000100c4), Param= 0 (0x00000000) EXIT I am, however, a little puzzled at what you are trying to do here. What is your aim with these tiny changes in calibrations? Normally calibration is a function of the hardware, not of the aircraft -- excepting quite different needs like helicopters version jets versus props versus gliders, say. And then, often, the assignments change too. It isn't that you are necessarily misusing anything, it's just that I'd like to understand what it is you want to do. As to the calibrations, I was just trying to find a more responsive( accurate) throttle response. It just seemed that the amount of movement on the throttle itself was inversely proportional to the amount of throttle response that was generated. I have tried multiple times to get a throttle that increases in a linear fashion, not an exponential one - if thre is an easier to do that than making multiple attempts, then please enlighten me, Thanks Ron
Pete Dowson Posted April 20, 2010 Report Posted April 20, 2010 Geez, you're not an easy guy to please, are you? What's the matter with you? I'm only trying to help! What's wrong with me explaining how to do things? That is surely not an insult, as you have obviously taken it! I won't bother trying to help if that's how you react! :-( If I stop FSX, leave the computer running and return to FSX later, the joysticks do not work That's a typical symptom of having power management in Windows turning off the power to the USB ports. Go into Windows device manager, find all of the USB hubs and devices with power management tabs, and turn those options off. Unfortunately some versions of Windows default them on -- Microsoft trying to be "green" I suppose. Here is an excerpt of the Ini file when that happens, note that I have deleted many of repetitious lines..... That is NOT the INI file, but the LOG. The INI file is where all your FSUIPC settings are stored. The LOG contains details of things that happen in this session of FS. They are different files. INI files are obviously kept between sessions to retain your settings. In any case it is irrelevant, because your problem is not related to FSUIPC in any case. As to the calibrations, I was just trying to find a more responsive( accurate) throttle response. "More responsive" might mean "less accurate". How do you measure "accuracy" with an analogue throttle lever? Are you noting the resulting RPM for each position or something? It just seemed that the amount of movement on the throttle itself was inversely proportional to the amount of throttle response that was generated. Sounds like your throttle is equipped with a log potentiometer instead of a linear one. Or you have set such a slope in FSUIPC, or that sort of response is programed into the modelling of the aircraft in FS. I have tried multiple times to get a throttle that increases in a linear fashion, not an exponential one The default FSUIPC slope is linear. If your actual throttle is producing an exponential curve then you'd need to adjust the slope inversely to counter it, if you think that is unrealistic. Maybe, however, it is more a function of the aircraft modelling? - if thre is an easier to do that than making multiple attempts, then please enlighten me Simply making multiple attempts doesn't necessarily help at all, at least not of its own accord. It is surely always best to read the documentation and simply apply what it says rather than blindly doing the same wrong things all the time? To change the response curve in FSUIPC (to make it non-linear) the only way is to use the "slopes" option in FSUIPC. You can choose a slope which counteracts the apparently incorrect behaviour of your throttle device. Certainly you might need to adjust it a little and try it till you find what suits you. If these are the "multiple attempts" you refer to, then how else do you expect to be able to adjust to your particular liking? 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