Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,765
  • Joined

  • Last visited

  • Days Won

    288

Posts posted by John Dowson

  1. To assign to presets, check the Select for Preset checkbox in the top-right of the Buttons & Switches Assignments dialog box. You can then click the Find Preset... button to find the relevant preset, ordered by provider, aircraft, subsystem etc. A more complete search interface can also be found at https://hubhop.mobiflight.com/presets/.

    Please also take time to read the User and Advanced User manuals. You will find more details on using presets (as well as lvars, etc) in the WASM section of the Advanced User guide.

    When I get time, I will make a FAQ entry on how to determine what to assign to using FSUIPC's logging facilities as I am continually explaining how to do this. For the time being, try using the support forums as such questions on assignments have been asked many times before.

    Let me know how it goes and if you have any further issues.

    John

  2. Please use the FSUIPC7 sub-forum for all issues/questions regarding FSUIPC7. I have moved your post.

    Many of the standard controls do not work for add-ons (or even some Asobo aircraft), especially complex ones, and you have to investigate other methods, such as lvars, custom controls, input events or presets.

    For the FSLabs lights, try presets:

    image.png.41a079c5f3ef1121d1a0a334ddab8e88.png

    As you see in that image, there is a Beacon ON and Beacon OFF preset you can use.

    In general, if standard controls don't work, check for a preset. If there is no preset, use FSUIPC's logging facility to determine what is being used. For The FSLabs, many buttons/switches can be controlled using custom control, via the standard FS control Rotor Brake, where the parameter indicates the switch. For example, see the following post where I explained how to do this for the APU Master switch in the FSLabs: 

     

    John

     

     

  3. I don't know why you pasted both your log and ini in your last post - I have removed them. They did not add anything new. I was just reminding you to exit FSUIPC7 before showing me files and did not need to see the same one again. And if a file is more than 10 or 20 lines, please attach it rather than pasting it - and this does not mean that I want you to attach them now. Only attach if you have followed my instructions and it is still not working.

    As for your issue, please re-read my last comments and report back, As I said, try starting FSUIPC7 after MSFS has started and arrived at the main menu, or use the auto-start feature. And if you get the same connection issues, read that FAQ entry and manually configure the initial connection parameters - and read the section on auto-tuning of start-up parameters in the Advanced User guide.

    John

  4. As I said, can you please exit FSUIPC7 before attaching log (and ini) files.

    But your log shows that FSUIPC7 couldn't establish a connection to MSFS.

    First, you started MSFS manually, and it looks like you did this before MSFS was running. If starting manually, you should start FSUIPC7 after starting MSFS, and one MSFS has arrived at the main menu. However, it is far better to use the auto-start feature so that FSUIPC7 is started by MSFS when ready. To use auto-start, please re-install and leave the selected components (to install) as they are.

    For details on tuning the start-up parameters for preventing connection issues, see the following FAQ entry.:  

    Note that once you have configured the DetectToConnectDelay DetectToConnectDelayAuto parameters correctly, you can also set the InitialStallTime parameter to 0 which will then instruct FSUIPC7 to wait indefinitely for a response to the connection request.

    Also see the section Auto-tuning of initial start-up ini parameters on page 11 of the Advanced User guide.

    John

  5. 2 hours ago, electricclay2000 said:

    I notice that the Aivlasoft  EFB v2 Client moving map doesn't move anymore ,after I added the    Init3308=13    to the FSUIPC7 .ini file.

    Is FSUIPC7 actually connect to MSFS? Maybe you can show me / attach your FSUIPC7.log file (from a session when you get this error, and please exit FSUIPC7 before attaching the file).

    If FSUIPC7 is connecting to MSFS and there are no error in your log, you need to contact Aivlasoft about this issye - I only support FSUIPC and not third party clients.

    John

  6. 18 hours ago, Braudoux said:

    I have double-checked the assignments within P3Dv4.5 and removed all default assignments...

    It is better to disable  controllers completely if assigning in FSUIPC, as P3D has a habit of re-assigning controllers which can cause issues.

    18 hours ago, Braudoux said:

    While attempting to calibrate the throttles, I noticed that the curve for each is working half way only, and not all along the curve (See screens). Consequently, if my controller's levers are on idle and I move them forward, the first half is not generating any action and the levers in the cockpit start moving when I reach the second half, which gives me a very short range to manage the power. 

    This is nothing to do with the curve, it is due to your calibration.. The minimum value calibrated is 4534 for throttle 1, and 3272 for throttle 2. Axis ranges usually go from -16384 to +16383, so you are losing more than half your axis range. Calibrate the minimum value correctly.

    The reason you only see the right-hand part of the slope is explained in the User guide:

    Quote

    For axes with no centres you only get to right-hand part of the slope, but the same variety is available. For axes with “off-centred” centres, such as the separate throttles with a small reverse zone below an off-centred idle position, the left hand part is kept linear in order to be sure that the very extreme left position can be reached. The slope changes apply only to the right-hand or positive part of the lever movement.

    Also, for future reference, please always attach your FSUIPC ini file when you have any issues with assignments - this tells me a lot more than images do (including which version of FSUIPC you are using, which you didn't mention!).

    John

  7. 1 hour ago, Pitter said:

    I will do as you suggested, and if it not work  -which I don´t think-  I will come back to you.

    As you have no assignments in FSUIPC that could cause such behavior, it mut be coming from somewhere else.
    First, just disable controllers in P3D and see if you get the same behavior - if not, the issue is with your P3D assignments. If you do get the same behavior, please show me another log file bit with logging for Buttons & Keys as well as Events (non-axis controls) activated.

    John

  8. 3 hours ago, Hollis said:

    I re-entered the license number and now it's working fine again. 

    Ok, but that is strange - you shouldn't need to re-enter or re-register your license on an update (unless you have changed your installation folder).
    When you update, the license page of the installer should be pre-populated (from your FSUIPC7.key file), and you should just skip the registration.

    John

  9. You have controllers set to ON in P3D:

    Quote

          265 Controllers are set to ON, using RawInput within P3D

    Either disable controllers in P3D, or check your assignments in P3D and remove those that are not needed. P3D has a habit of re-assigning controllers if not disabled.
    Better to disable controllers in P3D and assign everything in FSUIPC. If you must have assignments in P3D, then be aware that it can re-assign and give unwanted behavior.

    John

  10. 21 minutes ago, Hollis said:

    I just installed the new version of FSUIPC7 (7.5.4) and the options to change buttons and axes is not showing up on the menu, or when I right click from the system tray.

    This probably ,means that you are using an unregistered version, i.e. there is no license/key file (FSUIPC7.key) in your installation folder.

    Did you install into a different folder? When you re-installed. were your previous key details shown on the last screen, and did you skip key validation?

    Installation does not touch your FSUIPC7.key file, unless you opt to re-validate.

    John

  11. 1 minute ago, cteixeira said:

    The folder exist, what I don’t know is, if it existed before FSUIPC install.

    I don't think FSUIPC will create this folder, but not 100% sure.

    The FSUIPC installer reads the InstalledPackagesPath entry/line, then removes the first 23 characters (i.e. the characters 'InstalledPackagesPath "', then removes the last two characters, which should be the closing quotes and the new line character. Maybe there is no new line after your InstalledPackagesPath entry? If not, then the last character of the path will be removed.
    So, check there is a new line after the 
    InstalledPackagesPath entry.

    This is obviously not ideal - I will correct the installer for the next release to actually check for the new line and only remove if present.

    Let me know what your entry looks like when you get a chance.

    Regards,

    John

  12. Here's the analysis from Microsoft:

     

    Analyst comments:

    At this time, the submitted files do not meet our criteria for malware or potentially unwanted applications. The detection has been removed. Please follow the steps below to clear cached detections and obtain the latest malware definitions.
    1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender
    2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”
    3. Run "MpCmdRun.exe -SignatureUpdate"

    Alternatively, the latest definition is available for download here: https://docs.microsoft.com/microsoft-365/security/defender-endpoint/manage-updates-baselines-microsoft-defender-antivirus

    Thank you for contacting Microsoft.

    This was from yesterday. Should be ok with the latest virus definition update.

    John

  13. You can just remove/delete that line. This is the only place that FSUIPC stores that information - if it re-appeared, FSUIPC must still have been running when you removed it - I can't see how else it could have re-appeared.
    Only edit the LuaFiles section when FSUIPC is not running.

    John

  14. Here's the analysis from Microsoft:

    Quote

    Analyst comments:

    At this time, the submitted files do not meet our criteria for malware or potentially unwanted applications. The detection has been removed. Please follow the steps below to clear cached detections and obtain the latest malware definitions.
    1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender
    2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”
    3. Run "MpCmdRun.exe -SignatureUpdate"

    Alternatively, the latest definition is available for download here: https://docs.microsoft.com/microsoft-365/security/defender-endpoint/manage-updates-baselines-microsoft-defender-antivirus

    Thank you for contacting Microsoft.

    Click here for more information

     

     

    John

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.