Pete Dowson

This makes no sense. How is it you have two installations of FSX-SE? What are the different Modules paths? Which one are you running? Steam itself only installs ONE copy, which will go into the Steam folder (wherever you decided that should be). So C:\Program Files(x86)\Steam\steamapps\common\FSX would be correct if you let Steam itself decide where it should be placed. The log files named by SimConnect would be SimConnect0?.log, where ? runs from 0 to 9. Just look for files using the mask SimConnect*.log Maybe there are log files there but you are not seeing them. Maybe you have Windows Explorer folder options set (as they are by default) to hide known filetype names from you. Log files would appear just as text files most probably. To make it easier for you to find the log, why not just tell it to save the log to the C:\ root directory. i.e. file=C:\SimConnect%01u.log You say: I am wondering if this is the root of all your problems. There cannot be two copies if you let Steam do the installation. It isn't bad news for me, only for you. It seems likely that your Steam installation is in a right mess. If SimConnect won't load any DLLs then there's no way I can fix it from here. I can only make my program work when it is being loaded, which is FSX-SE's job.. I'm only trying to help you find out what is wrong with your installation, and so far all we seem to have discovered is that you have two installations! Looking back now at the Install log you posted I do now see that the registered path for FSX looks okay, but the one for FSX-SE, which should be identical, points to the incorrect one you mentioned earlier: Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX Parameter"Install_Path" ... >>> OK! FOUND FSX-SE! <<< ... SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX\steamapps\common\FSX Looking further down, the actual FSUIPC installation sensibly only uses the correct path: INSTALLATION FOR FSX:SetupPath="C:\Program Files (x86)\Steam\steamapps\common\FSX\" Checking version of the FSX EXE: ... Version 10.0.62615.0 (Need at least 10.0.60905.0) ... NOTE: This is actually FSX-SE masquerading as FSX-MS which also means it ONLY installed into the Modules folder in that copy, NOT in any Modules folder you might have in the place with the more convoluted path, the one which certainly looks wrong. So, are you perhaps running the wrong install of FSX-SE? Try running (double-clicking) the FSX.EXE in folder C:\Program Files (x86)\Steam\steamapps\common\FSX\ If that doesn't work, it might be best for you to start again. Uninstall it all, including Steam, and re-install from scratch. In fact given the mess int's in, it might be best to do that in any case. Pete

You just installed P3D version 3.1? Really? I think you should be on 3.2. Why are you now installing an older version? And I ALWAYS need version numbers. Just saying "latest version of FSUIPC" is no help. Folks have said that meaning the latest they bothered to download, or latest they already had on their system, and they've sometimes been a year old! Finally, I need more information in any case, like the Windows crash details, the FSUIPC4 Install log, and the FSUIPC4 run time log (two log files in the Modules folder). You can paste these into a message here. Pete

Of course. They are needed. As I said, it's the '-' characters (the hyphens) at the start of those three lines which are wrong/ No. Not only does it look completely wrong (the same path is there TWICE!), but it doesn't contain a filename! There is no way a SimConnect.log file can be produced because you've not told it what the filename should be! The filename is the name of the file you want to see. The path only tells it where to put it. You can put it in C:\ if you like! Did you not actually read the FAQ thread I mentioned. Look now. See the "file=" line? file=path to FSX\Modules\SimConnect%01u.Log Then see below where it says: where you need to replace the "path to FSX" by your particular path for the main FSX folder, Just so you can see this more clearly, I'll highlight in read the parts you seem to have ignored: file=path to FSX\Modules\SimConnect%01u.Log where you need to replace the "path to FSX" by your particular path for the main FSX folder, The "SimConnect%01u.Log" part is the filename. SimConnect will replace the %01u" part with a number, 0-9, changing each time you start FS again, so it can save the last 10 logs altogether. Your entry appears to be two copies of just the "path to fsx" stuck together: C:/Program Files(x86)/Steam/Steamapps/common/FSX/Steam/steamapps/common/FSX You also appear to be using / characters instead of the correct \ characters. The / character is used mostly in URLs (in browsers). File paths in Windows use \, again as shown in the thread you should have referred to So, unless you somehow explicitly told Steam to install it into such a convoluted path, it will be just C:\Program Files(x86)\Steam\Steamapps\common\FSX Also you omitted the "Modules" part of the path needed altogether. Putting it all together, the file= parameter you needed would be: file=C:\Program Files(x86)\Steam\Steamapps\common\FSX\Modules\imConnect%01u.Log Next time please read things more carefully. You made at least six different mistakes in doing something which was spelled out. Pete

