Pete Dowson

Again, FS itself doesn't simulate transponder modes. The virtual airline programs Squawkbox and FSINN do, however, and you would simply program whatever keystrokes they need for their operation. FSUIPC does have a transponder control for Squawkbox, though, using its offsets for FS9 or its Simconnect client data for FSX -- its listed in the assignments dropdown. Pete

No. FS does not simulate these things. Some add-ons do, but FSUIPC is an interface to FS not to the add-ons. You'd need to write your own logic, or use one of the systems simulation programs like pmSystems, Prosim737, etc. Regards Pete

Is there an error mentioned in the log? Maybe there's a syntax error I missed? Enable FSUIPC's key and button logging, rerun the test, so we can see what is going on. The logic is okay, so it has to be something simple. Regards Pete

What were you logging? If it's using offsets you need to log "ipc writes". No, you can't write a plug-in to show more data than logging can show unless you know what the device is doing in the first place so you can read the right things. Regards Pete

Okay, then you'd need first to monitor what it is set to. Try FSUIPC's Logging tab, right hand side. Enter offset 07D6 as type U16. Check 2FS display2 or "Advdisplay2 below. FSUIPC will dsplay the value on screen. It's in metres. FS does these things, not FSUIPC. BTW, how come the add-on aircraft you are using doesn't work in any case? It should have been implemented with the autopilot already coded to work they way it should. Regards Pete

Why didn't you enter what i told you? It won't work the way you entered it. Pete

Er, in your MCP or Autopilot altitude setting display? How else are you checking what is happening? What do mean by "desired" -- I mean "set" or "requested". This is getting very confusing. Pete

Are you calibrating with FSUIPC? have you followed all the steps? It sounds exactly as if it is simply not calibrated. Evidently you are not doing things correctly, then. Please read the relevant section of the FSUIPC user guide and follow the steps. It is simple enough. FSUIPC's calibration maps points on your axes according to the values they provide. The only way changing values will not make chainging inputs to FS is by bad calibration. i don't get about much owing to my poor eyesight. If i can get someone to go with me I may just visit Lelystad again this November. I missed last years. Regards Pete

There's no default copy of XML.DLL. it is only created when needed to get Simconnect to load any DLLs. If the file is not already present, FSUIPC's installer creates one. If you have an installation problem, please post the entire Install log, without editing, as i cannot diagnose anything from the fragment you posted. Pete

There's not enough information here. First please make sure you are using currently supported versions -- check the versions against those listed in the Download Links subforum here and update if your out of date. Then after a test and failure shown, close both FS and Wideclient, and show me these files: FSUIPC4.LOG and WideServer.LOG from the FSX Modules folder. Wideclient.Log from the Wideclient folder. These are text files and you can paste them into a reply here. Regards Pete

What does it set the desired altitude to? Pete

I don't actually believe all of that. Yes, configuring it in FSX will never give you a reverser in any case. FSX doesn't support reverser axes. But assigning in FSX is identical to assigning in FSUIPC to the "Axis throttle" comtrols, in the normal FS controls drop down list, except that this bypasses FSX's sensitivity and dead zone sliders. Regards Pete

Yes. But why use this? Why not just assign to the AP ALT HOLD control, which holds at the current altitude (or nearest 100 feet, depending on aircraft I think)? Only the AP PANEL controls use the values pre-set on the panel. There are separate toggle, on and off controls too for Alt Hold. Regards Pete

Ah ... so the Elite driver is operating like a fly-by-wire controller. Well, we knew that. What we don't really know is what it interfaces to -- offsets, controls, what? Sorry, I really have no idea. I'd need both the NGX and your Elite controler to find out. Regards Pete

Just FSX internal poking around, chasing pointers and finding tables. Pete

Must be something to do with their implementation. Sounds like they don't stop the reversing capability of "ThrottleN_Set" controls, even though they override the forward settings for the different thrust modes used in Airbus. But it does bode well for a separate axis assigned to the "Reverser" facility listed for Direct to FSUIPC assignment. Regards Pete

No, no ,no. You are still confused. Sending to FS as a norrmal axis does NOT bypass FSUIPC calibration. The calibration is optional no matter HOW you assign. They are two different things. You can assign how you like and calibrate how you like. I honestly don't know how you got yourself so confused! All this is surely clear from the User Guide? Where is all this misunderstanding coming from? First off, just setting that option (UseAxisControlsForNRZ=Yes) will not change anything unless you select the NRZ option in the calibration. Second, any add-on that can only use the standard FS axis controls for throttle cannot have reversers controlled by such an axis, because the complete axis range, from -16384 to +16383 only provides forward thrust settings -- the idle is at -16384. As far as I know, the add-on Airbus reversers cannot be operated by a reverse zone on a throttle axis. I don't have or use any Airbus, but this is what people say. You probably have to program something to send Throttle decrement contros, like pressing F2. Regards Pete

