Pete Dowson

Did you try using an aircraft defined with a longer flight number? FSUIPC just reads a string value and, as the documentation tells you, allows up to 12 character including the zero. I've no way of proving whetherr that's enough or too much. How did you prove it? Because FSUIPC3 offsets 3130 - 3177 inclusive are all read-only. The flight number is read from a token variable and there's no way to write those. The SimConnect SDK does indicate that the same value is writeable on FSX, but even there I don't know if it actually works. I've never tried it. Regards Pete

Er, you are confusing me. You surely can't get such an error in WideClient whilst downloading it from the web! After all it is a ZIP file you download, which then needs unpacking and putting on your client networked PC. You only run WideClient on your client PC AFTER downloading it and installing it! The error you are getting implies that you are running the client on the FS Server PC. If, so some reason, you want both client and server on the same PC you need to set WideClient to use a different class instance (one of its parameters). The clash arises otherwise because both WideClient and FS are trying to look like FS to prospective applications, same as trying to run two copies of FS on the one PC at the same time! So, why are you doing this? Pete

Good. Glad you found it. I've got the same problem on one of three otherwise identical Zotac Zbox mini-PCs I use for various networked parts of my cockpit. Regards Pete

All FS controls and a lot more are available through FSUIPC assignments, but the names are not always obvious. they are the intrernal FS names extracted from the CONTROLS>DLL and used in the assignments XML file in your AppData folder. If you aren't sure of a name to assign to, enable event logging in FSUIPC then use the control via keyboard or mouse, then check the FSUIPC log. The FSUIPC implementation of PAN VIEW, if you assign the hat as an axis in the axis assignments, is reasonable. It may not be quite as smooth. Try it first and see. Regards Pete

Well it certainly needs support from the aircraft maker then. Maybe it's designed only to be used with mouse and keyboard? Isn't there any documentation? seems odd you can't use a throttle lever. Sounds like you need a set of buttons to me. You can of course use the range assignments for an axis and program different controls to be sent as the lever passes through different zones. Sounds like you need to do it that way. Arent their other users of this aircraft? Is there a Forum where you can ask? If not, try the FSX Forum here or the AVSIM one. Regards Pete

But isn't it the G940 you want to disable in FSX? What's the problem? Disable the controllers, obviously not the keyboard! The latter won't interfere in any case. You can't pick and choose which controllers to disable -- it's all or none. In Settings - Controls, just uncheck "Enable controllers" on the main "Calibration" tab. Pete

FSX does that if it finds spare unassigned axes and buttons.You just have to disable controllers instead. Pete

No, Saitek devices are not supported by anything specific in FSUIPC. Regards Pete

I'm sorry but I cannot possibly support such an old version. The earliest supported version is 4.70 and the current release is 4.742. No, in FSX you can move it by Lat, Lon, Alt, Heading, Pitch and Bank, and even airspeed (not possible before FSX). Use logging to check your work. But please get up to date first. Regards Pete

I see there's still no reference to the 64,17 button you were intending to use. I'm not sure why you are using keypresses in any case. Haven't all of the switches in the NGX been discovered and shown to be programmable via controls or L:Vars? Check the postings in the User Contributions sub-forum. It is usually best to avoid using keypresses wherever possible. "U" lines are executed when you release a button, "P" when you press the button, so you can delay re-pressing it for as long as you like. Possibly you really mean a delay between the sending of two separate keystrokes by the one button press or release? If so, then, no, not without using a Lua plug in. You can use delays quite easily then. Regards Pete

Well you can program both initially in the Button assignments in FSUIPC. Just toggle your "virtual button" so that FSUIPC sees it, assign the Shift F4 key press to both "press" and "release", then edit the INI and duplicate the release line (U64,0 ...) with a new sequence number, and you are done. Why are you using a Flag? The change of a button from 0 to 1 is called "pressing" the button, and from 1 to 0 is "releasing". Or for a toggle, "on" and "off" respectively. What is the flag for? And if you are using 64,17 as you say, why do your parameters refer to 65,17? I can't work out what you are trying to use flags for. And the above doesn't make sense at all, so I can't even guess. Regards Pete

