Pete Dowson

That is always advised in any FS or P3D IF you are assigning axes in FSUIPC, simply because of the possibility of conflicts otherwise. The only additional thing in P3Dv3 at present is that you'd have to assign in FSUIPC if you want to calibrate in FSUIPC. This is wrong, and will hopefully be fixed. I have asked L-M but have had no response yet. I've no idea what FS Force is doing to make this necessary. However, there's a misunderstanding here. The ONLY reason for disabling controllers in FS or P3D is to avoid a potential (and I mean potential) conflict should at any time in the future FS or P23D automatically re-assigned axes. To reproduce an explanation I've already written in another thread near here: If you can live with the fact that such things may well occasionally happen, and then solve them there and then (by unassigning all the axes or buttons which have been automatically re-assigned), then you can do whatever you like, mixing this that and the other. The problems in the past have simply been the amount of problems folks get into with these conflicts, when they do arise, and the work in trying to resolve them which should not be necessary. Pete

No, I always disable controllers in the Sim. You should really do this if assigning in FSUIPC. No. How can it get "over-tasked".? Pete

It runs fine here on all those plus FSX. I need more information, please. Specifically what actually happens -- "will not run" is rather less than informative. And a view of the FSUIPC4.LOG file (in the Modulers folder) from the unsuccessful attempts would be handy. There's really no point in reporting things like this with no accompanying information, don't you see? Pete

No. It looks like a P3D corruption or driver conflict. I'd report it to Lockheed-Martin if Iwere you. Pete

If it is a purchased key, for FSUIPC4/WideFS7 (not FSUIPC3/WideFS6) then it will be correct. So this means you are making a mistake. ALL three parts -- name, email, key MUST be exactly right, exactly as listed in your SimMarket account. However, this part of your first post is nothing to do with Regsistration: This shows there's something wrong with your FSX-SE installation, and I can only help with this by looking at the Install Log file, as I asked. These are two completely separate matters! Pete

Thank you. But actually, you might not know it works .. yet. The auto-reassignment in FS occurred when FS thought the device was newly connected. Sometimes that's because you unplugged it and reconnected it, or sometimes it is an electrical oddity in the device, and sometimes it's just some update or other difference happening when re-booting the PC. However, I have high hopes that it is indeed not doing it in P3Dv3. They seem to have a lot of things to fix in this area in any case, and the FS auto-assignment action was a deliberate user-friendly facility in any case, so that beginners didn't have to worry about assignment of the more common and known device types. Pete

This is a P3Dv3 problem, Please read the pinned thread about this at the top of the Forum. Pete

First, please find the "Caps Lock" key on your keyboard off. Having messages in all caps is harder to read and comers across as shouting. I'm afraid there is not enough information here for me to help. I need to know what exactly you mean by "not start" -- FSUIPC doesn't check the Registration until it is actually running, and it cannot actually run until FS/P3D has "started", so I need to knnw exactly what happens. Then I need to know whether it crashes or freezes or what. I need the Windows error information telling me where it is crashing if it is. Finally, if FSUIPC is running far enough to check the registration, it is also creating a Log file in the P3D modules folder. Please paste the contents of that into a message here. Pete

Here too, and very responsive. Just look back! What IS the matter with you? Er, read what you wrote again. I found it most upsetting. I am getting on these days (72) and need to watch my blood pressure, and it is very upsetting getting comments like "I supose this would be the Fsui PC support and so I turned here for help, instead I get a rather frustrated answer instead of of plain answers." when there were clear plain answers there if you did but look! And "can just get my question answered ..." when the answer was actually provided -- why did you simply not read it. Here I'll repeat if for you -- it was just after the one sentence that seemed to get you so annoyed: If you mix assignment places you have to accept that sometimes it will all go weird because FS and P3D make auto-assignments. You also said "it is obvious that i have "had" a certain problem" -- don't you think I could be told about this certain problem, all the better to help? This is only in relation to problems with axes if you mix assignments between FSUIPC and FS/P3D. Many many folks have forgotten to turn off controllers in FS when assigning axes in FSUIPC, then there are all sorts of conflicts, and FSUIPC inevitably gets the blame. I have to tell them to use one or the other. If you are DELIBERATELY going to mix, then I cannot help. Isn't that obvious to you, at least now? I think you are being grossly unfair! I'm sorry if your huge annoyance came about from me questioning you instead of just giving a misleading Yes, which is what you evidently wanted. I'm just not like that when the question either doesn't make sense to me, or cannot be answered so simply as you wanted! Pete

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