Pete Dowson

It's a crash in Direct Input. Maybe your joystick drivers? Did you disable controllers in P3D? Does it work okay assigning in P3D itself instead of FSUIPC? Since it is specific to P3D and DirectInput I think you may need to report this to Lockheed-Martin. Pete

Hmm. Very strange -- it is actually using the FSX SP2 Simconnect! Can you please check that this file is actually present: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll On my system, despite the fact that I do have the FSX SimConnects present, it definitely still only uses my own module, thus: 20452 Trying E:\Prepar3D v3\Modules\SimConnectP3D2.dll 20499 Found it: trying to connect 20546 FS UNC path = "E:\Prepar3D v3\" I am trying to build a P3Dv3-specific version of my DLL, but I'm having difficulties with that -- my compiler doesn't like the latest data from L-M. However, comparing your results and mine, I don't think it would make any difference. Something else is going on. Maybe it's something to do with having P3D installed in the Windows protected Program Files folders ... but it shouldn't matter. The Modules folder isn't protected el;se you'd not get the Logs you show me! Pete

Sorry, it isn't related to FSUIPC -- you've proven that yourself (assuming you mean DLL.XML not DLL.EXE). BTW it is always quicker and easier to test without FSUIPC by renaming the FSUIPC4.DLL itself in the Sim's Modules folder). Pete

Theoretically, for FSUIPC, that shouldn't be necessary. I may try and build a P3D3 version of my SimConnectP3D DLL. But first, would you mind showing me the FSUIPC4.LOG from your successful start, please? In the long run you are better off installing the FSX Simconnects in any case, as many add-ons will need them. Pete

Aha, interesting indeed! I think you need to report that as a bug to Lockheed Martin! Thanks for getting back with the answer! Pete

Aha! So there was no "pulldown" to pulldown, not that FSUIPC was missing in the "pulldown"! ;-) That's correct. It's always been installed by the FSUIPC4 Installer for P3Dv2 or later because the P3D installer doesn't install the WinSxS SimConnect DLLs. Not relevant to FSUIPC. FSUIPC doesn't use Networking or the Internet. Simconnect.xml isn't relevant to FSUIPC unless you have it set incorrectly to prevent local use of SimConnect. As a test try removing that file altogether -- it is not needed unless you are using SimConnect applications across the Network. SimConnect.INI s irrelevant to FSUIPC. That's just to control SimConnect logging. WideServer.DLL and WideServer.INI have not been used since FS2004 days. What on Earth are you doing with those? However, none of that should affect FSUIPC connecting to SimConnect. Here it was not necessary to make a P3D3 version of my SimConnectP3D2.DLL modules, but maybe that's because I also have all the FSX WinSxS Simconnects installed too, like most other users who have any addons.. If it still fails when you remove the SimConnect.XML file, see if installing SimConnect helps. 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. Pete

Okay. Thanks from confirming. I could see for sure it was not FSUIPC OOM detection, not FSUIPC's "beep" but a Windows "ding"! Pete

If you didn't turn the autosave on (it's off by default), it couldn't be that, and certainly not every 3 seconds -- maybe every 60. And since your stuttering continued when you removed FSUIPC, it obviously cannot be involved now, can it? BTW, where did you get version 4.95 from? I've not released such a version yet! The ONLY version currently suitable for use with P3D version 3 is 4.946. Pete

Yes, several recent versions of FSUIPC have been needed to support pre-release Beta versions of P3D v3, but it needed changes for every single one of the 4-6 Beta releases (I lost count)! The only versions of FSUIPC which will work correctly with the Released P3D v3 are 4.946 (or later, as and when). Pete

This is usually a problem in the DLL.XML, but that looks okay, so check if there's an FSUIPC4.INI and LOG file produced in the Modules folder. If so it is running -- I'd need to see the LOG. Either way, what else is appearing in the "pulldown"? (I assume by then you mean the AddOns menu?). Since there's nothing else in the DLL.XML, perhaps you ought to check the EXE.XML too? If there are no addons there is no addons "pulldown". Pete

Nevertheless the value in 024C IS the value being checked when FSUIPC issues its warnings. And the check IS less than 250Mb (256000). You don't "turn on the log". There is ALWAYS a log. You have opted to monitor 024C on the title bar, near where you did that there is an option to monitor in the "normal log". You can't miss it if you've already managed to set it in the title bar! You can also log messages like Memory in use: nnnnMb, Avail=nnnnMb by adding Debug=Please LogExtras=x1000 to the [General] section of the INI file before running the sim. Also note that the check is only performed at most every 10 seconds, but it might be made much less frequent (up to 3600 seconds, or one hour) using the parameter OOMcheckInterval=10 (in seconds). Pete

