broncomaniac

Hi Pete. Thanks for the quick response. You were right - somehow FS had re-enabled the joystick. This isn't something I had done myself as I am certain I had disabled the controllers so that I could do everything through FSUIPC. I have now disabled it again, and as a safeguard also deleted the joystick assignments in FS. Everything is now working correctly. Thanks again. Adrian

Hi. I am trying to map buttons on my CH Yoke to bring up two sub-panels for my Flight1 King Air B200, replacing the keystrokes (shift+4 and shift+5 respectively). I have the latest version of registered FSUIPC4. I believe I have worked out how to do this correctly, and the sub-panels seem to open and close properly. However the buttons are also still performing their previous functions, namely gear down and flap extension, as well as opening the sub-panels. I cannot work out how to delete the old button assignments. I have checked on my FSUIPC4.ini file, and this suggests that the old assignments have been deleted: [Buttons.Flight1 King Air B200] ButtonRepeat=20,10 0=PB,5,K52,9 -{Key press: shft+4}- 1=PB,4,C66079,0 -{GEAR_UP}- 2=PB,7,K53,9 -{Key press: shft+5}- 3=PB,6,C65759,0 -{FLAPS_DECR}- 4=RB,11,C65615,0 -{ELEV_TRIM_UP}- 5=RB,10,C65607,0 -{ELEV_TRIM_DN}- 6=RB,2,C66278,0 -{RUDDER_TRIM_LEFT}- 7=RB,3,C66279,0 -{RUDDER_TRIM_RIGHT}- 8=PB,9,C66694,0 -{POINT_OF_INTEREST_CYCLE_NEXT}- 9=PB,8,C66693,0 -{POINT_OF_INTEREST_CYCLE_PREVIOUS}- 10=PB,0,C65791,0 -{AUTOPILOT_OFF}- 11=PB,1,C65875,0 -{PAN_RESET}- 13=RB,32,C65734,0 -{PAN_UP}- 14=RB,36,C65735,0 -{PAN_DOWN}- 15=RB,38,C65671,0 -{PAN_LEFT}- 16=RB,34,C65672,0 -{PAN_RIGHT}- 17=RB,33,C65856,0 -{PAN_RIGHT_UP}- 18=RB,39,C65854,0 -{PAN_LEFT_UP}- 19=RB,37,C65855,0 -{PAN_LEFT_DOWN}- 20=RB,35,C65857,0 -{PAN_RIGHT_DOWN}- Have I done something wrong? How can I rectify this? And secondly, as I will no longer be using the buttons for gear up and flap retraction either, can I simply delete these lines in the .ini file? Does it matter that lines 1 & 3 will be missing? Or should I change the numbering accordingly? Thanks for your help. Adrian

The OUT value is -16384. However the negative values are not reached until just before the lever is pulled fully back on the TQ. O corresponds to about 5% on the TQ, and then the values drop away sharply to -16384 when the lever is pulled right back to 0%. I have tried this on the default King Air 350 and my preferred Aerowork King Air B200. Here's the section from my FSUIPC.ini file: [JoystickCalibration] FlapsSetControl=0 ReverserControl=66292 MaxThrottleForReverser=0 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 SepRevsJetsOnly=No Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 Mixture=-16384,16383 PropPitch=-16384,16383 ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes ApplyHeloTrim=No FlapDetents=No MaxSteerSpeed=60 AllowSuppressForPFCquad=Yes UseAxisControlsForNRZ=No Aileron=-16384,-1170,1250,16383 Elevator=-16384,-1280,1170,16383 Rudder=-16384,0,0,16383 LeftBrake=-16384,16383/16 RightBrake=-16384,16383/16 Throttle=0,16383 Thanks for your help. Adrian

