Maltloaf
-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Maltloaf
-
-
Thanks, will do
-
As I guess most of us now know, MSFS does not simply use the list of commands FSX used and so cockpit building is somewhat frustrating. I have managed to get the Garmin 430 and 530 working using Mobiflight Event Lists with FSUIPC (I don’t use any Arduinos so I can’t use just Mobiflight) so that is a start.
Now the DC-6 hoves into view with its Gyro-pilot and I am back to the forums to work out how to control the beast from my rig. I found this here somewhere on MSFS Forum:
DC6_AP_ON#43401 (>K:ROTOR_BRAKE)
DC6_AP_OFF#43401 (>K:ROTOR_BRAKE)
DC6_AP_HANDLE_ON#40401 (>K:ROTOR_BRAKE)
DC6_AP_HANDLE_OFF#40401 (>K:ROTOR_BRAKE)
DC6_AP_PITCH_UP#440 100 * 8 + (>K:ROTOR_BRAKE)
DC6_AP_PITCH_DOWN#440 100 * 7 + (>K:ROTOR_BRAKE)
DC6_AP_ALT_HOLD_ON#43601 (>K:ROTOR_BRAKE)
DC6_AP_ALT_HOLD_OFF#43601 (>K:ROTOR_BRAKE).
And after asking John he tells me it is as simple as picking Rotor Brake from the FSUIPC dropdown list and using the parameter. I.e. to switch the AP on bind a button to Rotor Brake with the parameter 43401. That simple! So, half done. The 440100*8 is still a bit of a mystery. I assume the *8 controls the amount of increments the wheel move, maybe.
Anybody know?
Also, the yaw control is not mentioned. I assume that is in the SDK but not sure where that is.
Any ideas?
-
-
Do these show in the event log? Mine seems to be contiously logging Light Potentiometers to the extent you can't read anything?
-
Seriously! That simple! They just use the Helicopter Rotor Brake command with a parameter. Brilliant! I now need to work out the 'DC6_AP_PITCH_UP#440 100 * 8 + ' bit, ie what is the 6 fig parameter. I assume the *8 is something to do with how many increments it moves. And where the SDK is hinding, but that was far easier than I expected.
Thanks John
-
Another question on the same vain as I asked above somewhere. I have just bought the MSFS PMDG DC-6 and it is amazing. Not a DC-3 unfortunately but awesome just the same. I have the same issue with the DC-6 Gyro-pilot as I did with MSFS G530 etc. I don’t know the event IDs that will talk to the gyro-pilot. I found this here somewhere on MSFS Forum:
DC6_AP_ON#43401 (>K:ROTOR_BRAKE)
DC6_AP_OFF#43401 (>K:ROTOR_BRAKE)
DC6_AP_HANDLE_ON#40401 (>K:ROTOR_BRAKE)
DC6_AP_HANDLE_OFF#40401 (>K:ROTOR_BRAKE)
DC6_AP_PITCH_UP#440 100 * 8 + (>K:ROTOR_BRAKE)
DC6_AP_PITCH_DOWN#440 100 * 7 + (>K:ROTOR_BRAKE)
DC6_AP_ALT_HOLD_ON#43601 (>K:ROTOR_BRAKE)
DC6_AP_ALT_HOLD_OFF#43601 (>K:ROTOR_BRAKE).
Not sure what to do with it so I tried a new event list in FSUIPC
0=Mobiflight.DC_6_AP_ON etc
It appears in the FSUIPC lists and I can assign it but it doesn’t do anything. It was just a punt and didn’t expect it to.
But no luck. Any ideas?
-
John,
It all works!! Flipping wonderful, you sir are a genius. Now to give Mobiflight some love.
- 1
PMDG DC-6 for MSFS, FSUIPC and events not supported by the normal suspects.
in FSUIPC7 MSFS
Posted
I seem to have solved this (I think). I have set up the following:
All are as simple as picking Rotor Brake from the FSUIPC dropdown list and using the correct parameter
Toggle AP on/off 43401
Toggle AP Handle 40401
Toggle AP alt hold 43601
Pitch nose UP 44008
Pitch nose Down 44007
yaw left 44201 on press and 44204 on release
yaw right 44202 on press and 44204 on release
I think Abort AFE is 29 but not confirmed.
Hope this helps anybody else.