Pete Dowson

Sorry, I dont understand what you are asking. All I said was that, since we are trying to work out why the menu selection doesn't make the Options appear, providing extra logging without you even trying to open the Options will tell us nothing. How can it when you are not even trying the action which supposedly doesn't work? What's all this about changing the INI file? I thought you said you'd added the lines I mentioned. Those are there to give us the logging we need. If you take them out, what's the point of any ofr this? Please just do as i said. We are getting no where otherwise. Pete

Why are you "reloading the axis assignments". They never need actively reloading unless you've edited the INI file whilst FS is running. What is the symptom of them not being loaded? How can you tell? When you move the axes, what do you see which tells you this? Pete

From which version did you update? If that program is written well such errors should not actually stop it working. If it did then any temporary stoppage of SimConnect returns to fSUIPC would effectively kill it. Looking at your log that is what appears to be the case. It looks like you had a clean run for an hour and a half before the above problem arose. The error there is that SimConnect did not send any data updates for over the time allowed. That can be adjusted (SimConnectStallTime in the INI file), and defaults to 1 second. SimConnect may take longer than this, but it certainly shouldn't because a lot of the data needed updates every frame -- 30 times a second for example. But in this case extending it to, say, 2 seconds may allow things to continue better because I see, again from the log, that after the error the session recovered and continued without error for another two hours and 20 minutes! Pete

Okay, so it will not be of any use. Obviously (?) I need to see a log for you trying to open the FSUIPC options from the menu. Otherwise how can it tell me what is wrong? Pete

Ach! never mind. I just spotted the problem. In your FSUIPC4 log file, it was there all the time: .. Prepar3D has been renamed as "prepar3d.exe" This message should never appear unless you've renamed the EXE file in the main folder. It expects it to be "Prepar3D.exe" and if it is not it tries to match the new name in its own files -- the KEY, INI and LOG files, in fact. Can you check, please? The message above puzzles me, as it seems to imply that it was renamed with the original name (just lower case 'p' instead of 'P', which shouldn't matter ... though I'd need to check that). This action in fSUIPC derives from facilities included years ago to allow different FS CFG files to be used with different matching FSUIPC INI files. The different CFG files were named after thedfferently named EXE files. Everything sort of ties together. [LATER] No, renaming Prepar3D.exe as prepar3d.exe doesn't make any difference here. [LATER STILL] It looks like that message means it sees the Prepar3D program as being named Prepar3D.exe.exe which is most peculiar indeed. (FSUIPC strips off whatever follows the last '.' before putting the name in the message). Pete

I don't think that's right. The problem between ASN and FSUIPC was only that in versions between 4.924 and 4.925a, inclusive (fixed in 4.925b and later), things like wind smoothing and turbulence effects were prevented from operating because FSUIPC took over the hooks ASN needed into FSX. There has never been anything whatsoever in FSUIPC which can possibly cause ASN itself to crash. It is an independent program and doesn't use or need FSUIPC at all.. So, whoever told you that on the ASN forum is wrong. Please go back and try to get an answer from someone who knows what he is talking about. The problem you have sounds more like a corrupted install of ASN itself. Pete

What does "pops out" mean? And what is it which "pops out"? And how does it stop you not doing anything? If you have a problem with ASN you need to go to the ASN support Forum. That parameter certainly has nothing to do with "popping out", whatever that may be. It also has nothing to do with ASN. Sorry. Pete

The key file is in the correct Modules folder, and it is correct (i.e. it matches what you entered), yet FSUIPC still appears unregistered? That's only ever happened before when the computer system date is wrong, when it precedes the registration date. If you haven't disabled UAC, then the modules folder you are looking at may not be the real one. That's one problem of installing into Program Files. Best to switch UAC off or always instal in separate folders -- like C:\P3D, nice and short and easy! Else run Explorer by right-clicking on it and selecting "run as administrator". That should enable you to see the real folder. Maybe you should ZIP up the KEY file and send it to me at petedowson@btconnect.com. No, I don't think that's a good idea. in any case, NEVER delete P3D, use the proper uninstall in the Control Panel. No. Pete

So, what sequence of events will the log file relate to? Pete

This offset in FSUIPC: <Parameter7>000138fc</Parameter7> indicates the exact same error as in 4.927 not 4.927a. I cannot see any way for the path through here could possibly be okay for 5 hours then suddenly change. Are you absolutely sure those error details you posted are not from an earlier problem? They look identical to what you'd expect with 4.927, not 4.927a at all. Maybe you'll just have to change the InterceptTextMenu parameter to 'No' instead of 'Yes'. Or I shall remove support for the facility in SP2 -- because i don't think there will ever be a way for me to see why things changed after 5 hours! That routine is being used at a rate of something close to 50 time per second in normal flight! :sad: Pete

Sorry, I had to move your post from "download Links" to the proper Support Forum". For now it is here, in the 4.927 link but i'd really preferred you start a thread with an appropriate title. I can't really continue support in the SuForums which are designed as points ofrefference for users. All support needs to be carried out here, in the Support Forum. Which "fatal error" are you talking about? After 5 hours all the possible routes through FSUIPC have been thoroughly exercised! It doesn't change behaviour over time, so this is most puzzling. Okay, I'll take a look. But I'd like some context, please. What is this really related to when you say you thought "the fatal error had gone"? Pete

