Helibrewer
-
Posts
16 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Helibrewer
-
-
Tried to install, getting message that FSUIPC is already running. I rebooted and don't see it running anywhere but I am still getting that pop-up when trying to install. What am I missing?
-
3 hours ago, waqar_mw said:
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
I want to look into this, what software do you use for Linda?
Cheers,
Mike
-
I got it sorted. I don't know why the ini doesn't update that line but my log file shows 7.1.0f
The JoyName assigned 0 and A to the throttle. It assigned 1 and B to the Stick, at least according to the ini file. Why buttons pressed on the Throttle (A) map to (B) I have no idea but they do and it works.
Here is my solution that works:
M1 = B,14
M2 = B,15
M3 = B,16
To program FLAPS_DOWN using button B,2 on the Stick when Mode 2 is active (M2) on the Throttle:
53=CP(-B,16)(-B,14)B,2,C65603,0 -{FLAPS_DOWN}-
And this works, the FLAPS_DOWN button press only works if the Mode Switch is in position M2. B,2 only works if B,16 AND B,14 are NOT pressed.
On to more complex things now....
Thanks for your assistance
Mike
-
28 minutes ago, John Dowson said:
Are you using one of the FSUIPc7 betas? If so, this has support for outside the 32 button range, and button 32 is shown as 132, 33 as 133, etc. If you previously useda lua to access buttons > 32, they will be using the button flags, and if still running the lua you will see two button presses (but the virual devive for the virtual buttons should be 64 or above....). I don't know why thwy aee showing as 'B', which is a normal device letter. Maybe show me your FSUIPC7.ini and an FSUIPC7.log and I'll rake a look.
You don't need to do it this way. You can use compound button conditions. Please see the Advanced user manual. There are also many other support requests on using the mode switch in the X56 (and other devices) - if you have issues, try looking for one of them first.
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.
-
To expand on this a bit. The X56 Throttle has a 3-position Mode switch. In FSUIPC, Mode 1 is read as B,14...Mode 2 as B,15...Mode 3 as B,16. I have also found that occasionally when switching from one mode to the other, they can be read as A,133; A,134; A,135 respectively. This seems random and I haven't figured out why yet.
Anyway I would like to use flags for these modes so I can have any button perform 3 different functions depending on which of the modes flag is set. When FSUIPC and the sim first start I assume FSUIPC has no idea which position the Mode switch is in, so I am thinking I need to move the Mode switch out of it's current position after start-up and into (or back into) the position I want to use, and have that action set the selected position flag, and clear the other 2 flags. After that, any movement of the Mode switch would perform that same function each time (set current position flag, clear the other 2 flags).
Does this make sense? Is there a more efficient way to do this?
Thanks,
Mike
-
I believe it can access offsets, I will investigate that.
Thanks John
-
I don't really understand the inner workings of the FSUIPC wasm, but it is great to be able to assign buttons/keys to lvar's now, thank you so much.
One of the other things I am trying to solve is that I build virtual bezels in Air Manager to surround the pop-out gauges with functional softkeys. Does the FSUIPC wasm expose the lvar's to Simconnect? I believe that is what Air Manager uses for it's interface with the sim and many aircraft use lvar's for their softkey functionality.
What would I need to do to access the lvar's FSUIPC wasm finds in Air Manager (via lua).
Thanks,
Mike
-
Some of the H135 guys are asking if they need to have FSUIPC7 registered to play with this....I wasn't sure since mine is registered.
-
22 minutes ago, andhog said:
Unfortunately there's apparently something seriously wrong with the latest world update. Having a standalone WASM module in your community folder causes CTD when starting MSFS 😕
I can confirm this also.
-
18 minutes ago, John Dowson said:
There are (or should be) multiple files there - only 146 lvars per file, which is how many each Client Data Area created can hold, again a hangover from a previous implementation.
You usually actually get more lvars when you create lvar files, as it re-scans for lvars when doing this so you can get more than the initial scan. If you find that you get more, you can issue a reload command to the WASM to reload all the current lvars back to the client/WAPI.
Ah, I see that now, thanks again and thanks for all the work on this. Looking forward to figuring out how to utilize this in lua scripts in the future.
-
11 minutes ago, John Dowson said:
Yes its working - although I don't know why you would want to use this function. Its a hangover from a previous implementation. The files are created under your AppData\Roaming\Microsoft Flight Simulator\Packages\fsuipc-lvar-module\work folder (which is the WASM persistent storage area for the FSUIPC WASM module).
Found it, yes, it's an incomplete list compared to the "List LVARS". The main reason I was interested is because I thought it would be easier than trimming the values out of the listing windows to create my file of LVAR names.
Thanks for pointing me in the right direction, found it here:
C:\Users\MyUserName\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\fsuipc-lvar-module
-
1
-
-
Should the "Create Aircraft LVAR file" be functional yet in the test client? It is the only thing that doesn't seem to generate an output.
Thanks,
Mike
-
Really looking forward to this. I used the test client to interrogate and change Lvars in the H135 helicopter (MSFS 2020). Would love to use FSUIPC and/or Air Manager to operate all the soft keys in this aircraft (3 Helionix displays, 24 keys each).
-
Thanks, I created an events file named GNS530.evt and placed it in the installation folder. It just contains two lines for testing:
[Events]
1=MobiFlight.AS530_ENT_PushWhen I use the dropdown in "Assignments" -> "Buttons and Switches" the Mobiflight event is not listed. Am I missing a step?
Thanks,
Mike
-
The Mobiflight standalone wasm handles events for the G1000, G3000, GNS530, and KAP140 using MOBIFLIGHT_X_X_X event names. I would like to access these mobiflight events using FSUIPC and my X-56 stick and throttle. I cannot find a resource that identifies the event numbers that mobi is using so I cannot setup a custom event for a button. Is there another way to access these event ID's through FSUIPC? The wasm module sits in the Community folder as an add on. It works with Stream Deck though a plugin but all of the event ID's are published.
FSUIPC v7.2.0 beta support: Adding Lvars to Offsets
in FSUIPC7 MSFS
Posted
Never figured it out, rebooted, used the uninstaller and it couldn't delete the exe either. I was able to rename the exe, reboot, then I could delete it. I have no idea what was loading FSUIPC at boot but it didn't show in task manager that I could see. 7.2 is now installed so I can start figuring out this lvar offset stuff now....thanks!!