Pete Dowson

Real GPS updates aren't all that frequent in any case, and I would assume track takes time to compute because it involves taking two Lat/Lons and deriving the track from that. However, FSUIPC is simply getting the "GPS GROUND MAGNETIC TRACK" variable from SimConnect whenever it changes. What sort of user presentation needs a faster update of track? That's because a GPS track is based on a change of poistion. Any other method is really a guess. The track up on NDs is from the previous period, but presumably they simulate the IRS postion changes not the GPS. How are you determining that your method is not as accurate as those in the add-ons you refer to? The GPS will usualy be more accurate in any case I think, because it is based on further distance travelled between Lat/Lon positions. The faster you want it, the less accurate, i would have thought. Regards Pete

It's okay now. The link was okay but the file never got there. Pete

1. there are no personal details in the log, so i couldn't check them. 2. the log didn't finish -- you forgot to close FS9 first! 3. the log included axis logging. Please turn off all logging options. 4. the important file, the KEY file, wasn't in the ZIP so got deleted over the Internet as a "dangerous file". Please ALWAYS ALWAYS zip all files, preferably together. I'm away tomorrow, back monday, so there may be a delay. Pete

Strange. I've added " <custom Control>" but that shouldn't affect the sorting. All that stuff is standard Windows code, not mine, but I'll take a look. Thanks. [LATER] Fixed in 4.823, now up. I stupidly mixed up "killfocus" notifications with "selchange" notifications! Pete

Ah, good. I'll rebuild the installer and replace the 4.82 package then. Thanks for testing! Regards Pete

Same place as you find FSUIPC -- the Schiratti site or the Download Links subforum, as always. Pete

It is all precisely as documented, FS stored the frequencies in "BCD" (binary coded decimal), and only the 4 digits: 1370 in your example. The 100 digit is taken as read. Hex 0x1370 = decimal 4976. But you don't want the decimal. You want the separate groups of 4 bits for each digit. Hes 1370 is made up of 16 bits which are viewed in groups of 4, each running for 0 to F (A-F are used to represent 10-15). In this case, because they represent decimal numbers, you'll never see A-F in any case. If you want to convert to a string for display, you either need to use logical shifts and 'ands' to isolate each 4 bits and convert those to characters, or more easily, use the string.format function in Lua to get the hex digits in printable form, like: str = string.format("1%02X.%02X", math.floor(value/256), math.mod(value,256)) I've not tested that, mind, but you should get the idea. Pete

It'll be because of some facilities I've added which weren't supported in the original XP. I'm afraid I can't work out what those might be. it could be related to the Lua plug-in facilities for HID devices, or the DirectX sound playing facilities. Without being able to debug the cause of it not being loaded I can't tell -- and it might be more than one thing. The basic protocols WideFs uses haven't changed and won't change, and that version will still work with any version of FS and the Server in FSUIPC4 for FSX, so it isn't a problem. I can't support old versions, of course, but there should be no need. I don't have an XP installation here older than SP2, which is fine, and at present i can't think of any way to determine the dependencies which aren't being met without installing a development system with its debugger. If I can think of a way of finding out what it is needing to load, I could make those elements link dynamically, optionally, at run time rather than statically as at present. But it would be a lot of work in any case and I really don't have time right at this moment I'm afraid. Regards Pete

Since the point of the tracing is to find out why it is crashing, it isn't much good doing in in 4.811 even if the feature existed back then! ;-) There are two ways. One is to enable it one a load of FSX which doesn't crash -- i.e. with Linda not loading (I think you identified that already, did you not? The other, yes, it to add the line into the INI beforehand. the entry needed is. as always, documented of course -- it is in Item 7 in the changes list included with the updated FSUIPC4. To save you looking it up it is DebugLua=Yes in the [General] section. Please use version 4.821 now, not 4.820. See the Download Links subforum. [LATER] Hold on, don't do anything yet! ClaudeMan sent me logs and the NGCX lua and I've repro'd the odd characters in the Lua logs, and am fixing that now -- it'll be in 4.822 in an hour or less. Now at present i don't see how this would cause your specific problems if you don't normally run with that separate Lua logs option selected -- because then the log entries made by LINDA would go to the main FSUIPC4 log file and that doesn't have a problem. So, my question: do you always run with Lua logging separately enabled? If so, maybe you can try again, with 4.820 or 4.821, with no logging options checked (just remove the LogLua line from the FSUIPC4.INI file)? Maybe the crash problem is being caused by the corrupt logging, and is exacerbated in the case of LINDA because of the sheer number of log messages it seems to produce? Anyway, I'll fix the Lua logging now and release that as 4.822, interim update. Once I know one way of the other about the crash I'll decide how to proceed. I'm away Friday-Sunday inclusive, so if 4.822 doesn't fix it it might be next week now. [LATER STILL] Okay, 4.822 is up. Please go ahead, make it crash. If it does please only then get me that trace logging. If it is okay, please advise. thanks. Regards Pete

So why not ask the questions about the bit you don't understand, instead of asking for sometime to do it for you? You can look things up, can't you? Do so, and if you can't work it out (there's only a small sum to do -- (256 x 2) + 102. I even looked up the numbers for you for your example and included them in my last message! It isn't programming, it is merely selecting choices from frop-downs and putting numbers in places on a computer screen! Programming is completely different and involves logic, not mundane actions like this. If that was all programming was, I wouldn't do it! Pete ]