Assuming you are calibrating using the NRZ option ("no reverse zone", it probably likes only Axis controls to be sent. Please look up "UseAxisControlsForNRZ" in the FSUIPC Advanced User's guide. No, that is absolutely not true! How have you misunderstood that so badly? Why would I bother providing an option to assign in FSUIPC if it meant you had to assign in FSX as well? Can't you see that makes no sense? If you assign in FSUIPC you must NOT also assign in FSX. "Send to FS as a normal axis" just means what it says, it uses normal axis controls sent to FS ad then intercepted by FSUIPC if you are calibrating.. The "direct to FSUIPC calibration" instead bypasses FSX and calibrates first. It's more efficient but it can defeat some add-ons. Regards Pete

How would the device control anything if you block its link to FSUIPC? Sorry, I'm even more confused by what you say. Surely stopping the control program doing what it does is the same as simply not running it? Are you implying, by the way, that their driver operates FS by writing directly to FSUIPC offsets, and not by sending FS controls and so on? If it is writing to FSUIPC offsets then you could, in a Lua plug-in, intercept these -- using event.intercept -- and make those writes do something else instead. However, this would affect all writes to those offsets, from all programs --- unless you connected on a Client PC through WideFS and had the Lua plug-in running there. Regards Pete

It took a lot of hacking into FSX code, and some major help from the FSX Followme author, Daniel van Os. I don't know if he'd be willing to share. Regards Pete

Yes. In fact each number is one byte of 8 bits, so has a value of 0 to 255 as Ian has pointed out. The whole IP address is therefore 32 bits. The representation as 4 numbers is only a convention. This is only for IPv4 -- the newer IPv6, introduced to allow a far greater expansion in the number of addresses, uses more -- 128 bits, or 16 bytes. They changed the way they are written to groups of hexadecimal digits instead of decimal ones, and use colons instead of points, for example:2001:0db8:85a3:0000:0000:8a2e:0370:7334. Regards Pete

Sorry, you've lost me. This 'Elite' device, I assume it connects to USB or COM port? And it has a driver? does it look like a Windows joystick, or what? Ah, so it interfaces to FS via FSUIPC? In that case, can't you program it in FSUIPC? If not ... In the past I have made drivers for specific hardware, but I can only do it if I have the hardware. I use tools to work out what the protocol is and then write the software to suit. But there is no way for me to do such a thing remotely. And it isn't trivial. If it connects via a serial port or a proper USB you can work it out yourself using one of the Serial Port or USB monitor programs you can buy. They aren't cheap, but they are good. The ones I use are by AGG -- see http://www.aggsoft.com/. Once you know the protocol you could write your driver in any language, or, yes, possibly as a Lua plug-in. The COM library can handle serial ports and some USB type devices -- but not all. It might need some additional library facilities if it doesn't look like a HID. I think you are looking at quite a lot of work though, and certainly it would need money for the tools. you need. If you are not a programmer you'd need to get someone else to do it for you. Are you sure the hardware is worth so much to justify thus? Regards Pete

Ah, thanks! Pete

I've obiterated your key and I hope I did it before any pirates found it. NEVER EVER publish your key! If it gets used by others I will have to invalidate it! The values shown in Axis assignment is that actually read from the joystick axes themselves. FSUIPC does not invent values to show you. So if they are misbehaving you have a bad joystick or joystick driver. Check it in the Windows control panel. In joystick calibration the values can come either from FSUIPC's axis assignments or from FS's axis assignments. So in that can it could well be that you have the same ones assigned in both FSUIPC and FSX. Do not do that. Use either one or the other, not both. You seem to imply that it only happens when the PMDG 737 is loaded. If this is the case, it must be something is wrongly installed or corrupted in that add-on, though I can't think how it could possibly interfere with the direct reading of axes in the axis assignments mode. What "innovation"? Two things there: with a 2700K and a GTX 580 you should be getting a lot more fps even with the NGX and triple-head screens. Are you overclocking the 2700K? You should be able to comfortably get 4.8 GHz with a reasonable replacement processor cooler. Many commercial PC builders supply such configurations already overclocked to that level, or close. Secondly, opening any secondasry window in FS will reduce your frame rates, even to half or less. And WideFS cannot help because you cannot place FS gauges on a second PC -- at least not without running two fast computers, both running FSX, and linked with WidevieW (not WideFS). FS gauges depend completely on FS code to support their operation, especially the graphics. This is why products like Project Magenta, SimAvionics, FSXpand, aeroSystem737 avionics, and ProSim737 are quite popular. -- they provide external instrumentation you can run across a network. The same has also been done in one add-on package with the iFly 737NG "cockpit" package,. Regards Pete

If your Server is 192.168.0.10, as appears to be the case, then of course it won't connect using 1 instead of 10 -- they are two different numbers (10 being 9 more than 1). Regards Pete