Pete Dowson

Wow! That's looks pretty neat. I will have to have a look at LINDA one of these days! ;-) Thanks, Pete

No, not part of AdvDisplay. It was originally packaged with AdvDisplay, in the same ZIP, that's all. It has always been available separately here, in the Download Links subforum. Is there a way to achieve this using the later versions of FSUIPC, as it would be more benifictial to have the RC window on my laptop.[/CODE] ShowText works with any version of FSUIPC and WideClient. I've not seen your post in the RC forum, but I'll answer there too in case others are in some confusion. Regards Pete

Okay, thanks. BTW if you still haven't worked out what to do then simply save Andy's piece of code: val = ipc.readDBL("2B00") ipc.writeUW("07cc", val/360*65536)[/CODE] into the FS Modules folder as, say, "SetHdg.lua", then, in FSUIPC Buttons tab, press "reload" so FSUIPC reads it, and assign your button to "Lua SetHdg". That's all. Maybe you can use LINDA instead but I don't know anything about LINDA I'm afraid. Note that this code copies the Magnetic Compass heading to the Heading Bug, so be sure you are flying straight and level first. If you want he actual heading at any time, instead, then you'd need: [CODE]val = (ipc.readUD("0580")/65536) - ipc.readUW("02A0") ipc.writeUW("07cc", val)[/CODE] Offset 0580 contains the actual heading TRUE so needs converting to MAG by subtracting the variation (offset 02A0). Regards Pete

Well, you've provided no relevant information at all, yet. The hardware isn't relevant because FSUIPC/WideServer aren't hardware drivers. What osrt of crash is it ... what happens, when does it happen, what information does it supply, does it happen without WideFS operating, what version of FSUIPC is it, what version of WideClient, what version of FSX, what version of Windows, and where are the logs to show me -- FSUIPC4 log, Installer log, WideServer log, WideClient log? Regards Pete

Multiplayer facilities were incorporated into FS before SimConnect was thought of. I don't know of any MP facilities in SimConnect. All the SimConnect client/server activities are related to getting inforation to applications and events back. It's a different interface altogether. Regards Pete

Sorry, I thought you'd understand I meant only heading bug. I shouldn't have to repeat the same word to imply that. Do you think I'm so daft I don't know there are other bugs? Yes, of course, but in FS is is the same one, the only one. How many others are there in your aircraft? And why are you lecturing me like this? But Andy gave you the answer above, explicitly! Pete

There have been no changes which will prevent connection from any FSUIPC interfacing utility. The interface is the same as it has always been -- it has not changed for 12 years except for the removal of the access code checking back when FSX was released.! And 4.703 is not "the last version" -- there have been many since then. The current supported version is 4.823. I think you need to debug your program to see what is wrong with it. Regards Pete

I've never found them -- not that i looked for those specifically, but I most certainly wanted to intercept the ATC messages. Why would messages internal to FS be sent via SimConnect? SimConnect is an interface for add-ons. If you ever find a way to get to these messages, do let me know, please! Regards Pete

Nevertheless, the Client isn't receiving the broadcasts. That's what it is waiting for. It doesn't really need them -- you can provide it with the ServerName or ServerIPAddr and Protocol parameters instead. That's what folks with different workgoups have to do. Or maybe it's some sort of firewall blocking the ports being used? 8002 and 9002 by default. Wouldn't be any use to me anyway. I know virtually nothing about networks, only what i can look up when I have a problem. The Network part of the code in WideFS s lifted direct from Microsoft examples. Regards Pete

Ah, I didn't read that in your text at all, but I now notice the word 'bug' in your title. However, the autopilot heading bug IS the only bug, so I don't understand your differentiation between "Autopilot HDG bug" and "HDG bug itself". They are one. Normally you'd do that with the Heading bug inc and Heading bug dec controls, using a rotary knob (or two buttons maybe). If you want to set it immediately to the current heading you would need to have a Lua plug-in to read the current heading and write it back to the A/P heading offset, as Andy showed. You can write it direct to the A/P offset as that example shows, or use the Heading bug set control with the heading as parameter. Regards Pete

You mean you want to correct the gyro drift -- i.e. operate the adjustment to match the magnetic compass heading when flying straight and level? The Gyro Drift can be adjusted in the same way as the knob to turn the gyro compass card by using the controls "Gyro drift inc" and "Gyro drift dec", but if you don't have a rotary knob you can use and simply want to cancel the drift in one button press you could assign it to "Gyro drift set" with a parameter of 0. Regards Pete