One just arrived and I replied. Pete

Hmm. sorry, from that information I have no idea. Wideclient does trap errors in its own code and log them, but i know it cannot trap errors caused lower down, by crashes in the network code or driver in Windows. First, though, could you try the latest version of Wideclient, 6.899h, from the download Links subforum. Also see if you can get more information, like which module and the memory address. You might need to look in the Windows event logging for that. Regards Pete

Can you change the flight number by writing to that offset? I don't know. If you are talking about FSX (you don't actually give any context), then what you write and what you read may be different if simConnect either doesn't use what is written, or takes a little while to do so. Use the FSUIPC Monitoring facilities (on the Logging tab) to check. in this line ipc.set(fltn, ipc.ask ("Enter flt.no. for simming")) the name of the variable you want to set as a Global needs to be a string, i.e. "fltn", as defined in the documentation. Here, the global variable you create will be named by the string value of "fltn", which is probably 'nil' or something like that. Why not just do fltn = ipc.ask ("Enter flt.no. for simming") Regards Pete

I don't think you can any more. You'd have to go for Lockheed-Martin's Prepar3D -- L-H bought the ESP source license from microsoft when MS stopped development. Check http://www.prepar3d.com/. Regards Pete

Does the aircraft work with FSX generic thorttle assignment? Have you tried using the FS control instead? some aircraft rely on intercepting the FS control -- you may be bypassing that detection. I'm afraid those mean nothing to me. I do not know the aircraft at all. I'm sorry, but I'm lost with all that. What is "their detent" you "release" them from, and what is "cruise detent" meant to be -- what throttle value? Sorry, no. I really have no idea. All FSUIPC assignment and calibration does for you is manipulate the numbers sent with controls. The standard Throttles controls are AXIS_THROTTLE_SET (the generic all-engine one you seem to be using) and AXIS_THROTTLEn_SET (where n=1 to 4). Those are what FSX itself sends if you assign there, and you could do the same in FSUIPC. If your aircraft works with FSX assignment, I'd start in FSUIPC doing it the same way. Otherwise you need to find what values are needed by that aircraft for its various throttle positions or ranges. Regards Pete

It sounds like you have the toe brakes set the wrong way round. Try pressing them both fully down, see what happens. Most toe brakes available these days seem to operate with the axis values DECREASING from a high value when pressed, down to 0 when fully pressed. If so, you should have noticed this when calibrating. Zero braking is a zero value, maximum braking is a high value. Any axis which is behaving the opposite way to how it is needed has to be reversed. In FSUIPC's calibration -- there is a "REV" checkbox for this.Re-calibrate AFTER selecting REV or the values will be wrong. Also, as with any axis, leave a gap before setting the minimum value, to ensure that the brakes stay off even when steering using the rudder. Pete

The INI parameters look fine, nothing wrong there. It's a little odd how you've used a different assortment of entry boxes for the assignments -- generally folks just use the first one unless they need to assign multiple controls to the one axis. Perhaps you thought there were 4 entry positions to relate to engine numbers? That isn't so, there are simply 4 so you can assign up to 4 controls if you wished. However, it doesn't do any harm to do what you've done. When you say "the levers move appropriately in response to movement of the controller levers" do you mean FS's pictorial quadrant levers move when you move the hardware throttle levers? If so, then the levers are correctly operating the FS throttles -- so now I think you need to explain what exactly you meant by the earlier statement that "any aircraft I select will not respond to increasing throttle input." If you meant something different, please explain what you did mean. And in that case have you tried using the keyboard and mouse to see if the FS throttle levers respond? Regards Pete

