Pete Dowson

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

Where on Earth did you read that "I must to write in FSUIPC.INI the string : ASNwxRadarPath = C : \ Prosim737 "? That's nonsense. It's only part of what you must write!! You don't need "experience in the simulation"! You only need to read what is written properly! I assume you don't even know what a file name is? Prosim needs a FILE. You only told FSUIPC a path -- there needs to be a FILENAME in the parameter which tells it the name of the file you want. It is a Prosim matter, not FSUIPC. All FSUIPC needs to know is the path and filename. You are in the wrong place. FSUIPC is not written specifically for Prosim, it produces radar files for any application, and it is up to the application what it should be named and where it should go! Look properly in Prosim support. There's a long thread you need to read to the end: http://prosim-ar.com/forum/viewtopic.php?f=13&t=8971 Pete

The log is in the Modules folder as is everything else to do with FSUIPC. With a Toggle switch you should still not use hold or repeat! Program both press and release to use the same control, that's all. Pete

Buttons, as opposed to switches, are on when pushed and off when released. If you assign a button to a Toggle control you need to only program the 'press', NOT both press and release! And you obviously don't want it held or repeated! If it still turns back off then you probably have conflicting actions -- for instance, through not disabling controllers in FS. You can use FSUIPC's event logging to see what is going on. Pete

Switches and buttons can be programmed to use macros if you wish, of course. Pete

You'd need to program a Lua plug-in for any outputs, but FSUIPC should see any inputs -- i.e buttons and switches. Pete

This is more a question for the PMDG support forums than here. I would guess that the parameters for most of the PMDG added controls (events) are just Mouse Flag settings -- usually just one bit in the 32 bit value, better expressed in FSUIPC in hex, as in x20000000 for bit 29. If you know how to do it with the mouse, then it's only a question of setting the correct mouse flag to do the same. I am away from my PC until late Monday so I cannot really help with that more directly, but it might be worth looking through some of the entries in the User Contributions subforum, above Pete

You haven't referred to the Prosim instructions about this, or read the threads about this in the Prosim support forums? You not only need the path, it must include the filename too, whatever Prosim needs. It isn't dictated by FSUIPC. BTW I moved your post to the Support Forum. You mis-posted to the FAQ subforum instead! Pete

Hmmm. Are sure it isn't some other add-on opening the console? Or maybe you have a Simconnect.ini file enabling it? There's only one console per Process, and if it's opened everything uses it including FSUIPC's log. It is definitely unlikely to be FSUIPC unless that option is not truly being turned off. Check the console parameter in the FSUIPC.INI file, change it there if necessary. Pete

No, it cannot be done without the client application being changed to also use the different class name, because the one it uses normally is the same as FSX's. Why not run the MCP program on the main VS PC? Pete