John Dowson

What further documentation do you expect? It is just what it says, an offset area of size 64 bytes starting at offset 66C0 that is free for general use. You can write/read any values you want/need in that offset range.

This should now be corrected in v6.0.6, just released.

That is a very old version of FSUIPC4 you are using. The latest is 4.974 - first please download and try this version, available from the Download Links -> Updated Modules section, or over on www.fsuipc.com. If you still have issues after this, suggest you first check the forums for similar issues (there are many posts regarding start-up issues with FSX!), and only if you cannot find a solution in a previous post, then post again and include your .log file and further information - just saying 'I am not able to run FSUIPC4' doesn't give us any information to enable us to help you. John

Confirmed. The next pointer is not being initialised correctly on re-start. I will fix this in the next patch release.

No, not possible at the moment, sorry. John

Hi Philippe, we are currently very busy looking into trying to provide an FSUIPC version for the upcoming MSFS, and investigation into minor issues with offsets is on hold for the time being. I have flagged this and will look into it when time permits. John

Yes, you can do that. You could also check the DLL.xml file and remove the entry for FSUIPC5 to remove it completely, as well as the FSUIPC Documents folder.

Hi Cesar, for Project Magenta, you really need to contact their support. For setting/changing bits in a byte offset in FSUIPC, see the controls 'Offset Byte Setbits' and 'Offset Byte Togglebits'. Cheers, John P.S. You posted in the FAQ sub-forum. Please post requests in the main support forum - I have moved your post this time.

Sorry, I guess your problem is fixed! Maybe better to have added that after your support request, or as a separate comment. I still recommend that you update though!

First, could you download and install the latest version of FSUIPC6, v6.0.5. Once done, please attach your new log together with your ini file - Joyscan.csv is not needed. Thanks, John P.S. If using the dll.xml install method, there was a problem in the uninstaller generated by the installer in previous versions, which had the affect of leaving multiple FSUIPC6 entries in the DLL.xml file. If you are using this install method, best to check this file after install and remove any duplicate entries.

Hi David, you may get more help if you include the lua file that you are using so that folks can take a look. Im afraid that we're (i.e. me and Pete) far too busy at the moment to look into helping people with issues like this at the moment, sorry, but if you attach your lua someone else may be able to help. Cheers, John

It is recommended to install FSUIPC6 outside of the add-on.xml folder. You can even select your old Modules folder if thats where you want to keep everything, and you wouldn't have to change anything, except for renaming your FSUIPC5.ini file to FSUIPC6.ini. Please see the Installation and Registration guide.

First, you posted in the announcements sub-forum. Please post all support requests in the main forum - I have moved your post for you. As you were in the Announcements forum, did you not see this post:

Me too! Seems to be a problem with the version numbers in the previous build, but they look ok to me. I'll investigate sometime but this will be low priority - got a lot of things on at the moment! Cheers, John

Yes, very strange. Sorry about that - I will look into it. For the time being, you can manually delete the existing FSUIPC5.DLL (from your Modules folder) and then re-run the installer. John

I'll ask Pete to take a look. I'm not too familiar with FSUIPC3. May take a few days though.

Hi Matt, sorry, just checked you inis. They are empty apart from one assignment. Plugging and unplugging devices can change joystick ids. To get over this problem, there is a facility called 'JoyLetters',. See the user guide. Try the following: - remove your single button assignment (you can add this back later via the UI): 1=R0,0,K65,8 - enable JoyLetters by changing the AutoAssignLetters in the [JoyNames] section to: AutoAssignLetters=Yes Then restart the sim and try assigning again. John P.S. That won't solve the missing Yoke - will need to see the files mentioned in my previous post.

Hi Matt, could you also post your .log files for when all devices are connected, and also your Joyscan.csv file. Cheers, John

Request a refund from SimMarket. I'm sure Pete will authorise a refund for you.

WideFS6 does not work with FSUIPC6. You need WideFS7. Did you not read the REQUIREMENTS section for WideFS6: REQUIREMENTS FS2000 FS2002 FS2004 FSUIPC3 Note: If both WideFS6 and FSUIPC3 are registered, both registrations must use the same user name. WideFS6 IS NOT FOR FSX NO REFUNDS GIVEN!

Yes. Please see the installation and registration guide for FSUIPC6. It contains details of options for using P3Dv4/v5 together with FSUIPC6 (in one or two distinct installations) and how to migrate your FSUIPC5 settings. Licenses are available from SimMarket. For FSUIPC5 license holders, there is a substantial reduction (given automatically on check-out) or free if FSUIPC5 was recently purchased. Please see the following post (in Announcements sub-forum): Cheers, John

First, you posted in a sub-forum. Please always post support requests in the main support forum, not a sub-forum. WideFS is not compatible (or incompatible) with any aircraft - the question is redundant. WideFS7 is compatible with FSUIPC6. WideFS is used to allow programs that connect to FSUIPC to do this over a network, on a client PC. Please see the documentation.

First, you posted in the wrong place - please post all support requests here in the main support forum. You posted in the 'User Contributions' sub-forum. I have moved your post for you. Also please always give a relevant title - 'FSUIPC Modules' doesn't reflect your problem. I have also updated this for you. I see Pete has just replied... Also note that there is also a recent post with a similar problem (although using a different version of FSUIPC): To resolve your problem, you will need to follow the same steps to determine what is causing your issue.

There have been minimal changes in recent releases (check the changes/history log), and certainly none that have anything to do with your problem. No, not possible, sorry. Just check www.fsuipc.com every now and then, or at least before posting for support so that you know you are on the latest release. FYI, 6.0.5 was released yesterday. There have been a few patch releases recently to sort out some teething problems with FSUIPC6, but hopefully this will be the last release for a while - we have other things we need to start looking into 😉 !

Yes - FSUIPC4 and FSUIPC5 licenses are not valid for FSUIPC6. There is a special upgrade price for FSUIPC6 from FSUIPC5, but not for FSUIPC4.