Pete Dowson

Show me the logs -- WideServer.log from the FS PC and Wideclient.log on the Client PC. Also FSUIPC.log from the FS PC. Paste them into a message. Pete

FSUIPC.DLL would probably be FSUIPC version 2 or 3 or before, not for FSX or P3D, only for old versions of FS. And it won't be used or touched in any case. You'll need to check the other add-ons you are using, do a process of elimination. Pete

The sound devices which the App can choose from are listed in the FSUIPC INI file. It is probably using the default, which you can change in Windows Control Panel I think. Maybe, but that should never cause a crash like that. It definitely sounds like a broken driver. See if there's an update available. Maybe in a collection of stuff for your motherboard. Pete

Okay. Thanks. Yes, it did terminate tidily, as i thought. I might get back to this tonight before bedtime, but it's dinner time now. If it is an easy fix I'll post a 4.937a install package soon. Without making a mess of my existing systems it isn't easy to test here, but I'll see what I can do with a bit of judicious renaming! ;-) Pete

Okay. It probably does log that you did this and writes a final line, but maybe has nowhere to save it if it hasn't yet created the Modules folder. Pete

You must run it first, otherwise things the Installer needs aren't available. No, sorry. Okay, thanks. Is there nothing further after that last line? Did you abort when the error message box appeared? I'll investigate tomorrow. Too late for today. Looks like no one else ever had an installation without any WinSXS SimConnect versions at all. Presumably the new P3D doesn't need such? If you want to move on just run a SimConnect installer, either the ESP one (for which I believe someone posted a pointer, or it may be available in the P3D SDK), or the SP2 one from FSX. I suspect you might need to do this in any case for some add-ons being ported from FSX. Pete

But that cannot be the correct Modules folder, because it does not include FSUIPC4.LOG or FSUIPC4.INI. Those MUST be present, else FSUIPC has not been run. Your whole problem is looking in the wrong place or with the wrong privileges as I already stated. You are being rather blind and obstinate. There is ABSOLUTELY no possibility of those files I mention being missing if you are looking in the right place with the right privileges. If you persist in this strange and daft attitude there's no point in me trying to help you any more. Pete

Seems that 4.937 installed without problems too, else there's no way you could try to run it! So you need to investigate that other software? What is it? Maybe it is causing the problem in SimConnect which causes the crash when SimConnect tries to load FSUIPC. If FSUIPC is not make a new log then it is not running. See the FAQ thread on this subject. What does that mean? Pete

Ah, but that is from version 4.936, whereas you said you were using 4.937, and it shows an almost perfectly normal start, run, and close, no crash. I would have suspected it was an old log from an earlier time, but, no, the time stamp gives it away: System time = 10/10/2014 15:59:16 So, FSX did not crash after all? Or only after FSUIPC had been closed because the session was ending? FSUIPC didn't get as far as "Starting everything now ..." so you were never actually flying? Pete

The event log data shows a crash elsewhere, not in FSUIPC, so I'm pretty sure it is the SimConnect bug. What version of FSX are you using? If it isn't fully updated, SP1 + SP" or Acceleration, when I think you need to update it. The problem was much worse in the earlier releases. If there is an FSUIPC4.LOG file, which looks doubtful because it is likely that FSUIPC never even got as far as running, then it will be in the FSX Modules folder, along with FSUIPC4.DLL, FSUIPC4.INI, FSUIPC4.KEY (if you registered) and a subfolder called FSUIPC Documents. Pete

The first two prompts are standard and will occur every time you run FSX with a new version installed. This occurs with all unsigned DLLs being loaded automatically into FSX. But without further information about this "fatal error" I cannot really help. If you cannot read the detailed information off the screen, go to the Windows event viewer and find the correct entry in the logs there. If FSUIPC is producing a Log file, please show me that. If it isn't then you are probably suffering from the SimConnect trust bug. Please see the FAQ subforum here for more information about that. Pete

Yes, of course. You can either use the utility "ShowText.exe" (see Download Links subforum), or a Lua plug-in -- in fact the RC menu display is the example shown in the Lua library documentation, at the end of the wnd library section. Pete

