Pete Dowson

You want multiple screens showing the scenery / outside world? One PC can usually handle two or three screens quite well. If you spread scenery views over more than one PC you need something like WidevieW or OpusFSI to coordinate the separate FS installations. My programs, FSUIPC and WideFS, don't deal with those aspects. WideFS enables FSUIPC-based applications (various utilities) to be run on a separate PC, but nothing of mine coordinates separate FS installations. Pete

Worth trying. If you assign anything in FSUIPC (buttons or axes) you should assign them all there, and disable the controllers in FS. Otherwise you'll get conflicts. Pete

On the calibration tab, or on the FSUIPC assignments tab, watch the "IN value as you move the stick. If the number there does not change as you are moving the stick through your 'dead zone', then either that part of the movement is dead IN THE HARDWARE, or the changes are too small to be seen by the Windows driver! here's nothing any software can do to make the hardware give more than t is capable of. Maybe you have a faulty device? Are you assigning in FS or in FSUIPC? Pete

The -500 to +500 is so small (1/32nd of the travel) that it is hardly likely to be noticeable. But if you want a linear response why on earth have you selected a slope? That's much more likely to be the problem. And if you are assigning in FS, don't forget to set the sliders there correctly -- maximum sensitivity, minimum null zone. FSUIPC never changes the values in the INI file by itself. You'd need to go into the Calibration settings and do something there to change them. Do you really mean the IN and OUT values on the left in the calibration tab? Unless you are trying to fiddle the calibration to do something completely out of the ordinary (like limiting the amount of control you get) you NEVER need to edit calibration values directly in the INI file. ALWAYS use the calibration tab in FSUIPC options. One of the options on the calibration you have selected. You'll see it checked there. I'd need to look up the code to find out ... let's see:... ah, yes, "Filter". You have the control filtered! Why? That could actually make it a bit sluggish as it has to average readings over a number of steps each time. It's only for circumstances like a very jittery device (dirt?0, or poor power supply making the readings vary because of voltage changes. Pete

Flying without autopilot engaged always means keeping your hand on the controls and making little adjustments all the time, even if you properly trim. With autopilot engaged the trim will be adjusted by the aircraft to climb, descend or stay level according to your settings. In any case, please note that this forum concentrates on support for my software --mainly FSUIPC and WideFS. For general questions about flying techniques you do really need to check other more general forums. Pete

Oh dear. You need to install a current version of FSUIPC4 -- the earliest supported version at present is 4.943. Version 4.929 pre-dates the release of FSX-SE by about nine months, so it couldn't possibly work with it! Pete

