John Dowson

Hi, presumably, from your ini, your taxi lights are assigned to a button that stays in when pressed (i.e. no release), and then releases when pressed again? i.e. 112=P4,9,C69749,1 -{Custom control: <69749>}- 113=U4,9,C69749,0 -{Custom control: <69749>}- You have the same on your 777 but on a different button, which, as you say, works for you, which is strange. Also, if the same happens when you activate in the sim overhead, then it does sound like a PMDG issue. There are no events in your log - did you activate this as advised by Thomas? If not, can you activate logging for 'Button and key operations' and also 'Events (non-axis controls)' (from FSUIPC's Logging tab), and produce another log file that shows the taxi lights being activated. John

Hi Mark, for install error 1332, you can manually edit the Modules folder permissions yourself to allow full access, by right clicking on the folder properties: select Security-->Edit-> Add, enter Everyone as the object name, then 'Check Names' and 'OK'. Then give 'Full Control' to the Everyone group just added. John

Hi Ray, please try the following dll (5.152c) - I've increased the max space for LVAR names from 32 to 64 characters. I haven't tested this yet, so please let me know if there are any issues. Cheers, John FSUIPC5.dll

Hi, sorry for the late reply... What version of MakeRunways are you using? Did you check the MakeRunways documentation? For P3Dv4, MakeRunways uses a special version of the Lorby-Si add-on manager (included with MakeRunways) to generate a scenery.cfg file that it can use that contains the scenery from various add-on xml methods. Therefore, please check that you are using the latest version of MakeRunways and check the documentation. John

Hi Stu, please try the attached version (5.152b). John FSUIPC5.DLL

Hi Stu, Thomas, I'll take a look at the changes and build a new version for you to try. I'm a bit busy at the moment so it may take me a couple of days. John

Hi Daniel, do you have anything in the windows event log for the crash? If so, could you please post it. Thanks, John

Hi Rodger, your FSUIPC license for FSX-SE is for FSUIPC4. This license is also valid for P3D version 2.5, 3-3.4 (all 32-bit). If you are using P3Dv4 (64-bit), you will need to purchase a license for FSUIPC5, available from SimMarket. Regards, John

You could also compile your jar as a 32-bit "one-jar" and provide that. But it does look like your users would need to install a 32-bit JVM as well.

Hi Crazz, According to the documentation, the FSUIPC java interface was provided by Mark Burton (mark.burton@zenobyte.com). All sources are provided, so it should be possible to update this to a 64-bit dll. I can add to the SDK if anyone wants to take this on, otherwise I could take a look at some point but it will be quite a while before I have time to look into this. Cheers, John

Could you try activating axis logging (from the FSUIPC logging tab). Generate a log file that exhibits your problem (i.e. disconnection, reconnecting and going haywire). It will be quite large, so zip it up and attach to a post and I'll take a look to see whats happening.

Hi Steve, sorry for the late reply - I was hoping someone else who has tried this would jump in and advise. I can only tell you that we generally advise against installing the Logitech/Saitek drivers as these can create problems with FSUIPC. I can only suggest that you try to see if it works for you, and if not then uninstall. Maybe be a good idea to take a backup copy of your registry before you install, as their drivers have been known to leave registry entries after uninstallation that may affect behaviour (although I don't know if this is still the case with their latest drivers). Regards, John

I don't think that "input spike suppression" will help. Its not a 'spike', its caused by your wireless joystick device reconnecting and being re-scanned, so the axis values will be reset until it receives a new input value. I'm not sure there is anything you can do - I've asked Pete to see if he has any ideas that may help. Regards, John

FSUIPC can't help you with this. For USB sleep problems, its generally a matter of configuring the power management settings for USB hub. However, it seems to be your wireless device itself that is going to sleep (to save battery), so I don't think there is much you can do, apart from maybe contact Logitech support to see if there is a way to turn off (or extend the time of) this 'feature' of your device. John

No problem - glad its now working. John

Hi Roman, thanks for that - thats very interesting! As Bob is using a rotary switch, and its sending both a release (for previous position) and a press (for the current position), I thought he could add the MAGNETO*_OFF controls to the button release, but it looks like the release/press order is not consistent, i.e. it generates a release then press going clockwise, but a press then release going anticlockwise (for your Magneto1 only?!!). Therefore I think your solution of having multiple controls (i.e. sending an 'OFF'' first) is the thing to try. So Bob, following Roman's advise, can you edit your ini file and try the following [Buttons] section: John

Hi Bruce, I've no idea what 'Sync Pos' is, so can't help you with that. What aircraft are you using? Some add-ons, such as those by PMDG, don't work very well with FSUIPC calibration and you should send as FS command if you are using those. Also check that you have controllers disabled in P3D if you are assigning your axis in FSUIPC. Cheers, John

Before my time I'm afraid, but I guess it has to have a limit and 9 was a reasonable limit to have when this was added many years ago.

Hi Bob, I'll take a look a bit later. One thing though, you seem to be using an add-on aircraft thats generating lots of PANEL_LIGHTS_OFF events. These are just noise in the log really, so you may want to add DontLogThese=66057 to the [General] section of your FSUIPC5.ini file (I'll remove them manually from the above). Cheers, John

Hi, all your assignments and controls are stored in your FSUIPC5.ini file (in your modules folder). Take a look at that file. The format of the entries is described in the FSUIPC5 manuals. Comments are added automatically so that you can see what your assignments are. If you are using the 'profiles in separate files' feature, then you will also have an ini file for each profile. If you are going to edit it, make sure you take a copy/backup first. Cheers, John

Yes it is a limitation, only 1-9, as indicated by the document: RunReady1=, RunReady2=, ... RunReady9=: These are identical to the RUN options above, except they are not actioned until WideClient is actually connected to WideServer. John

So you re-enabled controllers in FSX for this? Make sure controllers are disabled in FSX if you are assigning your axis in FSUIPC. To use the full functionality of these, you should look into using the SPAD (freeware - http://fstools.weebly.com/) or SPAD.next (payware - https://www.spadnext.com/home.html) drivers. I use the latter (with FSUIPC) and it works very well. Cheers, John

Hi Matthias, It will rescan your devices. Does it also start working when you click the switch in the VC after opening/closing FSUIPC? It does sound like an issue with your add-on LJ35. You could try logging non-axis events and button presses (from the FSUIPC logging tab). This may show if something different is being sent after the spoiler retract. Cheers, John

The controls are events provided by P3D, so you need to look into the P3D documentation (e.g. see 'SimConnect Name' column in https://www.prepar3d.com/SDKv4/sdk/references/variables/event_ids.html). The specific controls added by FSUIPC are documented in FSUIPC' documentation. For your magneto problem, can you try activating non-axis event logging as well as buttons and switches (from FSUIPC's logging tab), generate a log file going through the magneto positions up and down and show us the results. John

Hi Urs, your WideClient.ini file is not correct. There is no [Programs] section - thats for FSUIPC (or WideServer)! As Pete said, you want to be using RunReady, which takes the form RunReady1=.... and is located in the [User] section of your WideClient.ini (or the [WideServer] section in FSX). Please see the WideFS Technical guide. John