Pete Dowson

FSUIPC has no access to the DirectX force feedback interface, if that's what you mean. If you are instead asking about variables to enable you to implement your own feedback according to aircraft forces, then of course it has all the velocities and accelerations in each axis you could possibly need. Force is dependent upon acceleration, and there are variables for that in the 6 degrees of freedom (X, Y, Z and the three rotations). G-force is another word for acceleration. Search the offsets list for acceleration, not G-force. Of course, pressure on a control such as the yoke is not just due to accelerations but pressure. If your aircraft is out of trim, there's more force on the elevator. When in a bank there's pressure to re-centre the aileron because of the wing dihedral making it tend to level out. Sidewinds and tailwinds will all play their part in providing different pressures. How you measure those and deal with them is a very complex area. Regards Pete

Strange. The FSUIPC installer is calling exactly the same facilities in Windows when it does it's check, yet it gets that peculiar FFFFFFFA error. That is an unlisted error number -- i.e. it isn't one even Microsoft would admit to. It is very suspicious, especially after I found that error FFFFFFFE has definitely been identified as a virus induced problem. I'm afraid I won't be available now till Monday. Away for the weekend from tomorrow morning. FSUIPC and WideFS really only consist of their DLLs. There's nothing going to change with a reinstall of those. There are no dependencies they create or install, no other bits, no registry stuff, nothing which will change. If anything is corrupted at all it would need either an FS reinstall, or probably more usefully a complete system reinstall followed by FS.. You don't need that if you backed up your FSUIPC4 KEY file as recommeded in the documentation. It is a text file containing all the registration details you need. Regards Pete

That shortcut is evidently pointing to another copy of FSX you must have installed at one time and forgotten about? You can easily make another shortcut to the correct one. Just drag the FSX.EXE to the desktop with the ALT key pressed. Regards Pete

No, sorry. I don't know anyway to change them without using the FS menus. You might be able to have a Lua plug-in which does it via the menus. There are examples of changing menu entries via Lua provided in your FSUIPC documents folder -- one for Fuel and one for Payload. You could problably adapt those to change the aircraft realism menu instead, then have that running from an [Auto ...] section in the INI for each aircraft/profile. Regards Pete

By the way, one clarification on this: I did not intend to imply that FSUIPC 3.999z shouldn't work with FS9.0. It does -- in fact I installed the original version on a separate PC just to make sure I'd not messed anything up. But there are many changes which other add-ons you have might tangle with which are fixed in FS9.1. Regards Pete

I doubt whether you really have to go to a specific tab and click anything. I suspect just going into the options and coming out again would do it. This is almost always due to the devices going to sleep because of Windows cuttin USB power. You need to go into the Windows Device Manager, fing every USB hub device and switch power management off in each one. Also make sure that if your devices are connected to an external hub it is a powered hub. If you are using Windows 8 I think that also has a bug which causes it to lose connections with devices. Regards Pete

Probably can't find your SCENERY CFG. See what files it produced. There should be one called Runways.txt, which is a log of everything it tried to do. Pete

Was there no FSUIPC.LOG file? If not, then FSUIPC hasn't actually been run. The crash would be occurring before it is loaded. And did FS9 actually crash 4 times at 6:13? The only information wanted out of all that appears in only two of those, just this: The other, the "information at the end" is similar. This is an Access Violation occurring in "ntdll.dll". And unless your computer's clock is wrong, occurred at 23:36, not 6:13. There's nothing indicating any involvement of FSUIPC at all. It is looking like your problem is not specifically realted to fSUIPC, except possibly just that with FSUIPC loading the timing and memory layout would be slightly different. I think there is one really big problem, and that is your FS9 installation is out of date. Version 9.0 is the original one with all its bugs. I most strongly suggest you install the update to bring it up to 9.1 level. The FS9.EXE version number will then read "9.1.0.40901". I cannot really help with the original one because everyone should have updated to fix the many bugs. Maybe when you built your new PC you forgot to install the update? If the problem still occurs after you've updated, I think you need to think about ways of narrowing down the problem further. If you have other add-ons, try without as many of them as possible, then gradually add them in. Make sure there are no other DLLs in the Modules folder other than genuine FS9 DLLs plus FSUIPC.DLL. Regards Pete

No, that's the Install log, not the FSUIPC4.LOG, which is produced when FSUIPC4 runs. According to the Install log, FSUIPC4.DLL is properly installed in "E:\FSX\Modules". But the SimConnect log says: 02169 File not found: Path="Modules\FSUIPC4.dll" So, it looks to me as if the copy of FSX you are actually running is NOT the one the Registry says is installed and where FSUIPC4 is installed. Take a look in your E:\FSX\Modules folder. There's an FSUIPC4.DLL there, right? And an FSUIPC Documents folder containing these files: Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX controls.pdf" okay Installed "GlobalSign Root.exe" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay So, check how you are loading FSX. Right click on the FSX icon you are using to start it, and look at the path where FSX.EXE is being loaded from. Try running FSX by double clcicking on FSX.EXE from your E:\FSX folder. Pete

