Pete Dowson

Wow! Thanks everyone!, It is much appreciated! Pete

The current installer is for 4.742, and the one previous to that was 4.728. AND the install finished successfully as you can see: That is evidently not for the same run as the file! Since the Installer replaces the Log file as soon as it is run, and builds the file as it goes, you should have at least got a partial file from the run your picture shows. It seems that you are looking in the wrong modules folder for the Log? The picture looks like it shows the problem in the Installer section for Prepar3D, and I'm pretty sure that's fixed in the current installer, 4.742. However, if it isn't I'm afraid the main information I need from your picture is obscured -- i.e. the AppPath= line. Is the AppPath it derives correct? Please, try to move the messageBox away from the information window next time. Please try the current installer BEFORE doing that, so that I can either feel happy that the bug, if there is one, is fixed, or, conversely, get the needed Log file -- or at least an un-obscured picture of one! Unfortunately unless this is done withing the next two hours it will be too late till October 25th ... Thanks. Pete

FSUIPC2? That's pretty old -- way back before FS9! ;-) Assuming you mean FSUIPC4, try using the Logging to see what is wrong. there's no way FSUIPC "translates" one keypress into another, but the logging might show what is happening. BTW after this evening I'm away till October 25th, so apologies for any delays in answering. Regards Pete

When the installer completes, the dialogue pops up and asks you if you want to register. Aren't you seeing this? If not, something else must be going wrong. Please paste the Installer log into a reply here. You'll find it in the FS Modules folder. BTW after this evening I'm away on holiday until Tuesday 25th October, so apologies for any delay if it isn't resolved tonight (UK time!). Regards Pete

1. The key is for FSUIPC3 or FSUIPC4, not any specific version, just one or other of those products. 2. The installer does not stop, it just tells you it hasn't replaced your later version number. I hate installers which don't check and destroy later versions. Mine does not! It carries on and does the whole job except replacing later files with earlier ones. Regards Pete

