Hi all -
Can someone tell me what does the “SimMAPPower” keyboard call-back do?
I imagine that it toggles MAP Power on/off. But more to the point, what is MAP, and how does it’s power state manifest in the sim?
Hi all -
Can someone tell me what does the “SimMAPPower” keyboard call-back do?
I imagine that it toggles MAP Power on/off. But more to the point, what is MAP, and how does it’s power state manifest in the sim?
Thanks I3, Stubbies -
I tinkered with TARGET briefly to turn-off the dang LEDs at computer wake-up. But haven’t done much with in since -
Morphine’s TARGET set-up seems very highly regarded! Will check it out (once I figure out where to find it for download)
Hi all -
It looks like this thread has run its course; but I can’t help but chime in -
I am trying to take advantage of TM WH’s Idle Detent feature. I’m running with Hardware > Idle Cutoff un-checked in the launcher’s configuration, and have managed to set-up DX in the key file such that “SimThrottleIdleDetent” is asserted both on activating (‘pressing’) and on de-activating (‘releasing’) TM WH’s Idle Detent ‘button’. Note that TM WH’s Idle Detent occurs entirely below the minimum throttle position -
What I’ve realized is that “SimThrottleIdleDetent” appears to work like a STROBE rather than like a TOGGLE. That is, it doesn’t appear to TOGGLE a state (Idle Detent) on/off, but instead appears to kick-off an action (based on throttle position as described in Frederf’s 9/26 post “That’s the key word, expect …”). This threw me a curve, as it seems fundamentally different from the real jet’s distinct idle cut-off latch states (latched or un-latched). In retrospect, the action is apparent from absence of e.g. “IdleCutOff_ON” and “IdleCutOff_OFF” call backs.
And I see per Red Dog’s 9/26 post “The [SimThrottleIdleDetent] is just a software detent overcoming that issue [of users that don’t have physical detents in their throttle]” (i.e. the call-back appears to be a work-around). But for TM WH owner’s, using the physical detent feature seems at first to be the default choice -
But I would say that it doesn’t quite play out correctly:
(the bit about having to diddle the throttle before sim will recognize it is omitted from below)
in the jet, with engine running (on tarmac) -
roll back TM WH throttle to idle (lowest position) -
assert “SimThrottleIdleDetent” (in my case, lift and pull throttle back to detent position)
assert “SimJfsStart” -
assert “SimThrottleIdleDetent” (in my case, lift and push throttle back out of detent)
*** AT THIS POINT, I’d expect the engine to begin spooling up to idle, since I’ve taken it out of ‘detent’ ***
move throttle position up a bit (but not yet above the GUI-defined idle cut-off position)
assert “SimThrottleIdleDetent” (this time, via keyboard)
move throttle position up a bit more (this time to above the GUI-defined idle cut-off position)
*** AT THIS POINT, I might also expect the engine to begin spooling up ***
assert “SimThrottleIdleDetent” (this time, via keyboard)
pull back throttle to idle position
Even though I have a reasonably representative ‘idle detent’ feature in the ThrustMaster WartHog throttle, the BMS code still seems to require a key_stroke “SimThrottleIdleDetent” to kick-off the engine spool-up (the TM WH detent feature cannot occur with throttle off of minimum axis position). And this seems to be BECAUSE “SimThrottleIdleDetent” is implemented as a STROBE rather than a TOGGLE. And I don’t think there’s any KeyFile magic that can turn a STROBE into a TOGGLE (because a STROBE fundamentally doesn’t know about ‘assert’ and ‘de-assert’) -
Well, it has been ‘fun’ reading these posts (especially the real jet videos), and figuring out how this jet start works -
And now that I know, … it’s all good! Hope the above helps others understand it as well -
Hi -
“why do I use TRIM/AP switch?”
I’ve been tinkering with keyboard layout that I find more-intuitive for the very many controls; it has helped me to explore all the different capabilities of this great sim! So far, I’ve been able to understand / straighten out all of the oddities that I created in tinkering with the assignments. But in working through panels, checking assignments, this is one aspect that I’ve stumbled upon and haven’t been able to reconcile. So I thought I’d ask -
Its just a curiosity; not essential to flying the jet or enjoying the sim.
But if my key-file or config. settings were responsible, I’d want to understand and fix it.
Hi -
Thanks for comments. TO-BMS1F-16CM-1.pdf p.17 that describes the MANUAL TRIM panel, and the TRIM A/P DISC switch says: “In DISC the stick trims and the autopilot are inhibited. Manual trim remains operative.” But my set-up seems to behave differently. That’s why I posed the question -
Update: I ran with “BMS - Basic.key” that is un-altered from U1 installation, and operated the MANUAL TRIM panel only with mouse clicks. Same behavior that I described below. So at least its not my key file -
I’d be interested if anyone else can confirm same behavior?
Hi -
4.33_U1: I’ve found that with TRIM PANEL’s TRIM AP/DISC switch in the DISC position, manual trim via keyboard (e.g. the SimTrim… call backs) DO move the dials on the MANUAL TRIM PANEL, but DO NOT alter the flight trajectory. If I flip TRM AP/DISC back to NORM position, whatever trim settings showing on the MANUAL TRIM PANEL suddenly take effect. Is this normal operation, or do I have a bug in my keymap file or elsewhere? My related keymap file entries are as shown here:
…
#===================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “2.04 MANUAL TRIM PANEL”
SimTrimRollLeft 309 0 0XD3 5 0 0 1 “TRIM: ROLL TRIM Wheel - L WING DN”
SimTrimRollRight 309 0 0XD1 5 0 0 1 “TRIM: ROLL TRIM Wheel - R WING DN”
SimTrimAPDisc 310 0 0X1E 5 0 0 1 “TRIM: TRIM/AP DISC Switch - Toggle”
SimTrimAPDISC 310 0 0XFFFFFFFF 0 0 0 1 “TRIM: TRIM/AP DISC Switch - DISC”
SimTrimAPNORM 310 0 0XFFFFFFFF 0 0 0 1 “TRIM: TRIM/AP DISC Switch - NORM”
SimTrimYawLeft 116 0 0XD2 5 0 0 1 “TRIM: YAW TRIM Knob - L”
SimTrimYawRight 116 0 0XC9 5 0 0 1 “TRIM: YAW TRIM Knob - R”
SimTrimNoseUp 309 0 0XCF 5 0 0 1 “TRIM: PITCH TRIM Wheel - NOSE UP”
SimTrimNoseDown 309 0 0XC7 5 0 0 1 “TRIM: PITCH TRIM Wheel - NOSE DN”
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -0 “REM: Trim-Reset (change @ CKPIT)”
…
#===================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “5.11 FLIGHT STICK”
AFElevatorTrimUp -1 0 0XFFFFFFFF 0 0 0 1 “STICK: TRIM Up - Nose Down”
AFElevatorTrimDown -1 0 0XFFFFFFFF 0 0 0 1 “STICK: TRIM Down - Nose Up”
AFAileronTrimLeft -1 0 0XFFFFFFFF 0 0 0 1 “STICK: TRIM Left - Roll Left”
AFAileronTrimRight -1 0 0XFFFFFFFF 0 0 0 1 “STICK: TRIM Right - Roll Right”
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -0 " REM: Trim-Reset (change @ CKPIT)"
…
#===================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 “9.10 STICK POV HAT - Normal”
AFElevatorTrimUp 0 -1 -3 0 0X00 -1 “STICK: POV Up”
SimDoNothing 0 -1 -3 1 0X00 -1 “STICK: POV Up-Right”
AFAileronTrimRight 0 -1 -3 2 0X00 -1 “STICK: POV Right”
SimDoNothing 0 -1 -3 3 0X00 -1 “STICK: POV Right-Down”
AFElevatorTrimDown 0 -1 -3 4 0X00 -1 “STICK: POV Down”
SimDoNothing 0 -1 -3 5 0X00 -1 “STICK: POV Down-Left”
AFAileronTrimLeft 0 -1 -3 6 0X00 -1 “STICK: POV Left”
SimDoNothing 0 -1 -3 7 0X00 -1 “STICK: POV Left-Up”
…
W7x64 or XPx32 - which will run BMS’ Falcon better -
DOS 5 on 486DX2 still runs JFII