The DLL is okay, and the same as mine. And I was wrong in my analysis above -- I was looking at the original code which was from when the order in which as_btstrp.DLL and FSUIPC4.DLL were loaded was important. That was fixed by later changes to ASN, but I kept the code in for folks who hadn't bothered to update ASN. The only reason I can see for offset 8600 remaining zero is that ASN isn't signalling that it is active. This is a flag which is accessed through a pointer which is provided when FSUIPC calls the as_btstrp.DLL exported function isActive. I'm afraid I've no idea why that isn't getting set. Are there no errors reported by ASN? I'm not sure where you'd check, but I think it may (possibly optionally) produce a log. Best to now ask over in the ASN support forum. Let me know what response you get there, please, and feel free to quote my diagnosis from here. If you don't get an answer there within a reasonable time, let me know and I'll email my contact there. Pete

The FSUIPC beeped warnings are based on a comparison of the value in offset 024C with 256000, which means 250 Mb left only, so the beeps at the point shown in your picture cannot be from FSUIPC -- or maybe the display on the title bar has frozen for some reason? Best to log to "normal log" so the progress of the value can be clearly seen, and even timestamped! Pete

Sorry, it isn't FSUIPC. You need to look elsewhere. Pete

Use the Event Logging in FSUIPC and activate the control Check the log to ensure the control is indeed being sent. If it is, then FSUIPC is doing its job. Then use the regular Spoiler Toggle keyboard assignment in P3D itself and see if that works. If not, you need to report the problem to Lockheed-Martin on their support forum. Otherwise let me know. Pete

How are you assigning the throttle? If you have the throttle quadrant then surely you have more than one? Is the throttle assigned in FS or FSUIPC and what to? Before you select "Map to 4 throttles" did you check that it responded there? No point mapping something that isn't being sen or isn't even assigned! Pete

This is because your P3D v3 is corrupt. It looks like Version 2 to FSUIPC -- see the line: Try uninstalling and reinstalling the Client (no need to reinstall everything). Pete

Well this line: means that if knows ASN is running and has a link to its "active" function, but it should be followed by: Ready for ASN WX radar The only way I can see that not appearing is if some of the functions needs are missing in the "as_btstrp.dll" module installed by ASN. It needs these functions or locations exposed as exports: AmbientIcing WshLat WshLon WshRange WshMinAlt WshMaxAlt SetRdrParams If any one is not, then that second message won't appear. I can't access my system with ASN till tomorrow, else I'd tell you the exact version number of my copy of that DLL, but if you'd like to ZIP yours up and send it to me as an Email attachment (you might be better renaming it from a DLL to a TXT file first, otherwise it could get stopped), to petedowson@btconnect.com. I can check it here -- but it may be tomorrow. Pete Pete

Hmm. I suspect the uploaded copy got messed up somewhere. I've uploaded it again, and downloaded it and tested it, and it seems okay now. just try re-downloading please, from the Download Links subforum above. Pete

Hmm. I'll need to see the Install log please. Pete

Did you try Lus trace/logging to see why it didn't work -- just a checkbox in the FSUIPC logging tab? Did you monitor the offset 04FE to see if was indeed changing? Did you even simply check the FSUIPC log to see if an error was reported? Since the value is provided alwady, as a parameter, slightly simpler would be: -- Seatbelt announcement function seatbelt(offset,seatbelt) if logic.And(seatbelt, 128) == 0 then sound.play("E:\\Prepar3D\\sound\\CA_seatbelts off.wav") end end event.offset(0x04FE,"UW","seatbelt") Pete

You need to use FSUIPC 4.946 (or later) with P3D version 3. The Toggle Aircraft Exit control (plus a heap of other controls) were moved into a different table inside the P3D CONTROLS.DLL module! Pete

You need to show me the FSUIPC4.LOG please, from the Modules folder. You can paste its contents here. Pete

For P3D version 3 you need FSUIPC 4.946 or later! Pete

If you are not using FSUIPC for incrementing / decrementing flaps, I'm not sure why you would post this question here? Maybe you need to provide more details, saying exactly what you are assigning to and where? Programming button press and release to the same action might do it, for certain. Pete