Pete Dowson

I've no idea what could make them "blink", unless it's to do with your video system. There's no "blink" built into the FSUIPC display action. If TAB won't confirm the action then they've changed the code so it doesn't work. Not sure why you'd even bother using Mouse Macros with PMDG 777X since PMDG provide assignable custom controls for almost everything, as they did for the 737NGX. Pete

But with any version of FS or P3D, FS9, FSX or P3D, you install by running the installer. It doesn't matter where you run it from. P3D is no different in this regard! You don't need to know beforehand "where it goes"! PLEASE READ THE INSTALL GUIDE DOCUMENT INSIDE THE DOWNLOADED ZIP FILE!!! Pete

Nevertheless, there SimConnect.DLL's are not found. The installer (and FSUIPC itself for that matter) searches ALL folders in Windows WinXsS folder, first for folders entitled *simconnect*<LVERS>* where * matches any one or more characters and <LVERS> is any one of: #define LVERS_ORIG "10.0.60905.0" #define LVERS_SP1B1 "10.0.61232.0" #define LVERS_SP1B2 "10.0.61233.0" #define LVERS_SP1B3 "10.0.61234.0" #define LVERS_SP1B4 "10.0.61240.0" #define LVERS_SP1 "10.0.61242.0" #define LVERS_ACCA1 "10.0.61245.0" #define LVERS_ACCB1 "10.0.61246.0" #define LVERS_ACCB2 "10.0.61247.0" #define LVERS_ACCB3 "10.0.61248.0" #define LVERS_ACCSP2 "10.0.61259.0" #define LVERS_STEAM "10.0.62607.0" #define LVERS_STEAM2 "10.0.62608.0" #define LVERS_STEAM3 "10.0.62609.0" #define LVERS_STEAM4 "10.0.62610.0" #define LVERS_STEAM5 "10.0.62611.0" #define LVERS_STEAM6 "10.0.62612.0" #define LVERS_STEAM7 "10.0.62613.0" #define LVERS_STEAM8 "10.0.62614.0" #define LVERS_STEAM9 "10.0.62615.0" Then it just needs to find a SimConnect.dll file within that folder, to which FSUIPC then links directly. From your listing above there are no SimConnect.dll files? This method has proved foolproof compared to the way Microsoft intended, through the ridiculously complex side-by-side manifest probe system which is the main reason many SimConnect client applications fail to connect. Pete

Just run the Installer. It will sort it out. That's what installers are for! Pete

... Failed to find a valid SimConnect needed to use FSUIPC4! I'm afraid this means exactly what it says. There are no suitable versions of SimConnect installed in your Winds\WinSxS folder. FSUIPC isn't too fussy. For FSX-SE it will use FSX SimConnects (RTM, SP1 or SP1/ACC) and also the version 62615 one installed by FSX-SE. Go to the folder Steam\steamapps\common\fsx\SDK\Core Utilities Kit\SimConnect SDK and you will find subfolders with all three of the FSX Simconnect installers. Execute each one of those in turn. Pete

Sorry, I can't really advise either way. How you update your system is up to you, up to how you want it to look. Pete

Mouse Macros actually depend on the actual memory location of the function they are calling. If you change the Gauge or cockpit files then you must delete all the macros relevant to those gauges or cockpit and make them again. You have to do this on every update to your target aircraft. There's no way around this. Mouse Macros are a "fiddle", a "hack", going direct into the code which the mouse rectangle detector would otherwise call. Pete

Hmm. Where they are in the [General] section, doesn't matter, because Windows accesses them only by Section name and Parameter name. The line must have been outside the section. Pete

What pedals? Sorry, I don't understand the question. What is wrong with assigning pedals in FSUIPC if you assign everything else in FSUIPC? You should disable controllers altogether in FS if you assign in FSUIPC, in any case. I assume you have some sort of problem, but since you don't say what it is I can't really help. I was away Saturday and Sunday in any case. Pete

