Pete Dowson

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

Use FSUIPC 4.946, the first version for P3D v3. Pete

i tried to, but every beta release, every update, changes things FSUIPC depends upon! Mostly 4.945a would have worked, but some crucial things changed. It was lucky I was working with the Betas because I only just got back and had a few hours work to do to release 4.946, now available! Pete

Where did you get P3Dv4 from? V3 only jsut got released! You should have had a warning telling you that FSUIPC was the wrong version and didn't know the version of P3D you were using. If you had then just acknowledged it, it would have carried on and let you Register. However, it won't work properly in version 3 or 4! The version of FSUIPC for P3Dv3 is 4.946, released today! Pete

Why have you just installed such an old version of P3D? The updates all the way to version 2.5 are free. Try getting up to date. Pete

Registration is part of the Installer, not in FSUIPC itself! 4.944 was nowhere near compatible with P3Dv3 -- it was out of date weeks ago. 4.945a was the most recent, but the only version at present which works correctly with P3D v3 is 4.946! Pete

Yes. They are all in the FSUIPC4.INI file (and Profiles subfolder if you are using Profile files), so just copy those into the new Modules folder. Pete

Depends entirely on the aircraft. some support Mouse Macros, some have keyboard shortcuts you can assign to, some have local panel variables you can write to (L:Vars). And unfortunately some have no option other than to use the mouse. First off, search the User Contributions subforum here for your aircraft. Maybe someone's already solved it. Pete