Pete Dowson

There is already a thread on this. Please use the same solution -- i.e. install SimConnect: You'll find all the versions of Simconnect in the P3D "redist" folders. Try the Simconnect.msi from redist\Interface\FSX-SP2-XPACK, for example. BTW I think you'll find you'll be needing at least the FSX-SP1 and FSX-SP2 SimConnects installed if you ever intend to use many FSX Addons with P3Dv3. Meanwhile, could you please right-click on the SimConnectP3D2.DLL file and see if it says it is locked in its Properties? I still don't understand why Windows says it isn't there when FSUIPC tries to load it. Pete

PMDG aircraft do not use FSUIPC, so I don't think that's relevant. I've no idea what "Aero.bat" is -- can you explain that? This error: 2869279 ***ERROR C0000005 at 070349D0 MonitorValues (Base 5, Offset 0000, Addr 67C72E74) 2869279 *** Access violation trying to read address 097BFFF8 2869279 *** EAX 097DE508 EBX 097DE4F8 ECX 097C0000 EDX 00000008 EDI 010146A8 ESI 097DE500 is FSUIPC trapping a crash which would otherwise have occurred. These can only be caused by an Add-On using FSUIPC in some odd way, so I need to know what add-ons you are using. The information in the log is not at all useful because you are using such an old version of FSUIPC, dating to February 2014. Please update to the current version, 4.947, and try again. Pete

So, is there a new question? Pete

Hmm. Something's certainly wrong somewhere. This is working here. Well, last time I used it (two weeks ago before I went on holiday), and others are reporting it as okay -- on the ProSim forum, for example, where it is used for the WX Radar on the ND displays. I'll look to see whether there's any way to get more information, but for now it is sounding like an ASN installation problem. Did you check for any ASN error log? Pete

Sorry, I cannot re-write so much of FSUIPC now. It is a huge amount of work and would require a lot of design effort even before beginning, because of the way structures and so on have been formed. I am simply not willing to jeopardise the stability of the program, and especially not in areas of code which are now very very old. You can do whatever you like with your devices using Lua plug ins. The Hid functions in the COM library can handle any sort of HID device, no matter how many of whatever they might have. The whole reason for adding the Lua plug-in facilities was precisely to allow capabilities to be increased without continually having to modify core code. Pete

Ah, you are using the demo application I provided? I tohught you were trying to enable it for ProSim or another application! It certainly sounds like ASN is not correctly signalling that it is active. I can check here, I'm afraid this will have to wait till I can get my system back up. And none of this has changed. Last time I used my sim with ProSim it was working fine. Whereabouts in the FSUIPC4.INI did you put the path line? Pete

The Windows Event Viewer (enter event viewer into the Start/Search edit area) has logs for system and application problems. Check the latter. I don't think any of the Weather facilities should be used with P3Dv3 -- I can check, but generally everyone these days uses a decent weather program, so none of those have been thortoughly tested. Maybe P3D doesn't support the changes those entail -- I'd need to check. Maybe you should delete your FSUIPC4.INI file, please and start with default settings? I hadn't realised you'd changed things. Show me a copy of an FSUIPC4.INI file which regularly crashes, please. Well it is certainly in P3D. I am suspecting that there are bugs in the weather setting facilities in P3Dv3. I'd need to do more testing in that area and report to Lockheed-Martin. I don't think, in these days of ASN and the like, that anyone uses the older FS2000-compatible FSUIPC weather filters, but I'll check them -- not at present though. Too busy. Pete

Well, I'll check that next time I have my system up and running. At present I'm working on some stuff in the overhead. ASN just provides a matrix of data to FSUIPC when it asks for it, about every 2-3 seconds. FSUIPC does nothing unless you add the one or two parameters to the INI file to tell it which filetype you want and where to put it. It generates either a bitmap, or a file with the raw data, or both, and places the file in the path specified. Isn't the documentation clear enough? What are you using this bitmap or whatever with? Pete

Okay. There's no Windows crash information here at all. The crash information gives the following sorts of data. I've no idea what you picked up instead: Faulting application name: uedit32.exe, version: 22.10.0.12, time stamp: 0x5589b3ca Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x10a9fd24 Faulting process id: 0xe18 Faulting application start time: 0x01d10120300477fa Faulting application path: C:\ULTRAEDT\uedit32.exe Faulting module path: unknown Report Id: b7f7805e-6d4f-11e5-a1ed-74d435ed54d3 With the correct Windows crash data the offending module can usually be identified, and even the location within. There's little can be done without this data. The FSUIPC log shows everything is fine ... it set everything up correctly and there's really nothing to go wrong after that. Running for 110 seconds and crashing when you load an aircraft suggests something else is going on. Unless the Windows crash data actually points to FSUIPC4.DLL then I am afraid your recourse must be to Lockheed-Martin support. But first i suggest you try a reinstall of P3D, as it sounds very much to me like a corrupt installation. Before trying again to get a proper Windows crash report, please install 4.947, just released. In case the crash report does point to FSUIPC4 I would need to match the data to my current version. Thanks. Pete

Do neither of you want to check the DLL properties for me, as requested, or try 4.946b for me? Too late for 4.946b -- I just replaced it with 4.947, with improved joystick scanning support. But I'd still like to see a log with that, pretty please? Pete