It is in FSX, in the Add-Ons menu, as documented. You said you'd already activated it -- you said you'd entered the Registration details, remember? That means you ran the Installer, so that's all done and dusted now. I'm 68 but new to lots of other things! Sorry. You seem to use lots of TLAs (Three Letter Acronyms) assuming I know them, but i don't. So far that's FSU (I guessed FSUIPC), FNG (still no idea) and now ROF and CoD? I thought "CoD" meant "Cash on Delivery". No idea about "ROF", usually means "Rolls On Floor" as in "ROFL" ("Rolls on floor, laughing"). That would be "NG". What about the "F" or is that unprintable? You use it as if it is generally used, but I've not seen it before. On your later message: What do you think the PDF "iNSTALLING AND REGISTERING" document is, then? That's your starting point. All the documentation, as for almost 100% of products, is supplied in the universally accepted PDF format, readable on every PC using the free Adobe PDF reader. There is no other free universal format! How have you got by with a PC without ever reading a PDF? :-( There are only 4 items in the official current FSUIPC4.ZIP file - 747 OHD.MCRO APCHART.MCRO INSTALL FSUIPC4.EXE INSTALLING AND REGISTERING FSUIPC4.PDF Seems like you are getting two separate ZIPs mixed up, or you've not downloaded the correct package. Pete

Are those the IN numbers? They sound like OUT numbers, which indicates very poor calibration. If so just opress RESET, then SET again and calibrate properly. If they are the IN numbers, which seems very unlikely, there's something wrong before it gets to FSUIPC because the IN numbers reflect what it is getting from the joystick driver (assuming you assigned in FSUIPC) or direct from FS (if you assigned in FS). I still want to see that Install log file please -- I need to work out what input it is getting from your computer which is causing a crash. Pete

Sorry, what do you mean, "where is it?" I assume by "FSU" you really mean "FSUIPC"? Have you checked the documentation? Did you look at the Installation and Registration guide which was included in the ZIP file you downloaded? It tells you what it is installing and where it is! So why do you want to know "where it is"? Use the facilities presented to you in FS, via the options dialogues. Sorry, I've no idea what an "FNG" is. But have you tried using the documentation supplied at all? That's the first step. I can answer specific questions but I'm sorry, I am not going to repeat the whole manual here! Regards Pete

"Virtual"? GPSout doesn't create ports, it only uses them. You'd not use anything virtual on the FS PC unless you were also running the receiving software on that PC, in which case you'd use VSPE or similar to create a pair of virtual ports connected together, to funnel the data. If you want to use a serial connection to another PC you'd be using a REAL port, not a virtual one, and a serial cable. For a serial port connection you'd need a USB serial adapter and a cross-connected serial cable. Or use Networking and WideFS. Regards Pete

petedowson@btconnect.com. But I am off on holiday after today, till 25th. Regards Pete

Why reinstall FSUIPC? That won't change any of your calibrations or settings -- they are all contained in your FSUIPC4.INI file, which is unaffected by installation. If you simply wanted to rever to default settings, just delete the INI file and let it build a new one. The Install log up to the time of the crash would be of more use. I'd at least know what it was trying to do at the time. The crash data you provide is rather meaningless to me. What is "BEX" for instance? I just googled it and find it either means "Buffer Overflow Exception", or "branch extended error", depending who you read, and may or may not arise from "Data Execution Protection", which I think is either a BIOS or windows setting or maybe both. The error code "C0000417" appears to mean "STATUS_INVALID_CRUNTIME_PARAMETER", which could imply that there's some sort of problem in the C RunTime libraries installed in your system. The offset, 0000A005 seems to be in something called "invoke watson", which is not annything I use and I think is related to crash detection in any case. If that's the case it seems the crash detection is crashing? Which is a bit mind-boggling. Which "site"? Do you mean the Schiratti page with my stuff on it? Didn't you look in the Download Links subforum here? No, I've never seen it before. The Installer is a fairly standard sort of Windows program. it doesn't do much that is complicated at all. I need more information, such as the log and what the last line was in the Window on screen. What's the problem with putting the DLL into the Modules folder? What was your previous version, and what has changed. Why exactly are you reinstalling? BTW, I'm not sure this is the answer, but I found this when reading about "BEX": To configure DEP settings Click Start, click Control Panel, and then double-click System. Click the Advanced tab. Then, under Performance, click Settings. Click the Data Execution Prevention tab. Click Turn on DEP for essential Windows programs and services only to select the OptIn policy. Click Turn on DEP for all programs and services except those I select to select the OptOut policy. If you selected the OptOut policy, click Add and add the applications that you do not want to use DEP with. Maybe it'll help? If it is a problem in the Installer I certainly need more information to narrow it down, starting with the log and progress shown on screen. I'd then need to add more logging to narrow it right down. Problem is I'm on holiday after tomorrow till the 31st, with a brief return on the 25th and 26th. Can't see how anything related to any yoke or other USB devices has anything whatsoever to do with the FSUIPC4 installer, which is only doing things like copying files. There's nothing in it accessing any such devices. Regards Pete

I've taken the liberty of moving your portions of the FAQ informative thread into the main Support Forum, as this is where they belong and where you should expect answers. The FAQ subforum is meant to be a repository of answers, not a series of support questions. I've moved it without waiting because I am off on holiday soon and was worried it wouldn't be answered. Your value 16777474 is, in hex, 0x01000102, which indeed does have the value 2 in Byte 660F. You appear to be writing a Double Word (SD = signed 32-bit integer), which is possible but odd with such an odd offset like 660F. I would guess that whatever is using the 3 bytes after 660F is changing them from the 00 00 00 you are writing. Without any other idea of what you are doing, or what 660F - 6612 are used for I can't really help further, but I'm suspecting that you really want to write and read a single byte (SB or UB) not 4 bytes as you are now. This seems likely when you see what you are reading: 02 in 660F 01 in 6610 00 in 6611 01 in 6612 They all look like byte values for switches or other settings to me! Regards Pete

Yes, I see. You are using the ButtonScreen to send virtual buttons to FSUIPC for programming. I suspect you've not yet programmed any of the buttons in FSUIPC's button assignment tab. All the WideClient INI file does is label them for you. You still have to do all the assignments. Nothing can work them out for you! Pete

Thanks. I've left it as a round 100 for now as I think it will be pretty dependent on the system you use it on and the type of rotary, so it'll always need experimentation in any case. Regards Pete

Checkboxes where? There are no checkboxes as such in the Offsets reference documents. For those offsets there's a definite "No" in the columns for both FS2002 and FS2004 support. I've a feeling you aren't even using the proper reference materials, as supplied in the FSUIPC SDK. The Programmer's Guide is the correct reference for FS9 and before, whilst the FSUIPC4 Offsets Status document is for FSX and later. Regards Pete

Thanks Pete, where do I find this information information. Is this something in the PC running FS9 or in the Ipad. Excuse my ignorance. Sorry, I am ignorant as well. I really have no idea. I have an iPad but i have no idea how to connect it to a PC by BlueTooth. I've only ever managed it between my iPad and a friend's, and then it didn't work very well at all. Perhaps you can tell me? What goes into the PC for this? Regards Pete

Actually my program is not called "Autosafe" but "Autosave". AutoSave has absolutely no control over WHAT is saved. It simply calls the FS flight saving routine at the intervals you specify. Apart from the automatic naming of the flights it is the same as you doing it manually by pressing ; and entering a name, of using the Flight Save menu entry. Try those methods and I'm sure you'll find the same results. So, it is some function of the add-on aircraft i assume you are using. You need to seek help in that direction. Regards Pete

Good! Sorry it took so long -- a lot of red herrings on the way! Okay, thanks. I'm thinking of providing the code as one of the samples in the Lua plug-ins package. Should I change the timing in that do you think? I assume you mean this line: FastTimeLimit = 60 -- Adjust to taste Better at 100? Thsnks, Pete

It'll be easy to detect it undocked, because it is then a top level Window, and FindWindowEx will find it by its title. When it is docked i'm not so sure. In Windowed mode it should still be a Window, but it'll be a child of FS, so you'd first need to get FS's window handle (FindWindowEx for classname "FS98MAIN" --- don't ask!), and specify that as the owner and/or parent. But in full screen mode I'm not completely sure they are true windows. But by all means experiment. Regards Pete