Hmm. FSUIPC is not designed to "stop dsconnects". If it does it is just coincidental to the way it operates. When I want to look in the Flightsimulator, with hold the space-bar and move the mouse, the view stand still and doesn´t move in any direction. When I want to zoom in or out with the mousescroller, the view is only going to the back-or to the front of the Cockpit, so it doesn´t zoom. I have everything tried, but it doesn´t work. Please always post FSUIPC support questions to the Support Forum, not to any of the SubForums which are repositories for reference information. Mouse look in FS is disabled when you disable controllers. That is why there is a Mouse Look facility in FSUIPC. Just enable it in the Miscellaneous tab. And you can then use the middle mouse button if you wish (more convenient), or assign mouse look to the space bar or to any button or key. Pete

FS Commander is not my product. You are in the wrong Forum altogether, -- and you posted in the FAQ reference subforum, so I moved it to the Support Forum so it can be answered! I cannot support other perople's programs! Pete

To help work out why you are not getting the file you need, I've added more logging to FSUIPC version 4.949b, available only through this link at present: FSUIPC4949b.zip If you have the parameter with the correct keyword and in the correct place in the INI file, it will be logged the first time FSUIPC tries to save it. So, if there's no such log entry, but still a bitmap file produced, then you have the parameter wrong or in the wrong place. On the other hand, it it does try to save it but this fails for some reason, then the path will still be logged, but with the Windows error number to show what is wrong. That's all for now. I'm away this weekend, back Monday. Pete

I know that the regular Saitek throttle quadrants have a button which presses when you pul the lever right back. But evidently I don't know about the device you are using. You could just go to the FSUIPC "Buttons & Switches" tab and try. But, of course, that won't automatically create a reverse function. You'd need to assign appropriate controls, as I said. Certainly, if the aircraft you are using it with had normal FS reverse support, you could do exactly that, even though the Saitek throttles are not really designed to work that way. But it looks like, from what Paul says, your B377 is different (as I suggested it might be). I'll have to leave you in Paul's capable hands. I'm away for the weekend. Back Monday. Pete

The installation and registration is fine. As it said in the Installation guide, all the documentation is in the FSUIPC Documents subfolder, in the FSX Modules folder. For separate settings for each aircraft type you'll want to create Profiles. But first I would recommend you just do some simple things, basic assignments, with default aircraft. I cannot give tutorials here (nor anywhere really). I am not a good teacher. I wrote the User Guide to be as clear as I could. I can answer specific questions if you get stuck, as can lots of others here. You'll also find useful stuff in the User Contributions subforum. I'm off this weekend, back Monday. Pete

I've been advised that these indications are not related to actually being overspeed or in a stall, but simply the pilot setting values above or below the current max and min safe speeds. My MCP can't show more than 4 digits, it can't show "A"s and can't flash single digits, so I've never seen this. The max airspeed would be the "barber pole airspeed", and there is an offset for that. You'd need to read the MCP setting and compare. Stall speeds VS0 and VS1 (clean and full flaps) are available in offsets, but not one for intermediate settings so I'd assume you'd need to calculate those yourself. Pete

POST MOVED FRO "FAQ" SUBFORUM TO PROPER SUPPORT FORUM First, please always post support questions to this, the Support Forum, where they may be seen and answered! Do NOT "download FSUIPC4.DLL into FSX". Download the ZIP file for the Installer, and run the Installer program. It will install FSUIPC4 properly. Please read the Installation guide in the ZIP. Pete

Do these Saitek levers actually have a measurable range (i.e. changing input numbers, as seen as the "IN" value in the calibration) before the idle detente? Because the Saitek throttle quadrants I've sen only have a programmable button there, no axis range you can use for reverse. You say: but maybe this add-on implements its throttle control in a non-standard way. Certainly many sophisticated add-on aircraft do (Aerosoft Airbus and PMDG 737NGX to name two). The reverse thrust range is actually not available on any regular FS assignable controls at all -- they only operate from idle to full thrust. FSUIPC achieves the reverse range by using old original FS98 axis controls which, luckily, are still actually implemented. But some add-ons do not recognise these properly. So, test your throttle reserse out on default aircraft first. Once you have it working fine there, f it is still not right on your A2A add-on then you would need to program reverse on F2 (actually "throttle decrease" control -- which has separate engine variants) instead. Aha! That seems to confirm what I thought and mentioned above, that Saitek throttles don't provide any reverse zone. Does your have buttons pressed when pulled back? If so program them in Buttons & Switches to use "throttle1 decr" and "throttle2 decr" when pressed, with repeat enabled, then "throttle1 cut" and "throttle2 cut" when released. Then you just keep pulling back for full reverse. Alternatively, if the throttles also simply do not work reverse in default aircraft either, treat yourself to some throttle quadrant which does work, OR calibrate idle further up, away from the detente, and just make a larger idle zone so you can find it without the detente. Pete

