Pete Dowson

Can you explain a little more clearer please? Is there a question here? What are you quoting from? Why is your Thread Title talking about "key not valid"? What key? If the FSUIPC installation (which cannot be for 4.97.4 because we are only up to version 4.947 at present) is giving you an error message, why not say so? If it is I need to see the Install FSUIPC log file which you will find NEXT to wherever you put the Installer. It is a text file. You can paste its contents into a reply here. Pete

Well you can try. But you risk things going wrong in strange ways, axes conflicting because of FS/P3D auto-assignment. Maybe P3Dv3 no longer does this I don't know. Try. But I cannot support you with any problems this may cause. P3Dv3 seems to have lots of Joystick problems itself in any case at present, judging by the reports on their forum. Hmm. I don't know what could cause that. Does it do the same with P3Dv3 assignment? All FSUIPC does is send the hat value as the parameter for the PAN VIEW control, exactly as FS/P3D assignment. Ah, you need to enable mouse look in FSUIPC. Oh dear. What a strange reaction! :-( I only thought it was an odd question because very few others ask this and without you explaining your particular problems there was no way for me to understand. There's surely nothing insulting or impatient in me thinking a question ass odd? Your reaction is way over the top and quite unwarranted. There is no point me just answering just yes or no. You would have to then be so precise in your questions and not be interested in any ramifications or consequences. If you read through this forum you will see I always try to be as helpful as possible. Look at the thread so far. How would it have been if I'd answered just Yes or No to all of your questions? I suspect will be very VERY reluctant to answer anything else from you. And especially not such a quick response -- you won't find such support in many other places! Yes of course. What's to stop you? Just don't come here for support. :-( Pete

Did you assign it in Axis Assignments to PAN VIEW? If so, that is the same as assigning it in FS. The only difference might be the scanning rate, You could try reducing the polling interval, but be careful -- the default has been chosen as the best compromise. (See the "PollInterval" parameter in the Advanced Users guide). FSUIPC offers assorted mouse functions. Please see the documentation. Mouse zoom isn't affected by FSUIPC assignment in any case. You use the mouse look option on the mouse, not pan view. Er ... why do you want to assign in FSUIPC in the first place? Why ask such an odd question? If you mix assignment places you have to accept that sometimes it will all go weird because FS and P3D make auto-assignments. If you don't need or want FSUIPC's joystick facilities, just do everything in P3D. I am now rather confused about what it is you are after? :-(

Yes, some of the names aren't so easy -- this is why I provide a full list in the FSUIPC Documents folder so you can search by keywords. FSUIPC doesn't assign the names, the ones in its drop-down lists are those which FS actually uses -- the same ones recorded in the FS files saving any FS assignments. It gets the list automatically from FS's "CONTROLS.DLL" so that it will encompass any changes as FS developed. Pete

You are not reading the messages properly. There's no "Profile" subfolder unless you created one. The folder I told you to copy is the Modules folder. I did say that IF (and only IF) you were using the Files facilities for Profiles, there's be a Profiles subfolder (in the Modules subfolder, which is what we were talking about), but if you copy the Modules folder you'd copy that too in any case! Pete

Right. You'll see that, on the P3Dv3 Client support forum, the are many problems indeed with the P3Dv3 handling of Joysticks. Yours will join the many! Pete

So what was all that earlier on about COUATL? Now i've no idea what your current remaining problem is. Sorry. Perhaps you should re-explain without the confusion? There's no point in showing me files for a system with no problem. There's nothing to fix! After all, you said: This is a common problem with SimConnect. It should then run if you allow it to. The problem is a long-standing one in SimConnect. It was much worse in the original FSX release, and they tried to fix it in SP1 and again in SP2/Acceleration, but not entirely. It's a timing problem in the "trust" system they implemented (nicely removed in P3D). I assume you ARE using a fully updated version og FSX? Pete

Where's COUATL and BGLMANX? I thought both were installed and loaded when you run Addon Manager? Pete

Yes.

What is "AUTO TO GA" in FSUIPC? FSUIPC doesn't provide such a function. There's a special function for Project Magenta, which only changes Project Magenta offsets. Maybe you mean the FS control "Auto throttle TO GA"? That's assignable in P3D as well -- it is called "Autothrottle engage (TOGA), and by default is assigned to Ctrl+Shift+G. Assigning it it FSUIPC does no more than assigning it in P3D it is exactly the same. You need to report this to Lockheed-Martin, then. But don't say it is FSUIPC. Try it with P3D assignment to see. And with a default aircraft, as it may be a PMDG problem. Pete

No idea at all. PMDG do not use FSUIPC. What are you assigning to? That may be the clue. I didn't think that action for PMDG aircraft was exposed in FS at all, so not assignable -- except possibly by using the PMDG 777 custom controls.. Pete Pete

It is not an FSUIPC problem because it happens before FSUIPC is even loaded. In fact it is a SimConnect problem, a very long-standing one. I too have had problems specifically with COUATL, and only managed to get around them by juggling with the different entries in the EXE.XML and DLL.XML files, which control the loading order by SimConnect. If you wish me to suggest changes (my system is now okay) I'd need to see your EXE.XML and DLL.XML files. Pete

FSCrew is not FS. It will see whatever you assign wherever you assign it, won't it? Otherwise this question is best directed to FS2Crew support. I'm afraid I don't know it. Pete

Everything related to FSUIPC is stored in the FS Modules subfolder, no where else. You can simply copy everything over, or only the configuration settings (FSUIPC4.INI, and any macro or Lua files. Also the Profiles subfolder if you are using Profile files. Note the pinned thread at the top of the forum:- currently P3Dv3 does not allow calibration in FSUIPC unless you assign in FSUIPC. Pete

Didn't HiFi point you to anything like a log or error file to check? I'll try to remember to drop my contact there an email about it, but it'll be Monday now. Pete

I've just managed to run my system now. As soon as FSX is "ready to fly" and ASN is running, offset 8600 changes from 0 to 1, and the Bitmap file is created in the place I asked for it to be. This is not at all related to what you use the file for, so it is nothing to do with the Lua program or the Macro file. For some reason your ASN module is simply not signalling that it is active. I really don't know how to diagnose that -- the bit in 8600 is set when the A_BTSTRP.DLL's "IsActive" exported value goes to "true". I think we still need HiFi to sort this out, or at least tell us where to look. First though, let's compare notes. On the ASN Welcome Screen, at the bottom, the version number mine says is: 1.0.5707.28711 Yours? My as_btstrp.dll is version 1.0.0.34, same as yours. Is your ASN set for FSX, or FSX-SE? Check that this mode is selected correctly, else it almost definitely won't work. Also, I just noticed that there was a Beta update for ASN released on 30th September. Is that the one you are using? It does mention something about a WX radar change. Pete

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