John Dowson

What version of FSUIPC5 and P3Dv4? If you posted your log & ini files, this will tell me. If you have nothing programmed in FSUIPC, then it won' be doing anything and I can't see how FSUIPC can have anything to do with your buttons not working. Is your version registered? Could you also please give more details on what your problem actually is - is it just the key assignments that are not working? Can you control with the mouse? How are the key assignments set-up? You could try logging 'Button and Key operations' to see if keypresses are being caught and forwarded to the sim, and maybe 'Events' to log any controls being sent when the you activate the buttons. John

What version of FSUIPC are you using? What version of P3D? What aircraft? Have you programmed FSUIPC to do anything? Could you please provide more information, and post your ini and log files. John

Hi Beck, that looks very weird...To be honest, I've no idea, but looks like a UI problem. Does this affect the functionality? It looks like your tick-box backgrounds are black for some reason, but I've no idea what could be causing this, very strange...What happens when you select? Do they turn white? Is this an FSUIPC problem only, or do you have issues with anything else? John

Is your lua script activated? You need to add it to the '[Auto]' section in your ini file, or program to activate on something. Please check the documentation. Cheers, John

Hi, it should be relatively straightforward to do this with a short Lua program. Check the lua documents and examples in your FSUIPC Documents folder. Basically you want to write a function that monitors the pmdg offsets (using event.offset) and in your function you can update the P3D offsets. Good luck! Cheers, John

No, sorry - only the latest version is made available (and supported). Any reason why your friend can't upgrade to 4.1 (or better still, 4.4)?

Yes, it should be in the module folder. Please check that you have set Explorer to show 'hidden' files. If you still can't see them, it may be due to this error in your install log: Attempt to set the ACL entries for Modules access permissions failed, error = 1332 To resolve this error, please see this post. Once resolved (access permissions corrected on modules folder), you should re-run the installer to verify that the error is no longer present. Alternatively, you can run P3D as administrator (and also set the exe to be always ran as administrator by write clicking and changing the file' properties). Cheers, John

Hi, are your separate ini files using profiles? If not, the first thing to do is to convert them to using profiles. Information on doing this profiles is provided on page 19 of the User Guide under 'For users already having Aircraft Specific settings'. Once you have both ini files converted to profiles, you can just copy across the profile specific sections from one ini file to the other. Cheers, John

Which version of P3D are you using? If its v4.x, then there are currently no friction facilities. For P3D v1-3 (and FSX, FSX-SE) there is a parameter called PatchSIM1friction, from the FSUIPC4 Advanced User guide: PatchSIM1friction=No: A is provided to assist with better ground friction and braking. This is enabled by a parameter added to the [General] section of the FSUIPC4.INI file, and applies to both registered and unregistered installations. It operates by patching values in FS's SIM1.DLL, and applies equally to FSX (RTM, SP1, SP2 or Acceleration), and Prepar3D version 1.4. Just add PatchSIM1friction=Yes to the [General] section of the INI. A number of ground friction and braking coefficients are changed. The values set are those currently derived by experiment by Johan Dees (please see the example Lua Frictions.lua for details of the changes -- more below). For registered users, there is more flexibility using plug-ins instead. In this case the parameter is not necessary. Full details can be found in the Lua Plugins package -- see, especialy, the two example Lua plug-ins "frictions.lua" and "DynamicFriction.lua". The provided lua examples also only work with FSUIPC4, as they also rely on the ipc.SetFriction function which is implemented in FSUIPC4 only. Cheers, John

Changing graphics cards/monitors should have no effect on FSUIPC, so your ini should be ok. Problems can arise for system updates/changes when joystick ids change, but these problems can be avoided by using the "Joy Letters" facility, or overcome by manually editing your ini file (or re-assigning joy ids in the registry). Cheers, John

What version of FSUIPC are you using? Which Flight Sim (FS)? Could you also post your ini file, one before you try to assign (or before you start the sim) and the one after you have done the changes. When you say " It is as if there is no INI file", what do you mean? Basically no ini file means no assignments. Is this a new FSUIPC installation? If so, maybe there were permission problems, so if this is the case then please also post you install log. Cheers, John

