Pete Dowson

Profiles are sets of assignments and calibrations for one or more aircraft. "Aircraft spcific" settings are obsolete and only still supported for compatibility with older installations. The default is Profiles. Whether you create one called "Jet" or use more specific names like "A320" or "B737" is up to you. The name of a Profile is just that, a name, for reference. When you load the King Air there will be no profile assigned to it, so you simply choose one from the drop-down list when you click the Profile button in an assignment or calibration tab. There are pictures in the User Guide showing you example drop-down lists for this. you'll see you can elect to use an existing one, or create a new one. You can even create a new one based on one of the existing ones (so you don't need to re-do everything, for example). Pete

You never need to delete FSUIPC. A fresh install with a later version with simply update the existing one. You deleted your registration as well!!!? Everything about FSUIPc is in the Modules folder. If you delete it all you start over! Where does it say "error code 64". There's no such messge in the Installer's registration dialogue. if it says the registration isn't valid, then you are making a mistake. All three parts of the registration -- name, email, code -- MUST be exactly right. Copy and paste from the details in the SimMarkt account. Pete

Windows is not deleting the files when asked. To see why add these lines to the [General] section of FSUIPC's INI file: Debug=Please LogExtras=4 This will result in messages in the FSUIPC log file like this: Autosave: deleting "xxx" (where xxx is a filename including the full path) for successful deletions, or *** ERROR: Autosave couldn't delete "xxx" (error n) where 'n' gives the windows error number. Pete

What software are you using which has a "mask value with" field? I don't recognise the picture you included, it isn't from my software. Are you in the wrong Forum? Pete

I'm sorry, really have no idea. How do you operate it with the mouse? Maybe experimenting with the Click Type in the Mouse Macro would do. for instance instead of Left Click (3) Right Click (1)? The click codes are listed in the User Guide, page 32. These aren't questions about Mouse Macros, per your subject title. I think someone else might be able to help you, soneone who knows your aircraft, if you used a properly titled thread for each different subject. Mention the aircraft and the problem. I am on holiday soon (imminently) until Wednesday 18th July. Need it too -- constant sun and temperatures up to and over 30C do not suit my 75-year old bones. Pete

There's a mix-up here. I said it was best NOT to install ANY joystick drivers or software. In your case something is evidently wrong with the Saitek install. It is best just to rely on the default Windows treatment. You said you wanted to install the Saitek stuff to use it for calibration. but if NOT using it allows FSUIPC to load, as before, then you can use FSUIPC calibration! Right? No. SimConnect is built into P3D. That's what FSUIPC uses. There's nothing separate it needs. The SimConnect DLLs installed by other programs are for EXTERNAL programs which use old legacy 32-bit interfaces (from FSX and FSX-SE). Pete

