John Dowson

Usually you would send the brakes direct to FSUIPC for calibration and reverse them. You shouldn't need a center zone, as the axis goes from -16383 (off) to +16384 (full on).

Its in the Modules folder - if you go to the FSUIPC 'Logging' tab there's an 'Open Folder' button which will take you there. You may have to configure explorer to see system files/known extensions.

Hi Max, if you can't see it as an axis, but you can see the other two levers, then I suspect its either faulty or you have a dodgy connection somewhere. Can you see all 3 rocker switch buttons (6 buttons)? Can you check what axis the device is reported as having in your fsuipc log file, you should find something like this: 16813 Product= Saitek Pro Flight Yoke 16813 Manufacturer= Saitek 16813 Vendor=06A3, Product=0BAC (Version 3.4) 16813 GUIDs returned for product: VID_06A3&PID_0BAC: 16813 GUID= {327F7D90-F534-11E7-8005-444553540000} 16813 Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255 Cheers, John

Yes, the SDK is available from here: You could also try Paul Henty's FSUIPC Client DLL for .NET: https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/

This is a problem which only exists since Windows 10, and only when you let P3D install in Windows\Program Files. That folder is protected unless you run "as administrator". Now, for most installations, this isn't a problem because provided you run the Installer "as administrator" it is able to change the permissions (just on the Modules folder) automatically. But on just a few systems it is prevented and gets that Error 1332. Sometimes this can cause issues as it can prevent files from being installed and the log and ini files being created. However, your as your docs were installed and you have log and ini files, I wouldn't worry about this too much, but if it you want to get rid of this and If you didn't run the installer as an admin, you could try that, otherwise you can manually edit the Modules folder permissions yourself (to allow full access by right clicking on the folder properties: Security-->Add Everyone as a user name, then check 'Full Control' access below). This won't be the cause of your issue with EFB2. Best to try their support forum for this. Cheers, John

Sorry, I have no idea. Please take a look at the provided documentation and look in the FAQ / user contributions sections to get an overview of what you can do with FSUIPC.

Sorry, but I have no idea what you want to achieve or what you want to do with FSUIPC. Please check the documents folder for information on the interfaces provided.

You can retrieve your codes from your SimMarket account, where you purchased FSUIPC.

Have you tried the 'Reload all assignments' button from the 'AxisAssignment' tab', or the 'Reload all settings' from the 'Joystick Calibration' tab. I'm sure one or the other (or both) will pick up the new lua... Cheers, John P.S. Just checked - its the latter!

Good to see someone solved there own problem - and posted the solution! A message box may be appropriate, but probably a note in the user manual more so. I'll have a look and think about this. Regards, John

What sim/fsuipc version are you using? And what aircraft - is it the FSLabs A320/A321? Maybe try with a default aircraft first, as it may be a a problem specific to this add-on. Presumably your button 'down' and 'up' are actually different buttons (or button numbers). Are you assigning to button press or release? Maybe switch to the other (or try on both). Could you also please post your FSUIPC5 (or 4) ini file. Thanks, John

Glad its now working - thanks for the update. Regards, John

Hi Fred, Try to install SimConnect (for FSX-SE) by running the SimConnect.msi (as admin) in these two folders: C:\Program Files (x86)\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-RTM C:\Program Files (x86)\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1 Then re-run the FSUIPC4 installer. Regards, John

Its in the 'FSUIPC Lua Library' document, page 9:

Hi William, Certainly nothing to do with FSUIPC - contact the support forum for whatever is producing that log file extract (VABase / VA Acars). Looks like its trying to find FSUIPC but can't - maybe a (unregistered) version is required - have you installed one? Cheers, John

