Pete Dowson

Quote No idea how you playback, but there's also "SimDirector Toggle Flight Recordings". What does "Toggle Playback Controls Window" do? I guess the only way is via the menus or SimConnect. All FSUIPC can do is list the events indexed by P3D's "CONTROLS.DLL". There are lots of new facilities in the P3D versions of SimConnect, but the job of FSUIPC is to provide ongoing compatibility with FSX/FSX-SE (and even as far back as FS98!) across the years. For new stuff specific to new sims I would expect folks to use the new facilities. When Microsoft invented SimConnect it was actually meant to replace the need for FSUIPC and I was preparing to retire back then! Fat chance! Pete

All numbers in the program are in binary! It is how numbers are represented in computers! If you display it then the Lua functions convert it to a string. Your byte value n is 168 in decimal but it is actually the bits 10101000, or hex A8. To display or log a value it has to be converted to character form, which is NOT the same as being a number! Characters are actually represented by ASCII binary numbers, so "168" in a string or display is in the computer as hexadecimal 313638. A new line would be decimal 10 or hex 0A and a return/enter decimal 13 or hex 0D. I think you need to get your head around numbers in computers before you can mess with the values you need. Pete

These symptoms are normally results of bad calibration in Windows (use Windows controllers) or, sometimes, incorrect entries in the Registry. If the throttles are dead in default aircraft too, please see the FAQ subforum thread entitled "Fixing joystick connections not seen by FSUIPC ". Maybe also the thread " Some Saitek axes only provide partial movement " would be relevant to your spoilers. Also always check out your spoilers when in the air -- FS raises spoilers automatically if you are on the ground even with a small movement through the "arm" position. I'm pretty sure that with the PMDG 737NGX and 777X you have to assign only to the "Axis Throttle ..." FS controls and not calibrate. Those PMDG aircraft read the throttles directly and if you assign differently or calibrate in FSUIPC they will conflict. On the Pic on your second message it looks like you just haven't calibrated correctly. Please follow the step by step instructions in the FSUIPC user guide. But as I say, don't calibrate in FSUIPC for the PMDG aircraft. Pete

Assuming you meant "hexadecimal", then all vlaues are supplied as numbers. They are in binary, so you can express them any way you like. No. A number is only in "decimal" if it is converted into a decimal string using "string.format" or attached to a string. All numbers in computers are in binary -- i.e. strings of bits. This is fundamental to any understanding of programming. If you want hexadecimal strings you use a string.format with the %X facility. However, if you want to test or manipulate bits, which is what I assume you want to do, you should use the binary number as received. Otherwise you will have a lot more difficulty! Extracting or testing bits is done in Lua using the logic library functions supplied by FSUIPC. (Lua itself does not include bit manipulations, which is why I added these functions). BTW the programmer of that aircraft seems to have gone out of his way to make it complicated! Pete

If you would like to send it to me as an email attachment (petedowson@btconnect.com), I can upload it to the repository here and give you a link to include in your text. Pete

Okay. I should be able to check this here tomorrow (Wednesday). Pete

Is this the only circumstance? Do the GSX menus continue after this sequence? Which Flight Sim are you using? I will try to reproduce it, but it might not be for a day or two whilst I'm catching up. I use GSX and ProATC/X extensively on my cockpit setup and so far have never had a problem with the menus appearing. But currently I am using FSX-SE. I plan to install P3D 3.4 on my cockpit Pc later this week and will test then. Pete

No, I really hate those installers which litter my screen with icons, and I will not beome a maker of one of them. Sorry. Just reading the "Read Me" type document included in the ZIP you have to open doesn't seem like a big chore, and it sure only needs reading once. Certain not a day and night job! Pete

The installer will still work, just ignore the warning that the version of P3D is later than it knows. Let it carry on. Then replace the FSUIPC4.DLL with the latest Interim Update (4.956), in Download Links above It works fine with 3.4. I'll update the Installer this week, after I've caught up. Pete

If your driver writes axis values to the axis offsets (3BA8-3BC7) then they can be assigned and calibrated in FSUIPC. Pete

