foreigndevil

I am not 'accusing' you of anything, just stating that the user guide, IMHO, is not written for the average user. And yes, I'll try to get things sorted out by trying different Saitek drivers and getting them to work in FS first. But don't tell me I got in this mess because I didn't follow 'the simple steps' in your user guide. I did and it didn't work. I'm not blaming you or your program for this, I just wanted some more information to understand what was happening. So, indeed, let's be sensible. I'll try to work out the faulty reactions of the hardware and then try assigning in FS and (maybe) FSUIPC again and will contact you again if there are more troubles then. I suggest you close this thread.

Okay, now it's clear to me, the axis is just a letter assigned to the action lever/button. That's what I wanted to know. I can understand that you don't understand what I try to find out because for you this is all very simple and logical. After all, you created FSUIPC. But try to understand that some people don't understand your FSUIPC 'language' because it is completely 'alien' and not at all 'obvious'. Most FS users are used to plugging in the USB device and play, they're not familiar with what axis goes where and why. It is all done automatically. I'm one of those. When I read your user's manual, I see it was written by a programmer for people with at least some knowledge of programming. It is not written for the average user who for some reason or other gets into trouble because the hardware doesn't do what it is supposed to according to the FSUIPC manual. Too little explanation makes one look for more detailed explanations and that's what I'm trying to do. Don't worry about me complicating things, I don't. It's just that we didn't understand each other because we see/look at things differently. I'm not a computer illiterate, just an FSUIPC one. And yes, I can always go back to my plug-and-play CH yoke and throw away the throttles and FSUIPC (would be quite a waste of money) but I'm pretty sure I'll get them working somehow.

Thanks for the explanation. Some of it is clear to me, some of it is not. I'm not familiar with programming and need to learn the basics. What I meant by the throttle 'values' is indeed "something like +16384 and -16384" but they are different for both throttles, one has 0 and 16384 for instance, whereas the other has "something like +16384 and -16384" (and they may change each time I try to calibrate but they are never identical). Then, when I move the handles to set the axis in FS, the axis Z, Y or X is created automatically, nothing I can do about it and one throttle becomes Z/Y, the other X. What I don't understand is what this axis actually means, is there a connection between how they move and the type of axis, in which case I would logically expect the two throttles to use the same axis (and they never do). There is also the throttle axis and the axis for each throttle individually. Do I assign all three or just the two individual ones? Maybe the throttle axis is for only one throttle? I have tried both ways and no luck. And should the first one have an X/Z axis and the second one Y or what would be normal? I have downloaded 'new' drivers for the Saitek throttles from their website that should get rid of bugs and will see if this changes things. It seems I have a lot of work and study ahead to assign a few buttons and handles:roll: Thanks for taking the time anyway.

I would expect that there is a slight difference in reaction speed between one throttle (T) and the other (that's indeed realistic), but I can't understand why in the FS aircraft one moves forward and one stays in place or why they have only two positions: full open or full closed (no way to get them somewhere in between). The yoke and quadrants are made for FS, so, that's not the problem. But I guess that if you heard about an erratic buttons fault, that's exactly what I'm experiencing! The reason why I bought FSUIPC was to get the controls to work as realistic as possible. Now I feel I'd better not bought the quadrants nor FSUIPC. Anyway, I'll look for help elsewhewre, starting with Saitek. But there's some clarification I need from you: when trying to set the T's up in FSUIPC I notice that the values for each of the T's are different from one another; is that normal? shouldn't they be the same? also which axis goes with which throttle (they also differ)?

I start to believe it is impossible to use throttles in FS! I spent some more hours trying to get them to work without success. :( If they work it's only one that reacts normally, the other one is just too slow. I've tried deleting the Saitek throttles and using two levers on the CH Yoke as throttles and they react a little better (i.e. the second one reacts a bit faster) but I cannot get them synchronized. I've tried setting them up in FSUIPC but they just stop working after a while. If I change something, the throttle action gets connected to the raise/extend landing gear and the cycle view function (I've deleted these functions from both the yoke and throttles many times now, only to find that they always come back! FS should be fun but this is getting into a nightmare. Can you please give me plain and simple instructions on how to set up the throttles (what axis, what values go where, etc.) to make them work simultaneously. Thanks.

That last remark is very helpful. I didn't know how to set those sliders and left it up to FS but then it wouldn't work well. I then tried to set them in another way but also without good results and clicking the 'reset defaults' button wasn't helpful either, because then I had to re-program every axis and button again! Going to try this suggestion now! Thanks!

According to the FSUIPC user guide I just had to move the .dll file from the Modules folder, which is what I did. I spent the whole evening trying to get things working using only FS assignments. Got rid of the yoke TPM assignments but still have problems with the TMP on the quadrants. It seems I can only get one T to work properly, whereas the other responds too slow or does something it shouldn't do if I change something. The last stage was that I got them working (sort of), but the engines didn't get enough power when I pushed the throttles. I'm probably doing something wrong but I had expected it would be more straightforward to program them. I'll just keep trying some more, using FSUIPC this time.

Yes, I know but it doesn't work. I'll uninstall FSUIPC, then try to delete the assignments again, re-assign the quadrants in FS again and then see if they work. After that I can try to install FSUIPC again.

I've tried to set up using FSUIPC first but also tried in FS without using FSUIPC. I haven't installed the Saitek control manager because I read somewhere that it's better to use FS or FSUIPC (I did install the Saitek drivers). Maybe the CH yoke and Saitek quadrants are not completely compatible? What puzzles me most is that the TPM handles on the yoke keep working even if I delete the assignments in FS.

I'm trying to set up my CH yoke and pedals and 2 Saitek throttle quadrants. I've tried using the User Guide, the downloadable manual and the FS control set up, all to no avail: I always get the same problems. :( Here they are: I can set up the Saitek quadrants to use as throttles (T), mixtures (M) and props (P) but I cannot delete the same TMP assignments on the yoke. When using the Saitek controls I may get one T to work properly, whereas the other may work (too late) or may not work but usually makes the gear extend (an assignment that is not controlled by the quadrant); the M's and/or P's may do the same or they may change my view from VC to outside etc. The yoke controls work as they originally did (without the Saitek quadrants) but then I don't want the yoke to control the TMP's. Is anyone using the same configuration and is there a solution for this? I'm an average pc user (not a programmer) flying FSX Acc on a Vista 32 pc.

Thanks. I had only entered my surname without entering my first name! :oops:

I've just bought and installed FSUIPC for FSX from Simmarket. When trying to register a problem occurs: when I fill in my registration key it is not accepted! :?: How can I register?