This is my comparable log section running FSRaas20: and all those WAVes played okay. Your system is crashing in the sound system just after this linr: 96924 WRITE0[308] 4200, 4 bytes: 01 00 00 00 which is simply the command to play the sound wave identified beforehand, i.e "on runway.wav". I'm sorry, but I can't think what else could be wrong other than a corrupted "on runway.wav" file. Does it play okay on its own, through Windows media player or somethnig? Pete

There's been no change to this part of Installation. In fact the only change in the Installer is to allow the increasing Build numbers without warnings. Many folks have installed for P3D with no problems, clean or otherwise -- everyone's system starts off "clean". Are you sure you ran P3D before attempting to install FSUIPC? Have no not installed any prior version of P3D before this? I would certainly like to see the Install Log please, which you omitted. Best to simply paste its contents into a message here -- just use the <> button above the Edt area to encapsulate it. Pete

If there's no FSUIPC4.INI nor KEY file then either you are looking in the wrong place, or FSUIPC has never been registered nor run. It ALWAYS creates an INI file, and the KEY file is created when you register. There is no way "FSUIPC works fine" if it isn't even running. If it IS running there is most certainly an INI, a LOG and a KEY file, amongst others. You are looking in the wrong place for certain! This is why you do not see the LUA files, because you have put them in the wrong place!! Try running Explorer "as administrator" (right-click, select "run as ..."). Maybe you have limited rights and you are looking an an alias to the Modules folder not the real one. Windows 7 and 8 play silly tricks like that if you have UAC enabled. Please yourself. But only you can work out what you are doing wrong, I can't see your PC from here. Pete

Sorry, I don't understand. AIBridge was just a program used to put Multiplayer aircraft into FSUIPC's TCAS tables, alongside the AI traffic data it already gets direct from FS. I don't understand why AIBridge has stopped working, but there is no code in either WideFS or FSUIPC to handle or understand multiplayer aircraft. It only knows about AI traffic. Pete