Oh, dear. Why do I write documentation? Have you not bothered to even look? If you have, why not ask specific questions which i can answer rather than make me do it for you? Do you have the Advanced User's guide for FSUIPC handy? Look up the Key press/release control, near the back. Just search for "Key Press and Rellease". See? See where it tells you how to work out the parameter for the keycode and shifts? Elsewhere in the book you find the keycode and shift code list, tabulated for you. All on one page. You'll see + is ambiguous. Do you mean the =+ key on the main keyboard or the + on the numeric keypad? If the latter its keycode is 107. You'll find the code for control is 2. Now do you think you can work it out? Please do not ask me to look all these things up for you. It takes me just as long as you. I can answer specific questions but i really don't see why I should do the work which you have not bothered to do. Pete

Thanks for the data. I'll try to check it out, but none of my Lua programs exhibit such oddities. I'm still hoping someone with these problems will actually use the Lua tracing option INSTEAD of the separate Lua log option, as this should show me a lot more. That's why I added it! I have asked several times but no one has yet done this! :-( Pete

Wow! You still have a parallel port on your PC? They've almost completely died out -- though I know some motherboards do still sport the pinout headers for them. So you know how to program the parallel port, or you have a driver provided with the ULN2003? Not specifically for that board, and i don't know of any parallel port implementations at all. but getting one item of information out in in a VB program should be very easy -- there's a simple example in the FSUIPC SDK. Why not just adapte the program you have already written? Regards Pete

You'll need to deal with this by email. Write to petedowson@btconnect.com, please. Regards Pete

I think there are some control cards with interfaces written by others for FSUIPC, but i don't know any details. You might ask in the MyCockpits forums where many cockpit builders can be found. http://www.mycockpit.org/forums/ Alternatively, If you can find a suitable control card with a USB HID or COM serial port interface, you could write a little driver for it as a Lua plug-in for FSUIPC. Regards Pete

Your reply was rather difficult to read. What are you using as an editor? You can assign axis zones to keypress combinations by using the FSUIPC-added control "key press/release" with the appropriate codes, as listed in the documentation, for the parameter. Pete

Okay. Version 4.821, available now in the Download Links subforum, contains facilities in the Buttons, Keys and Axis assignment option tabs to assign "custom controls", being FS controls in the range 65536 to 131070. I'll make the same facilities available in FSUIPC3 is due course. Regards Pete

Okay, 4.821 is released. See the Download Links subforum. Regards Pete

Sorry, my fault. Typo in those two lines. The F should come before the signs, i.e. 107=CP(F+15,0)170,14,Cx3009400,x0000026C 108=CP(F-15,0)170,14,Cx3009400,x0000026B That'll teach me. Normally I refer folks to the documentation where there are correct examples of the use of these flags. I should have done that this time too instead of trying to do it for you. I'm juggling so many differnt things in the air at any one time that i make silly typing errors when trying to answer quickly. Regards Pete

I expect that aircraft does not use the standard FS values for those things. You will have to find the cirrect method of setting things for each complex add-on. The FS controls operate the FS values Is there any documentation supplied with the aircraft? maybe it supports keyboard short cuts for these things? Regards Pete

You posted your support query to the FAQ subforum, where it won't get answered. That's a repository for helpful information on "Frequently Asked Questions". Please use the Support Forum in future. I've moved this one for you. 4.80 is out of date. The current version is 4.82. You have a corrupted FSX installation. Have you been trying to uninstall or reinstall it, or rolling back the Windows registry? Those are the usual reasons. You could try installing SP2 or Accceleration again. Otherwise it could be a total reinstallation job. This problem won't just affect FSUIPC, it will affect any and all Simconnect using applications. Regards Pete

All of the controls you need for the 737NGX are listed in the one file in its SDK. You just use the control numbers. I will make it easier in FSUIPC to assign those control numbers in an update soon, but meanwhile it is easy enough to put them into control assignments in the FSUIPC4.IINI file directly. Regards Pete

Okay. Found it! It isn't AI aircraft traffic, but the AI ground vehicels. You can fix it by simply changing the "DeleteVehiclesForAES" setting in the FSUIPC4.INI file to "No" instead of "Yes". AES isn't supported in SP1 or earlier in any case, so this will do no harm. I will change FSUIPC4 so that it doesn't ask SimConnect for ground vehicle data before SP2 in any case. That'll be in the next update (4.821), but meanwhile the fix is that INI change. Regards Pete

Enable button logging in the Logging tab, and also add 9400 to the monitor list on the right, selecting type U32 and checking 2normal log" below. Then operate the button and show me the log. Also try 3840 in the first of the 3 lines in place of J15B0. Maybe that option isn't correct in your FSUIPC version. I'd need to cross-check. Regards Pete

Sorry, I have no idea what you are talking about here. There are no PMDG 737NGX options listed in the buttons assignments. If you see any then they must be derived from some macro file you have installed, not part of anything i have done from the PMDG SDK. The facilities added into FSUIPC4 for the PMDG 737NGX are merely to populate new offsets with the data provided by the SDK. That is all read-only. To control the aircraft you have to use their controls, as explained in the document included with FSUIPC 4.82. Regards Pete