Pete Dowson

You must mean your program will, not FSUIPC. FSUIPC is not formatting anything for you. Since it must be your code which is formatting the values, it has to be your code which determines what format to use, surely? And is the country of origin of FS relevant? Surely it is the locale of the user which is relevant. Windows provides these facilities, not FS. Regards Pete

Download it and install it. There are instructions. It is easy. Pete

If the installer couldn't find the FSX.CFG file it couldn't have found or created the DLL.XML file and so FSUIPC4 couldn't have been loaded by SimConnect. If FSUIPC4 isn't loading then WideServer cannot run, which you seem to have disproved by posting its log. Pete

The server is fine. If there's no WideClient log then you haven't run WideClient, which explains why it cannot talk to the server. You need the client program running in the client else they cannot talk to each other! :roll: There's just nothing happening and I can't figure it out. Help or ideas, please. Thanks. Why not try running the WideClient program on the client PC? If there's a problem then, show me the client log file. Pete

Yes, but that was with an application, wasn't it? When WideClient doesn't have much to do the exchanges with the Server are simply to maintain contact, so it just sends a frame every so often (a few seconds I think). The max of 2 fps was during the initialisation, exchange of identities etc. This is why i said that if the problem was to do with buffers or memory leaks it should last a lot longer with no applications. That was the reason for that comparison. Well, we knew if wasn't from the original logs i think. It is just that most of the time it is not in control -- something low down in Windows/Network stuff is. That's where it is stalling, or almost -- in fact just going so slow that applications give up.. But I already suggested this (well 100 mbps), rather than Auto? Please check back! No, nothing except what I explicitly suggested you tried!! How did you miss it? Here, I'll quote it again to save to looking all the way back! (Please do read things else I'm wasting my time). There is one hardware setting which can cause problems for some folks. I was reminded of this over the weekend in Lelystad: sometimes the auto-sensing "media type" property on the Ethernet card/device doesn't work so well. Again device manager - properties for the device - "Advanced" tab - then the entry called something like "Mediatype" or "Link speed and duplex" or "speed/duplex settings". It's usually set to "Auto" or "Autosense" or "Auto negotiation" or similar. Try selecting 100 Mbps full duplex instead (both ends). Why? You haven't been messing with it, have you? There's nothing you can do in there, except possibly set the preferred protocol. Pete

Why are you "running as admin" and why "winXP/SP3 compatibility"? You should just run FSX native, at normal privilege levls. Who told you to do otherwise? The log shows lots of repeated button activity, lasting 4 minutes -- did you forcibly terminate it then> What showed in the Joy/Button number displays top centre? Did you actually press any buttons? Does it "recover" if you pull the joysticks out? I've actually never seen anything like that -- it seems to get signals from a number of joystick devices (#3, 4, 5, and 6). Are they all real? 4 devices connected? Loads of signals emanating from them! Regards Pete

Does it last longer with no client applications, or just the same? What is the frame rate without any applications? Whether a queue builds up fast or slow would depend on that, not on the application actions per se. Wasn't that at the end, after you terminated WideClient, or when it appeared to freeze? Not much to it. Where you have "Protocol=TCP" in the Client INI, or "PreferredProtocol=TCP" in the Server, change "TCP" to "UDP". Eras far as Networking in Windows in concerned, I know only as much as most others. In fact less than many. All my Network programming has been standard Microsoft server/client code lifted direct from their examples. And my hardware experience of Networking has been relatively limited simply because it has always worked on all my PCs, right back since Windows 95/98 days. I don't know why it works nor why it doesn't. For me it remains a matter or trial and error. In your position I'd just keep trying things till I found out what it was. Regards Pete

The fact that they connect and work happily for several minutes indicates that there's nothing wrong with the basics. The operating systems you are using are obviously fully supportive of the facilities needed. It's something else. If things work okay for a time and then don't, it's got to be one just a few things (at either or both ends of the link): 1. A build up (queue) of requests not getting processed for some reason 2. A memory leak in one or the other PC with gradually removes the ability of the network drivers to assign buffer space. 3. Some sort of power-saving action caused wrongly by something not registering the usage. 4. Some other hardware incompatibility or setting which causes any of the above. Did you try the UDP protocol? I don't recall. If not, try that. Does it still fail? If so, does it last longer? UDP has less checking and therefore no retries. If the build up and blockage was being caused by failures and retries, then UDP should see less of these, so last longer. If this is the case i'd suspect the hardware, the cable, or some hardware related settings being incorrect. Memory leakages can be checked by monitoring, from time to time, the resources being used as listed by the Windows task manager. The only power-saving setting i know of is in the Ethernet card/device's properties: find the device in device manager, select its properties and find the "power management" tab, turn off the option for Windows to save power. There is one hardware setting which can cause problems for some folks. I was reminded of this over the weekend in Lelystad: sometimes the auto-sensing "media type" property on the Ethernet card/device doesn't work so well. Again device manager - properties for the device - "Advanced" tab - then the entry called something like "Mediatype" or "Link speed and duplex" or "speed/duplex settings". It's usually set to "Auto" or "Autosense" or "Auto negotiation" or similar. Try selecting 100 Mbps full duplex instead (both ends). I can't think of anything else. Maybe others can. Regards Pete