Sorry, but if you've lost your .ini file, you've lost your assignments and have to redo ;( Check that you don't have it somewhere though, should still be there after a graphics card update - or did you trash your FS installation (no version mentioned! Always helpful....) and re-install also? Or change your hard disk/ssd? Cheers, John

Its not in the FSUIPC ini file, its a P3D option, under Information -> Miscellaneous Text.

What do you mean by 'it doesn't save'? You have to add some assignments to a profile otherwise there is nothing to save. John

Hi Annick, once you unzip the FSUIPC5.zip file you will get the 'Install FSUIPC5151.exe' (+ an install document), which is the latest (released) version. Run the installer and that will copy the dll to the correct folder, as well as installing the documents and updating the dll.xml (so that FSUIPC is started with P3D). Cheers, John

I see you are also assigning in P3D as well as in FSUIPC. It is advised to disable controllers in P3D when assigning in FSUIPC, especially if you do your axis assignment in FSUIPC as P3D has a habit of automatically re-assigning if controllers are not disabled. John.

Hi, you need to look into using 'profiles'. Take a look at the section 'User profiles for all control settings' on p18 of the User Guide in your 'Modules/Documents' folder. For your use case, you can just override the button assignment with a profile specific one for the jet in question. Cheers, John

Hi Annick, your browser is probably caching the original link/download - try clearing your cache and downloading again. Cheers, John P.D. Its 'www.schiratti.com/dowson.html' not 'www.schiratti.com/dawson.html'!

Hi Annick, sorry about that - I accidentally uploaded the dll only to the link pointed to by the SimMarket / Schiratti site. This has now been corrected - please try again. Regards, John

The thread you posted advises you to "...Remove any throttle axis calibration in FSUIPC...", so why do you want to calibrate?

Hi Alvaro, FSUIPC4 is the version you use with FSX. For P3Dv4, you need FSUIPC5 which requires a separate license, available from SimMarket. All FSUIPC products can be downloaded from here. Regards, John

Hi Dane, copying across your old files should be fine (presuming you installed FSUIPC first), with some caveats. However, if FSUIPC is not recognising your devices, we need to see the files (log, ini and joyscan.csv) from your current installation, the one with the issue, not your old system. Cheers, John

Hi again Peter, I just tried again with adding 'SendKeyPresses=Yes' option to the WideClient.ini '[User]' section and this does work, sending key presses from the WideClient pc to the sim pc when WideClient has the input focus. KeySend is used in WideClient, but for receiving KeySends from the sim PC and directing these as key strokes to other programs on the WideClient pc. Regards, John

Hi Max, from what you say, it certainly sounds like you have faulty hardware or a faulty connection. You also say: By 'cursor' do you mean 'lever'? Still, I suspect that your hardware is faulty. FSUIPC receives the axis values from Windows, so I'm afraid if Windows is not seeing that lever, then there's nothing that can be done in FSUIPC to resolve this problem. FSUIPC will only recognise the first axis movement/value it receives. Having two axis values for one lever movement sounds very suspicious - either a hardware problem or a driver issue would be the culprit. Btw, have you installed any Saitek driver software? If so, please remove this and re-test. If not, I think you have a hardware (or Windows) problem. Cheers, John P.S. Don't forget to try without LINDA, and also please post your ini file.

Hi Max, the third lever should be the U axis, and the axis is given in the details for that device. As I said, I think you have a hardware or connection problem if the axis can't be seen. Anything device/axis thats seen by windows should be available in FSUIPC. Maybe try temporarily enabling controls in your sim to see if the sim can see it (but I doubt it!). I also see you are using LINDA - try without this to see if that makes a difference (e.g. rename your ipcReady.lua to ipcReady.disabled), but again I doubt this will do anything either but quick and worth a try. Is this a new device? Have you ever been able to use/assign to this axis? Are you also using a VRInsight device? This error indicates that its either not connected or on the wrong com port: VRI port 1 "com0" failed to open Maybe you could also post your joyscan.csv file, also located in the Modules folder. Cheers, John