Er, just monitoring those offsets doesn't change them. It doesn't change anything. You must have done something else differently. Maybe you didn't have WX Radar switched on before? You didn't add those two lines to the INI file I mentioned, so the logging is not diagnostic in any case, so if it wasn't working it wouldn't have helped. All the monitoring shows is: Before everything is started: 43337 Monitor IPC:861C (U16) = 0 ......range = 0 43337 Monitor IPC:8624 (U16) = 0 .......wx radar = off Then things kick off: 94677 Starting everything now ... 94693 ASN active function link set 94693 Ready for ASN WX radar and the Radar is switched on nearly 30 seconds later (presumably when Prosim starts): 147000 Monitor IPC:861C (U16) = 50 ........range 50 mn 147000 Monitor IPC:8624 (U16) = 130 ........radar switched on with stabilised antennae option selected 7.5 seconds later: 154519 Monitor IPC:8624 (U16) = 2 ............radar switched off again! (Maybe the battery was off and Prosim just finished initialising) 16 seconds later, I assume you switched things on, and the WX Radar is switched on again: 170353 Monitor IPC:8624 (U16) = 130 This is what FSUIPC's monitor is telling us. But monitoring values does NOT change them, so you definitely did something differently! Pete

Sorry, but it appears it is local to you after all. In my hurry to test and compare with FSX, I didn't quite get things the same in the tests. In fact, because the parameters were not correct in my P3D test, the WX Radar was turned off. When it is turned off you get a blank file of 1kb. I ran some more tests, and once things are definitely the same in both FSX and P3D, then the results are definitely the same -- a good Radar image. To check that your radar option has been turned on by Prosim, you need to examine some offsets (the WX radar is controlled by offsets, as listed in the back of the "ASN WX Radar facilities in FSUIPC4" document in your FSUIPC Documents subfolder. So, as well as the logging I suggested earlier, do this: In FSUIPC options, Logging tab, on the right-hand side add these two offsets to the 4-entry table: 861C type U16 (this is the range in nm) 8624 type U16 (the top bit here is the ON/OFF switch, the other bits are for options). Then check "normal Log" below, and ok out of there. Run like that with ASN running and Prosim presumably asking for weather radar for display, then show me the log. Pete

Since my post above, I installed P3D3.2 on the same PC on which I use FSX-SE and ASN, and installed the P3D version of ASN, to test. With exactly the same weather being set in ASN, FSX-SE does generate the weather radar data and it is received regularly by FSUIPC. In P3D3.2 there's never any weather data provided. I checked with exactly the same settings in both FSX-SE and P3D3, so I think either ASN os broken in this area, or there's a P3D bug. I have no way of finding out which, so I have asked the folks at Hi-Fi (the makers of ASN) to check this out for us. I'll post any further information about this I may receive, but I can't do anything further myself at present. Pete P.S. For information, these were used in my tests: ASN version = P3D, 1.0.5921.17125 FSUIPC version = 4.949p P3D version = 3.2.3.16769

53 decimal = 35 hexadecimal. There are exactly the same value. The only difference is in how it is presented to you. In binary (which is how it is actually stored) it is 00110101. Key press and button programming is exactly the same. If you think the same thing is working in one and not in the other, please show me the FSUIPC4.INI file with both programmed. Pete

I can't see anything even vaguely related to such a setting exposed by SimConnect, so I wouldn't know how to find it. I'm well past my hacking days I'm afraid, the techniques I used for FSX and before, and now I have to relay on what SimConnect provides. Let me know if you can find any way to detect it, and I'll implement it. Pete

But it should be "radar.bin" not "radan.bin"! 1kb or 0? What do you mean by "NULL" for 1kb? It migh well be 1kb if there's no weather to display. I don't know. The size will vary according to the range and resolution selected by Prosim. All FSUIPC does is pass its requests on, receives the data and writes it directly to the file. If the file is being created then FSUIPC has does its part. It might be useful to check the FSUIPC4.LOG file. It will include the line ... Creating WxRadar binary file as: ... the first time it makes the file. Maybe -- did it work for you before 3.2? However, this facility is all to do with ASN making use of specific facilities in SimConnect. Have you contacted the ASN folks about it? Are there any P3Dv3 users with it working? You can get me some extra information about the interface between FSUIPC and ASN by adding these lines to the [General] section of the FSUIPC4.INI file: Debug=Please LogExtras=5 Pete

You asked for this in another thread, a while ago, and I see I said: It is on my list, by other events (like my daughter being trampled by cows) have set me back a bit. I will try to get to it next week. Pete