Its always better/more efficient to have scripts auto-ran and monitoring something to re-act on, rather than starting on a button press. As to the number of scripts, its probably better to have a reduced number but this is less important really - you just get an additional thread per running script. Adding lua autostart + visibility via profiles is on my list to add to the features this year, so hopefully that will also reduced the number needed for those who separate luas via aircraft. Cheers, John P.S. Spokes: Rush I'm guessing - remember it from 35 years ago, will have to dig it out...! P.P.S. And yes, 'Temple of Syrinx' reference missed me..

Hi Fred, its not very clear where your error is - is it with ADE, when you install FSUIPC or when you run FSX-SE? Does FSUIPC install/run ok without ADE? If so, then you probably need to contact ADE support. I don't have/use ADE, but this post suggests that you need to uncheck 'Connect only to Matching FS Ver' - can you check this? Are you also sure nothing has changed on your system between Friday and Sunday? Regards, John

Seems to me that A2A re-purpose/re-use a lot of sim events/commands. I generally fly A2A and have quite a few log exclusions to keep a cleaner log file when flying with such aircraft. Look at the DontLogThese parameter, documented in the advanced user manual, page 8. Cheers, John P.S. Of course, applies to all aircraft - add the exclusions from the 'noise' events for any aircraft. Thinking about this, probably a good idea to make profile specific...I'll look into this

Hi Achim, yes, the sim should be paused - can you verify that its in the same state/position after you close FSUIPC? The sim going into pause state when you exit FSUIPC is due to P3D - I don't think it does this in v4.4 though (I'm away from my main pc until Tuesday now, I'll check when I return). BTW, you should update the the latest FSUIPC5 version, 5.15 when you get a chance - only the latest version is supported. Regards, John

Hi Achim, What version of P3Dv4 and FSUIPC5 are you using? The 'pause on task switch' tick-box only comes into affect when switching from P3D to an external program (FSUIPC is embedded in P3D). However, opening up FSUIPC sets the sim to 'Dialog Mode', which *should* blank the visuals and stop the sim. When you close FSUIPC, the sim should restart in the same mode as it was in before you entered the FSUIPC dialog. Sometimes you still here some sim sounds when the FSUIPC dialog box is visible (if a wav file is being looped), but the sim is not running. Is the screen blacked-out when the FSUIPC dialog box is displayed? Regards, John

Hi. mouse macros do not work with xml gauges in FSX, only those build using the C/C++ Guages SDK. You should maybe investigate if any L:vars are available instead. Regards, John

You will lose the pedestal view as you have removed it! Did this not leave the default P3D camera view for that definition? Did you try the other 'View select' controls? It also seems strange that the camera definition 4 is mapped to view select 3 - I would have thought that the numbers would match as they both start from 0...

So the [CAMERADEFINITION.004] is overriding the default P3D spot view. I guess you would need to remove (or comment out) the whole section so that the original view is still available. Did you try some of the other camera's with the 'View Camera Select x' control? If other camera's are (locked) spot, you could use them instead.

If F11 is sending 'View Camera 3' when you press F11, then your add-on aircraft is using 'View Camera 3' for 'Pedestal / Radio' and you won't be able to use this control. Similarly, if you have mapped your button press 'View Camera Select 3' and this works for default aircraft but not for your A320/A321, then that control is being remapped by the add-on aircraft. Alternatively, your add-on aircraft may have remapped F11 for its own use (and is sending a different control). First try assigning your button directly to the control 'View Camera Select 3', not the keypress (F11). If that doesn't work, you can try some of the other 'View Camera Select' controls to see if they provide what you need. Otherwise check the aircraft documentation (or support forums) to see if provides any other method/control for view selection. If not, you may have to live with using the view mode, sub mode, and next/prev controls. Sorry but I don't have the A320 /A321 so can't really help any further with the specifics of this aircraft.

Also look into the P3D Options -> Key Assignments. By default' F11 is mapped to 'View Camera 3 (select)'. You could try assigning another key (or key combination) to this, and then assign your button press to that key (or key combination). Or, better still, assign direct to control 'View Camera Select 3' (66853). John