No, Ivap does not use FSUIPC and FSUIPC has nothing at all to do with multiplayer. You need Ivap support. According to the Registry you do not have any Prepar3D version 1 installation at all, only FSX-SE in its usual place! E:\Jeux Steam\steamapps\common\FSX If you are still using P3Dv1, try installing P3D (properly), and avoid all of those horrid migration tools which make a real mess of things. And NEVER try to force FSUIPC's Installer to try FSX as P3D or the other way round. FSUIPC does completely different things for each version and you will simply get into a further mess and crash. And you are using a very old version of FSUIPC. I cannot support old versions. So go get the current version (after you've installed P3D) -- you should be on 4.949 (or later) today. That also supports P3Dv2 and P3Dv3,. Pete

Blinking "8" and "A"? Where do you see such things? Overspeed gives one clacker sound, underspeed gives the stick shaker. Don't know what you mean by 8 and A? Did you search the Offsets list? I searched for "overspeed" and found it immediately. "Underspeed" would be "stall", Please do use the documentation provided. Pete

If there's no Radar.bin then there's no WX radar data Prosim can use! Pete

Well, the radar link to ASN is working, and FSUIPC is getting the data. You simply MUST have something wrong with that parameter. Maybe some spurious non-printing characters? Try deleting it and entering t from scratch next to your BitMap parameter line. Pete

Aha! I've found another way t gets the name -- from P3D itself, in the "Language.DLL". It is stored there as string number 36864. I must have added this as a much more reliable (!) and efficient way of getting it. This SHOULD be the same name as actually used by P3D. Does your normal flight selection in P3D v3 work properly? Here's the RESHACKER decompilation of the relevant part of my Language.DLL: STRINGTABLE LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US { 36864, "Prepar3D v3 Files" 36867, "SCENERY" 36869, "SOUND" 36870, "TEXTURE" } You see #36864 is correct here. So, have you got a different Language.DLL? Mine reports file and product version 3.1.2.15381. dated 17/12/2015 08:15. Please check. Pete

Oh dear. Very few offsets are FLT (32-bit floating point). Where they are it says so. 07BC is just a UD (unsigned double word), i.e. a simple number, and is most certainly either 0 or 1. Same for the yaw damper. Pete

Hmm. That's very strange. I'll try disabling WideFS and see if I get the same. The construction of the path is based on FSUIPC's knowledge of the version you are using, and this is definitely confirmed as v3 by this line: Running inside Prepar3D v3 on Windows 8.0 It isn't the sharing which makes it use UNC paths so much as whether WideFS is enabled or not. I'll get back to you. Pete

Is that where Prosim737.exe is executed from? And exactly where is it in the INI file? As another check, you can add a line like: ASNwxRadarBitmapPath=C:\RadarPicture.bmp to get a displayable bit-map which you can view with any graphic display program. (Change the path to put it where you like). Full details of the ASN WXRadar facilities in FSUIPC, including the programming data which ProSim is using, are in the document in your FSUIPC Documents folder entitled "ASN WX Radar facilities in FSUIPC4". You'll see these were added as long ago as FSUIPC version 4.93. On your centre console somewhere. Normally between the captain and FO's mic switch panels forward of the transponder. If you haven't got the WX Radar panel you should program some buttons to increase/decrease gain and the same for tilt. You assign them in Prosim. BTW you can get more logging from FSUIPC about its relationship with ASN radar facilities by adding these lines to the FSUIPC4.INI [General] section: Debug=Please LogExtras=4 If you do that, paste the Log file here, in a message. Pete