Okay, I can investigate that now. Could you do it once more, please, but this time enable IPC write logging in the FSUIPC logging tab before running FSRaas? (Don't press anything else in that tab). The log from that should nail it down more exactly. [LATER] Okay. I found a copy of FSRaas20 and ran it with my FSX setup, and it works fine. Looking again at the crash report in the Log I think it is crashing in one of the sound functions provided by Windows. Without knowing just what system DLL is located at memory addresses 77418E19 and 76F48E19 I can't really advise the exact action you might need to take, but the following come to mind: 1. Uninstall the sound device, whether it be an add-in board or the main motherboard (all my PCs only use main mobo sound). Re-boot to let Windows reload the sound stuff. 2. If you are using an add-on sound card, try the mobo sound system instead. 3. Try reinstalling FSRAas20 altogether, removing all previous files, in case it is down to a corrupted file. FSRaas is using FSUIPC's sound facilities to play the sounds, and FSUIPC calls the Windows sound facilities to play them. I am pretty sure it is somewhere in those where the crash is occurring. Since it works fine here I can't really delve any deeper. Pete

Sorry, I don't know what "did the trick". I just found that the code I gave worked and didn't think to check whether things I was writing actually did change things. Checking FSUIPC's internal table, yes, I agree, writing to 0246 probably doesn't do anything. Maybe just writing the correct Local and Zulu times does the trick. Or even just one or the other. FSUIPC itself doesn't actually have anything writing time -- I use that Lua code from my Clocks and I believe the program "FSRealTime" does something very similar. Probably you cannot force a time zone other than the one the aircraft is actually in, which makes sense in any case. Pete

Sorry, but version 4.53 of FSUIPC is extremely old (it dates back to August 2009!), and long time unsupported. The earliest supported version is currently 4.937. You must update. Pete

Well, FSUIPC doesn't need MSVCR1000.dll and doesn't use it at all, so I think that's misleading. I suspect you are not updating FSUIPC to keep up with P3D changes. The current version of FSUIPC is 4.937 which was released to work with P3D 2.4. Every time you update P3D you will need to look for the subsequent matching update to FSUIPC. Please, in future, ALWAYS state the version number of FSUIPC you have installed. Without such information diagnosis is not possible in any case. Pete

FSUIPC Documents is there the documents are, not the files I mentioned. The Lua files must NOT go there, only in the Modules folder!!!!! i.e. C:\Program files (x86)\Microsoft Games\Microsoft Flight Simulator X\....Modules Why are you putting everything in the documentation folder? That is where the documentation is!! Pete

But earlier you said that you had put the Lua files "near the files of FSUIPC". If there are none of the files of FSUIPC there, why did you say that? Are you sure your confusion is not simply because you have Windows Explorer hiding the types, DLL, LOG, INI and KEY from you? If so please do change the Windows folder options to show them, as instructed in FSUIPC documentation. If the FSUIPC Documents folder is there, and you are "happy with FSUIPC4", then it obviously MUST be there -- it is just that you are not seeing it for what it is!!! Er, this must be a folder you have created, or the folder where you downloaded FSUIPC! FSUIPC NEVER creates any folder for installation -- the Install FSUIPC program is the one you must have already run, as you said you entered the Registration key AND that you were "happy with FSUIPC4". So, sorry, what you now say is not making any proper sense whatsoever, and I am concerned that you are going off half-cocked and making a real mess of things! :-( I must ignore the rest of your report as it makes no sense. If you have ever used FSUIPC4 at all, and as you say you are "happy" with it I must assume you have, then there will be those files I mentioned AND the "Install FSUIPC4.LOG" file too. The fact that there's an FSUIPC Documents folder also means that the Installer was run okay beforehand. Please stop messing about as you will make things worse not better. There's really nothing to go wrong with FSUIPC4 installation unless you start messing with file positions and Registry entries. Please just do as I advise. Pete

The FSUIPC.BAS file is most certainly inside the "UIPC_SDK_VisualBasic.zip" file along with the other files relating to VB. That ZIP in in the FSUIPC_SDK. It has not been changed for many years. All of the files in the SDK are contributions from others, programmers in the respective languages. If you want a more up-to-date interface facility you may wish to look at Paul Henty's .Net interface package -- see the separate SubForum dedicated to this, above. Pete

The list is only selectable AFTER you have selected a key for assignment. They will be listed as Lua <name> where <name> is the Lua file name. Only the first 127 Lua files in the Modules folder can be handled. Please do make sure you placed the files in the correct FSX\Modules folder. There will also be the files FSUIPC4.DLL, FSUIPC4.KEY, FSUIPC4.INI and FSUIPC4.LOG, as well as a subfolder, FSUIPC Documents containing the documentation and Lua examples. If you still have a problem, please show me the LOG and INI files. You can paste their contents in a message here -- enclose them with the <> button above the edit area. Pete

I can only show you what appears to work using FSUIPC's Lua plug-in facilities. This code sets the current date and time correctly: t = os.date("!*t") minsdiff = ipc.readSW(0x246) ipc.log("Date/Time Set: " .. os.date("!%c")) lhour = t.hour - (minsdiff/60) if (lhour < 0) then lhour = lhour + 24 elseif (lhour > 23) then lhour = lhour - 24 end lmin = t.min - (minsdiff%60) if (lmin < 0) then lmin = lmin + 60 elseif (lmin > 59) then lmin = lmin - 60 end ipc.writeStruct(0x0238, "6UB", lhour, lmin, t.sec, t.hour, t.min, t.day, "2UW", t.yday, t.year, 0x0246, "1SW", minsdiff) Offsets used here are first 0238, 0239, 023A which makes:LOCAL TIME 023B, 023C which makes ZULU TIME 023D ZULU DAY OF MONTH 023E ZULU DAY OF YEAR 0240 ZULU YEAR 0246 TIME ZONE OFFSET So, what I think you need to do is set Zulu data and the time zone offset, at minimum. When setting it to other times (eg with my Boeing 737NG clocks) I read the current offset and write it back with the new time. It took some experimentation to get this working. Pete