fs2024 version CWS yoke button assignment
-
@Black-Square blacksquare perhaps i am misunderstanding something here, are you saying that there is no way of activating the inbuilt cws function on the TBM via a button binding, or that the cws feature doesnt actually work in the sim. lets say i was able to click the yoke cws button and see the announciated cws appear on the EADI, would it then work correctly?. The way i read the tbm manual new feature section v1.1 is that its a new feature therefore i assumed it wouild not only be accessable but also work correctly? Or If i use a 3rd party binding software i should be able to activate this feature using a joystick binding and see it announciate on the eadi and its just the native sim option K:SYNC_FLIGHT_DIRECTOR_PITCH that has no variables to trigger the cws flag and indication on the eadi?
-
@Black-Square is there a way of setting cws up with fsuipc? as in binding a joysick button to activate it so that it clicks the cws button on the yoke and announciates on the eadi just by pressing a button on my yoke?
-
You are correct on all accounts, but one clarification is also necessary.
No, the CWS message will not appear on the EADI when using K:SYNC_FLIGHT_DIRECTOR_PITCH, because the simulator does not have a method for me to access when this event is triggered. This is just an oversight in the sim, which has probably existed for 30 years in its code.
Yes, you can easily use fsuipc to trigger L:var_PilotCws_IsDown, so the message will illuminate and the pitch sync functionality will be triggered.
Clarification: What you are triggered here is a pitch sync functionality, and not CWS. The simulator's native autopilot implementation does not have any sense of real control-wheel-steering.
-
You are correct on all accounts, but one clarification is also necessary.
No, the CWS message will not appear on the EADI when using K:SYNC_FLIGHT_DIRECTOR_PITCH, because the simulator does not have a method for me to access when this event is triggered. This is just an oversight in the sim, which has probably existed for 30 years in its code.
Yes, you can easily use fsuipc to trigger L:var_PilotCws_IsDown, so the message will illuminate and the pitch sync functionality will be triggered.
Clarification: What you are triggered here is a pitch sync functionality, and not CWS. The simulator's native autopilot implementation does not have any sense of real control-wheel-steering.
@Black-Square thank you for the explanation. I'm struggling to find any documentation on how to set this up in fsuipc, do you have any info in that? seems like i would have to write some code snippets or at least edit the fsuipc ini which ive tried and no luck so far
-
@Black-Square thank you for the explanation. I'm struggling to find any documentation on how to set this up in fsuipc, do you have any info in that? seems like i would have to write some code snippets or at least edit the fsuipc ini which ive tried and no luck so far
-
@Black-Square Food for thought on the native K event, Nick; JustFlight has something similar in the 146 that allows you to disengage the AP servos to set a new VS reference datum, similar to how I think CWS is being described as working here. In their case, they use a throwaway binding; I think there's one for press and hold functionality and one for just an immediate snapshot, but they're both bindings like Afterburner Toggle. Unless this is another instance of things possible with WASM that aren't with whatever you work your magic with.
@airvice Have you made any progress on this? I have some code snippets I can provide from both the TBM (where I have a button for 850 mode) and the Starship (where I have a button for checklist advance) that might help illustrate how it should work. I may also switch to the CWS_IsDown instead of using the native K event binding in the sim.
-
@Black-Square Food for thought on the native K event, Nick; JustFlight has something similar in the 146 that allows you to disengage the AP servos to set a new VS reference datum, similar to how I think CWS is being described as working here. In their case, they use a throwaway binding; I think there's one for press and hold functionality and one for just an immediate snapshot, but they're both bindings like Afterburner Toggle. Unless this is another instance of things possible with WASM that aren't with whatever you work your magic with.
@airvice Have you made any progress on this? I have some code snippets I can provide from both the TBM (where I have a button for 850 mode) and the Starship (where I have a button for checklist advance) that might help illustrate how it should work. I may also switch to the CWS_IsDown instead of using the native K event binding in the sim.
ive been through the fsuipc advanced manual i have the pay version, but i just cant get it to work. Im not an expert at fs coding so im sure it's user error but i think the manual assumes those using it are already at an advanced level. im not. If you have any suggestions id appreciate it, however i would need very clear and full instructions on how to do it as im new to all this from the back end
-
@Black-Square Im using the pms50 gtn750 paid version. Well regarding range rings and tod i was thinking of the nav gps system somewhere?
-
ive been through the fsuipc advanced manual i have the pay version, but i just cant get it to work. Im not an expert at fs coding so im sure it's user error but i think the manual assumes those using it are already at an advanced level. im not. If you have any suggestions id appreciate it, however i would need very clear and full instructions on how to do it as im new to all this from the back end
@airvice The exact layout of everything you do will ultimately depend on how you have FSUIPC configured. I am a fan of using the "UseProfiles=Files" option in the FSUIPC.ini file, which separates all of my different aircraft profiles into separate .ini files in the Profiles folder, instead of just cramming all of it into the FSUIPC.ini file. In my FSUIPC.ini file, there is only a single line relevant to all of this (well, technically two):
[Profile.TBM850] 1=Black Square TBM 850 Red & GoldThis tells FSUIPC that when I load the aircraft model titled "Black Square TBM 850 Red & Gold" to load the profile named TBM850. This is really just FYI to showcase how I call it; as I said, how you call it will depend on how you set it up, and I really can't help with it remotely. The meat of my TBM850.ini should be more easily usable from a plug & play sense, though.
My TBM850.ini file is relatively simple:
[Profile] Created=19/10/2024 22:31:24 [Buttons] 0=PD,11,C66006,30 -{PROP_PITCH1_DECR}- 1=UD,11,C66007,0 -{PROP_PITCH1_HI}- 2=PD,13,Cx0100A000,x01 -{offset byte set, offset A000}- 3=UD,13,Cx0100A000,x00 -{offset byte set, offset A000}- [LvarOffsets] 0=L:var_850Mode=UB0xA000There are four simple operations in this profile.
- 0=Pressing button D11 on my Velocity One throttle, which for me corresponds to the button at the end of my propeller axis, will decrease the propeller pitch axis by a value of 30. This effectively puts the propeller pitch lever in the TBM cockpit into the Feather detent, and it feathers the prop on the aircraft.
- 1= Releasing button D11 on my Velocity One throttle sets Propeller Pitch 1 axis to the High value, which just moves it out of the feather detent, and the propeller unfeathers.
- 2= and 3= I don't believe I generated, I let the Button configuration screen in FSUIPC set that for me. More on this in a bit.
Under [LvarOffsets], I have a single entry, 0=L:var_850Mode=UB0xA000, which basically says to FSUIPC "when you see offset 0xA000, that means this Lvar." Exactly what an offset it and how it works is beyond the scope of this post, which is fortunate because it's beyond the scope of me, too. However, experimentally I have seen that simply setting Lvars directly may or may not work, but it will not animate whatever you are trying to do, which is half the fun. Setting the 850Mode Lvar to an offset allows the 850 mode switch in the TBM cockpit to move in and out of its position as I toggle it.
Wherever you end up putting your TBM commands, put this text to start:
[LvarOffsets] 0=L:var_PilotCws_IsDown=UB0xA000
Once you are in the sim with the TBM loaded, go to the Button and Switch assignments screen in FSUPIC and press the button you want to bind. Make sure that ProfileSpecific is checked (maybe do this first so that the profile is created for you, then find whatever you named it when creating it either in the FSUIPC.ini file, or as a separate file). For this button, you want Select for FS Control in the upper right, then navigate to Offset Byte Set for the Control sent when button pressed and released. Enter the offset (in this case xA000 is the first freely available one), and set the parameter to x01 for pressed and x00 for released. Then save it.
It "should" be as simple as that, once that saves, you should be able to press your button and see the CWS button work in the virtual cockpit.
EDIT: since I had to bring everything up anyway, I figured I might as well go all the way and do it myself to verify.
After adding a second line into the LVarOffsets area and then binding button B9 to the above settings, my TBM850.ini profile now looks like:
[Profile] Created=19/10/2024 22:31:24 [Buttons] 0=PA,11,C66006,30 -{PROP_PITCH1_DECR}- 1=UA,11,C66007,0 -{PROP_PITCH1_HI}- 2=PA,13,Cx0100A000,x01 -{offset byte set, offset A000}- 3=UA,13,Cx0100A000,x00 -{offset byte set, offset A000}- 4=PB,9,Cx0100A002,x01 -{offset byte set, offset A002}- 5=UB,9,Cx0100A002,x00 -{offset byte set, offset A002}- [LvarOffsets] 0=L:var_850Mode=UB0xA000 1=L:var_PilotCws_IsDown=UB0xA002I have not flown the TBM yet with this, but I can see the yoke button depressing and releasing in the cockpit so I assume it will work.
-
Oh my goodness, I did all of that so long ago I forgot what I learned for the Starship and the Dukes. There's a much simpler way to go about it.
//Black Square/TBM/Autopilot Pilot_CWS_Down#1 (>L:var_PilotCws_IsDown, bool) Pilot_CWS_Up#0 (>L:var_PilotCws_IsDown, bool) //Black Square/TBM/Engine 850_Mode_On#1 (>L:var_850Mode, bool) 850_Mode_Off#0 (>L:var_850Mode, bool)Put that into a file in your FSUIPC directory called myevents.txt. If it doesn't exist, create it. From the Buttons and Switches Assignment screen, select your button, do your profile stuff (you really should so that it auto loads profiles depending on what aircraft you load), then just click Find Preset for both press and release.
It will be under Personal-->Black Square-->TBM and so on based on how it is listed in myevents.txt. How to set it is already done in the so-called "calculator code" I have above in the snipped that goes into myevents.txt. CWS_Down will always send a 1, CWS_Up will always send a 0. There is some very powerful RPN coding possible in there that I haven't yet been able to make heads or tails of, but this is a simple enough way that it should get you up and running pretty quickly.
