John Dowson

Hi Sunny, your GUIDs may change again with an OS re-install. After you re-install, use your original ini and start P3D, load an aircraft on a runway (to initialise FSUIPC), then exit. Then check your log an ini files - if your device GUIDs have changed, simply replace the new GUIDs for each device in your original ini. If you have any difficulties/issues, attach your log & ini files here and I'll take a look. Cheers, John

Hi Scott, Pete has retired from FSUIPC development, although he is still active on the support forum. I've taken over development of FSUIPC5 since the beginning of the year (I'm Pete's son). I'll discuss this with Pete and have a think about it, but as Pete mentioned it looks like it could be quite a complicated/involved update. For your example though, a standard way of handling this using one rotary is with a lua script, which would time the requests and send different controls depending upon the delta between them, allowing you to rotate slowly for fine control and faster for course control. Cheers, John

Did you manage to get any values for "L:Eng1_ThrottleLever,number"? Check out this post for monitoring specific lvars: John

Hi Urs, is there a way to launch WideFS, which resides on a client PC, via FSUIPC on the main PC? No, this is not possible. Unfortunately, when WideFS starts at Windows startup, the program does not start what I want when launching WideFS. Do you mean that WideFS is not starting external programs correctly when it is automatically started at Windows startup? Does it work ok when you start WideFS manually? You could try adding Log=Debugallto the [user] section of your WideClient.ini (or add the [user] section if not already there), then let WideFS autostart (and exhibit your problem), and then post your log file. Cheers, John

Sorry, FSUIPC4 is now closed for future development. Cheers, John

Hi Alhard, here's a minor update to remove that 'quirk' mentioned above - now the permanent ignores (from the IgnoreThese ini parameter) are maintained in a separate list from the temporary ones from the 'Ignore' button. Cheers, John P.S. Its 'Dowson' not 'Dawson'! FSUIPC5.dll

FSUIPC5 works with P3Dv4, you don't need anything else if you have one PC. WideFS works with all versions of FSUIPC, and allows connection to FSUIPC from slave/secondary PCs. What you need to buy depends on your set-up and what you want to achieve really... Cheers, John

Hi Alhard, please try the attached version (5.152a). It will accept the IgnoreThese ini parameter in the [Axes] section using he same format as the one in the buttons section, except that you specify the axis letter after the '.'. Note that there is one 'quirk' in the way I have implemented, in that if you clear or change this parameter when FSUIPC/P3D is running, and you reload the assignments, the initial axes you ignored will still be present and so still ignored. To clear this completely, you need push 'Clr Ignores' button. Please try this and let me know how it goes. Regards, John FSUIPC5.dll

*** Moved from Download Links - please post support requests in the Support forum *** All sales are handled by SimMarket - please contact them directly. If you have a WideFS license, that will work with FSUIPC4 and FSUIPC5.

Please see section 'Changing or removing Profile assignments' in the User Guide (page 22). John

No problem - I'm glad that its now working for you.

0x654c is a 4-byte float32, so you need to use ipc.readFLT and not ipc.readSD. Presumably you have enabled these offsets as described in the offset mapping document for the PMDG 777X? That document also contains the size and type of each offset, which will help you to determine which ipc.read function to use. John

Hi, you can log the COM data by adding these lines to the [General] section of your FSUIPC5.ini file: Debug=Please LogExtras=x40 The data will be in hexadecimal of the ASCII byte values. John

Then thats an lvar! You will need to log that with a lua script. There is one provided (called 'log lvars.lua') that will log ALL lvars for you. You can try that, or as you know the lvar name, should be pretty straightforward to write a short script to read the value (using 'ipc.readLvar') and then logging the value returned. John

Please try the following: FSUIPC5.ini

As Pete says, I'll take a look at this later this week, and I'll post an updated version here for you to test. John

Could you attach your original/backup ini file please. If its too big, you can try zipping/compressing.

Hi Sunny, please post/attach your latest FSUIPC log and ini files, and also your joyscan.csv files (all in your Modules folder), and I'll let you know how to update... John

there is nothing in the log as you need to select 'Normal log file'. Please check that option. 3AE8 is also a float64 (FLT64), and 3A28 also as a float64 only. I don't know why its not updating the 088c value though in the FS/simconnect display window. Could you maybe try also with a default aircraft? John

You can just use the 'Export' facility from regedit....

I assumed it was a typo! So the key is correct but the value wrong. Change it from 'F:' to 'F:\P3Dv4\'.

I have correct registry entries for P3Dv4.5HF1.....no point showing you my value though, as I have it installed in a different place....

Oh - you may want to make a copy of your key and ini files from your old Modules directory (if you have them), and drop them into the new one once FSUIPC5 is installed, or just rename your f:\Modules folder (rather than delete) so that you still have access to them, if needed.

You could try editing your registry. Make sure you take a back-up first. Then: Ignore this. Presume 'StuPath' is an error? Anyway, change so that you have SetupPath set to 'F:\P3Dv4\' Thats ok. You will also need to remove and re-install FSUIPC. To do this, remove the FSUIPC5 entry at HKEY_LOCAL_MACHINE\SOFTWARE\FSUIPC5, and manually delete the F:\Modules folder. If you then re-run the FSUIPC5 installer, it should hopefully find your P3D installation and install in the correct place, as well as correcting your dll.xml file. Alternatively, maybe uninstalling and then re-installing the P3Dv4 client may correct your registry for you, but I'm not sure on this. Let me know if you have any issues. John

Yes, as Pete said, there is something strange in your installation. However, as you selected the P3Dv4 directory when you installed FSUIPC5, this is the directory that should have been used, so there is also an issue in the FSUIPC5 installer that I will look into. As the original problem is your P3Dv4 installation, it would be better going forward for you first to correct that, then you can re-run the FSUIPC installer to install to the correct place. I will be releasing a new version later this week (5.152), so I'll correct this installer problem before I release. John