Hi Pete. Thanks again for the reply. Sorry to have puzzled you. Let me explain how I came to be where I am now. Most of the time I fly a King Air B200 or a Seneca II, both of which are twin engine. So when I bought my TQ I did some research and was told that it was perfectly possible through FSUIPC to use the 3 levers of a single TQ to operate what in effect are 6 levers in FS. I was also told that it was a very good idea to set decent null zones, so that you are sure of getting 0% on each axis before pulling back into the negative or reverse range. This is important to avoid so called hot starts on the B200. When I first read through the documentation on FSUIPC and looked at it from within FS9 my immediate perception was that the null zone settings were only possible from within the 4 engine set up, i.e. pages 3-5 on the calibration tool. So having researched further I was told that in the axis assignment tool I needed to set e.g. my throttle axis to both Throttle1 and Throttle2, and likewise with prop pitch and mixture. So that is what I did and it did seem to work OK, with the exception of the anomalies that I first reported. Having made the adjustment with the NRZ as suggested by you, the TQ was operating perfectly. However...the B200 that I have requires that you carry out separate operations on the throttle, prop and condition levers for each engine in the engine start up procedure...and with the way I had the TQ set up it was now not possible to select engine 1 or 2 using the E+1 or E+2 keystrokes. This was therefore a significant problem, just when I thought I had everything set up fine. So I have now taken your advice and re-assigned my axes to be just single throttle, prop and mixture. Having then calibrated them I now have struck on another problem. The throttle lever functions fine, as does the mixture. However, the prop pitch range now seems to be limited to 50-100% only. In other words, if I bring the TQ lever all the way down to 0 the tool tip in FS indicates 50%. A 50% position on the TQ equates to 75% in FS. If I then bring the prop lever back down into the feathered range, the lever in FS jumps down to the 0 mark and indicates props feathered. If I then come out of the feathered range to just forward of 0% on the TQ, the lever in FS jumps forward to 50% and beyond. In other words there is no means of setting a prop pitch of 0-50%. This is similar to the problem I had before with the mixture controls, but which I was able to cure using the NRZ option. However, this option does not exist in the generic controls, so I am now at a total loss to know how to rectify this. I have tried recalibrating to no avail. And I've checked the .ini file and there does not appear to be any remnant of the previous settings. Please could you give me some advice on how to rectify this problem with the prop lever? I don't really want to fork out another £50 for a second TQ if I can avoid it, but I'm starting to think that that might be my only decent solution. Thanks again, Pete.

Hi Pete. Many thanks for your quick and detailed reply. The NRZ tip was the solution. I was doing everything right except for the NRZ check box. I have checked that for the throttle, props and mixture levers and everything seems to behaving as it should now. I'm glad you pointed this out to me, because to be honest NRZ doesn't get a huge mention in your User Guide. As I said before, the Saitek TQ differs from other models in that the levers operate solely in the positive range, i.e. they only go from 0%-100%. There is no negative range on these levers at all because reverse thrust, prop feathering and fuel cut off (albeit triggered by the same levers by pulling them down from the 0% detent) operate as button assignments and not as part of the lever range. Might I politely suggest that you could consider adding a note for Saitek users (like you have for PFC throttle quadrants and Wilco Airbus pilots) in your next version of the User Guide? Thanks again for the help. Adrian

FSUIPC version: 3.991 (registered) FS version: 9.1 OS: Windows 7 64 bit FS hardware: CH Products yoke and rudder pedals, Saitek Pro Flight throttle quadrant Hi Pete and others. Hope you can help me with a really baffling problem. I have just bought the above throttle quadrant (TQ) from Saitek to go with my existing CH Products yoke and rudder pedals, because I wanted the extra range of movement in the 3 axes that it gives over the limited axes on the yoke, and therefore the extra sensitivity you get when flying. But I'm having a real problem configuring the axes so that they do what I want them to do. I mainly fly twin-engine turboprops/pistons like the Seneca and the King Air B200. I didn't have the money for 2 TQs, but I have found that it is perfectly possible to operate both throttle levers in the aircraft with one TQ lever and the same with the prop and mixture/condition levers, so that is not the issue. I should add that I have chosen not to install the Saitek drivers (in the same way that I never installed the CH drivers for the yoke and pedals), as I've read that they are not that great and that it is perfectly possible to configure all of the axes through FSUIPC. My problem is the values that I'm getting on the TQ axes in FSUIPC. My understanding is that all axes should run from approx -16383 to +16383. The reality is that not all of them do and for those that do there are anomalies in how the levers behave. Let me take them one at a time. Throttle This runs from 0 to +16383. However much I try to recalibrate it it will not go below 0, let alone anywhere close to -16383. If I look at the throttle pedestal in the VC and use the mouse tips I can see that when my TQ throttle lever is at 0% the corresponding levers in the VC are also at 0%. Likewise if I throttle up to the 50% and 100% marks on the TQ I get the corresponding levels in the VC. Reverse thrust seems to work as well. But I have to say that the engine pitch at 0% throttle does sound quite high, so I'm actually wondering whether I'm actually getting something closer to 50% at 0%, since 0 is halfway between -16383 and +16383. I don't know...perhaps it's my ears. I have tried to edit the INI file to have a range from -16383, but that seems to make no difference. Props This axis does run from -16383 to +16383. And the levels on the TQ match those on the VC prop levers. I have also got prop feathering to work. However, what confuses me is that, if I watch the behaviour of the axis configuration in FSUIPC, I see that at 0% props the axis reading is -16383. Yet if I move the lever just a smidgin up from 0 the FSUIPC axis reading is immediately in the positive range. In other words there is nowhere on the axis that corresponds to -16383 to 0. It jumps from -16383 to +1 in a flash. Is this correct behaviour? Mixture/condition This is where I'm having the biggest problems. Like with the props this axis runs from -16383 to +16383. However unlike the props this axis goes all the way from -16383 to 0 before going into positive values. Where it gets crazy is that if I slide my TQ condition lever down to the 0% mark the levers in the VC only go down to 50%. At 50% on the TQ the VC levers are at 75% and at 100% on the TQ the VC is at 100%. This means that in my King Air the condition levers never go below 50% and therefore nowhere near "low idle", which is the setting (around 25%) for most of the phases of flight. If I bring the TQ lever down into cut off the corresponding VC levers drop suddenly into the cut off point and the engines do indeed cut off. However much I try to recalibrate this axis it always behaves in the same way. And because a low idle setting is so important in the King Air B200 I am at a point where I cannot fly it. So you can see that in fact all 3 axes behave in different ways, yet my understanding is that they should all behave alike. Or have I got it wrong? For the sake of clarity, unlike on the CH Products TQ the Saitek TQ works such that idle is precisely that...idle. Reverse thrust, prop feathering and fuel cut off are not part of the axis range and work as button assignments. So all I'm interested in is the range from 0-100% on my TQ. Is there anyone out there that can please throw some light on what is going on here? I'd be very grateful for some tips. Adrian

