Pete Dowson

Strange!, because I cannot reproduce this here. When I create a new profile whilst UseProfiles=Files, it creates a [Profile.<name] section in the main INI file, listing the aircraft name (this part is needed so FSUIPC knows there is a profile for this aircraft), but the settings are then saved as <name>.INI in the Profiles folder. If this is not happening for you, perhaps you could please tell me step by step what you do -- maybe there's a path through the assorted options which does have such a problem. Pete

But I've read just as many reports that say it doesn't help. I really don't see any reason why it may help as it uses pretty much the same Windows options as FSX. Sorry, I really don't know. It just uses the standard DirecInput interface to Windows, and there's really never been problems with Win7 or XP. There seems to be many problems with Win 8 and Saitek devices especially. Have you tried using their software? Perhaps there'll be more help on the Saitek Forum? Personally I'm steering well clear of Windows 8 (and Saitek, for that matter). Pete

No, not in FSUIPC. But you can specify that they should not be run until you are ready to fly -- put "READY" in as well. For more ambitious schemes you could use the Lua plug-in library ext which handles running of external programs. Pete

Unless this action is simulated in the specific add=on aircraft, it isn't anything supported internally in FS. If the switch on the panel does work, and the aircraft maker has not supplied a key press shortcut for it, then there may be one of two possible solutions, but it isn't guaranteed: 1. FSUIPC mouse macro. This where where FSUIPC traps your use of the mouse to activate the switch, and then provides a way of doing it directly. This method only works with panels designed in C/C++ with the Microsoft SDK. Look up mouse macros in the FSUIPC documentation. 2. Local panel variables, or "L:Vars". If you can find an internal variable used for the switch you might be able to program a button to write to it You can use the added FS control to log L:Vars, or use the Lua plug-in provided to monitor them as they change. Pete

OKAY. Please download the Install FSUIPC4937 package again from Download Links. I've made the Installer bypass the SimConnect check for P3DV2 (only). Before your report I hadn't realised P3Dv2 installed without any separate SimConnect DLLs at all. I knew it was capable of supporting SimConnect without those in the WinSXS system, and has been so since version 1.4, but the older P3D installers did actually install the ESP version of the DLL in the WinSxS folder. Odd that we've reached the 5th version of P3Dv2 and you are the first to discover the problem. Thanks for reporting it and sorry for the delay. Regards Pete

Okay. From the look of it the Server broadcasts simply are not being received on the Client. That maybe because the FS PC and Client PC are on different workgroups -- you can change one to match the other, or simply put the ServerName and Protocol parameters into the WideClient.INI file on the Client, as described in the part of the WideFS documentation which has the RED instruction urging you to read at least some of it -- i.e. configuring the network. By having the server name and protocol defined in the INI file the Client doesn't need to wait for any broadcasts from the Server, so it can be more efficient too. The broadcast method was only added to make it simpler most of the time. Pete

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