Best to paste into a message in any case. I don't understand how you can have a runtime log file which shows everything okay, yet you have this error reported about the very same module: Problem! My signature check fails on the installed FSUIPC4.DLL. (Error ref FFFFFFFA) I can't find any reference for error FFFFFFFA. The nearest is FFFFFFFE which seems to be caused by trojan virus infection in the Windows system. Can you check the signature manually please. Find FSUIPC4.DLL in the FS Modules folder, right click on it, select Properties then Digital Signatures then highlight the SimFlight signature and clcik Details. You should get "The digital signature is OK". Pete

It varies according to operating system, but can be found in the FSUIPC4 Install log, where it does actually log what it is doing and even tells you how it found you had P3D installed in the first place! Please check your FSX, ESP or P3D Modules folder! Pete

Correct. Aircraft or Profile specific sections are only loaded when a matching aircraft is loaded. Pete

Apart from the options made available to you after registering, this has absolutely no affect on any weather settings made through FSUIPC by client programs. That interface is completely unaffected by registration. Arn't ypu the ;ucky one! I've been looking forward to that program for a long long time. The website has been saying "PFPX is in its final stages of development!" for months now! FSUIPC doesn't "let" anything except the application / FS change the weather how it likes. All the smoothing does is record the last requested value as a taget and progress towards it at the rate you set. If zero wind was the target it should reach it. Regards Pete

You don't have every livery and variant of every plane with its own otherwise identical details, do you? If so you should be using common profiles for common aircraft. It would be much more efficient. The size is limited by section only -- a section being one with a heading like [Axes ...]. For efficiency in processing parameters, FSUIPC loads each section at a time and currently it does limit sections to a max of 120000 bytes. Pete

Oh dear. I told you the control name. just look up the number in the List of FS controls installed in your FSUIPC Documents folder! Pete

As I already told you, controls can be sent via offset 3110. Cannot SIOC write to an offset? Pete

The only reason it is doing that is that the entries in the Registry still say P3D is installed. Did you uninstall P3D by simply deleting it, or using it's own uninstaller? If the latter then that uninstaller is faulty. You should report that to L-M. Meanwhile you'll need to edit the registry. How often are you actually re-installing FSUIPC4? Seems an odd complaint to make for somethng probably only needed about once every 6 months to a year when major updates are issued! Pete

There's never been any need to do that except in versions of Wiindows before XP SP1. You seem to be making some assumption about whatever it is going on without information. Show me the FSUIPC Install log file and, if one is present the FSUIPC.LOG file. You'll find both in the FS Modules folder. Also see if you can find the Windows crash data fr this -- in the Event Viewer, Windows Logs, Application. I need most of the details there -- module name, offset, and error code. Paste logs into a message. Pete

It's either Next view or Next subview. I don't recall. If you don't understand the controls in the list but know how to use them on the keyboard, just enable Event logging in FSUIPC, use the keyboard for the control, and check the log. The name and number of the control will be shown. Pete

Oh, those. Purely user choice. I always found the default values quite good. Keeping every 1 knot wind change from occurring for 8 seconds at a time is quite extreme -- the actual intended wind at you altitude or location will tend to be wildly different to what it is supposed to be and what the reports say because it would take so long to change! And the third figure is a suspension of freeze on weather after going into the Menus and changing weather, not after any programmed update. That's so that new weather being deliberately set there can take effect and avoid confusion by nothing happening! That is indeed a pressure change and it will occur when moving from one weather area to another. Again 30 seconds is a ridiculously long time to keep a 1 hPa change to. The default always worked fine for me. I think you seem to be desperately trying to suppress quite normal things in FS. A more reasonable type of smoothing will stop outrageous changes which can even stall the aircraft, but you must expect weather to change when flying as it does in reality. As does turbulence -- why suppress it when it is set to occur according to the real weather? If you don't like weather changes why use a weather program at all? Just set the "clear weather" theme in FS and be done. Regards Pete

So I need to load up FS9 and look? Can't you say what they mean? It would be quicker, else it'll be tomorrow night now. Flicker is caused by weather updates. If you stop your weather program it will stop. Or update to FSX and use global mode weather. Er ... I thought you actually MEANT pressure changes when you referred to "altimeter flux". Obviously pressure changes affect the altimeter reading. Altimeters are just barometers, measuring pressure! What on Earth did you think was going on if not pressure changes? Regards Pete

That looks better! So what's the result? Does it work or not? You don't say. If not, where's the FSUIPC4.LOG file? Pete

That would prevent FSUIPC working properly, and would in turn lead to WideFS not working too. I think you need to close FSX and show me your FSUIPC4 log file. Sorry, I don't understand that comment. And i always thought 000 wasn't valid in that position? No, it means WideClient didn't find a plug-in called Initial.lua to run so it didn't run it. It's only relevant if you want such a plug-in to run. Regards Pete

Sorry, unlikely as I haven't used FS9 for so many years. What's 0 8 8 mean? Sorry I don't understand what you mean. Regards Pete

By making all three monitors one large screen you can stretch a single copy of PM PFD over the whole width and have pilot, eicas and copilot screens all in one window. I'm afraid I can't really explain how to do it -- I've not messed with my PM setup for years and don't want to disturb it as it took months to get right. I'm not using Expanded F6 mode any more -- I have spearate mini-PCs for each part. It's the only way I ever got them smooth enough. Ask on the Project Magenta support section of MyCockpit (http://www.mycockpit.org/forums). Pete