Pete Dowson

I'm sorry, but unless he left contact details in the package, I can't help with that. But if you want to supply an updated package for me to include in the SDK, please go ahead. Pete

Just calibrate. FSUIPC doesn't care what the numbers coming in are, you just need to calibrate for your specific hardware. There's a whole chapter in the FSUIPC user guide about calibration, and it has always been one of its main functions. Just follow the numbered steps. Pete

Jitter in axes is due to poor connections, poor power supply, or dirty pots on the device. Large discrepancies would be due to conflicting assignments, but jitter is definitely hardware, not software, related. Pete

The "latest" being which? Version number please -- it is ALWAYS required. And what was your previous version? Do you think it is just the update which changed things, because that is extremely unlikely. Updates never change your settings. This cannot be anything specific to FSUIPC. In fact I can think on no possibly cause at all, unless the sound output is somehow interfering with your trim input and when the sound smooths out it stops. Are you using an axis for trim, or buttons, or no hardware at all? What's "auto trim"? Is this an add-on you are using? Pete

Why? Why not use the Installation instructions included in the downloaded ZIP file? I have never published anything called a "quick start tutorial"! The installer is the program in the downloaded ZIP called "Install FSUIPC4.exe". Do you think this is a confusing name for it for some reason? There is no file called "FSUIPC4.exe" and there never has been! The installation instreuctions are short and easy. You just run the installer. Where does any of the documentation mention a Modules item? In FSX and P3D it has ALWAYS been Add-ons and is documented as such. I think you must be referring to very old documents, and not the official ones supplied with FSUIPC. Please, try to learn to use FS before plunging in to us add-ons. And when using them., please refer to the supplied documents, not ones you might find elsewhere. Pete

You cannot have two sections with the same name, i.e. [Auto] 1=Lua frictions and [Auto] 1 = LUA DynamicFriction Only one of those sections will be applied (and I'm not even sure which -- it is a Windows function). Why do you want to run two friction programs at the same time, one fixed and one dynamic? They'd conflict in any case! Just delete the section you don't need. BTW those aren't specifically for the 737 NGX, but all aircraft. Did you only want it specifically for the 737NGX? Pete

You'd be better off posting a new thread rather than adding to an old one referring to an extremely old version of FSUIPC. Pete

Sorry, I don't understand much of that. Are you saying PMDG use MakeRunways? That's news to me! What "compares AIRAC with the sim data? What is "ARPT_RWY.dat"? From inspection, I can see no way possible for it to provide a runway width of zero unless that is what the field shows in the BGL. Can you give me an examples to check, please, one of the default airports you say is affected? Did you check the entries in the log file, Runways.txt? Why not at least paste the relevant small section out of that you show me? It is serious -- there are programs which use that information! If you believe it is a bug I would need to analyse the causing BGL to find out whay it is happening. MakeRunways is now about 15 years old and this is the first such report, which is odd. Please, information needed. Pete

Sorry, I'll try to do something about that on the next update. Meanwhile, try opening the FSUIPC Options in FS and look at the real window. Pete

You need to ask EZCA support. Make sure you are using a P3D compatible version. It s evidently some sort of timing problem,and with FSUIPC installed the timing is different. Pete

I've no idea -- it would be a function of the device. The only relevant value is probably the bits per second. That's normally 4800 for NMEA standard devices, but I know some devices can be set higher. The speed is actually set in FSUIPC's menu in any case. The ones in the Windows device manager settings are only defaults, in case the program doesn't set them. I think your investigation should be centred on the phone device itself, not on the app or FSUIPC -- maybe it just won't support what you want to do. I'd have no idea how to do it on an iPhone or iPad, for instance. Pete

It sounds rather as if there are conflicting assignments or actions going on. There's no way FSUIPC will change any parameters itself. You can paste text file contents into messages. But there's no point merely pasting in a normal log. You'd need to enable some relevant logging option and conduct a more scientific test. Pete

I'm afraid you'll need to provide a lot more details, like version numbers (both FSUIPC and P3D), how you are assigning, what add-on aircraft you are using (and whether it is approved for P3D), and exactly what the crash details, from Windows, are. It could be a bug in the 777 or in P3D. Have you checked those support sites? Pete

What is different from before you reinstalled? Did you delete all your settings? What version of PFCHID have you installed? How have you assigned the quadrant axes? Pete

Where did you get 4.09 from? Pete

Apologies for the delay. As you will have seen, I have been away on holiday. Do you mean elevator trim? Why "2"? What action do you use in the NGX? Pete

Do you know how that can be done, because I don't. There's a program that does all this for you -- fsps-fsx-fiber-accelerator It works very well. I don't think I should offer facilities in FSUIPC which usurp the functions of available programs. Regards Pete

You must be using an out of date version of that document! Install a current version of FSUIPC and you will find the values, added in the PMDG SP1D update for the NGX, in the additional offsets. Please always do check that you are up to date with your software and documentation. AND PLEASE DO NOT POST SUPPORT QUESTIONS IN "ANNOUNCEMENTS". I have moved it for you. Pete

You can delete profile sections by editing the INI file. But how can you make a new profile without programming one? Surely if you delete the profile you lose the settings for it and so have to make new ones. Pete

Nothing arrived in my email from you until 12 minutes ago. Now I see another copy arrived 6 minutes ago too. The log you sent seems to show that you don’t have anything assigned to the Lua plug-ins. they are starting up, but never being asked to do anything! The throttles are not actually assigned as I said you must. This would explain why you are still seeing normal unlimited throttle action – I suspect you have them still assigned to the throttles, not to the Luavalue! If you think you have assigned them correctly, please show me your FSUIPC4.INI file so I can see what you’ve done. Pete

Okay. now what you should do, if you want the other stuff running again, is to add the entries from the old DLL.XML file, the one you saved or renamed, back to the new one, one at a time, testing by loading FS each time. The sections are the parts between (and including) <Launch.Addon> and </Launch.Addon> add them before that last </SimBase.Document> line. There's no need (and no point) adding any section which contains <Disabled>True</Disabled> Pete

Sounds like they don't have IDs asigned to them. FSUIPC relies upon Windows assigning IDs, but some installers don't seem to work well, especially in Windows 8. You could try setting the IDs yourself. There's a utility to help do that called JoyIds http://airgroup51.net/forum/index.php?PHPSESSID=09e506505bba7e42a1f9efa9ceff9383&action=dlattach;topic=2435.0;attach=2966

I just noticed your post on AVSIM FSX forum asking for help, in which you say that the throttle input is "not limited at all". This seems to indicate that your assignment is still to the throttles, not purely to the plug-ins. If the Lua plug-ins weren't running you'd get nothing on the throttles because there's then no active assignment. Have you still got the controller enabled in FS? I'm waiting for the log file so I can help before I go. Pete

I'm not off till the morning. Enable button/key logging, and lua debugging options in the Logging tab, then close FSX and restart it. Briefly try the throttle levers, at least once eacvh in each range, then close FSX. ZIP up the FSUIPC4.LOG file and send it to me at petedowson@btconnect.com. Pete

You appear to have purchased FSUIPC3/WideFS6 separately in 2007, then FSUIPC4 on its own in 2008, then WideFS7 early in 2012, then again in December 2012. The name and address certainly matches each of the later purchases. I still think the only way it can reject the key is if you are using the key for FSUIPC3/WideFS6 [EDIT] Also check that your computer system date is correct! Please confirm that you are installing FSUIPC 4.939n (the currently supported version). If so, email me the details you are trying to register with -- do NOT post them here. My email is petedowson@btconnect.com. After this evening I am away till the 27th May. Pete