Pete Dowson

Thank you!! ;-) Pete

No one has helped me nail down the reason for the problems with Linda and 4.939m, seeming to have preferred just to retreat to an older, unsupported and never to be developed version. :-( But please now see this thread: http://forum.simflight.com/topic/79274-fsuipc-old-versions/ Pete

I have not received any information to help me definitively solve the Linda problems,, which I presume are the ones you are referencing, but I have re-vamped the code around the Lua event system again -- in version 4.939n, and I have hopes that this will fix it properly! I've been waiting for some reply in the other thread, but seeing as folks seem to have retreated to the k version and don't want it actually fixed properly, I've been unable to get it tested yet. So, now you are here, please try it and let me know. Here's the download link: FSUIPC4939n_Test.zip. Thanks, Pete

What problems? I'd really rather solve the problems than allow folks to go backwards. Pete

I think the way that's being done in FS must be by-passing the normal message queue, reading the keyboard state instead. FSUIPC doesn't have enough privilege to hook that low in the Windows system I'm afraid. Sorry. Pete

You'd have to program it as a toggle, Press and Release separately. Pete

Best to disable controllers altogether in FS, if you are assigning in FSUIPC. Sometimes FS will automatically reassign default axes, all by itself. It does this when it thinks the device is newly connected. If you mean the Profile called "Test", then delete the complete sections [Profile.Test] [JoystickCalibration.Test] and [Axes.Test] (Sections are delineated by those parenthesised [... ] names). I notice you haven't assigned any buttons yet. Don't you use buttons? Pete

The devices attached at the time you start FS are scanned by FSUIPC automatically and their details are added to the INI file then. You need do nothing, just connect devices and run FS. Pete

Yes, but for added security you should also add R.GUID={E068DE30-0837-11E4-8009-444553540000} T.GUID={CB9C6560-90F1-11E4-8001-444553540000} Y.GUID={E068DE30-0837-11E4-800A-444553540000} Then your devices are full identified both by name and number (GUID). Pete

The problem is simply that you appear to be running P3D as if it is FSX, so FSUIPC is configured to run in FSX mode. Please remove the FSX.EXE from the P3D folder, and re-run the FSUIPC4 installer. These so-called "migration" tools are a menace! [LATER] In version 4.939m, which you are using, I went to great lengths to properly identify the version of FS which FSUIPC actually finds itself running within. I have just tried making a copy of Prepar3D.exe in its folder and renaming it FSX.EXE. When I do that, it doesn't matter if I execute the Prepar3D.exe or the FSX.exe copy, FSUIPC still identifies that it is P3Dv2 immediately. It does this from the version number of the EXE being run, not from the name, as it used to. Somehow, this check isn't working in your installation, so I would dearly like to know exactly what your "migration tool" has done! So, can you tell me, please: 1. What EXE files do you actually have installed in the main P3D folder (not in subfolders), and 2. Which of those EXE files are you actually executing when starting P3D? 3. When right-clicking on that EXE, and selecting Properties, what Version number is showing? I'd like to understand how my version number check is failing to identify things correctly. Maybe I can try to cope with this. Pete

Not by FSUIPC, no way. More likely you reconnected the USB -- if you want to make the assignments safe against Windows re-assigning device IDs you need to enable joystick letters -- please see the User Guide. If you are assigning in FSUIPC you MUST disable controllers in FS altogether. Otherwise there will always be conflicts. To get any axis working correctly, follow the calibration instructions step by step -- there's a chapter for it in the user guide. Pete

You've moved the USB connections around. If you want to be able to do thast you must use Joy Letters -- please see the chapter in the FSUIPC4 User Guide about that. Pete

Sounds like a bad joystick driver. There's no way a simple reconnection will cause FSUIPC to hang and if FSUIPC hangs so does P3D, so you wouldn't be able to exit. Pete

ASN doesn't use or need FSUIPC! FSUIPC is not part of FSX, it is installed by the installer for FSUIPC. If you want to purchase FSUIPC (why?) you go to the purchase page on SimMarket. FSUIPC has nothing whatsoever to do with fps, so I've no idea where you are getting this weird stuff from! Pete

FSUIPC never ever wipes anything! All your settings are saved in the INI file in the Modules folder. You can only delete them all by deleting that file!

You'd need to adjust the rudder axis. The only ways I can think of which may work are either: 1. Have two little Lua plug-ins, each of which responds to one or other of the button presses by incrementing or decrementing the axis value -- it would need to read the axis value from the appropriate offset, add or subtract something from it, and send it as a parameter to the Axis rudder set control. or 2. If the aircraft will respond to direct setting of the rudder axis through SimConnect, then you could assign one button to the FSUIPC control "offset sword inc" with the offset set to the rudder offset, and the parameter set to the increment value you want, and the other button similarly to "offset sword dec". I could help you more on either of these, but I don't have the aircraft so cannot test here. I am away for the weekend, so if you need more help, please ask on Monday. Pete

Only from very many years ago. Since the release of FSX FSUIPC has been installed with an intelligent installer, and the installer is where you enter registrations. Please refer to the document entitled something obscure like "Installation and Registration" which is included in the downloaded ZIP file. Maybe you missed it? You need the email address, your name, and the 12 digit key (not custormer number), and all three parts must be exactly the same as when you purchased the program. Pete

Mouse macros only work with gauges written to the standard Microsoft C/C++ gauges SDK. They can't be used with XML gauges. However, it may well work fine using the relevant local variable (L:Var) -- it looks like L:SelectedNav2 has something to do with it. Check using the FSUIPC assignable control to log L:Vars, or use the Lua plug-in provided to monitor them. Pete

And how do they move the rudder? What do you assign them to do? If they are assigned to the same controls as the keypresses (on the numpad), then maybe the Airbus is programmed only to accept axis inputs, to the rudder let/right increments. Have you checked whether the normal default FS keyboard assignments work? Pete

What's "C1 and C2", and how are there two things, not just one? The rudder is just one control axis not two. Pete

Yes, I know of Linda, I just do not know it -- I cannot debug it for you. Since I've not knowingly made any change between version 4.939k and 4.939m which would affect any programs adversely, there is no way I can sort out what the problem is without information -- and probably details of the exact problem from someone who knows Linda. No, nor do I. I have no information, you have supplied none. I did suggest that you show me the Log file, which may or may not help. Do you have access to help for Linda? Maybe they have a Forum where you can ask someone to work out what is wrong and, if it still points to FSUIPC, to let me know so I can help fix it. No. I don't see any point in doing that -- unless you've been changing them of course. Updating FSUIPC with the Installer only replaces the program, it doesn't change any ofyour settings. Pete

I'm sorry, but there is no way I can support old versions. Please update to the currently supported version (4.939m) and try again. Do this before trying to post any INI or LOG files. Pete

I would need more information to help -- especially the actual version number of FSUIPC, and what actual controls you are assigning to. If everything has been working fine for years, whay are you changing things? What have you changed? So the Dash 8, which you explicitly mention for the problem, is irrelevant? Maybe you should show me your settings -- the FSUIPC4.INI fie from the Modules folder. Pete

I'm sorry but there is no way I can possibly support such an old version as 3.47 -- that's about 10 years old and has been superseded around 100 times! Pete

Well, not according to the INI file you showed here. My detailed analysis above is correct, and in any case, according to that INI file there are no devices attached that can use in any case. If there were any they'd be listed here: [JoyNames] AutoAssignLetters=No Maybe you aren't showing me the actual INI file you are using, the one in the Modules folder of the installation of P3D , FSX or whatever. Pete