Thanks again Pete. You say you need me to send you "everything". What specifically do you need me to send? Thanks.

Thanks for the reply Pete. Since I sent my posting yesterday I found another posting on the forum (page 4) with the exact same problem. That told me that updating to the latest version would solve the problem as I could use a different address. I didn't realise there was a more up to date version, but I have now downloaded and installed version 3.98. I use Windows 7 64 bit, and I have tried the installation both as administrator and not as administrator - with the same results. I have tried all possible options in the registration window at the end of the installation process, including deleting the old registrations and re-registering both FSUIPC and WideFS - whatever I do I find that when I go into the module in FS either FSUIPC is registered and WideFS not, or vice versa - even though both registrations were apparently successful. I understand that I can use different addresses now, but the problem is that there are different names associated with those addresses. FSUIPC is registered for example under "John & Peter Smith", and WideFS under "John Smith" (not my real name!!). I had to give my brother's name for WideFS as we were using his simMarket account and his e-mail address. I have tried changing the name on the WideFS registration to "John & Peter Smith", but it won't accept that because it is expecting just "John Smith". I am now in a loop that I cannot get out of without your help. If it helps, we purchased FSUIPC on 14/04/05 (simMarket order 163148) and WideFS on 16/10/10 (simMarket order 665186). If you need our exact names, e-mail addresses or whatever I can send these to you by e-mail or PM. Please let me know. Really sorry to be a pain, but I really do think this issue needs to be made much clearer on simMarket. I have since seen the registration notes on the latest FSUIPC documentation, but it is now rather a case of shutting the gate once the horse has bolted..... Thanks for your help.

My brother and I have just purchased WideFS as we will be installing and running FlightSim Commander from a laptop which is networked to our gaming PC. We have had a registered version of FSUIPC for a number of years. When I try to register WideFS in the FSUIPC window the module refuses to accept the 12 character key we received from simMarket. It says it is not a valid 12 character key - but this is not true as it was copied and pasted from the e-mail. It seems to me that the cause of the problem is that we used a different e-mail address to purchase WideFS to the one used to purchase FSUIPC. We have several e-mail addresses, and we used the one that our simMarket account is registered to. However FSUIPC is linked to our joint e-mail address, and this is the name and e-mail address that appears at the top of the registration window. The registration window tells you to enter the 12 character key "using the exact name and address details you enter above". Presumably the key is being rejected because the name and e-mail address don't match. Unfortunately it is not possible to edit the name or e-mail address. I can prove that this is the cause. I decided to try to fool the system by modifying my FSUIPC key file to contain the name and e-mail address used to purchase WideFS. If I then try to register WideFS it will accept the key, confirms registration and tells me to restart FS. I do so and go to the FSUIPC window, and it tells me that FSUIPC needs to be registered! So I shut down FS again, go to my FSUIPC key file and modify it again to show the original name and e-mail address which are correct for the FSUIPC registration. I start up FS again, go to the module window and then discover that FSUIPC is registered but WideFS is not!! This is really daft. It seems that FSUIPC requires you to register both FSUIPC and WideFS using the same name and e-mail address. This is not a reasonable expectation, as it could be a number of years between registering each product and your e-mail address may have changed - or it could be a very short time but your e-mail may have changed for a number of reasons - or you had simply chosen to register WideFS using a different address. I have just spotted on simMarket that it states "FSUIPC3 with key issued to the same name and e-mail address is required". I presume this is what I should have read, but this is not very clear English at all - why can't it say that you need to use the same name and e-mail address used to register FSUIPC? Furthermore I have just noticed on the FSUIPC registration window that it says that WideFS registration is independent of FSUIPC registration, "but uses the same name and address when both are registered". Unfortunately you don't get to see this until you have already purchased WideFS and try to register it. This again is another case of rather unclear English - it says that it "uses" the same name and address, but doesn't make it clear that you need to use the same name and address when purchasing. So what do I do? Surely I don't have to purchase WideFS again using the correct name and address? If it's any use, I have FSUIPC 3.96 and WideFS 6.78. Please help me. Thank you.