Jump to content
The simFlight Network Forums

John Dowson

Members
 View Profile  See their activity

  • Posts

    11,076

  • Joined

  • Last visited

  • Days Won

    219

 Content Type 

Posts posted by John Dowson

  1. Cockspur C510 assignments too complicated

    in FSUIPC7 MSFS

    Posted

    17 hours ago, DaveSCUSA said:

    Developers should provide a list of simconnect events or at least add their aircraft to MobiFlight or SPAD.neXt.

    Well, they should provide information on how to control the aircraft, whether this be standard events, lvars/hvars or input events. However, it is not difficult to detemine how any switch works, by either using FSUIPC logging (which will log events and input events. when selected) or using the facilities provided by MSFS (devel functionality, mainly behaviors console).
    I wouldn't expect developers to provide presets or Spad.Next snippets. These are both community-driven efforts. And as the C510 seems to mainly use Input Events, you cannot use presets/calculator code for most functions of this aircraft.

    And you must see the difficulty here. Your Alpha/Bravo controllers are nothing like the actual instruments in the C510, and so some mapping is necessary, and people will want to map these controls differently. For example, the Alpha uses a magneto to start the aircraft (i.e. it is for GS aircraft). There is no sensible mapping of this to engine L/R start buttons - you have to decide how you want to do this. But once you have decoded which controls/buttons to use. it should be relatively straightforward to implement/assign. I got these working using my saitek X55 controllers within a few minutes, assigned to the appropriate Input Events.

    I will look into assigning these on my alpha/bravo. What would you like to use, for example, for the engine start buttons on the alpha/bravo? 

  2. FSUIPC needs VC140 runtime.dll

    in FSUIPC7 MSFS

    Posted

    First, you posted in the wrong sub-forum - I have moved your post to the correct place, the sub-forum for FSUIPC7.

    17 minutes ago, Joop Verboom said:

    I cannot use FSUIPC 7 because a get the message: VCruntime. dll not find on this PC. How to solve this?

    This issue is documented in the README.txt file that comes in the zip file you downloaded (as well as in many other support requests in this forum):

    Quote

    Problems running FSUIPC7
    ========================
    1. If you receive the following error when running FSUIPC7:
            The code execution cannot proceed because VCRUNTIME140_1.dll was not found. Reinstalling the program may fix this problem.
       then you need to uninstall the 2015, 2017, 2019 & 2022 VC++ redistributables from the Windows App management panel (any/all that are installed),
       and then install the latest combined redistributable packages (both the x86 and x64 versions recommended, although FSUIPC7 only requires the x64 version)
       from here:
           https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist
    ...

    John

  3. Cockspur C510 assignments too complicated

    in FSUIPC7 MSFS

    Posted

    2 hours ago, kaha said:

    I have the Cockspur A22, battery and alternator switches are not working with standard assignments. But it has input events for it, named "ELECTRICAL_Battery_1" and "ELECTRICAL_Alternator_1". Maybe the C510 also has it?

    The C510 does have these input events, although I think the standard controls might also work, or at least some. Will take a look when I have time, but also need to familiarise myself with the start-up procedure first.

  4. Honeycomb Bravo issues

    in FSUIPC7 MSFS

    Posted

    You may as well aslo remove these entries if you no longer use these devices:

    Quote

    [JoyNames]
    ...
    B=Flight Throttle Quadrant
    B.GUID={C8C09580-948F-11EA-8001-444553540000}
    ...
    E=Logitech G HUB G29 Driving Force Racing Wheel USB
    E.GUID={A3B6B5D0-539B-11ED-8006-444553540000}

    John

  5. Honeycomb Bravo issues

    in FSUIPC7 MSFS

    Posted

    Note that you have no general assignments and you are not using substrings for your profiles. Therefore if you load an aircraft that does not exactly match a profile entry, you will have no assignments in FSUIPC7.

    Revise your profile strings - they all look a bit strange. For example, change this:

    Quote

    [Profile.BAE 146]
    1=Just Flight 146-200 WAT
    2=Just Flight 146-100 WAT
    3=Just Flight 146-300 WAT

    to this:

    Quote

    [Profile.BAE 146]
    1=Just Flight 146

    and this:

    Quote

    [Profile.B737]
    1=PMDG 737-700 WAT-BW
    2=PMDG 737-800 WAT-BW

    to this:

    Quote

    [Profile.B737]
    1=PMDG 737

    etc. Do this for all your profile aircraft, i.e. use substrings to match all variants.

     

  6. Honeycomb Bravo issues

    in FSUIPC7 MSFS

    Posted

    Just now, voltigeurramon said:

    That's my bad, I thought I selected this one. Is there a way to reverse this axis as the Bravo axis is apperently reversed (but of course that's not done by FSUIPC)

    You can reverse in the calibration page.

    1 minute ago, voltigeurramon said:

    I attached the ini file (forgot about that, sorry). Thanks for your help!

    But what am I looking at? You have reported so many issues.

    Lets do one issue at a time please. Load an aircraft you are having issues with. Activate appropriate logging for your issue (i.e. if it is with an axis, activate logging for an axis). Then reproduce your issue, exit FSUIPC7 and then attach both your FSUIPC7.ini and FSUIPC7.log files and I will take a look.

  7. Honeycomb Bravo issues

    in FSUIPC7 MSFS

    Posted

    47 minutes ago, voltigeurramon said:

    I got different issues with each aircraft since switching from the Saitek throttle quadrant to the honeycomb Bravo. Is this a FSUIPC thing?

    This is not a 'FSUIPC thing'...

    An axis is just an axis, it depends how it is configured. Configuring an axis for throttle on the Bravo is EXACTLY the same as configuring an axis on a saitek device. There is no difference as far as FSUIPC is concerned, it is just another axis on a controller. So it all depends on how it is configured.

    Did you re-configure you assignments for the Bravo? Did you disable the bravo in MSFS, or at least remove the default assignments?

    52 minutes ago, voltigeurramon said:

    Aerosoft CRJ:

    The CRJ doesn't like the FSUIPC throttle axis controls for some reason, so I have to use the sim for that. With the Saitek I used "send directly to FS". That doesn't work anymore with the Bravo.

    You are assigning to the wrong controls. For the CRJ, you need to assign to the _EX1 controls (i.e. THROTTLE1_AXIS_SET_EX1 & THROTTLE2_AXIS_SET_EX1, or THROTTLE_AXIS_SET_EX1).
    If your throttle was working on your saitek controller, then you must have been using this axis control.

    For each aircraft. you need to check how your axes were assigned with the Saitek and then redo your assignments with the bravo. I don't understand how you would expect it to work without doing this. Please do this.,

    Any further issues, please at least attach your FSUIPC7.ini file so that I can see your assignments.

    John

     

     

  9. LUA globals and event monitor question

    in FSUIPC7 MSFS

    Posted

    4 minutes ago, jr2mey said:

    For LUA globals, I am not seeing event monitor for changes in globals to perform an assigned function.

    There is no event function associated to lua globals.

    5 minutes ago, jr2mey said:

    For LUA globals, I am not seeing event monitor for changes in globals to perform an assigned function.

    I know that i can use ipc.get(global) and do successfully change its value across a network.

    But what I would like to do is execute either a macro or lua script function, based on a change in global value, without having to use a polling timer. Or am I being completely dense here.

    No, you would have to use polling to do this - maybe on a timer, and use this to determine if the lua global variable value changes and then call your function. Otherwise, to use an event callback, you would have to use a free offset, i.e. write the lua variable value to a free FSUIPC offset in the server and monitor that offset in the client with event.offset.

    John

  10. LUA globals and event monitor question

    in FSUIPC7 MSFS

    Posted

    1 hour ago, jr2mey said:

    I am curious to know if it's possible to use the IPC.SET() to create a global on a client computer and have it read on the server computer to initiate a macro or lua script without having to use a polling timer.

    Please see the FSUIPC Lua Library document - the ipc.set finction is documented as follows:

    Quote

    Stores a Lua value (any simple type -- i.e. numbers, strings, booleans) as a Global with the given name. This can be retrieved by this or any other Lua plug-in by using “ipc.get”. This mechanism provides a way for a Lua plug-in to pass values on to successive iterations of itself, or provide and retrieve values from other Lua plug-ins.

    With effect from FSUIPC version 4.958, in combination with WideClient version 6.999z2, the ‘Globalness’ of these values extends between Clients and Server in a WideFS network, so can be used to communicate values and strings over the network without resorting to user offsets. This only works if Server and Clients are in the same workgroup.

    Use of this should be sparing – the Windows Mailslot system is used and may not cope with excessive use very well. Also note that there is no backlog – the globals are only broadcast when being set (by ipc.set), so anything set before a client is actually running won’t be seen by it. Also the Network protocol used is not checked – messages are not guaranteed to arrive. Retries, maybe by a system of Acknowledgement values, are up to the plug-in and would be advisable in any “mission-critical” application of this facility.

    Note that there are limits on the sizes for network Globalness: the variable names must not be greater than 32 characters, and string values should be no longer than 384 characters. Values outside these limits do not participate.

     

    1 hour ago, jr2mey said:

    Looking over the event lua library, I am not seeing one that I can use to monitor globals or any changes to them.

    Given the above, why not?

    John

  11. Cockspur C510 assignments too complicated

    in FSUIPC7 MSFS

    Posted

    7 hours ago, DaveSCUSA said:

    Do you use the Alpha and Bravo with your C510. If so, could you show a few entries that work?

    I have the Alpha and Bravo on my flight system, but I don't have the C510 installed there yet - and haven't used this system for quite a while now and everything will need updating.
    I also don't fly this aircraft - I purchased to help others out with assignments as it is quite different from most other aircraft.

    7 hours ago, DaveSCUSA said:

    Specifically, when I turn my Alpha battery switch on - cockpit remains dark. Turn the battery on via Air manager, turns on. AVN PWR doesn't turn on with the Alpha, works with Air Manager. Also, no joy with the Alternators.

    Ok, I can look into the assignments needed for the batteries and the alternator.

    7 hours ago, DaveSCUSA said:

    Please can you give me some examples from your setup to help me thru this.

    As I said, I don't currently have this fully configured - only a couple of assignments on my development system. However, I will take a look and get back to you.

    Looking at your ini, these assignments are wrong:

    Quote

    22=PF,137,PC510_Pitot_Switch_On,0        -{Pitot_Switch_On}-
    23=PF,138,PC510_Pitot_Switch_Off,0    -{Pitot_Switch_Off}-

    and should be:

    Quote

    22=PF,137,CPC510_Pitot_Switch_On,0        -{Pitot_Switch_On}-
    23=PF,138,CPC510_Pitot_Switch_Off,0    -{Pitot_Switch_Off}-

    Did you manually change this?

    John

  14. Programming TFDi MD-11 Event ID's

    in FSUIPC7 MSFS

    Posted

    30 minutes ago, xkoote said:

    The event between 32906 and 33422 is a successful programming and implementation of selecting a button in the cockpit. (SD ENG page). The events between 37812 and 38047 show how even though I programmed the button exactly the same way as the previous one. It does not work.

    What event/control numbers are those? Third-party events start at number 69632, and the first/lowest custom event number shown in that web page is this one:
        EVT_MD11_PED_CPT_RADIO_PNL_XFER_BT_LEFT_BUTTON_DOWN            69644
    i.e. event 69664.

    If you look at the log file you posted, you will see this:

    Quote

         4140 Mapping custom control numbers 69632 - 84232

    So this is the range you can use for third-party events (also known as custom controls). Looks like the TFI Design MD-11 uses third-party control numbers from 69644 to 96323, so you currently won't be able to use those above 84232. This is currently a hard-coded maximum. For the next release I will add an additional ini parameter so that the max custom control/event number can be specified. I will release the next version shortly after SU15 is released, which should be any day now. Once I have made this change, I will also post details in this topic and can maybe supply you a beta version to test (if not released yet).

    Your log file shows errors when using custom events above 84232:

    Quote

        37812 Button changed: bRef=0, Joy=2 (L), Btn=11, Pressed
        37812 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 70=PL,11,C86094,0
        37812 FS Control Sent: Ctrl=86094, Param=0  <86094>
        37812 Exception 1 "ERROR", Ref 19655, Index param 2 on TransmitClientEvent, object=1, id=86094 (????), data=0
        38031 Button changed: bRef=0, Joy=2 (L), Btn=11, Released
        38031 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 71=UL,11,C86095,0
        38031 FS Control Sent: Ctrl=86095, Param=0  <86095>
        38047 Exception 1 "ERROR", Ref 19656, Index param 2 on TransmitClientEvent, object=1, id=86095 (????), data=0

    These other errors in your log file:

    Quote

         5109 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 17=PJ,31,CPMD11 AutoBrake OFF,0
         5109  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '1 (>L:md11_ctr_autobrake_sw,number)'
         5109 Button changed: bRef=0, Joy=1 (J), Btn=16, Pressed
         5109 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 31=PJ,16,CPMD11 No Smoking AUTO,0
         5109  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '1 (>L:md11_ovhd_lts_no_smoke_sw,number)'
         5109 Button changed: bRef=0, Joy=1 (J), Btn=18, Pressed
         5109 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 32=PJ,18,CPMD11 Seatbelt AUTO,0
         5109  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '1 (>L:md11_ovhd_lts_seat_belts_sw,number)'
         5109 Button changed: bRef=0, Joy=1 (J), Btn=24, Pressed
         5109 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 34=PJ,24,CPMD11 Landing Light Left OFF,0
         5109  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '0 (>L:md11_ovhd_lts_ldg_l_sw,number)'
         5109 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 35=PJ,24,CPMD11 Landing Light Right OFF,0
         5109  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '0 (>L:md11_ovhd_lts_ldg_r_sw,number)'
         5109 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 36=PJ,24,CPMD11 Taxi Light OFF,0
         5109  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '0 (>L:md11_ovhd_lts_nose_sw,number)'
    ...etc

    are because you are trying to use  buttons assigned to presets before everything is loaded. You cannot use presets/lvars/hvars until the WAPI has established a connection and the initial set of lvars have been received, which is logged here:

    Quote

        12047 -------------------- Starting everything now ----------------------
        12047 Starting WideServer now ...
        12047 Starting WAPI....
        12047   [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 1.0.4 (WASM version 1.0.3) using connection -1
        12047   [INFO]: Connected to MSFS
        12109 Lvars received: 1584 L:vars & 0 H:vars now available

    So you need to wait a short while (an additional 7 seconds or so) after the aircraft is loaded before you try and operate it via FSUIPC7 assignments to presets.

    John

  15. Phantom Xbox Controllers on Startup

    in FSUIPC7 MSFS

    Posted

    I have added a new ini parameter that goes in the [JoyNames] section that will allow you to ignore a device, which hopefully should help with this issue.
    I have attached a beta release below if you could try it. To use this to ignore the phantom Xbox controller, add
        IgnoreDevice=0x28DE,0x11FF
    to your [JoyNames] section.

    I have only added this to the HID scanning which should be sufficient, but if there are still issues I can look into ignoring in the reg scanning as well.

    FSUIPC7.exe

     

    John

     

     

  16. Using On/Off button with events

    in FSUIPC7 MSFS

    Posted

    9 hours ago, DaveSCUSA said:

    i messed up as the profiles in the Profiles folder weren't working.

    Are you using "profiles in separate files" then? The usual reason for profiles not loading is that the aircraft name doesn't match the names of the aircraft in the profile entry, usually due to a different livery being used. To prevent this, when you add an aircraft to a profile, you should edit the name of the aircraft in the profile section of the ini file to a shorter substring to catch all variants of the aircraft. This is my entry for the C510:

    Quote

    [Profile.C510]
    DontLogThese=67227,65568,65962,66523
    1=Cockspur C510

    The profile used is not logged, but if general button or key definitions are overridden by a profile, then this should be logged.

    If you are having issues, please explain and attach both your FSUIPC7.ini, your FSUIPC7.log and also your profile ini, if using profiles-in-separate-files.

    John

  18. New FSUIPC 7.4.11 contains trojan virus and it`s imposible to register

    in FSUIPC7 MSFS

    Posted

    1 hour ago, Bambiigamingttv said:

    I have the same issue, both Edge and Opera gx will not download the latest version due to an virus in the file

    As already noted many times, there is now a false-positive report in Windows Defender since the recent update (1,409.80 from 06/04/2024 or maybe a day or two earlier or later, depending upon when the update was pushed). This is definitely a false positive and I have reported it to Microsoft and am awaiting a response.

    There is nothing that I can do about this at the moment. To download and install FSUIPC7 (on Windows 11, 10 should be similar), you will have to temporarily allow this threat. To do this, go to the Windows Security panel and select the Virus & threat protection page, ant then select Protection History. Select the entry for the installer (should be the first entry), and then under the Actions menu select Allow. This will allow you to download and run the installer.

    Once you have installed FSUIPC7, Go back to the main Virus & threat protection page, click on Allowed threats, select the entry just added (will be Trojan:Win32/nyonm) and click Don't Allow.

    You will need to do this to install FSUIPC7 for the time being. Hopefully Microsoft will resolve this issue soon.

    Note that when downloading from fsuipc.com you may also get an 'insecure download blocked' warning. This is a separate issue and is because the fsuipc.com site is still on http and not https (sorry, haven't had time to update this yet, been on my to-do list for several years...). Just click Keep (or similar) in your browser. The file itself will still be downloaded over https so this is not an issue.

    For other users who are experiencing this, there is no point posting about this as it is a known issue. I will update this topic when I get a response from Microsoft or have any new information.

    It also seems that the latest beta release doesn't have this issue (no idea why!), so you can also use/try this if you do not want to allow the current installer to run, available here: https://fsuipc.simflight.com/beta/Install_FSUIPC7beta.exe

    John

  21. FSUIPC7 7.4.12c (beta) release with auto-tuning of start-up parameters

    in Announcements

    Posted

    1 hour ago, Tigerhawk said:

    The next time the hotkeys didn't work again.

    There seem to be two issues here:

    1. The variable time it takes MSFS to start and arrive to the main menu. Your second set of log files indicate that it took around 40 seconds longer for MSFS to load to the main menu compared to the first. The start-up time can depend on your system load during start-up, but I think these large differences/variations in start-up time are mainly due to online activity that MSFS performs during start-up as well as the aircraft it is loading (i.e. the aircraft in use when MSFS was last exited), and can vary quite a lot due to both network performance and the speed/load on the MSFS data serves.

    2. There seems to be an issue with the request to receive key press/release events from MSFS when there has been several connection attempts, and this issue seems rather random (i.e. it can sometimes cause an issue, other times not).

    I am not sure what I can do about issue 1. What I will do is:
        - if auto-tuning is not running but re-connection attempts are detected, I will flag auto-tuning to be ran on the next auto-start run of FSUIPC7
        - allow the user to completely disable auto-tuning, so that they can use the parameter value that they determine and this will not be adjusted
    For the time being, I recommend that you manually set your DetectToConnectDelayAuto ini parameter back to 220 (or possibly 240) to try and prevent this key-detection problem.

    Issue 2 is also rather baffling...and I have never experienced this issue here and it is difficult to understand why this is happening. Could you show me/attach your FSUIPC7.ini file so that I can check if there are any settings that could cause this issue, I will also add some additional logging for this.

    John

     

  22. New FSUIPC 7.4.11 contains trojan virus and it`s imposible to register

    in FSUIPC7 MSFS

    Posted

    It seems that the latest beta release is not affected by this - I don't know why. This is an exe rather than a zip, so is missing some documentation (README.txt and changes.txt files), but you can try downloading this if you have issues with the official release:
        https://fsuipc.simflight.com/beta/Install_FSUIPC7beta.exe

    However, there will most probably still be issues with BitDefender and the RegistrationChecker in this version.

    John

  23. PMDG 737 offset 0x6568 not displaying correct value

    in FSUIPC7 MSFS

    Posted

    First, note that the gauges display the temperature in Fahrenheit, but the offset holds the temperature in Celsius.

    However, there does seem to be an issue. When I start the PMDG 737 I see the offset increase in value from 0 up to around 80, and if I adjust the temperature this can go above 100C!
    This is obviously not correct, and should be reported to PMDG.

    John

     

  24. PMDG 737 offset 0x6568 not displaying correct value

    in FSUIPC7 MSFS

    Posted

    FSUIPC just populates the PMDG offsets with the data received from the aircraft. If it is not holding the correct value, then this can be due to one of two things:
       1. The PMDG data format has changed. I can check this.
       2. The data PMDG is sending is not correct. I cannot do anything about this and this should be reported to PMDG.

    I will take a look at 1 and get back to you.

    John

    • Like 1
×
×
  • 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.