It wasn't necessary to do any of that. The Lua files don't run unless you tell them to. All you needed to do was not push the button to start HidDemo -- you certainly don't want that running at the same time as the Rotaries one. As they stand they conflict. If you want to run both together I can tell you how to change one of them so they don't conflict. The Lua log shows: 34913 Button 30 pressed 34975 Button 30 released 36285 Button 30 pressed 36379 Button 30 released 37892 Button 31 pressed 38001 Button 31 released 39218 Button 31 pressed 39327 Button 31 released So that's fine. The FSUIPC4 log shows the first 4 events, 34944 WRITElua 3340, 1 bytes: 01 . 35006 WRITElua 3340, 1 bytes: 00 . 36317 WRITElua 3340, 1 bytes: 01 . 36410 WRITElua 3340, 1 bytes: 00 . each occurrence being only around 30 mSecs after the Lua logged it. But then nothing for button 31. Now the one glaring error here is that in your Lua program, button 31 is listed BEFORE button 30. So button 31 should be joystick 64, button 0 and button 30 should be button 1. But we are seeing button 0 for 30 and nothing for 31. So it looks like the error is in the Lua code (untested as we now know, at least before you started using it!). Button 31 is probably trying to be button -1. ie. the code is one out. Interestingly, if you'd used buttons 30 and 29 (etc) you'd have been fine and we'd never have discovered this bug. Only buttons 31 (and probably 0) would go wrong. So, the error is in this line: mask = logic.Shl(1, Rotaries[j]-1) This is written assuming you count button numbers from 1. But we don't. Your buttons 31, 30 are the last two -- the first would be 0. Obviously we don't subtract 1 from 0 to compute a shift to the left! I think this mistake arose from the mixture between thinking in "C" (my native prograsmming language) and in "Lua" (which is certainly not). Lua always counts from 1. "C" alsways counts from 0! The correct line is: mask = logic.Shl(1, Rotaries[j]) Now please tell me this works! ;-) Note that this will reverse the rotary action. Rather than reprogram it in FSUIPC you might want to simply swap the button numbers over. i.e. Rotaries = {30, 31} Then we need to find other postings of the code and correct those. Can you tell me the source you found, please? Regards Pete

Sorry, i don't know any way to determine when ATC audio is playing. As for the ATC window, i can only suggest you use the FindwindowEx API to see if the ATC window exists and is visible. Use its title -- "ATC Menu" I think). I'm not sure if this can be done if the ATC window isn't undocked, but i suspect it should be possible. Regards Pete

Yes, but the DLL has a Version number in its "Properties", and it displays the version number on screen in its options, and it logs the version number in the Log it provides. That's at least three easy ways of finding it. Was there some information in the screenshot? Sorry, i couldn't read it, and actually I don't see the point of going to such trouble when it is so easy for you to find version numbers. Ah! it is time to learn then! You'll certainly need to know one day: ;-) First, something you can use with pretty much any program or DLL: 1. Right click on the program or DLL, select Properties- Version, or Properties-Details (depending which Windows version you use) Second, for any of my programs which produce a Log (FSUIPC, WideServer, WideClient, PFC etc) 2. The version number is shown in the first line of the Log file. Third, for FSUIPC3, FSUIPC4, PFC, PFCFSX and several others, programs which add a menu item into FS: 3. The version number is shown in the Option setting dialogue, normally on the first tab. Pete

Please do try the more recent PFCFSX.DLL from the Download Links subforum. Currently it is version 4.379. i think there was a change in the way the fonts are selected for the dialogue which did get around some types of graphics driver differences. Pete

Okay, good. FSX does not allow any program to set the height of the clouds. It determines that automatically using some algorithm based on cloud types. FSUIPC4 just ignores the "UpperAlt" value. it is used in earlier versions of FS. Sorry, I think I missed the question? Pete

A screenshot of what? What does "a dll only file" mean? Did you not read my reply? All I asked was the version number. (If not 3.998e or later, try that). Pete