Jump to content
The simFlight Network Forums

waqar_mw

Members
  • Posts

    17
  • Joined

  • Last visited

Posts posted by waqar_mw

  1. Hi, 

    Can someone please guide me as I am not able to use the lua file with multiple functions in FSUIPC. I am unsure if this is even possible to do, basically what I am trying to do is use someone's lua file for the PMDG737 and use certain functions from that lua file in FSUIPC for example how do I assign "PMDG_GLSD_EFIS_NAV1_cycle" function to a key on my keyboard. 

     

    Do I have to create multiple lua files with each function? or can I just use one lua file and assign different functions to different keys. I am sorry if this has been asked before I tried looking it up but couldn't find an example.

     

    Thanks.

    FSUIPC7.ini PMDG737.lua

  2. 5 hours ago, Helibrewer said:

    I want to look into this, what software do you use for Linda?

    Cheers,

    Mike

    Use Linda with FSUIPC and it will work great there are some posts on linda forum you can have a look for them and you can write lua scripts too.

  3. 17 hours ago, Helibrewer said:

    I am using FSUIPC7, Version 7.1.0f.

    Flight sim is FS2020

    I do not use any lua files.

    The Mode dial is located on the X-56 throttle (JoyName: 0, A)

    Reading through the Advanced manual seemed to indicate flags were the direction to go. The Mode "switch" is a 3-position rotary dial(M1, M2, M3) so there is no "un-pressed" state, it is always in one of those three positions.

    If the dial is in position M1 when I start the flight sim, no buttons or axis have been manipulated, does FSUIPC know the what position the dial is in?

    I have not tried any programming using the Mode dial because I wanted to understand how FSUIPC interprets a dial position first.

    I will continue to look through threads here but none have helped so far in my understanding. 

    FSUIPC7.ini 4.79 kB · 2 downloads

    I know this forum is just for support for fsuipc but I am currently using Linda to use the mode switches each mode switch acts a shift key basically and each toggle on the HOTAS can be used as 3 different functions then depending on the position of the mode switch. The only reason I used Linda is because it has an easy to use interface and does not take much of learning to get used to the software. But you can do the same thing with FSUIPC too using compound actions, it is a bit of a long process but once set up correctly it would work without any issues at all. 

     

    Regards

    Waqar

    • Like 1
  4. On 4/14/2021 at 7:09 PM, John Dowson said:

    I think they work in the A320 without using lvars, but you may need the FBW mod or the MobiFlight event module (also via WASM), or probably both.
    Anyway, as WASM modules are broken in the current release, I can't check this for you at the moment (and I'm still downloading the latest update!).

    Yea, I am waiting on an update as well about WASM modules to be fixed. Thanks for your reply I will let you know how it goes.

  5. 14 hours ago, John Dowson said:

    I also noticed this in the 747.

    There is an lvar (on the 747) for standby power: XMLVAR_StandbyPower_Selector. However, I've just tried this and it only seems to work switching between AUTO and BAT, and cannot switch to or from OFF.

    As for lvars in FSUIPC7, I have just released an early-access version with lvar support. For documentation on how to use lvars with FSUIPC7, you have to look at the FSUIPC6 documentation for the time being (and also have the WASM module installed - just download, unzip and move to your community folder, instructions on the WASM announcement page). I will be updating the documentation and the installer (to handle the WASM) in the coming days, and hope to release this as an official beta release later this week (or early next week).

    I will try that with the A320 and see how lvar works and will give it a go maybe today and will post my results here so it may help anyone else looking out for the same problem. Thanks for your help, it is appreciated.

  6. On 4/12/2021 at 5:06 AM, John Dowson said:

    Have you tried assigning to that event/parameter?

    Also maybe try the stable or vanilla version - I have had reports of different things working in different versions of the FBW mods.
    Maybe also check for lvars as these will be available shortly (via lua or macros),

    Yes, I did try that control event with parameter 6 and it does nothing in the simulator even with Asobo A320. Then I tried with paramter 0 and that just turns off everything in the cockpit but overhead panel buttons don't move at all. I will try your suggestion with different version of the mod.

     

    The thing is I tried fiddling around with your WASM Module but I couldn't figure out how to get LVARS and the thing is there is no documentation on it yet so I can't follow any guides as I am quite new to lvars. I will have a look around and try to gather some information on lvars, I hope someone can help you write a guide for the usage of WASM module. 

     

    Regards

  7. I am using the FBW A320 Development Build, it is version 0.6 I believe. On the FSUIPC console when I log the events and press the battery switches in the plane it gives this as an event output:

    3860625 *** EVENT: Cntrl= 67073 (0x00010601), Param= 6 (0x00000006) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE

    I will give these offsets a try and let you know how it goes. There are some other things in the plane such as the APU switches which don't work with the normal controls and when I try to write a lua script in Linda for it the event gets logged but nothing really happens in the plane. I am trying to get all these buttons and switches to be sorted out because I want to not use keyboard and mouse when I fly in VR. Thanks for your help it is really appreciated.

  8. 5 hours ago, John Dowson said:

    Forget about lvars/hvars for now - they are not yet accessible via FSUIPC. But they certainly shouldn't be needed for master battery. Search for existing topics on this please, I'm sure there are already posts on this... and maybe check the offset documentation spreadsheet.

    Also, please remember, if using LINDA and have issues you need to go to the LINDA forums. 

    I haven't looked at your files as I beliebe @jaxx identified your problem. But if you still have issues, please post again, and also attach your latest files.

     

    Thanks John, yes @jaxx solved my issue. I am glad everything is working now as expected on the HOTAS side of things.

    I'll have a look as you said but with commands such as ADIRS and mastery battery etc I have not had much luck as I don't see any ADIRS commands in FSX and master battery toggle just turns of the battery instead of turning them back on when required. 

    Anyways thanks for your help. 🙂

  9. 7 minutes ago, jaxx said:

    You're still having a default assignment for C5 configured (11=PC,5,C65759,0     -{FLAPS_DECR}-).
    Also do you want to use a button flag? From your description it seems you want a shift-function while button 134 is hold, not toggle a shift with a single press?
    11=CP(-C,134)C,5,C65759,0     -{FLAPS_DECR}-
    22=CP(+C,134)C,5,C67187,0     -{BATTERY1_SET}-

    Thanks I will give that a go btw that button flag I was just trying them out but couldn't figure it out at first. Anyways thanks for your reply I have finally figured it out how to use shift functionality with Linda as well as FSUIPC from your post. But now I have run into another problem such as I can't get master battery to work and I am reading about LVARS and HVARS, I am finding it a bit complicated but I am trying to work through it.

  10. I am currently trying Linda as it is a bit easier, but I would still love it if I can figure out a way for mapping everything within FSUIPC. If not I will post my results here for everyone using x56 so it may help them out. Currently I mapped toggle master battery with Linda and it would just turn off the batteries but not turn them back on when the key is pressed again. Thanks for your help.

    FSUIPC7.backup.ini

  11. On 4/5/2021 at 10:13 PM, John Dowson said:

    To use as a type of 'shift' key with FSUIPC, you can use  'compound button conditions', where the assignments on one button are dependent on the state of another button. Please see the Advanced User Guide for details.

    John

    Hi John I have tried this please check the my log file it is sending two commands at once even when the state of the other button is on.

    Log for shift keys.txt

  12. 13 minutes ago, John Dowson said:

    To use as a type of 'shift' key with FSUIPC, you can use  'compound button conditions', where the assignments on one button are dependent on the state of another button. Please see the Advanced User Guide for details.

    John

    Thanks John for the quick reply, it is getting late here I will try that tomorrow I think I know what you mean as I have read some posts about compound buttons. I will give that a go tomorrow and let you know and thanks a lot.

    Regards

    Waqar

  13. 50 minutes ago, John Dowson said:

    There are various threads on how to get this working with FSUIPC, eg. 

     

     

    I have deleted all the drivers and software related to x56. Now the switch mode acts like another button instead of being like a switch key. Do you think I can map it as shift key and get more inputs in my simulator.

    Further more I wanted to thank you for this software it works really well. Thanks and I have installed the latest version as requested.

     

  14. Hi,

     

    I have set up all the axis and buttons as I want them, but for some reason I can not figure out how to configure the switch modes to get more button assignments in my simulator. Can someone please guide me as I have not found anything similar to my question online. Any help will be appreciated thank you. 

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