Pete Dowson

I have made good progress. Please see the Sticky above about VRInsight users. Regards Pete

Yes. You'd have to put a loop in for the longer press. Taking my original example: -- This was a longer press, send VIEW FORWARD repeatedly while ipc.testbutton(joy, btn) ~= 0 do ipc.control(65674) ipc.sleep(50) -- 50 = 20 repeats per second. Adjust to taste! end or, better, to make sure you do get at least once instance (which the above doesn't guarantee) -- This was a longer press, send VIEW FORWARD repeatedly repeat ipc.control(65674) ipc.sleep(50) -- 50 = 20 repeats per second. Adjust to taste! until ipc.testbutton(joy, btn) == 0 Regards Pete

According to the information I have, the AV400 format does not include the VS. Regards Pete

Please review the Announcements above, particularly the one called "Updates and other Goodies". I think you'll find your first problem is one of those listed as fixed in the latest interim update available there. As for the LevelD aircraft, I don't know if the MCP will work on that without a special driver as I think LevelD use their own autopilot. You need to check with the GoFlight website about that. Regards Pete

Is it actually running? You can tell by checking to see if it has created a new FSUIPC4.LOG file in the FSX Modules folder. Additionally it will have revised the INI file so the date/time on that will be up to date. If there's a Log file then it is a SimConnect problem. Please show me the Log (paste the Text here). What have you changed between times? The FSX.CFG file isn't relevant. Your dll.xml file appears to have its first line missing. It should start with: <?xml version="1.0" encoding="Windows-1252"?> Otherwise it looks okay. Regards Pete

You can set parameters in the FS CFG file to remove such messages. You shouldn't really get flickering anyway, but an alternative is to use Slew mode, again with the on-screen message inhibited. Sorry, I don't know why it should stop processing it. You'll need to apply some debugging to see why. Is it still running? Has there been some sort of network glitch? Regards Pete

No, not a Double. Although a Double is 64 bits it is a floating point number, and the latitude and longitudes are not, they are fixed point numbers. Totally different format, as I think I mentioned. Pete

It would be worthwhile reporting this to PSS though. I assumed you've checked for updates already? Regards Pete

I'm afraid I don't know VB enough to give you any solutions -- I'm sure others can do that -- but the big error I can spot is that your are reading 32 bit (4-byte) fixed point numbers into 64-bit (8 byte) variables (Doubles), and then treating the results as a 64 bit Doubles. If you must read them in two parts because you can't find a 64-bit integer variable type, you must at least read them into the right type of variable and treat them for what they are. Floating point formatted numbers are very different. BTW, do statements like latHi = "0" really work, and give no compilation error? You declared "latHi" as a Double yet you appear to be assigning a string to it! Regards Pete

Well, just the obvious, really -- signed numbers have a sign: in other words they can be positive or negative. Unsigned numbers can only be positive (or zero of course). So, for example, a signed byte can contain -128 to +127 whilst an unsigned byte can be 0 to 255. Similarly a 16-bit (2-byte) word is 0 to 65535 unsigned, or -32768 to +32767 signed. Pete

Not little round ones, but they certainly have some sort of microswitches which can be activated, because they appear in both FS and FSUIPC as buttons. They operate the buttons, then. Of course. They are seen as normal Buttons. They are the ones discussed in this thread as having TWO different joystick numbers in FSUIPC because they are seen both as GoFlight devices and regular joysticks. That is why I added the new parameter I mentioned, to avoid the confusion of having two numbers for the same buttons. Pete

On the subject of the buttons being seen as both normal joystick buttons and FSUIPC special GoFlight buttons, you mean? The TQ6 buttons can be suppressed by changing the FSUIPC INI file option, PollGFTQ6, as described in the list of recent changes in the Updates announcement. That is the resolution, perhaps you missed it? Sorry, what is the "same problem"? The assignment of the buttons was never a problem, only slightly confusing in FSUIPC because the same buttons gave two different numbers. Hence the option to suppress the GoFlight number and just use the normal FS one. As for "FSUIPC seeing thrust reversers as buttons", there is no way to "see axes as buttons", ever. FSUIPC it sees the joystick axes as axes for assignment in the usual way. FSUIPC3 can handle up to 6 axes per joystick connection, XYZRUV. In FSUIPC4 you can see 8, XYZRUVST. The "buttons" we were talking about are those also built into the TQ6 and, I think, depressed when you pull the sticks right back. Regards Pete

I've added two new commands to the Lua ipc library: state, x, y, cx, cy = ipc.getdisplay() This returns 5 values: state = 0 for no display, 1 for docked display, -1 for undocked display x, y are the screen coordinates for the top left cx, cy are the display sizes, horizontal and vertical, respectively ipc.setdisplay(x, y, cx, cy) Sets the current display to a new position and size. You should normally get the details, modify the values, and set the values, but if you know exactly what coordinates and size you want, then you can simply use setdisplay. Note that there is only ever one Lua display window, and any Lua plug-in can use these commands -- so you could have a separate plug-in to set specific sizes and placements. It doesn't have to be done inside the one currently using the display. These changes are in the latest incremental updates to FSUIPC3 and 4 -- version 3.971 and 4.587, available now. Regards Pete

Well, in the 11+ years of FSUIPC and WideFs it's really the first time anything like this has come up. I'm not sure how I can make a generally applicable facility. Supposing both programs were being run on the same PC? FSUIPC doesn't distinguish between client programs these days. The best I could do within reason is to add a facility in WideClient to block selected offsets being written. Parameters similar to those for "monitor" perhaps. Have a look at that and see what you think. [LATER] I implemented a Deny facility, as I mentioned, in WideClient 6.793, now available in the Updates announcement. Regards Pete