What has this got to do with Any Lua program? Have you never assigned any of your joystick buttons before? To assign a joystick button or switch you have to press it! When FSUIPC recognises it, the assignment tab will come alive, show you the joystick and button number and allow you to assign to it. None of that has any relationship to any Lua facility at all (in fact none of the rest of your message does). You seem to be very confused. If you want to assign a key press to the Lua action, use the Keys tab, not the Buttons and switches tab. The Buttons and Switches tab is for assigning Button and Switches. Use the Keys tab to assign Kerys. (The clue in in the names on the tabs ;-) ). They will be until you press a button or change a switch so that it knows which one you are assigning to! Regards Pete

Try it in Windowed mode (ALT+ENTER switches between full screen and windowed). If it then works, you have a video driver problem. Find a better driver for your card -- don't use the default one from Windows 7. Pete

240 functions with a 3-position selector? does it have 80 other buttons, then, to give 3 x 80? It sounds like you need the documentation for the device itself, or possibly its own CH software? I'm not sure why that would come into it in any case. Regards Pete

Hmm. without writing a program to ask Windows to restore the focus to the program concerned, and maybe also "bringing it to the front" (set foreground window), I don't think anything WideClient can send to it will do. Why? What do the program do with ALT+Space+Enter? That's a new one on me. I didn't think windows supported anything like that, with two normal (non-shift) keys. Well, those wouldn't do ALT+Space+Enter, but ALT+Space, then Enter on its own. Is that what you wanted? If you want them altogether you'd need to hold the first two whilst pressing the Enter then release the first two. How would you know? What happens when they are sent ALT+Space, or Enter, on its own? Are these documented functions in their lists of keyboard commands? A program which doesn't have the focus and isn't in the foreground cannot easily make itself so. It is the User's prerogative what windows are active and seen. Programs CAN be cleverly programmed to get into the limelight on requests other than by using the real keyboard or mouse to activate them, but i suspect the ones you are dealing with never thought of adding such functions. Maybe you are thinking of trying to get Windows to activate the programs. But sending keypresses to be processed by the program's own message processing doesn't accomplish that. In fact i really don't know how you'd accomplish it without cooperation from the programs themselves, or writing a program to try to force the change. That said, I did manage to get a Lua facility working ( ipc.keypressplus) which is able to switch focus to FS from another program, and, more importantly in this context, from FS back to the original owner. It's a messy business and I'm not even sure it works in all circumstances, but I suppose it could be tried. It would have to be an additional facility in WideClient, a "special" like the PTTs. Regards Pete

If you get FSX crashing without FSUIPC being there, then it cannot be from FSUIPC. If FSUIPC is not loaded and running it cannot crash, obviously. Your pictures are pretty but totally unhelpful I/ afraid. I need the log files from the Modules folder, and, since you evidently know how to make a SimConnect log, that too. I'll need to know what add-ons and add-ins are running, and what you do to create the problem. i would also like to know what happens if you use the latest interim update from the Updates announcement above. ZIP up files and send them as attachments to me a petedowson@btconnect.com. But I only want to know about FSUIPC, not the crash you get when FSUIPC isn't installed. You'll need to look elsewhere for that. They may well be related of course. Regards Pete

Some aircraft panels have the aileron and rudder trip controls and indicators on screen. Okay. Maybe with that aircraft you are really supposed to have them dead centre in any case. Really you only use either trims in an engine out scenario. Well, these things aren't really preset there. It sounds like there's something in the Flight file you are using which has them offset. Best thing to do is centre them exactly and save a flight. Use that flight to start with for that aircraft. If you don't assign any joystick axis to them then you don't calibrate them -- there's obviously nothing to calibrate. Unless you want to use those trims (e.g. you are planning to try emergencies like engine failures), then I'd recommend just getting them to zero and leaving them there. Probably thee easiest way to be sure (assuming you have no panel trim indicators) is to edit the values in the FLT file -- look in the [Controls.0] section. There should be two lines: RudderTrim=0 AileronTrim=0 There are FS controls you can assign to buttons or keypresses (via FSUIPC) for trim adjustments (Aileron trim left, Aileron trim right, Rudder trim left, Rudder trim right), but without a good gauge showing you the values/centre, they won't really help. You could get FSUIPC to display them for you -- Logging Tab, right-hand-side. Enter offset 2EB0, type FLT64, and offset 2EC0, also type FLT64. Check the "FS window" or "Advdisplay" option below, and OK. The two values (aileron trim and rudder trim) will be displayed on screen. 0.0 is centred. the values are in radians of deflection angle. Regards Pete

