Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Everything posted by mslim

  1. I recently did a reinstall of FSX-SE due to some problems I was having. I downloaded 4.971 but the installer said I had a newer version and wouldn't install it. When I tried to register the version I had, it did not automatically supply my key as it did in the past. I had written the key on a word doc as I do with all purchases but apparently it got purged when I uninstalled FSX-SE. Is there a way to recover the key by the purchaser's name or email??
  2. DISREGARD solution found. spurious entry in FSX controls was causing the malfunction of the Gear Toggle command. ObieGearToggle.zip
  3. Hi, I am using FSUIPC to control toe pedal brakes with Saitek Cessna rudder pedals. I would like more braking friction from the pedals. What parameter do I adjust for more braking action? Thanks.
  4. I had everything running great last night. I carefully made a copy of my .ini as a backup (with a different name of course) so I would have a reference. I logged on to fly tonight from Paine Field WA, PNW NA to Port Angeles in a Twin Otter X and everything loaded fine. I could use my pan view fine as it is the only button on my TF Hotas X that is routed directly to FSX. None of my other controls or buttons would work. The only thing different that I can remember from my configuration last night is that tonight I was using FSFO V2 as a verbal checklist. I am very frustrated. I thought I had this wonderful addon finally dialed in. If anyone has a chance to look at my log and ini files and see if they can deduce what is going on I would greatly appreciate it. Thanks. Slim WDS_FSUIPC4_INI.zip WDS_FSUIPC4_LOG.zip
  5. Thanks for the reply Pete. Hope your holiday went well. Pan View is not assigned in FSUIPC. (but I will be experimenting with doing so in the future) Sorry for the outdated Log file. Somehow all the Hotas X assignments ended up assigned to the rudder pedals so I will implement your AutoAssign suggestion. Best Regards, Slim
  6. While I hope Pete is enjoying his holiday, it seems my FSUIPC has decided to take one as well. I use a Thrustmaster Hotas X with all buttons (except the coolie hat which is mapped to pan view thru FSX) and axes mapped thru FSUIPC. I no longer have the use of any FSUIPC functions. I know the USB connection is OK since the pan view still works. I have attached both my INI and LOG files in the hopes that they will reveal my problem. Thanks in advance for any help offered. Best Regards, Slim WDS_ FSUIPC4.1.zip WDS_FSUIPC4_INI.zip
  7. Just wondering if any forum members have had any luck at assigning a smooth view to the coolie hat switch on the Thrustmaster Hotas X? I would like to totally dump any FSX control of the joystick and throttle assignments but my attempts at assigning the VC view thru FSUIPC have been markedly inferior (jerky) to the FSX assignment. Maybe I'm missing something here? Slim
  8. Hi Pete, Thanks for the quick responses. Of course nothing is wrong with "trying things". It's just that said experimentation can be more productive if you have the basic concepts clearer in your mind. Otherwise assumptions of results may be flawed or incorrect. I fairly well understand the X, Y, and Z axes slopes from sensitometric curves in photography but I was just trying for clarification on the throttle axis. For decreased mid-range sensitivity would that be a positive or negative value? Best Regards, Slim
  9. Yes I did experiment with the manual settings thru the controller. It was very hard to get the + and - values to match. The controller is spring loaded and always trying to center itself so I was working against that. I wasn't really looking for a wide dead zone just a reasonable one to take the "stick twitch" out of the controls. I am working with slopes as you have seen in the next post. Is -512, 512 considered a wide or narrow dead zone? Best Regards, Slim
  10. I know this is very basic for experienced users but I just wanted to check my understanding of these values. Can I manually edit the fsuipc4.ini to increase or decrease the nulls or deadzones in my controls? I found it tricky to consistently set them moving the controller. Here are my current settings: Aileron=-16380,-512,512,16380 Elevator=-16380,-512,512,16380 Throttle=-16300,16300 Rudder=-16380,-512,512,16380 By increasing values 2 & 3 will I increase the deadzone? Thanks. Slim
  11. I am beginning to make profiles and fine tune them for specific aircraft. In the case of the P51 the middle part of the throttle response is very critical. You can go from 40" to 70" of manifold pressure with a small movement of the throttle controller. If I wanted to have less sensitivity in the middle of the throttle axis is that a positive or negative number? Also tweaking rudder response, I would like more control movement at the extreme ends of the rudder pedal travel. If I understand pgs. 48-49 of the User guide, that seems to me to be a positive value slope. Did I interpret that correctly? Thanks. Slim
  12. Hi Ian, I was unable to see the image you posted but I posted my window. The only choice is "Import from a URL" or "Gravitar". Even though I don't show the "Use a custom photo" button enabled it doesn't open an additional choice. Most other forums have a button that says "browse" that enable you to upload from your computer. Am I missing something here? Slim
  13. How in the heck do you upload an avatar photo from your computer? The only choices are "upload a photo from URL" and "Use Gravatar". Shouldn't there be a "Upload from file - browse" button.
  14. Couldn't agree more. Former (lapsed) RW pilot here. I was taught to trim out control pressure and not fight the airplane. That, and proper power and pitch settings, make your flying a lot safer and enjoyable. Thanks again for the invaluable guidance. BTW where did you take your initial flight training? Most of mine was PDK and VNY. Obie
  15. Thanks Jetblst for taking the time to give me this excellent help. This is exactly what I was trying to implement. I couldn't have done it without your assistance. Kind Regards, Obie
  16. Hi Andy, I am using the HOTAS X hat switch for view (pan) directly in FSX so it's not available for rudder trim. I guess if you have the beautiful Warthog controller you have many buttons you can assign. I have assigned all my buttons to higher priority functions. Maybe I'll just use a key press if Pete doesn't have any suggestions. I liked the idea of the rocker switch for rudder trim as that is the way Pilatus did it on their military aircraft. Slim
  17. Thanks Andy and jetblst for the prompt responses. Jetblst I was aware of the X0C04 offset for rudder trim as per the SDK and User Manual. However something I did (or did not do) is preventing a useful implementation of rudder trim. Andy I believe that the ini file reflects the assignment to direct to FS Controls as you suggested but it seems to be an all or nothing assignment. When I hit the rocker switch to the right it jumps to 100% right rudder trim. I obviously need steps or smaller increments. I wonder if it would help to utilise the "set up to 10 ranges of action" box? The rocker switch on the Hotas X is only available for assignment as the S axis. It is not available AFAIK as a joystick button. There is possibly a mechanical problem in the rocker switch itself although the rest of the joystick pots are smooth and consistent. When I try to look at the Delta value it is either 0 or -16383 or +16383, very twitchy. I do not see intermediate values as with the other axes. I know Pete is probably overloaded w/ emails and work after the Holidays but perhaps when things settle down he'll dissect my ini file and make some suggestions as I really need the rudder trim for high torque AC such as the P51 and Skyraider. Best Regards, Slim
  18. Hi, I have been slowly working my way through FSUIPC and I see why everyone raves about it. I have managed after a few false starts to have an efficient set up on most of my controls and buttons. The one item I can't seem to implement correctly is the rudder trim. I have a Thrustmaster Hotas X with a horizontal rocker switch on the throttle (S axis). On the RW Pilatus PC-7 this is used for rudder trim. I would like to implement this switch as rudder trim. I am using Offset Increment/Decrement Controls from pg 32 of the User Guide for my elevator trim and it works extremely well. I have tried using it (x0C04) for rudder trim but it is not working correctly. Please take a look at my ini file and see what I'm doing wrong. Feel free to point out any other glaringly poor choices in the file. Thanks in advance for any assistance this forum can offer. Regards, Slim [General] UpdatedByVersion=4853 History=F6W7LBF5VNGCLWG3XB3OB InitDelayDevicesToo=No MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No DeleteVehiclesForAES=Yes AutoScanDevices=Yes VisibilityOptions=No OneCloudLayer=Yes CloudTurbulence=No CloudIcing=No GenerateCirrus=Yes SuppressCloudTurbulence=No MaxIce=3 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=Yes WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=20 RudderSpikeRemoval=Yes ElevatorSpikeRemoval=Yes AileronSpikeRemoval=Yes ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=Yes TimeForSelect=4 LoadFlightMenu=Yes LoadPlanMenu=Yes PauseAfterCrash=Yes BrakeReleaseThreshold=75 SaveDataWithFlights=Yes 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=Yes OOMcheck=Yes WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 Console=No LogEvents=Yes LogLua=Yes DebugLua=Yes LogAxes=Yes LogButtonsKeys=Yes FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0 SimConnectUsed=10.0.61259.0 [JoyNames] AutoAssignLetters=No 1=Saitek Pro Flight Cessna Rudder Pedals 1.GUID={2F122DF0-5981-11E2-8001-444553540000} 0=T.Flight Hotas X 0.GUID={05B0A020-0713-11E1-8001-444553540000} [buttons] Buttonrepeat=20,10 2=R0,3,Cx32000BC0,x3FFF0100 3=R0,2,Cx42000BC0,xC0010100 4=P0,10,C65570,0 5=P0,4,C65758,0 6=P0,5,C65759,0 7=P0,6,C65580,0 8=P0,11,C65751,0 9=P0,7,C66541,0 10=R0,1,C65588,0 [MacroFiles] 1=Meggitt2100 [AutoSave] Next=1 Interval=60 Files=5 SaveOnGround=No AutoSaveEnabled=Yes AlsoSave=my restart AlsoInterval=60 5=Thu 192129 1=Thu 190731 2=Thu 190835 3=Thu 190935 4=Thu 191631 [GPSout] GPSoutEnabled=No [GPSout2] GPSoutEnabled=No [WideServer] WideFSenabled=Yes [sounds] Path=C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Sound\ Device1=Primary Sound Driver Device2=Realtek HD Audio output Device3=Modem #0 Line Playback (emulated) Device4=M-Audio Delta AP Multi Device5=M-Audio Delta AP 1/2 Device6=M-Audio Delta AP S/PDIF [Keys] 1=81,10,65876,0 2=190,10,65752,0 3=70,10,66237,0 4=33,8,65775,0 5=34,8,65777,0 9=40,8,65771,0 10=38,8,65769,0 [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=0S,256,D,28,0,0,0 4=1X,256,D,7,0,0,0 5=1Y,256,D,8,0,0,0 6=1R,256,D,3,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 Aileron=-16380,-512,512,16380 Elevator=-16380,-512,512,16380 Throttle=-15867,15738 Rudder=-16380,-512,512,16380 Rudder Trim=-16380,-512,512,16380 LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 SlopeThrottle=-4 SlopeRudder=6 [Profile.Single Engine Prop] 1=American Champion Citabria FSX Red and White 2=American Champion Scout FSX Midnight Blue with Red 3=American Champion Decathlon FSX Starburst Red 2 4=Maule M7 260C Yellow and Blue 5=Maule M7 260C paint3 6=Tiger Moth VHDHA 7=Warbirdsim P-51D Mustang "Carolyn's" 8=American Champion Scout FSX Midnight Blue with Red [Profile.Twin Engine Prop] 1=Milviz Baron 55_3 2=Milviz Baron 55_6 3=Beech AT-11 N501 4=Milviz Baron 55 5=Milviz Baron 55_1 6=Milviz Baron E55 7=Milviz Baron E55_1 8=Milviz Baron E55_3 9=Beech D18S N412K 10=Beech D18S Shupe 11=CBFS Mosquito Mk.IV W4069_1942. 12=CBFS Mosquito Mk FBIV DZ360 single 13=CBFS Mosquito Mk FBIV DZ633 double 14=CBFS Mosquito Mk FBIV USAAF 15=CBFS Mosquito Mk FBIV DK333 single 16=CBFS Mosquito Mk FBIV DZ421 single 17=CBFS Mosquito Mk FBIV DZ461 single 18=CBFS Mosquito Mk FBIV DZ548 single [Profile.Twin Engine TurboProp] 1=Aerosoft OV-10 CDF Porterville 2=Aerosoft OV-10 CDF 3=Aerosoft OV-10 Blue Angels x1 4=Aerosoft OV-10A Marines Close Air Support 5=Aerosoft OV-10A AirForce Close Air Support 5=Aerosoft OV-10A Marines 6=Aerosoft OV-10A Marines 7=Aerosoft OV-10A AirForce 8=Aerosoft OV-10A Marines CAS A Shau 9=Aerosoft OV-10A AirForce Forward Air Control 10=Aerosoft OV-10A Marines Forward Air Control 11=Aerosoft OV-10A NAVY RRS3 12=Aerosoft OV-10A Marines LR 13=Aerosoft OV-10A AirForce LR 14=Aerosoft OV-10A AirForce Training 15=Aerosoft OV-10A Marines Training 16=Aerosoft OV-10 Nasa 524 17=Aerosoft OV-10B G-BZGK 18=Veneaviones Turbo Commander 690B WL N927SM VC 19=Veneaviones Turbo Commander 690B WL N1050P VC 20=Veneaviones Turbo Commander 690B N36SW 21=Veneaviones Turbo Commander 690B N840JC VC 22=Veneaviones Turbo Commander 690B N425RR VC 23=Veneaviones Turbo Commander 690B N26MA VC 24=Basler U.S. Forest Service 25=Basler BT67 US Department of State 26=Basler BT67 Airborne Support 27=Basler BT67 Mauritania Air Force 28=Piaggio P-180 Avanti V2011 Avantair 29=Piaggio P-180 Avanti V2011 Maserati 30=Piaggio P-180 Avanti V2011 AMI 31=Piaggio P-180 Avanti V2011 ESERCITO 32=Piaggio P-180 Avanti V2011 [buttons.Twin Engine TurboProp] 0=R0,9,C65602,0 1=U0,9,C65604,0 2=P0,8,C65589,0 [Profile.Single Engine TurboProp] 1=PC-9 Release Version 1 #3 2=PC-9A Release Version 1 #0 3=PC-9A Release Version 1 #1 4=PC-9A Release Version 1 #2 5=PC-9A Release Version 1 #3 6=PC-9A Release Version 1 #4 7=PC-9A Release Version 1 #5 8=PC-9A Release Version 1 #6 9=PC-9A Release Version 1 #7 10=PC-9 Release Version 1 #0 11=PC-9 Release Version 1 #1 12=PC-9 Release Version 1 #2 13=PC-9 Release Version 1 #4 14=PC-9 Release Version 1 #5 15=FSD Porter BushMaster Air Charter on Wheels 16=FSD Porter Air America on Wheels 17=FSD Porter Aussie Army on Wheels 18=PC-7_ASF 19=PC-7SAF v.2 A-949 20=A-29B 21=A-29B_FAC 22=A-29B_RAFdesert 23=A-29B_USMnsawc 24=A-29B_USN 25=PC-9 Release Version 1 #0 26=PC-9 Release Version 1 #1 27=PC-9 Release Version 1 #2 28=PC-9 Release Version 1 #4 29=PC-9 Release Version 1 #5 [buttons.Single Engine TurboProp] 0=P0,8,C65589,0 1=R0,9,C65602,0 2=U0,9,C65604,0
  19. I am new to FSUIPC so excuse me if there's a better way to do this but last night I was wrestling with this same problem. I first mapped to the FSX default keypress F1 and F2 with these commands. After more investigation I just mapped directly in FSUIPC to "THROTTLE DECR 65602" and "THROTTLE CUT 65604" and it worked well. Slim
  20. Which takes precedence to the controller, FSX joystick commands or FSUIPC? I know there is check box in the FSX controller that allows a global override of FSX controller but If I wanted a mixed assignment controller, such as joystick in FSX and button pushes in FSUIPC would I simply delete all the button pushes and keyboard assignments in FSX to allow FSUIPC to control them? Obie
  21. Hi Pete, Thanks for the prompt response. Apologies for my inept description. I do not know how the condition levers are controlled or assigned in FSX. Aerosoft has done a massive workaround somehow in an attempt to replicate to some extent the fixed shaft Garrett TPE-331 turboprop. I don't think they are linked to the mixture controls. Here is a Garrett description of what the levers do: The Speed Lever, sometimes called the Condition Lever (when linked to the manual feather valve and fuel solenoid manual shut-off lever) or RPM Lever, basically serves one function: to select the engine operating speed. Normal Speed Lever positions are: High, Cruise, and Low. The RPM selected is according to the flight or ground condition, and once set, requires resetting only when the flight condition changes. High (100%) RPM is used for takeoff and landing, Cruise (96-97%) RPM for normal climb/cruise/descent operations, and Low (65-73%) RPM for engine starting and ground or taxi operations. The condition/speed lever does more than control prop pitch. My last statement that was so confusing was only meant to indicate that a normal prop pitch increase/decrease command thru FSX does not work with the Bronco X code. Thanks for your patience. I was hoping perhaps another forum member with a Bronco had encountered this problem. Kind Regards, Slim
  22. Hello everyone, Newbie here with no coding skills trying to take advantage of FSUIPC implementation. As it is required in every flight of the Aerosoft Bronco X to move the condition levers from the landing/take-off position to the normal flight position soon after takeoff, I wondered if this could be programmed to a keystroke with FSUIPC? I normally have my propeller rpm increase/decrease handled this way but I know as a condition of the Garrett geared engine workaround that this doesn't work the regular way with the Bronco. The FSX tooltip shows the condition levers as Throttle just as it does for the power levers. Any suggestions from anyone that has successfully enabled condition lever control will be greatly appreciated. Kind Regards, Slim
  23. mslim

    Album 2

  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.