No, there's no way to do that. If you are only talking about the FD on/off status, doesn't the last one operated win? Surely neither of them keep writing the same thing? Regards Pete

If that gauge is susceptible to the mouse macro treatment, yes, that would be the easiest way. Regards Pete

Strange. I think there's an occasional bug in FSX, because it does always use the screen position values from the FLT file, but not always the size. This is different from FS9 where it always seems to use both position and size! It isn't consistent. Sometimes when I load a flight and open a Lua window, it is the right width and length, sometimes only the right width, and sometimes default width and length. If it isn't a bug in FSX then I can only think that it needs more data in the structure I'm providing -- i.e. a larger one -- and the results depend on what is in the memory after it. However, tracing through the FSX code doesn't seem to indicate this can be true. I'll carry on looking at this for a little while, but I'm not sure it will lead to anything. Maybe I can add a Lua facility to specify the size instead, though I'm not sure that's possible either, yet ... Incidentally, I cannot reproduce your problem of the Window data not being saved when you save a flight manually -- it always saves here, 100%. Maybe you don't have the Window active at the time you do the save? Regards Pete

Okay. There are 4 separate FS controls for each radio frequency -- increment and decrement both for the fraction and for the whole number part. There are 8 for the transponder, 2 for each digit, but I added some special controls in FSUIPC to do it in 4 controls using pairs (Xpndr low NNand Xpndr high NN ..). Yes, of course. The gauge is noting the radio selection and sending the appropriate control. That'll be some coding internal to the gauge. Note that with the default FS radio stacks, and add-ons based on those, once the appropriate part of the frequency has been selected, the main keyboard =+ and _- keys do the job. They send the controls "PLUS" and "MINUS", respectively, and that in turn sends the appropriate radio inc/dec control. However I don't know how you'd select the whole number or fractional part of your radio. Regards Pete

What does it do when you operate it? I can usually tell you what controls do what, but I can't guess at a knob labelled in German. Perhaps you could translate, please? If it operates an FS control (which it might not do -- some gauges have switches and knobs used for purely internal purposes), then enable Event logging in FSUIPC's Logging tab (one of the checkboxes on the left hand side), and operate the knob. You should see which named FS control it operates by looking in the FSUIPC Log file (which you will find in the FS Modules folder). Regards Pete

Yes, I understand that. I'm not sure how to do it automatically though. That's really strange because the autosave is calling the exact same routine as you do when you manually save. There's never been any difference shown before. I'll try some experiments with FSX then. Doesn't the undocked one disappear when you want it to? Really, the possibilities of the FS window facilities have not been explored much in the directions you are asking. I was trying for ages to get different font colours and sizes, and background colouring, all to no avail. There are some parameters I don't yet understand so all I can do is experiment a bit and see what I can dig up. I can't promise anything. Regards Pete

You don't need to register FSUIPC to run FSC, which is a licensed FSUIPC application. However, I'm sorry, but there is no way to use WideFS before purchase. Best to try FSC on your FS PC first. If you like it, it will be just as good on a Client PC with WideFS. That's all WideFS does, allows you to run FSUIPC applications on a separate PC. Regards Pete

It should auto-expand vertically to suit the number of lines you send. That is FS's doing, not mine. The width, though, is subject to user setting. Hmm. not sure how that works. I thought the same as you, that if you sized it and saved the flight it would come back the same when you reloaded that flight. You shouldn't need to add it manually. I thought FS saved it in any case. I don't know. Certainly not in anything of mine. FSUIPC simply calls FS routines for all this stuff. What FS version are you using? I'll have to do some experiments. The same mechanism is also used for the Radar Contact window and the applications window facility used via the FSUIPC offsets -- that's it, 3 separately named FS windows which FSUIPC can handle at present. Have you tried the undocked window? That saves separate size details in the FLT file I think. Regards Pete

The flight plan is not available through FSUIPC. I don't know anyway of retrieving it internally, and in any case it is of indeterminate size and therefore not really suitable for the mapped memory based interface used by FSUIPC. You need to use the current .pln information to read the plan file yourself. Regards Pete

There's no way to "disable" FSX ATC. You just need to turn its sound right off in the Sounds menu. In FSX? I've never heard of any ATC crashes in FSX. I've been using Radar Contact with FSX ever since FSX was in Beta and never had a single ATC crash. There were certainly nasty problems in FS9, for which I provided patch facilities via FSUIPC3, but those certainly weren't carried over into FSX. I think you must has misread something. There are such facilities in FSUIPC3 for FS9, but they do not apply in FSX and are not needed. I think you must have some other problem in your FSX installation. I realy have no idea what could cause ATC.DLL to crash in that. Sorry. Regards Pete

REX is predominantly a texture program. Once the textures are installed it isn't doing much, unless you are thinking of using its weather facilities instead of a dedicated program like ActiveSky. Does REX use FSUIPC for weather on FS9? I don't think it does in FSX. Generally I would expect you to have to install it on the FS PC because of all the texture manipulation involved. VoxATC may run okay on a WideFS client. That's something you'll nee to check on their Forum or support site. I am a long-time Radar Contact user, not VoxATC. Yes, I think both the Squawkbox and FSInn/CoPilot options can be run from a client PC, albeit with dual installation (i.e. you have to install on the FS PC as well). But on FSX neither use FSUIPC so they aren't using WideFS. On FS9 and before, Squawkbox uses FSUIPC and WideFs if needed. Regards Pete