4.942 was the previous version -- you said you had the "latest". I was only pointing out that 4.943 is the latest! ( It's just a little annoying when folks always think the version they actually have is the latest without first checking). All of which isn't so relevant. The facility to assign custom controls has been in FSUIPC for a long time. You'll find the selection near the top, or even at the top, of the button assignments list -- where you assign things to buttons in FSUIPC. Please do check the documentation. There are pictures too to show you what the various tabs in the FSUIPC options look like. First, though, you need to find the custom control number, which is in the PMDG installed stuff, in the .h file in its SDK. I don't use any PMDG aircraft so I cannot help there, sorry. Pete

The updated version has facilities for controlling pretty much everything by assigning to "custom controls" You'd need to look up the function you need in the Header (.h) style document, in the 737NGX SDK folder I think, then assigning that number to your button using the <custom control> assignment facility. BTW the currently supported version of FSUIPC is 4.943. Version 4.942 is not the "latest". I think that's where FSX stores its own assignments. No need to go there -- there's an assignments dialogue in FSX for that. However, it doesn't cope with custom controls. Pete

Please use the Support Forum in future! The ANNOUNCEMENTS subforum is for Announcements! FDC? Flight Deck Companion? I don't know it. Why deleted? Is it relevant? FSUIPC does not touch anything else in your system, only creating the Modules folder in your FSX folder, and placing ther the FSUIPC4.DLL and documentation. You only need to delete it. It is listed in the DLL.XML file, but that is only so it will get loaded. If you delete it it will not load. And what error is that? would it be better to resolve that instead? Pete

I tend to taxi around 20-25, so with such a low cutoff I couldn't use the tiller. Are you only taxiing at about 5 knots? A cut off at 20 means it's already down to only 50% effective at 10 knots. Pete

There are several possibilities: 1. Yes, possibly a faulty rudder axis (maybe just a dirty pot which could be fixed with electrical switch cleaner). 2. A conflicting assignment for the rudder axis, though since you say a "twist" removes the jitter, this seems unlikely. 3, A dodgy USB connection, or USB hub. However, I would have thought you had more than just the rudder on that connection? If the jitter is just around the centre position, just calibrating with a larger dead zone there would help -- many pedals don't always return to dead centre after use in any case, and this would help with that. If using FS assignments the dead zone facility there does the job ...but, better, when assigning in FSUIPC, instead just set the two "centre" calibration values further apart. Pete

If you assign and calibrate both tiller and rudder in FSUIPC then FSUIPC automatically takes care of the gradual transfer of effect from one to the other, tiller winding down from 100% at 0 knots GS to 0 at 60 (by default), whilst the rudder effect is increased from 0 to 100% at 60 knots. At 30 knots they would be 50:50. This is all documented for you in the FSUIPC documents, and there you would also find that the 60 knot value is user settable by parameter in the INI file. FSUIPC's tiller actually uses the rudder -- they BOTH control only the rudder, not the nose wheel -- there was no nose wheel steering option in FS9 and before, and this facility dates way before FS9. The only thing making the two rudder controls different is how you calibrate -- obviously you would calibrate the steering tiller to have more effect with smaller movements. Since they are both only using rudder, there's no way this can contribute to a wheel getting "violent movements", so I think you can only ascribe that either to you assigning to the FSX steering control, which FSUIPC does not calibrate or interfere with at all, or there is something wrong with the aircraft model you are using. Pete

I don't know what PFC equipment you have -- all mine is either serial port driven using my own PFCFSX.DLL driver or USB but needing my PFCHID.DLL driver. I suspect the stuff you have is pure USB Joystick type hardware, which needs no special drivers and is recognised by Windows as joysticks in any case. I don't use any PMDG aircraft, but I think most users fund they need to assign throttles to the normal FS controls, even in FSUIPC, and NOT calibrate in FSUIPC either. I think they may even program reverse on a button assigned to "throttle decrement" controls. But don't take my word for it. Ask around. What are all of the other buttons numbered 0-6 or whatever? Are there missing numbers? You are really not providing any technical information I can use. When you assign this non-working button, what is entered for it in the INI file? When you've programmed it and go back to look in the assignments, has it mysteriously lost its assignment? Sorry, but I cannot see your PC from here and you are not providing anything I can help with. Again, sorry, but I've never heard of a "PFC hardware configuration tool" and have no idea what on Earth it may be doing. I'm afraid you are most certainly dependent upon PFC support for that side of things. i worked closely with PFC years ago (my cockpit was built by PFC), and produced the drivers for all their kit a while back, but I've no idea what they've been doing recently. I thought their current stuff was either standard Joystick USB, or, special USB (with displays as well as inputs, like their consoles and radio stacks), which would use my PFCHID driver. Pete

Yes, that is possible I suppose. No, multiple assignments to the same button can't be changed or edited in the dialogue. But if it works as you wish it to, no problem, eh? Pete

Sorry, I've no idea. If two programs both on the same PC report different things for the same data, then it cannot be any of WideFS, FSUIPC or FS, it must be the individual program. It sounds as if it is just using zeroes for everything. Without more information -- logs in particular -- I can't really help further. Sorry. Pete

If it is all standard USB joystick-style connection, then it is a matter of Windows seeing it properly, not FSUIPC, because to FSUIPC it will just be another Windows joystick. Does FS see them all? That's just a matter of numbering conventions. FSUIPC has always numbered buttons from 0, same as Windows does internally. Other programs simply add 1 to the button number as they assume folks won't understand numbering starting from 0. Why do you think it is so "important"? The buttons could be called Ginger, Fred, Alice, and so on, as long as when you assign them they stay consistent. I don't understand your angst. Sorry, that does not follow. Program button 7 and your "button 8" will do what you ask. There's no "consequently" about it! Modern joysticks ARE all USB devices, so that makes no sense. You can assign wherever you like, but don't mix. Either everything in FS, or everything in FSUIPC. It doesn't matter unless you want different assignments for different aircraft, which FSUIPC can handle automatically and FS can't handle at all. If you assign in FSUIPC, disable controllers completely in FS. That depends on what you are using it on, what addon aircraft. Some add-ons do not like the "direct" method. Otherwise, that is more efficient, that's all. There are some options only available "direct". Do please peruse the documentation installed in your FSUIPC Documents subfolder! Pete

What does FSUIPC display it as in the button assignments tab when you press that button? In the Windows system it is defined as: VK_OEM_WSCTRL 0xEE (EE is 238 in hexadecimal). I don't list all the esoteric keys found on non-UK/US keyboards, but every value 0-255 is used I think. Pete

Not if you are simply doing the action once, with the plug-in being assigned to a button or keypress. Think of the plug-in as a sequence of commands as in a BATch file, or a Visual Basic script. Depending on what you need it for you can turn it into a continually running program, based on events, and have it loaded automatically (even according to aircraft profile) using the [Auto] sections of the FSUIPC INI file. You do really REALLY need to look at the Lua plugin documentation and the examples in your FSUIPC Documents folder. Yes. Such information is easily found in the Offsets Status document. Why not look? Pete

Hmm. In that case I did not understand your question in the first place. Sorry. Pete

Closer, but 66C0 will not work as it stands as it looks like a decimal 66 with C0 stuck on. It's a hexadecimal number and needs 0X in front of it (or quotes round it). ipc.writeUW(0x66C0, ALT_set) If you had started out just stating what it was you were trying to do, which you still haven't done, it might have been quicker. Why do you want the value in an offset in any case? Pete

No! Please please do read the Lua library documentation! The event library is there to call a function in the Lua plug in when something happens! event.offset("66C0", "ALT_set") is actually wrong in any case, You missed a parameter out! which specifies the type of value being tested. A more correct line: event.offset("66C0", "UW", "ALT_set") would tell FSUIPC to call a function called ALT_set when the Unsigned Word at offset 66C0 changes. You have no function called ALT_set and you are not writing anything to 66C0. I think you are completely out of your depth, or just haven't actually studied the documentation or any of the many examples provided for you, to help. Writing to offsets is done by other functions in the ipc library. Please go and look them up. Pete

The INI file has all Button assignments in sections called [buttons], obscurely perhaps? :-) There are no separate parts just for FS controls as opposed to FSUIPC direct or offset assignments. You have to check the button (actually a checkbox) yourself -- you choose whether to assign to FS control, direct to FSUIPC calibration, or to offsets. It's part of the USER choices offered! Please please please refer to the User guide, in your FSUIPC Documents subfolder! Pete

There are no 'normal offsets" for L:Vars! The L:Vars are LOCAL to specific gauges. I cannot include in FSUIPC a general facility for all possible LVars in all possible add-on aircraft! As you've already been told, you can READ or WRITE LVars, once you know their names in Lua plug-ins. If you need a value in an offset, write the result of reading one to an offset. I already told you this, and I also told you that you can use the offsets 6C00-6CFF which are reserved for general uses like tihs. Pete

Er, where are you "returning" the value to? I have no idea what you are attempting to do. Pete

You'd need to write it to a User Offset (one in the range 66C0-66FF). There are Lua ipc Library functions for writing to offsets. Pete