No, don't do that. I see the results, this time, of entering your key was logged as "successful". And you say there IS a KEY file -- in the P3Dv2 modules folder? That is actually a Text file, and it contains your name, email and Key. That's all. Don't post it here, but load it into, say, Notepad, and check it. It that is correct. If it is, and it IS in the installation of P3D you are actually using (i.e. in C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules, then I am stumped. The last time we had anything like this it (eventually) turned out that the chap was actually booting FS from an entirely different installation which wasn't known to the Registry and therefore not updated by FSUIPC's installer. You DID run the installer with right-clicking and selecting "run as administrator", as instructed, didn't you? Windows has an awful habit of protecting all Program Files (x86) files frombeing changed, and even shows tyou aliassed versions of the folders in Explorer. Regards Pete

Is this the message you were telling me about: ? Did you enter your name, email and key when asked? If not, then you need to do that! If you did, was it accepted? I'm trying to work out what you are doing and what you see. It isn't easy to understand from what you tell me. Regards Pete

In that case it never gets connected to SimConnect, because that logging logs a line every time it receives anything from SimConnect -- including the response to the Open request. If it never gets anything from SimConnect it logs an error and keeps trying to reconnect, logging every time. Your earlier log shows no such things happening. So, I think you didn't add those two lines correctly in the INI file before running FSX. Perhaps you'd better show me the INI file. Pete

Where do you see that? Is the registration accepted in the dialogue when you enter it? If not then you are getting something wrong. every part -- name, address, key -- must be correct. How were you entering your details before? It's nothing to do with that. Deleting P3D is not the same as uninstalling it. That's probably where it is all going wrong, but I can't tell a thing without seeing the Install log file. Paste it here please. Well, if you deleted the Modules folder, yes, of course you did. All you needed to do was copy your INI and KEY fies from P3D 1.4 to P3D v2. I think the problem will be that non-uninstalled copy of P3D 1.4. The registry will still be setup for that version. But I can tell from the Install log file. Pete

Sorry, what did you expect to happen? All those lines are for are to generate extra logging, in the FSUIPC4.LOG file, so that I can see what is happening. They don't change anything else! If you mean the LOG files you pasted in earlier, of course they were text files, otherwise you could not have pasted them here. Log files are logs of events happeining, and are written with text so they can be read. Well, unless Roger Wilco replaced some Windows components, or corrupted SimConnect or other parts of FS, which seems unlikely, that is probably just a coincidence. I haven't got enough information to help yet, that's why I asked for the extra logging. Pete

Unfortunately that isn't any help at all. If it were in SimConnect then it would most likely be a corrupted SimConnect installation. FSUIPC does use SimConnect extensively and continuously, so a problem in Simconnect would certainly be more likely to show up with FSUIPC installed. The NTDLL modules is a collection of most of the more common functions used by all programs in Windows, so identifying that is no help at all. If it only happens when using the on-line module then its additional full use of SimConnect would be contributory -- if it doesn't fail with FSUIPC installed but the on-line module not installed, that would be an equivalent indication to a different 'cause' as the one you are intimating, wouldn't it? You do really need to consider all aspects of what you have installed. There may also be other Simconnect clients contributing to the problem. You would really need to do a full exploration of the alternatives. BTW you don't mention the version of FSUIPC. The currently supported one is 4.927a. Regards Pete

If this still happens with controllers completely disabled in FS, and no [Axes] sections at all in FSUIPC4.INI, then the only way is a process of elimination between all the add-on programs and add-on gauges you may have. Regards Pete

Yes, right. I found a silly typo affecting SP2 only. The work-around above will fix it, or download 4.927a now available. Sorry, It's been a very busy period what with ASN mods, P3Dv2 and Christmas with family coming looming, all just after a holiday! Oh, and I'm definitely getting senile! Regards Pete

Ouch! Are you all using FSX SP1 or SP2, not Acceleration? Please let me know. I need to nail this. Meanwhile please change the InterceptTextMenu parameter to 'No' instead of 'Yes'. Pete

What version of FSUIPC? Please try using the latest installer. The only reason found for the problem you describe is a failure to copy the KEY file generated in a P3D version 1.4 folder to a version 2.0 folder when there's no FSX installation. That was fixed a couple of releases ago. The current release is 4.927. Pete

Hmm. That all looks perfect. The menu entry has been added and there are no errors reported from SimConnect. I assume you tried using the Menu during this log period? (If not, then the log is not indicative anyway). I need more information, more logging. .Please add these lines to the [General] section of the FSUIPC4.INI file: Debug=Please LogExtras=x4001 The log might get quite big. If so ZIP it up and send it by email to petedowson@btconnect.com. Pete

Hmm. Never heard of that before. Can you show me the FSUIPC4 Install log and the FSUIPC4.LOG files from the FSX Modules folder please -- paste them into a message here. Pete

Is there an Add-Ons menu? What is listed in it? Pete

Which is true. It looks like that is a data file. You need to run the program which loads it, instead, giving the panel name as a parameter. The only reason it runs when you use the mouse is that you, or an installer, has told Windows that this type of file is associated with that program -- just like a file of type PDF gets Adbe Reader to load, and .TXT files are default associated with Notepad. File associations only work with Explorer, not with the "CreateProcess" methods used by WideClient to run programs. Regards Pete