The installation is fine, it installed correctly. The only thing I see which is odd in the DLL.XML is the '-' character in front of these lines: -<SimBase.Document version="1,0" Type="Launch"> -<Launch.Addon> -<Launch.Addon> Are those characters really there, or are they an artefact of the way you've pasted the file? There must NOT be there! Is VRS_TacPack supposed to provide a menu entry too? does it? Try renaming the DLL.XML file and re-running the FSUIPC Installer so it makes a fresh one just with FSUIPC4 loading. If that doesn't work then I need to see a SimConnect log file -- see the "FSX HELP: logging Simconnect" thread in the FAQ subforum for details. Pete

I need to see the FSUIPC4.LOG file too, please, and a list of your other add-ins (DLL's in the DLL.XML file). Also perhaps you can tell me about any Luaa plug-ins you might have had running at the time., as it looks like something is still trying to use parts of FSUIPC during close down. Pete

iMy EPIC driver for FSX/ESP was released only in Beta form 13 (THIRTEEN) years ago and never fully tested due to lack of harware on my part and lack of users. There is no way I can actually support it, but if it works with current versions of FSUIPC on P3D 1.x (also now unsupported) it should certainly work with P3D 3. So I can only think it's something to do with your configuration. The FSUIPC.ini file has nothing to do with any additional modules. It just stores your settings, those made from the FSUIPC menu. None are related to anything outside FSUIPC and WideFS. Sorry. Pete

Is this with the current version, 4.949p? If so please let me see an FSUIPC4.log after P3D has closed. Pete

It needs the count and size, of course. It cannot guess! So it should be: ipc.writeStruct(0x66c0,"9UW",Amps,EGT,FuelFlow,OilTemp,OilPressure,EngRpm,FuelPressure,BattVolts,CylHeadTemp) Incidentally, using "UW" you are assuming all of the values will be positive (U = Unsigned). That won't always be true for some -- temperatures and voltages, for instance. If you treat a negative value as unsigned it will appear as a very large positive number! You need really to use SW for the type. But be sure the values don't go outside the range -32768 to +32767. The range of UW is 0-65535. Pete Pete

Really? How can you tell? What is the symptom? I've never heard of such a thing. Can you explain? Generally, by default, installers get administrator status in any case, so I don't understand what it is you think is wrong. Since registration is only ever performed in the Installer, to register you have to run the Installer. It doesn't matter how many times you run the installer! In any case, "uninstalling" FSUIPC is just as it says in the documentation, deleting it. Since it only installs in the FS Modules folder that's dead easy. But there's no point in doing this unless you genuinely don't want it any more. Pete

It isn't anything to do with how many writes you are doing, it is simply that all your values are overlapping. "writeUW" means "write an Unsigned Word". A word is 16 bits in size, or 2 bytes. You are writing 2 bytes at 1 byte spacing -- 66C0, 66C1 ...66C8. So every subsequent write is overwriting the 2nd byte (the high 8 bits) of each previous value! BTW your code would be much more efficient if you used ipc.writeStruct. You could write all the values to offsets in one call the. Pete

The focus information is only logged, for information only, because of the logging options you have set. It is a facility I added to help discover why sometimes FS seems to spontaneously minimise to the task bar. Perhaps you need to determine what that program "dwm.exe" is and whether it is the cause of your crashes. I just googled it and found this: http://www.processlibrary.com/en/directory/files/dwm/71288/. So it appears to be to do with the desktop, so maybe it too is a symptom of the crash -- the desktop gaining focus as a consequence. I don't know. You still need to go through a process of elimination of everything you've added which isn't a default part of P3D. Have you tried asking in the P3D forum on AVSIM, or in the L-M forums? Why are you so determined to relate it to FSUIPC? Pete

In disabling ASN did you also stop its DLL loading? (The "as_connect" entry in the DLL.XML file). Tht would be the only component which could crash the sim. Not that I think it's related to aSN, unless your version is out of date. I run the latest version, and with lots of AI supplied both MyTraffic6 and UT2, and have never seen the sorts of errors you are reporting. Mind you, I'm not (yet) a big P3D user -- still mostly prefer FSX-SE as it allows me far higher levels of AI Traffic, with good performance, than I can achieve with P3D. It think there are still some bugs, or maybe incompatibilities, in P3D version 3, at least judging by the number of hangs and crashes still being reported on the L-M forums. I've released a further update to FSUIPC -- 4.949p. No significant changes apart from the use of the P3D SimConnect interface instead of needing to use FSX ones, but the difference in the codebase may just move things enough to give different symproms as far a FSUIPC is concerned. Pete

Well, yes, probably, though I'm not sure io.write has the same buffering facilities built into it as the FSUIPC offerings. FSUIPC uses separate read and write threads running in the background. Pete

If you have a well-programmed B777 model installed it should feel right in any case. But have you calibrated the yoke axes at all? Follow the numbered steps to good calibration in the Calibration chapter of the FSUIPC User Guide. If you want to change the feel you can then make it more like a fighter or stunt plane be increasing the central slope in the Slopes option in Calibration, or, as in this case, if you want it less responsive in the central area, choose one of the slopes with the flattened central area. But either way you are really telling the add-on aircraft designer he's got it wrong. Pete

Okay. Let's see: First please remove the - characters before some of the lines. Don't know why they are there. Here is a better version: <?xml version="1.0" encoding="WINDOWS-1252"?> <SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>VRS_TacPack</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path> </Launch.Addon> </SimBase.Document> Second, this is evidently NOT the one you posted earlier -- it only has FSUIPC4 and VRS TacPack in it. Have you tried with this one? Is "VRS_TacPack" really a folder inside the Modules folder? If not and you aren't using it you should delete: <Launch.Addon> <Name>VRS_TacPack</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path> </Launch.Addon> So where is it? It's no use making a log for me to look at then not showing it to me! I don't understand. What did you expect to change? Pete

com.write simply sends whatever you want, whether one character or many bytes, whether binary data or character strings, out of the serial port or USB port you have opened. That is all. Nothing clever. It just tries to shove whatever you want shoved out of the port, in the format you provide it. For changing values, send the changing values (of course?). Just be aware that there will be a limit on the speed of the transmission, depending on the device, the settings and so on. Best just to send values at intervals. If you want to see smooth changes on a gauge or something then 10-30 changes a second would be in order. For lesser needs maybe once per second might be enough. I can't tell you how to program your device. Just be aware that there's nothing clever or mystical about com.write (or com.read for that matter). It just does exactly what you ask. It does exactly what it says in the La reference you have in front of you. What else would you expect? Pete

The hook errors are some weird result of something going wrong elsewhere, they are symptoms not causes. Some software elsewhere in P3D is going wrong. The hooks are only placed once, during FSUIPC initialisation, and the code is never used again -- the initial placement, which is for wind smoothing, should ever the option be enabled) works okay as logged here: 483 --- Wind smoothing fix is installed You'll need to engage in a process of elimination to see what is causing the crash or hang. For instance, if you see AI Player as a part of it then try without AI traffic and see if that helps. Pete