Yes. Don't delete ANYTHING first. Then you don't need to re-register (just choose "not now", and all your settings are retained. BTW this is called "updating" not "upgrading". Pete

But whilst taxiing, surely you should be in the cockpit looking where you are going? Pete

The format of button assignment lines is clearly explained in the Buttons section of the FSUIPC Advanced User's guide. If you want to mess with them then you should check. P is Press, U is release (U for Up -- to distinguish it from R for Repeat), 1,0 is the joystick number and button number, K says is is assigned to do a keypress, and the numbers after that are the Key codes (as listed in the Doc) and Shift codes (ditto). But when you need to search for something, the PDF versions on screen are easier. searching printed matter is not easy. Pete

This is not FSUIPC, but if the log is the same as the last one in this thread, then there's no doubt it's the installation of the devices. Why not calibrate in FSUIPC? Why do you have FSUIPC if not? I definitely suspect that Saitek software. What change to you think updating to P3D4.3 made? It isn't really part of this. Pete

The one which makes no sense? I think you need to ask in the L-M support forum, because it is smething to do with checks they are making, which make no sense on a lone DLL being loaded which is demanding no other resources. Pete

Interim release 5.132c includes a new parameter alongside MaxSteerSpeed: "RudderBlendLowest". This gives a ground speed below which the rudder input is used fully with no tiller use. The parameter defaults to 1 knot, so the aircraft needs to be stationary (or very close to stationary). Pete

I will implement a check on Ground Speed being 0 ( or less than a parameter value which you can set), and if so then NOT limit the rudder. So there would be a lower GS limit on the blending as well as the higher one (MaxSteerSpeed). I think that will be sufficient. and better than having to switch anything off and on with an assigned button or key. I don’t see a need to stop the tiller. You don’t want to use that for the rudder check in any case, surely? Just leave it alone for the check. Pete

If P3D is suspect here, it would probably be sufficient to merely uninstall the Client and re-install that. The thing is that you say: but FSUIPC is in no way related to any sort of animation whatsoever. It has no part to play there. And it doesn't change over time. It is an interface and does what you or you add-ons demand of it. Of course, without knowing anything about what you installed FSUIPC for, nor how other programs are using it, I can't swear for them. Perhaps some process of elimination of other add-ons would merit attention. It sounds like you have many if "uninstalling P3D2" is "starting over". even uninstalling all three parts -- content, scenery and client, is by no means a big job. It takes only a few minutes, and almost all add-ons will remain intact, maybe only needing running things like OrbX FSX Central again to restore some files. Take a back up of SCENERY.CFG first if you have scenery installed that way instead of the new AddOns XML way. You should also consider deleting your Prepar3D.CFG file and letting it rebuild, setting up your options in P3D again afterwards. Reading the AVSIM support forum suggests that is also a potential cause of big problems. Pete

Ah, I have been pointed to your Log title which does say 5.132, not 5.124 as you thought. so at least you are up to date. And from what I can make out from the CSV file despite its odd formatting, all three devices are acting correctly and being dealt with by FSUIPC normally. So, you need to try things: 1. without Sim-Avionics, and 2. with a default aircraft, not the Sim-Avionics 738 you have loaded there. Also, rather than remove "all P3d buttons and axis assignments, from all three controllers, normal & slew.", simply disable controllers in P3D. You can leave all assignments intact there. It is more important to disable the controllers. Finally, the FSUIPC assignments are relevant, so please post your FSUIPC5.INI file. it will probably be more elevant that the Log file. Pete

Okay. good, thank you. Thanks. I think you'll need to, as this statement: has me really puzzled. How would entering and exiting a program's option settings screen affect anything at all? FSUIPC has nothing to do with any "feedback", whatever is meant by that. It is a passive interface, waiting to be told what to do. Pete

Sorry, I have no idea about FSFS nor its use of FSUIPC, nor why you have to enter theoptions merely to exit. If you want help you need to state basic things linke: 1. Version of FS (FS98, FSx, P3D?) 2. Version of FSUIPC - and if not one of the supported versions stated in the Announcements above, update first. I have a feeling that you should be in the FSFS support forum. Pete

No, it wouldn't. Well, of course. The sim cannot load FSUIPC from a moved Modules folder. What makes this interesting is the Modules Folder was empty. Well of course, you created it so. Pete

You should be on FSUIPC 5.132 with P3D 4.3. And there's an update for that too, 5.132b in the Download Links subforum. Why on Earth didn't you simply leave the Settings alone? There's no need ever to delete settings. If they work, leave them alone. updating FSUIPC won't touch them. Doesn't that deal with most things. You say: So doesn't Sim-Avionics come in here? Next time, please attach joyscan files rather than paste them. It completely ruins the foramt and makes them pretty much unreadable. The log shows nothing wrong. Please update FSUIPC before posting again. Pete

What "website"? I don't have anything but this Forum and its subforums. If you mean the Schiratti site that isn't mine and i have no control over it. Enrico Schiratti simply maintains a "Dowson" page with links to many of my programs -- all the links go to this place, where you are now! If you read my previous post, just above, I actually said See how it tells you where to get the update? "from the Updated Modules thread in DOWNLOAD LINKS subforum above." Pete

That's a shame. I'm sure the aircraft designer's could sort that out. The only way I can think of dealing with it externally to P3D or aircraft code is to continually re-write the rudder deflection setting via SimConnect, much as the FSUIPC "magic battery" option does for the battery voltage. I suppose I might be able to intercept rudder axis controls and alter the parameter, but I'm not sure that will work with all aircraft. PMDG oes tend to do their own interception for example. But your original complaint was not being able to observe the animation of the rudder when doing the pre-flight checks. Going back to what you said: " In FSX & now P3D43, I've preferred to use "fsuipc direct to" for assigning a tiller (twist) axis on a LPro3D & the rudder to (Saitek) pedals along with MaxSteerSpeed=-60 .... but lament the "nuisance" of not seeing the correct animations inside (LDu Sys) & outside the aircraft for a controls check before taxi (turning the tiller moves the rudder !!)." I realise I still don't fully understand the problem. The MaxSteerSpeed facility operates when FSUIPC blends its Direct Tiller input with the rudder input. and as you say, both use the rudder. So you should be able to do your rudder movement check on the ground (but using the tiller axis movement). Now the problem seems to have morphed into being one about a 7 degree limit rather than about the animation. Or is it both? If the 7 degree limit is somehow imposed, then FSUIPC's own Tiller won't be any use because, as you say, you need up to 70 degrees. Does the sim's built-in Steering axis use the rudder too? With the FSUIPC blending facility perhaps I could not limit the Rudder Axis input when the Ground speed is zero (say) or the Parking Brake is on, so you could perform rudder checks before starting to taxi out. Would that work for you? Using the FSUIPC steering, though, since it uses the rudder for steering, there's no way to limit the latter to 7 degrees and have any useful steering when taxiing. Pete

That's a very strange error considering FSUIPC doesn't use any separate resource files, and certainly not images. It smacks of some sort of corruption. First I'd try re-downloading the FSUIPC 5.132 installer, running it, THEN get the interim update, 5.132b from the Download Links subforum above, and copy the updated FSUIPC5.DLL nto the P3D Modulesfolder, overwriting the 5.132 version. Then at least you'll be on the same version as me. If there are still problems I'd suspect corruption in P3D probably caused by a bad weather file. Try first just deleting the wxstationlist.bin file from yout AppData\Roaming P3D4 folder (the same folder containing your Prepar3D CFG file. That file will be re-created by P3D i any case. If it still doesn't help, then delete all the .WX files in your Prepar3D Files folder in Documents. If you are using an external weather program like Active Skythey won't matter in any case. If you think you need them, just make a safe copy of them somewhere. Pete

FSUIPC Version 5.132b fixes the issue with Mouse Macros on PMDG aircraft. Questions about LINDA need to be addressed to the LINDA authors. You could try posting questions about it with a subject title mentioning LINDA. Meanwhile you could go back to Mouse Macros after downloading the replacement FSUIPC DLL 5.132b from the Updated Modules thread in DOWNLOAD LINKS subforum above. Pete

There are lots of examples supplied, and more I think in the User Contributions subforum. and it is easy to debug them as you simply check the log for errors, make a change and immediately test again. It's a quick process, and trial and error is not a bad way to learn in such an environment (something not possible in my original programming environment where jobs were submitted for overnight tests in a Bureau type operation! Pete

Starter1 Set with parameter 0. (See above). It is as I said to start with! "SET" controls for on/off actions generally have 0 for off and 1 for on. Pete