Check the latest list of FS controls included in the current interim FSUIPC update ZIP. I think these are added now (but I'm not sure). Pete

Can you not take the existing Python stuff and update it? You'd need someone who knows Python I expect. The SDK controbitions like this are from other users. Note that FSUIPC, and indeed FS itself, only run in Win32 mode, so i'm not sure what you'd do with AMD64. Pete

Sorry, you don't provide enough information. Maybe a log file and you settings (FSUIPC4.LOG and FSUIPC4.INI, from the Modules folder). You can paste their contents into a message here. Pete

What is the "issue"? How are you assigning and calibrating it? Both in FSUIPC? Or assign in FS? More information is needed in order to help Pete

Once you have the correct <custom control> number for the Autopilot switch on the 737NGX, just use the button's flag to make the two controls alternate. It means editing the FSUIPC4.INI file Examples are given in the FSUIPC Advanced User's guide. Pete

Sorry, I don't have time to investigate this now, catching a flight early in the morning. For now I suggest you try tmake all your blocks the same size, and read fixed length blcoks. I know that works fine. Remind me after September 20th and I'll check into it then, after I've caught up with the backlog. Pete

Sorry, I an not understanding. Did you use the terminator in the event? Why are you reading the strings when they are supplied for you? What's the difference on your system between morning and "now"? Pete PS I am away soon now, until 20th September.

If you edit the INI file whilst FS is running, you need to tell FSUIPC to re-read it -- use the "Reload Buttons" button on the Buttons & Switches tab in the Options. Well, the simply offset test condition facility doesn't do multiple tests I'm afraid. I suppose you could use one offset to set a button flag (there's an assignable control for that) and then test that flag as well as the second offset in the Exit assignment line. However, really, if you want to program the way things behave in any such ways you would really be far better off using a Lua plug-in instead. You can do almost anything you like that way. Sorry, I've no idea what this means. The offsets are listed in the supplied Offset Status document. Pete

I don't know about the former, but the latter problem is one of the Saitek driver or its definition in the Registry. It isn't related to FSUIPC. I think there's a solution posted in the Saitek forum, but first see the FAQ subforum here -- see the thread entitled some saitek axes only provide partial movement Maybe the same sort of thing, or just very bad calibration. Always calibrate in the Windows driver's calibration screen before trying to use FSUIPC calibration, otherwise you start off with it all wrong. Also, if you are assigning the axes in FS, make sure the sliders are set correctly -- sensitivity at max (full right), dead zone at minimum (full left). As above. Really you should get everything working properly with a default aircraft before attempting to do so with an add-on, because many add-ons do their own thing. Once you know your controls are set correctly, then you can work out the differences with the add-on. There's no "paid" and "unpaid" versions -- the difference is just the Registration. And what matters is the version number. If you are using anything earlier than 4.955c you should update. I don't support old versions. You should also always say whether you assign in FSUIPC, whether you calibrate in FSUIPC (two different and independent facilities), and whether you have disabled controllers in P3D or not. Pete

You use WideFS? See if the pauses occur still if you disable it (main 'About' tab of FSUIPC options. If not then I susepct you have something wrong with your Network settings, or network driver. No, not possible. You can't run them both at the same time in any case, and all their files and settings are independent of each other. Do you have pauses in FSX too? Is P3D3.3.5 your first version of P3D? When did the pauses start, or have you only installed FSUIPC recently and never used it before? Pete

This generally is an indication that something which depends on FSUIPC is having a problem. There's nothing in FSUIPC itself which causes any sort of pauses, though if you enable the AutoSave option the action of FS when doing the requested flight save will cause a noticeable pause -- mainly with very sophisticated aircraft which also save all their settings. Nothing wrong showing there. What about your settings (the FSUIPC4.INI file)? Right, so the pauses aren't due to that. Unless you have some Lua plug-ins operating which might cause problems I don't see anything which can make any pausing. But please do show me the INI file. Pete

Speed isn't everything. Just choose the highest valid speed which gives reliable results. Normally on a USB-converted connection the baud rate is more a formality than a true indication or control of speed. Pete

These are other COM receptors, where, exactly. Running in FS? Lua is interpreted. It is also not given full reign over the processor so that plug-ins do not cause FS performance to drop. Don't forget that, whilst being a separate thread, it is part of the FS process. It is likely that more data arrived whilst you are processing/reading the stuff you were notified about. You won't get another "event" signalled whilst you are in the event function. The logging takes time, too -- it needs to call upon other threads to do that function. You are testing it just after receiving the data, assuming there was no delay between the data arriving and the event being triggered. That will vary with FS performance and other activities. As you've now added \n (new line) as a terminator for each block, why aren't you using that in the event.com call? Then each call into your function would contain one block. event.com(dev, 10000, 1, '\n', "readSerial") You could then simplify the function enormously, so: function readSerial(handle, string) ipc.log("com: " .. string) end You only now need to process that string. You don't need "serial_string" any more. BTW, 10000 for a max forces FSUIPC to allocate that much memory. Do you really intent to have such large amounts of data arriving in any block? I think you should make that a realistic maximum, not a fictional one. Pete

That should work, assuming the regular "Toggle Aircraft Exit" control works on your loaded aircraft. What's the problem? That line works fine here. Pete

In a few days I am off for a while -- back 21st September. Sorry. Others here should be able to help. If not I'll be catching up when I return. Pete