This is with default aircraft too? Do they respond to throttle changes via the keyboard? When you display the throttle quadrant on screen, do the levers move there? By mouse, keyboard, throttle levers? If your throttles are properly assigned (you don't say how you assigned them -- there are several different ways and different controls) and are seen to provide properly varying values in the assignments tab and the relevant calibrations tab, then there is nothing stopping them in FS. Please provide more information, and also the version number of FSUIPC. If it isn't at least 3.99 you need to update first. Regards Pete

Yes, I see it. You are either using an old version of FSUIPC (current is 3.998g, but any version since 3.99 is supported), or, more likely, you are making a mistake entering one of the fields. All parts -- name, email and key, must be EXACTLY correct. Cut and paste is best to avoid making errors. But you have found 'them' (me actually) -- you are here! Pete

I assume you must mean 4.746. It sounds like you are using a throttle assignment and calibration which uses a Reverse zone, but the aircraft doesn't support reverse of the throttle axis. More information is needed really: Throttle assigned in FSUIPC as well as calibrated? If so, assigned by which method (direct or via FS control?), and if to an FS control, to which, the Axis Throttle Set control or the Throttle Set control? Where are you calibrating: page 1 in the tab (next to ailerons, elevators and rudders)? Or the 4-throttles page? If the latter, have you tried setting the "no reverse zone" option? BTW this question has arisen before, but unfortunately, so far, after advice the posters haven't returned to say whether or how it was resolved. Check these threads: http://forum.simflig...hrottle-control http://forum.simflig...ne-jets-ch-yoke http://forum.simflig...x-2-with-fsuipc Pete

The normal way is to assign THROTTLEn_DECR (or THROTTLEn_DECR_SMALL) for engine n. The "F2" keypress used by many is simply the generic all-engine equivalent (THROTTLE_DECR). Have it repeating whilst pressed. If you want full reverse as soon as you press the button you'd need to assign to a THROTTLEn_SET with the parameter set to -16384. But this may not work with all aircraft. Regards Pete

I think you are misunderstanding. The FSUIPC PTT controls use Roger Wilco messages, not keypress or button operations. That's the whole point, to bypass those and send messages direct. There's nothing to do in SB. I cannot possibly support such an old version, sorry. The minimum supported version of FSUIPC is 4.70 and the current release is 4.745. That is not generally a good idea and there's is no reason for it. The logs you show are not relevant and show nothing wrong. The messages for PTT (and PVT) are sent automatically by FSUIPC and by all connected WideClients, but by running SB "as Administrator" you are probably preventing those messages getting through. Please update to a supported version if you want further support. Pete

Since this new software works using the WideFS protocol (i.e. is serviced by WideServer in the FS PC), and since WideFS cannot supply L:Var reading facilities even to PC clients, except by invoking Lua plug-ins to write the values to offsets and reading those, there's really no chance. The software described in this thread is actually a moving map, a WideFS version of FSXFollow, as it says. It is not an FSUIPC interface. FSXFollow needs its own module installed in FSX to service it, whilst WideFSMap just needs WideFS enabled on the FS PC, and so can work with all versions of FS since FS98. If you are capable of writing programs for the iPad/iPhone/iPod, then you could do it easily enough using a Lua plug-in on the FS PC to read the L:Vars and provide a service over the Network on a selected TCP/IP Port, and connect to it to receive the data on the iDevice. Evamples of using the Lua sockets library are included in the Lua plug-ins installed with FSUIPC -- the example provided actually links up two copies of FS, one running as slave to the other. But the principle is the same no matter what the data or how it is used. Regards Pete

It sounds like you have a button or dial which is constantly flickering on and off. You need to find out which it is (use Button logging or check in FS assignments if you can't read it in FSUIPC), and either get the device fixed, or use the "IgnoreThese" facility in the FSUIPC INI file -- searching for that in the Advanced User's manual. You could of course find out which device it is by unplugging them one by one, but in case when plugging them back in windows changes ID numbers on you, it would be best to change FSUIPC to using joystick lettering instead if you've not already done so -- see the User Guide section entitled "Keeping track of multiple control devices". You could also first try pushing every button, operating every switch, and turning every knob, a few times each, just on the off-chance that it's a partial contact which will clear itself by action. Regards Pete