Sorry, typo. And the correct version of FSX.EXE was most certainly there as well, otherwise neither the installer or FSUIPC would have been able to get it. FSX even confirmed it was the Acceleration version when FSUIPC connected to it, here: 28174 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) Anyway, the new install log you just posted shows the correct install for FSX-SE. So he fact that there is no run-time log means FSUIPC isn't getting loaded, which points to an error in the DLL.XML file. But again you posted a completely unformatted version of the DLL.XML file which is pretty nigh impossible to check without first spending ages formatting it properly. Why is this? Here's mine, just copied and pasted from Notepad: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Repaint Wizard</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>D:\Repaint Wizard\RepaintWizardFSX.dll</Path> </Launch.Addon> <Launch.Addon> <Name>AFXModule</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>D:\AFX\AFXModuleFSX.dll</Path> </Launch.Addon> <Launch.Addon> <Name>AirnavBridge</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>E:\FSX\AirnavBridgeFSX\AirnavbridgeFSX.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Flight Recorder</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path> </Launch.Addon> <Launch.Addon> <Name>RAASPRO</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <DLLStartName>module_init</DLLStartName> <DLLStopName>module_deinit</DLLStopName> <Path>.\RAASPRO\RAASPRO.dll</Path> </Launch.Addon> <Launch.Addon> <Name>as_connect</Name> <Disabled>True</Disabled> <Path>as_srv\as_btstrp.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> If you want me to help fix it, please try and paste it correctly formatted -- use Notepad as I suggested earlier, it works fine! But note that it looks like there are references in there to FSX and its SDK utilities, which progrably won't be there for FSX. And is "VRS_TacPack" really installed in the Modules folder? Anyway, if you rename your DLL.XML, or save it somewhere else, so there isn't one there, THEN re-run the FSUIPC4 installer, it will make a good one with only FSUIPC loading. Do that as a check. If that works then the problem was that your DLL.XML was corrupted before you installed FSUIPC. If it still doesn't load the I need a SimConnect log -- please see the FAQ thread about this for instructions. And also look through the [Trusted] section in your FSX.cfg file and delete any lines mentioning FSUIPC4. Pete