I can probably help the developer if he needs something looking at my end. but I don't have or use the product and can't really solve his problems for him. He has my email anyway. Pete

Please always use the Support Forum for support questions: the Announcements subforum is for ... announcements! What do you want to "install in FSUIPC"? If you mean install FSUIPC into P3Dv3, just run the Installer for the latest version (4.946b at present). There are even instructions provided in the ZIP file. Pete

In P3D settings dialogue for controls, of course. Where else? Pete

There's no difference in the FSUIPC interface when using P3D. I've no idea what the "connect to FDC" option would be for. Surely it's the other way round -- FSUIPC applications connect themselves to FSUIPC. FSUIPC never connects the other way around and never provides "connect" menu entries. I think you really need the FDC folks to diagnose the problem for you. P3D has been available for a long time now. I'm sure there are many happy FDC users with it. Have you asked around, in the FDC and P3D forums? Pete

The only other reports of crashes on loading have all turned out to be bad installations of P3D, especially ones which have been altered by migration tools. But I cannot guess anything. I need to see the FSUIPC4.LOG after such a crash, and the Windows crash data. It may even be a bad joystick driver. You don't need to "run a log". FSUIPC always automatically makes a Log when it runs. And don't try sending anything. You'll need to paste the text into a message. Pete

I don't have P3D documentation to hand, but the option is obvious when you go to the P3D settings where you would go to assign things and set responses and so on. Maybe P3D has a Help menu? Pete

No ideas at all because there's no information here. Is a Log produced? If so I need to see it. At what exact stage does it crash -- i.e. what is on the screen? What is the actual version number of FSUIPC (I always need this)? And please show me the Windows crash details from the Windows event viewer. Also it might help to have a list of other add-ons you are running at the same time. It may be some clash. Have you tried stopping everything else BUT FSUIPC, just to be sure? Pete

The problem has been that too often the Sim automatically re-assigns axes if it thinks they are newly connected. It does this according to pre-defined axis functions for known joystick types, which are defined in assorted fiiles. There was a way to stop it doing this, effectively by deleting the relevant entries in those files, but this is inherently unreliable and difficult, especially if the software is ever updated. I honestly don't know if P3D is still doing this sort of thing, but certainly FSX and FSX-SE do. I suspect P3D v1 and v2 do too -- v3 might have changed. They seem to have changed a lot in this area. Pete

Not if the problem you have is the one now answered. Pete

Yes, certainly you cannot have two programs both trying ot use the same axes! As clearly stated, you need to disable controllers altogether (one checkbox) in the Sim if you are assigning anything in FSUIPC! Manuals for what? FSUIPC documentation is in the FSUIPC Documents folder, in the Sim's Modules folder, as clearly stated, with a list, in the Installation guide. Pete

There is NO page 3 of 11 on the Assignments Tab. You are taslking about Calibration, NOT assignment! Yes, one quadrant THREE levers. So you can assign up to THREE throttles. I was only asking why you were only using ONE. I never asked or suggested multiple QUADRANTS!!! Oh dear. You are talking about CALIBRATION, NOT assignment! I was asking if it responded IN FSUIPC, before you selected that option. you never answered. Please see again the IMPORTANT pinned topic in this Forum. At present you CANNOT calibrate in FSUIPC unless you ASSIGN n FSUIPC, which you have not done. Please read things much more carefully! You misunderstood every question. Pete

As the image shows, you are logging the value as a UW, Unsigned word! The values over 32767 will actually be negative. It's all in the interpretation -- you are just displaying them wrongly! Pete

Having received no clear answers to my questions, I've made some assumptions about what you folks actually mean in your vague reports. I've found that L-M have made a substantial change to the way they handle joysticks in P3Dv3, and this currently prevents actual calibration of axes in FSUIPC if they are assigned in P3D. This does not affect calibrations already made in a previous version and copied over, nor does it affect assignments made in FSUIPC. I have asked L-M abnout this, but it may turn out to be a permanent change. Please see the Pinned "IMPORTANT" topic at the top of this Forum. I'll post further details there, as and when ... Pete

Having received no clear answers to my questions, I've made some assumptions about what you folks actually mean in your vague reports. I've found that L-M have made a substantial change to the way they handle joysticks in P3Dv3, and this currently prevents actual calibration of axes in FSUIPC if they are assigned in P3D. This does not affect calibrations already made in a previous version and copied over, nor does it affect assignments made in FSUIPC. I have asked L-M abnout this, but it may turn out to be a permanent change. Please see the Pinned "IMPORTANT" topic at the top of this Forum. I'll post further details there, as and when ... Pete

Okay, but i cannot make it happen here on any of my systems. Yes, of course I have FSX SimConnect's installed, and it isn't a worry when that is the case. But I need to get the reason for my DLL sorted out. This could be extremely important in the future if I want to take advantage of any new SimConnect facilities offered by P3D -- there are some already which would improve some of the things FSUIPC does. Can you right-clcik on the SimConnectP3D2.DLL, go to properties and see if there's anything there which suggests the DLL is suspect or protected. My only guess is that it's to do with Windows "AppLocker" actions. If it is locked, before Unlocking it (which I am sure you can do in Properties), please download FSUIPC 4.946b and run with that -- I need to see the Log to check whether the alternative call I am using will override the lock. If that makes no difference, try unlocking it in its properties. Please let me know. Pete