John Dowson

Hi Gil, no problem, glad you found the issue. Rather than clearing out p3d settings, its better to just disable controllers in P3D. Otherwise you may find that P3D will automatically re-assign (usually when it thinks its found a new axis). Cheers, John

Hi Gil, I'm not sure I understand your problem. Button 7 on the Saitek flight yoke is spring loaded (no?) and sends a button press when pushed to the right and a release event when released. You have programmed the gear toggle for the press only, so the press will activate the control and the release does nothing. So, each time you activate it it will toggle between gear up/down on the button press and do nothing on the release. I therefore don't understand what you mean by 'and lowers the ger when it is released'. Maybe you can activate 'Button and key operations' and 'Events (from non-axis controls) in the logging tab so that you can see what is actually being sent on both the press and release. If FSUIPC isn't sending anything on the release, check you don't have controllers enabled in P3D. Please post your log + ini file once generated and I'll take a look. Btw, is this with a default aircraft or an add-on? If an add-on, please try with a default aircraft first. Cheers, John

No problem. You can always check if you have a registration key by going to your SimMarket account. Cheers, John

No, version 4 has never worked with P3Dv4. P3Dv4 and FSUIPC5 are 64-bit, whereas FSUIPC4 and P3Dv3 32-bit.

If your key is for FSUIPC5, then it should work. FSUIPC5 is a different product to FSUIPC4 and requires a separate key. If your key is for FSUIPC5, please make sure the details are exactly the same as in your registration email that you received from SimMarket. Cheers, John

Also FSUIPC only scans one folder for lua plugins, which by default (unless 'LuaPath' is specified) is the Prepar3D v4\Modules folder (or the location of your FSUIPC5.dll), not the Prepar3D v4\Scripts folder. John

No, sorry, there is no such facility.

You can have multiple actions in one macro by editing the macro file - see the section 'Multiple actions in one macro control' in the Advanced user manual, page 37. Cheers, John

Yes - best to disable controllers completely in P3D if assigning in FSUIPC otherwise it has a tendency to re-assign. John

Your [Auto] entry should be 1=Lua Belts John

Could you post you log and ini files please.

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