How did you come by those IP addresses? They are not in the normal ranges allocated for Local Area Networks. i think this causes a problem. These are the reserved local addresses (from http://www.ibm.com/developerworks/linux/library/l-lan/index.html , but you can see them in many places). Most folks use the last one, 192.168.xxx.xxx. I've never seen anyone use internet addresses for local PCs and I cannot see how it cannot cause all sorts of problems. PC2 is not receiving the broadcasts from the Server to tell it the Server IP address and protocol. The usual reason for this is that the PC is not in the same workgroup, but another possible reason is that the version of Windows on that PC is earleir that XP SP1 whichy is, I think, when the broadcasting facilities were implemented. Regards Pete

I don't know. There are things you could try, like overwriting vaues in some of the flaps offsets. You might need to do this conitnually (i.e. at short intervals). Check offsets 30E0 to 30EE Regards Pete

I've never used it so I can't say, but I would doubt it unless your VC is firmly fixed in position on screen. Why not refer to the support site for that product? Regards Pete

You can easily display one-line messages for display in the same bar as ATIS messages, for example, by writing them to offset 3380 and putting a time-code into 32FA, From Lua, something like this: ipc.writeSTR(0x3380, "This is a one-line message") ipc.writeSW(0x32FA, 5) The 5 in the second line makes the display last for 5 seconds (or until replaced). You can put 0 for no limit. The message must not be longer than 127 characters. Regards Pete

mouse macros only work with gauges designed and written in C/C++ according to Microsoft's gauge SDK. Fewer and fewer aircraft are made that way these days, and most of Microsoft's own aircraft aren't even compliant. There are lots of examples provided in the ZIP of Lua examples in your FSUIPC Documents folder, and in fact listed in the Lua documentation PDFs provided. Several of them create windows on screen. Regards Pete

Really? Yet you declared these: and even stated your conversion: Even after I repeated what the documentation states, that 2B00 is a 64-bit floafing point value. In the offsets list each value is described. I don't know what you are using, but against 2B00 in the official lists, the only ones i produce, it clearly states 64-bit floating point for this offset. That IS the explanation. If you want floating point defined you'll need to look it up elsewhere. It is a sufficient description for use in any language which supports the underlying intel processor architecture. I rarely use the term "double" because that is a C/C++ type, not a description -- I ddn't even know it was "Double" in VB6, but i am pretty sure it isn't using that word in all languages. Data type wors are language dependent. Sorry, I don't know what you mean. Monitoring the value in 0BB8 I can see it changing constantly whilst the autopilot sets or changes heading. I'm using FSInterrogate to watch it. Didn't you search the offsets list on the word "aileron"? You'd have surely found offset 2EA8, where I see that, contrary to my statement above, I did describe it as a double -- also a FLOAT64, which is of course a 64-bit floating point nmuber again. Please do use search facilities in your PDF viewer. That's all I do when I need an offset. I don't remember them all, you know. Pete

Peter Hayes' advice was in order ot do things really smartly, with the best possible set up. You don't want that, you want to keep to your old ways (though from what you said your old ways were a LOT more complicated, indeed!). If the button is visible in FS it is visible in FSUIPC. Just go to the FSUIPC options, Buttons & Switches tab, press the button, and when it is seen assign to a keypress or FS control as you wish. That's it. Nothing else to do unless you also have the button assigned in FS for some other function, in which case now you'll get two functions not one, so unassign it in FS. BTW there is a User Guide provided with FSUIPC, and there are even pictures in there. Is it realy so hard to find out how to do these simple things? Foks have been assigning buttons happily in FSUIPC for over 12 years now! There are French versions of the FSUIPC documentation available if you don't understand English. They aren't so up to date, but they are certainly valid still. Pete

There's no change in how that offset operates. It works fine. Try it yourself -- assign a button to "Offset Word Set" for that offset and parameter 0 for "up", 16383 for "down". To check whether your software is working correctly, monitor the offset as type U16 on the right-hand side of the FSUIPC Logging tab. You can select "FS display" to get its value on screen in real time. If they aren't writing it, it won't work, obviously. No idea what they mean by that. Sorry, I know nothing at all about fs2phidgets. Don't they have their own support somewhere? I think you need to ask there. Regards Pete

Strictly speaking you are not allowed to use either FS2004 or FSX for commercial purposes, though I'm sure Microsoft must make some allowances. However, yuo are in luck now because Lockheed-Martin have recently reduced the price of their Prepar3D (a development of ESP, the commercial-use version of FSX) to less than 50UKP for use in educational applications. See the Prepar3D website. www.prepar3d.com. Regards Pete

Well the IP address you've specified in the WideClient INI file appears to be one for an Internet provider in Thailand. It most certainly is not a Local IP address. IP: 180.180.10.99 Decimal: 3031698019 Hostname: 180.180.10.99 ISP: TOT Public Company Limited Organization: TOT Public Company Limited Services: None detected Assignment: Static IP Country: Thailand State/Region: Lop Buri City: Lop Buri Latitude: 14.7981 Longitude: 100.654 [/CODE] WideClient is not able to connect via the internet, it is intended only for use on a local internet. Why did you put these parameters in? If all three computers are in the same WorkGroup they should find each other automatically? If you must put the IP address in, put the actual local IP address you've assigned to the Server into the INI files. Regards Pete

Why do you have to assign all axes and buttons in FSUIPC? Who told you such nonsense? And why is assigning in FSUIPC any more complicated than in FS? It's simply a matter of moving the axis or pressing the button and selecting the acytion you wish to assign from a drop-down list. How does that really differ from FS assigning? Pete

Good! That's a really big relief! ;-) Regards Pete

Yes. Yes, yes, all of it Regards Pete

Hmm. Which actual file, from which website? All the files from me are thoroughly checked before they are placed on the download site. But some AV packages do give false indications. The latest update for WideClient is in the Download Links subforum here. Regards Pete