It doesn't matter how the throttle values get into FS, as the Lua program is working with FS's internal values, not your joystick or quadrant inputs. Regards Pete

I have no idea what that device is, but if it can be connected to a PC, and you are a programmer and can write a driver for it, then you can certainly get whatever information you need to make it move however you want from FSUIPC. Don't the makers support it? Maybe they already have a driver? If you want to write a program to get data from FS via FSUIPC, you need to download the FSUIPC SDK. Regards Pete

That sounds like a USB power saving problem. Go into the Windows device manager, find all the USB entries with power management and disable the option for Windows to save power. The folks that sell you these devices should be able to support their products and tell you such things. Regards Pete

That's the same as right-clicking each time and selecting "run as administrator", as I suggested. Changing it in the properties just saves having to remember that each time. All the programs involved need to run at the same privilege level. There should be no need to run any of them at the elevated level, but if you do, you have to run them all that way. Regards Pete

That is correct. The multiplayer traffic is injected only for airborne traffic in order to drive TCAS displays. You do not want ground aircraft on TCAS displays. There's no facility to have them in the ground traffic tables. Even if such a facility were requested now, and i added the capability to FSUIPC, it would need changes in the on-line flight software (IVAP, FSInn, SB3, SB4, AIbridge) to put them in. I don't think they'd want to do this. Regards Pete

Where's the erorr message -- or is that it "error msg#14"? Does it in any way attribute anything to FSUIPC? If not why do you think it is anything to do with WideFS or FSUIPC? I'm pretty sure FSCommander needs data access to FS files aside from its connection via FSUIPC -- from ther posts here that seems to be folks usual problem. Have you asked FSC support? The logs only show that you connected the client for 16 seconds, and it ran okay, before you terminated the FS session and also WideClient. Was 16 seconds long enough even for FSC to fully initialise and get itself ready? I think that is because you are in the wrong place. Try FSC support, as I don't know it (I don't have it and have never seen it). Your WideFS connection is fine, though you could consider running FS for a bit longer than 16 seconds after connection. Regards, Pete

Well, someone told you wrong, because although you do need FSUIPC installed to use FSC and/or WideFs, you certainly don't need to buy it (only WideFS). There's nothing you need to know in them in any case, except installation. That is completely unrelated to either FSUIPC or WideFS. It is a function of FSC working on FS's data, and it doesn't use FSUIPC or WideFS at all for that stage. So, you are in the wrong place. You need to go to FSC support -- assuming that is that you've read the FSC documentation and cannot find the answers there, which would surprise me. No, you don't need to set it up. it just needs installing. You don't even need to register it. That was a waste of your money. Regards Pete

Great! What is the "default one which doesn't work"? The only one I know for wing de-ice is "TOGGLE_STRUCTURAL_DEICE". Doesn't that work? What does the log show when the switch is operated? Regards Pete

As I said, offset x0D0C in a 16-bit WORD with 10 or its bits acting as one light switch each. The offset documentation is in the FSUIPC SDK, as I thought I mentioned? What part are you confused about? This particular offset has been discussed in this Forum before too. Search for "lights", or probably better "0D0C". Did you use the logging as I suggested? Are you sure these are FS simulated and not merely local to the panel you are using? Regards Pete

You can trap FS events like that in a Lua plug-in, and then issue whatever controls you like -- or manipulate FS offsets to accomplish even more. The plug-in can be started automatically for the whole FS session by putting the code into the FS Modules folder in a file called "ipcReady.lua". The latest Lua library documentation is provided in the Announcements above. That updates the copies already installed by the FSUIPC installer. The Lua library facility you want is the one called "event.control". Have a look. I can help if you don't understand anything, but take a look at the sample Lua programs provided first. The code for the Lua plug-in would be quite short and not complicated. I'd rather help you do things rather than do them for you as you might then be able to do a lot more as the needs arise. Regards Pete

There are 10 individual light switches, for all lights supported by FS, in offset 0D0C. You'd need to use the Offset Word controls (Setbits, Clearbits or Togglebits) to operate the switches that way. Offsets are documented in the FSUIPC SDK. No idea. That sounds like a mechanism peculiar to the panel. How do you do it with the mouse, hold the mouse button down? If so have you tried using the assorted numbers on the end of the macro which qualify the mouse action -- maybe you need a "button down" when you press your real button and "button up" when you release it. The numbers that can be used are listed in the FSUIPC dox. Don't the FSUIPC-accessible FS generators work for that panel? Have you tried using the Event logging in FSUIPC to see if those clicks merely generate FS controls? The FS names include "toggle alternatorN" for each engine 1-4. Otherwise check the FSUIPC offsets and use the offset controls. Regards Pete