Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,697
  • Joined

  • Last visited

  • Days Won

    288

Posts posted by John Dowson

  1. 45 minutes ago, Flusi2004 said:

    As I wrote in my last post after a new installation of the normal 727 it works now without lua and offset with the binding Throttle.... ex1.

    Yes, I know - but it does not work in the super version. I know that the lua + offset assignments work in the basic version of the 727. So I would like you to try to get that working (you can switch back to the _EX1 events afterwards). Once you have it working in the standard version, THEN you can see if it also works in the 'super' variant. I suspect os, bit honestly have no idea as I still have not seen what input events this aircraft is using.

    48 minutes ago, Flusi2004 said:

    And of course, if I tried the 727 super the lua file was in the fsuipc folder and the correct entry in the ini. And I found out, that throttle bindings in the super moves the reverse axis.

    Can you please show me your log and ini for this?
    As I said, it would be good if you can confirm it works in the stabdard version, as I know it does here, and then try the super variant. One step at a time....

    50 minutes ago, Flusi2004 said:

    Any way, the normal 727 works and for the 727 Super I will wait for an update from FSS. For now it is ok for me. Thanks again.

    Well, I think that you can get this to work in one way or another. But if you do not want to try, I will consider this closed.

    John 

  2. In the first log, you were using the aircraft 'Boeing B727-200 Condor | Retro | D-ABMI' - is that the 'super'? I suspect so, as this is listed under your 'Boeing 727 Super' profile.
    But that log shows nothing - no lvars or input events.

    The second log was for the aircraft 'Boeing 727-200RE Passenger - Cougar' - is this a 'super'? If so, it is not using your 'Boeing 727 Super' profile. That log shows lvars but no input events.
    I would like to see the input events available in the 'super' version, as well as the lvars.

    20 minutes ago, Flusi2004 said:

    it is quite tiring for me because english is not my native language and I don't unterstood all your instructions.

    I understand - but it is better to ask if you don't understand something rather than ignore it. It is difficult to get to the bottom of an issue when my questions are ignored, and I am getting no feedback from the solutions I am providing.

    21 minutes ago, Flusi2004 said:

    Yes, I have tested also the offset and the lua without succsess.

    In what version? What was the issue? I know this works in the standard 727, so you should at least try to get it working there. Once that is working, you can then try in the 'super' version. If you have issues getting this to work in the standard version, please let me know, and attach your ini and log files.

    Your latest ini shows that the lua script I provided has not even been installed into your FSUIPC7 installation folder.

    John

  3. I could possibly get the Super to look into the throttle, but before I do this I would like you to at least check and try what I have already said.
    i.e. check the input events for the 727 super and if the throttle ones exist, try the lua I provided. Also, it would be useful if you could attach another log generated when using the 727 super, and showing the input events (i.e. activate logging for Input Events) and the lvars (i.e. list the lvars).

    John

  4. 12 minutes ago, Flusi2004 said:

    Of course I have tried to use with the Super the same FSUIPC Profile like the normal 727-200.

    That is not what I asked...

    I asked if the Super has the same input events (or any input events for the throttle). If so, you should try that lua I provided - maybe modified if the input events have different names.
    I keep asking if you have tried this but you are not answering this question. If you want me to help you to set this up with FSUIPC, you need to try what i suggest and provide feedback.

    John

  5. Did you try the lua script I provided? That will move the throttles using the input events.

    I have updated to the latest version of this aircraft, and the script looks to be working to control the throttles and I can now move the aircraft.
    Seems to work just using the input events, so I have removed the code to also send the throttle set events in the attached lua, so please try this one.

    John

    FSS-727Throttle.lua

  6. 6 hours ago, rickmatrix said:

    2. Add the line in FSUIPC.ini
    [LuaFiles]
    1=iFlyRwyOFF
    2=iFlyRwyON
    (file names for example)

    You should never modify the [LuaFiles] section manually - this is maintained by FSUIPC. It will add lua files to this section automatically, when found in the installation folder (or in LuaPath, if that is set).

     

  7. If using FSUIPC7 (for MSFS2020 and 2024), please use the specific sub-forum for FSUIPC7. I will move this topic to thst sub-forum.

    And if using FSUIPC7, you may find it easier to use the available presets for the PMDG 777, which use the custom controls via the Rotor Brake method. In the assignments panel, check for 'select for Preset', click the Find Preset... button, then navigate to the MobiFlight PMDG 777 presets, which will grouped by subsystem.

    John

  8. Your FSUIPC7.log does show some connection issues and didn't connect until nearly 90mins after it was started (presumably when you re-connected). First, you need to increase your DetectToConnectDelayAuto ini parameter.  This is set to 40 - you should increase this to 80. Can you also add:
         TestOptions=x800
    to the [General] section of your FSUIPC7.ini (and yes, turn off event logging!) and show me another FSUIPC7.log file when you get your connection issues again.

    John

  9. 13 hours ago, JUrso said:

    My main issue is that I can't see my lua files on the "Control sent when button pressed" droplist.

    If you have the lua files registered by FSUIPC and they appear in the [LuaFiles] section (presuming you did not add these manually), then they should certainly appear in the drop down menu.

    Are you sure you do not see them? It will be called 'Lua Test_Log' in the menu, and you have to check 'Select for FS Control' after pressing your button.

  10. 16 hours ago, EisernUnion said:

    Example to Set COM1 Active

    Dial your Freq, e.g. 123.150 will be the Variable1 (String) 

    On 'Button down' e.g. 'COM1 Active' this RPN will be executed [The current active COM1 will be SET to COM1 STBY (to switch back) and the Variable1 will be set as Active]

    (L:Variable1, String) stod 1000000 * (>K:COM_STBY_RADIO_SET_HZ) '' (>L:Variable1, String) 1 (>K:FENIX_A3XX_MY-SWAP)

    Thanks. Thats interesting, and would seem to indicate that the COM_STBY_RADIO_SET_HZ works (and possibly COM_RADIO_SET_HZ for active), at least when using calculator code. The FENIX_A3XX_MY-SWAP k-event looks strange though - this must be a custom event for the Fenix (I have not seen a custom event like this before!). Not sure why those double quotes are there (and only one), and why the Variable1 lvar is being updated ('(>L:Variable1, String)')  or why FENIX_A3XX_MY-SWAP is taking two parameters...

    John

  11. Just now, JUrso said:

    I've gone through troubleshooting but can't seem to get WASM to start.

    The FSUIPC WASM module is automatically started by MSFS on start-up, You cannot manually start this. if it is correctly installed in your MSFS2024 Community folder.
    Is it installed? If so, why do you think it is not started?

    1 minute ago, JUrso said:

    My most recent step was to run "fsuipc7.exe --fsuipc-wasm in a command prompt. No console output is generated, FSUIPC7 just starts up as normal.

    Why would you think this would do anything, using an unknown/not revognised parameter?

    FSUIPC7 and the FSUIPC7 are two distinct applications - starting one will not start the other - and you cannot manually start the WASM. As I said, this is started by MSFS.

    Can you please clarify what your issue is. If the WASM isn't started, it isn't installed - show me / attach your InstallFSUIPC7.log file so that I can verify it is installed correctly.

    John

  12. 5 hours ago, JUrso said:

    The reason I asked is that I can't type in the "Control sent when button pressed" field to specify the lua file to use. I do see my lua files in the ini file, so they are being recognized. Any thoughts?

    You should really raise this as a separate issue as this is not related to the trial license.

    You can't type into that field until you have pressed the button to assign and that is registered, and then have selected for the control type (e.g. 'Select for FS control' for lua scripts). 

    It should be in the menu - just click on the menu, wait for it to load and then type 'l' (for 'lua') - the menu should position at the first entry with an l/L. Then scroll down to find 'Lua <yourLuaFilename>' and select that.

    Any further questions/issues, please raise a separate thread/topic. This topic is only for trial license requests, not issues.

    John

  13. I have assigned now to get the throttles moving, but I don't think they are actually working, i.e. no sound and no movement in the aircraft.
    If you could let me know how to actually use the throttles with the mouse (so I can get the aircraft moving), this may help me...

    To move the throttles, I assign your axis using 'Send to FSUIPC Offset', select Offset Dword Set and give an offset - I am using xA030, xA034 and xA038. If you use other offsets, you will need to update the lua script.

    Then save the attached lua script to your FSUIPC7 installation folder (or Lua script folder if you have this set differently).
    You then need to start the lua - best to have it auto-started by adding this to your ini:

    Quote

    [Auto.B727 Super]
    1=Lua FSS-727Throttle

    The script uses the input events to move the throttle lever. I have also tried adding the sending of the Throttle1/2/3_Set control to see if this is also needed (both as a standard control and via calculator code), but I still don't seem to get any thrust.
    I will look into this on Friday, and after I have been able to update.

    If you can provide me the info on how to use the throttles in the VC, that would be helpful. I really don't want to have to go through the documentation to learn how to move this.....!

    John

    FSS-727Throttle.lua

  14. Just took a quick look - I have quite an old version of this aircraft (1.0.7 - latest is 1.1.3) and can't seem to update. I will try and update to the latest version - I have raised a support ticket for this an am awaiting a response.

    In the meantime, I am not familiar with this aircraft. If I advance the throttles in the UI, using the mouse, they jump back to idle. Do you know why this is? Is there some sort of throttle lock that I have to disengage first?

  15. Please attach files only, not screenshors (unless specifically requested). The lvars are not listed in the log you provided. Please show me a log file that lists the lvars.

    However, your log does show some input events that may be of interest:

    Quote

         5078 InputEvent found: 'ENGINE_Throttle_1' with hash=5200770593375785755 [type=0]
         5078 InputEvent found: 'ENGINE_Throttle_Reverser_1' with hash=16985579028055341929 [type=0]
         5078 InputEvent found: 'ENGINE_Throttle_2' with hash=10321682380435769518 [type=0]
         5078 InputEvent found: 'ENGINE_Throttle_3' with hash=14829538403500064317 [type=0]
         5078 InputEvent found: 'ENGINE_Throttle_Reverser_3' with hash=7951428358750099023 [type=0]

    Not sure there is no ENGINE_Throttle_Reverser_2 though....

    Looking at the log of the ENGINE_Throttle_1/2/3 input events, it seems that these take a value between 0 (for idle) and 100 (for full thrust).
    You could try using these for your assignments. To do this, you need to assign your throttle to update an FSUIPC offset, then have a lua script that monitors this offset, calibrates the axis value to the 0-100 range, and then send this value using the appropriate Input Event.

    I have just realised that I actually have the FSS 727, so I will look into this (and the lvars) and get back to you - but it may take a day or two as I am busy until Friday.

    John

     

  16. 4 hours ago, michelmvd said:

    Can someone help me with the values for the fuel cut off witches eng 1 and 2 ? 

    Which FS and version of FSUIPC are you using?

    Try setting logging for Events (non-axis controls), open the logging console and activate the switches in the virtual cockpit - what do you see logged? Try assigning to the control (and parameter) that is logged.

    You will probably see custom controls logged. These are maybe the custom controls needed:

    Quote

    // Pedestal - Control Stand - Fuel Control
    #define EVT_CONTROL_STAND_ENG1_START_LEVER                (THIRD_PARTY_EVENT_ID_MIN + 520)    
    #define EVT_CONTROL_STAND_ENG2_START_LEVER                (THIRD_PARTY_EVENT_ID_MIN + 521)    

    To use those (for a toggle control), you would assign to the Rotor Brake control, with a parameter of 52001 (for engine 1) and 52101 (for engine 2). See the following FAQ entry on how to use custom controls when using mouse operations:

    If you want separate events for cut-off / idle, better to use the custom controls directly (i.e. with a parameter indicating the state, not the mouse operation) - this post shows how to do this: 

     

    John

    N.B. If using MSFS2020/2024, then you can also use the available (MobiFlight) presets - and you have posted in the wrong forum!

  17. Your log shows many Throttle 1/2/3 Set controls logged, but for some reason this is using 2 parameters and both are 0. Very strange as these controls only take one parameter...

    Can you please re-read my earlier posts carefully and look into what I have advised. Namely:
       - check the EFB throttle configuration
       - log Input Events (also list them) and see if any are applicable
       - list the lvars to see if any of them look applicable

    The log file you attached shows no lvars or input events.

    Also, please remove any throttle assignments (and calibration) you currently have and just move the throttle in the VC (i.e. using the mouse) for the time being.

    John

  18. How have you assigned the throttle axis? Which controls have you tried? e.g. have you tried the *_EX1 throttle controls?

    If assigning using 'Send direct to FSUIPC calibration' doesn't work, switch to using  'Send to FS as normal axis' and try the various throttle controls there. Best to remove any calibration when trying this, at least until you find an axes control that works. If you find one that works, you can then try to see if this can be calibrated.

    You can also try logging  Axes Controls, move the throttle in the VC, and see what control is logged. You can then try that assignment, but there is still no guarantee that this will work.

    You can also try setting logging for Input Events and move the throttle, to see if any Input Events are logged. If so, I can how you how to assign an axis to control an Input Event.

    Also list the available lvars - do any of them look like they control the throttle? If so, there are various methods that you can use to assign an axis to control an lvar.

    Finally, if the standard controls don't work when assigned outside of MSFS, it may be possible to define a preset to control the throttle.
    I can also help with this, but I need to know what control is logged when you move the throttle in the VC (with logging for Axes Controls set in FSUIPC).

    I don't have any FSS aircraft, so cannot look into this here. Try the above and report back what you find (attaching any relevant log files) and I can possibly help further.

    John

  19. 2 minutes ago, trayced said:

    Is there any documentation or tutorial for adding those offsets and using the python wrapper?

    To add lvars to offsets, see the Advanced User guide, page 47.

    The Python wrapper around the FSUIPC was provided as a user contribution, and as such comes as-is and I cannot support this.
    In fact, it is quite old now and may need updating to be compatible with MSFS2020/MSFS2024, as otherwise it may not recognise the FS version. It may work as-is - I just don't know as I have not used this wrapper. I have attached the README.txt.

    John

    README.txt

     

    • Like 1
  20. 2 hours ago, trayced said:

    Do you know if there’s any way to read the MobiFlight output values directly (e.g. from memory, logs, or via a virtual device), or if FenixQuartz could be used to expose them in a way that Python could access?

    No, I do nut use or support MobiFlight. If you are using MobiFlight, try MobiFlight support (via their discord server).

    If they are standard lvars, you can also use FSUIPC to read/write these, and use the python wrapper of the FSUIPC SDK.
    However, the python wrapper is quite old and will not use the WAPI/WASM, which is the API that I provide to access lvars. You will therefore only be able to access lvars via FSUIPC offsets, which means that you would need to add the lvars you want to use to spare/free FSUIPC offsets before they can be read/updated. 

    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.