ckovoor

member
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

21 Excellent

About ckovoor

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

544 profile views
  1. Some minor corrections to my post above in red: (1) Left Quadrant Lever 1 is mapped to Spoiler Axis. (2) Left Quadrant Levers 2 and 3 mapped to Throttle Levers 1 and 2. (3) Buttons T3 and T5 on the Left Quadrant are mapped to the TOGA buttons on Throttle Levers 1 and 2 (4) Buttons T4 and T6 on the Left Quadrant are mapped to the THROTTLE CUTOFF LEVERS (toggle) (5) When Buttons T4 and T6 are toggled to the OPEN position, then moving the Throttle Levers 1 and 2 from the IDLE position down into the DETENT slot causes the Throttles to move into the Cutoff Position. Similarly Throttle Levers 1 and 2 can only be moved out of the Cutoff position by first toggling the THROTTLE CUTOFF LEVERS at Buttons T4 and T6 into OPEN. (6) Right Quadrant Levers 1 and 2 mapped to Reverser Levers 1 and 2, giving full range of reverse thrust. The Detent slot is not used. (7) Right Throttle Quadrant Lever 3 is mapped to the Flaps Axis.
  2. THIS POST MIGHT INTEREST THOSE WHO ARE USING TWO SAITEK THROTTLE QUADRANTS I am here giving an outline of how I used FSUIPC4 button/axis programming + LUA scripting to obtain full-range reversers on a second Saitek Throttle Quadrant, as well as realistic mapping of throttle/fuel cutoff levers, and mapping of the throttle/fuel cutoff position(s) to the detent of the throttle lever(s). See the photo: (1) Left Quadrant Lever 1 is mapped to Spoiler Axis. (2) Left Quadrant Levers 2 and 3 mapped to Throttle Levers 1 and 2. (2) Buttons T3 and T5 on the Left Quadrant are mapped to the TOGA buttons on Throttle Quadrants 1 and 2 (3) Buttons T4 and T6 on the Left Quadrant are mapped to the THROTTLE CUTOFF LEVERS (toggle) (4) When Buttons T4 and T6 are toggled to the OPEN position, then moving the Throttle Levers 1 and 2 from the IDLE position down into the DETENT slot causes the Throttles to move into the Cutoff Position. Similarly Throttle Levers 1 and 2 can only be moved out of the Cutoff position by first toggling the THROTTLE CUTOFF LEVERS at Buttons T4 and T6 into OPEN. (5) Right Quadrant Levers 1 and 2 mapped to Reverser Levers 1 and 2, giving full range of reverse thrust. The Detent slot is not used. (6) Right Throttle Quadrant Lever 3 is mapped to the Flaps Axis. Steps (in my setup, the Left Throttle Quadrant is part of my Saitek Pro-Flight Yoke system which is Joystick "K", and Right Throttle Quadrant is Joystick "E". (1) Throttle Axis Range in CRJ Manager: FSUIPC without Reverser Range (2) Here are the relevant parts of my FSUIPC4.ini file [JoyNames] AutoAssignLetters=Yes E=Saitek Pro Flight Quadrant E.GUID={DBCB2B40-097E-11E1-8005-444553540000} K=Saitek Pro Flight Yoke K.GUID={5287F0D0-C921-11E1-8002-444553540000} [LuaFiles] 99=CRJ700box (3) Here is the LUA script entitled CRJ700box.lua ipc.display("CRJ700 BOX actuated",5) -- TQ_TOGA function ASCRJ_TQ_TOGA_1 (joynum, button) ipc.writeLvar("L:ASCRJ_TQ_TOGA_1", 1) end function ASCRJ_TQ_TOGA_2 (joynum, button) ipc.writeLvar("L:ASCRJ_TQ_TOGA_2", 1) end -- TQ_CUTOFF function TQ_CUTOFF_1_TOGGLE (joynum, button) if ipc.readLvar("L:ASCRJ_TQ_CUTOFF_1") == 0 then ipc.writeLvar("L:ASCRJ_TQ_CUTOFF_1", 1) else ipc.writeLvar("L:ASCRJ_TQ_CUTOFF_1", 0) end end function TQ_CUTOFF_2_TOGGLE (joynum, button) if ipc.readLvar("L:ASCRJ_TQ_CUTOFF_2") == 0 then ipc.writeLvar("L:ASCRJ_TQ_CUTOFF_2", 1) else ipc.writeLvar("L:ASCRJ_TQ_CUTOFF_2", 0) end end -- TQ_THROTTLE_1_close function TQ_THROTTLE_1_CLOSE (joynum, button) if ipc.readLvar("L:ASCRJ_TQ_THROTTLE_1_POS") > 395 and ipc.readLvar("L:ASCRJ_TQ_CUTOFF_1") == 0 then ipc.writeLvar("L:ASCRJ_TQ_THROTTLE_1_POS", 500) end end -- TQ_THROTTLE_2_close function TQ_THROTTLE_2_CLOSE (joynum, button) if ipc.readLvar("L:ASCRJ_TQ_THROTTLE_2_POS") > 395 and ipc.readLvar("L:ASCRJ_TQ_CUTOFF_2") == 0 then ipc.writeLvar("L:ASCRJ_TQ_THROTTLE_2_POS", 500) end end -- TQ_REVERSE_1_POS function TQ_REVERSE_1_POS_0 (flag) ipc.writeLvar("L:ASCRJ_TQ_REVERSE_1_POS", 0) end function TQ_REVERSE_1_POS_15 (flag) ipc.writeLvar("L:ASCRJ_TQ_REVERSE_1_POS", 15) end function TQ_REVERSE_1_POS_30 (flag) ipc.writeLvar("L:ASCRJ_TQ_REVERSE_1_POS", 30) end function TQ_REVERSE_1_POS_45 (flag) ipc.writeLvar("L:ASCRJ_TQ_REVERSE_1_POS", 45) end function TQ_REVERSE_1_POS_60 (flag) ipc.writeLvar("L:ASCRJ_TQ_REVERSE_1_POS", 60) end function TQ_REVERSE_1_POS_75 (flag) ipc.writeLvar("L:ASCRJ_TQ_REVERSE_1_POS", 75) end -- TQ_REVERSE_2_POS function TQ_REVERSE_2_POS_0 (flag) ipc.writeLvar("L:ASCRJ_TQ_REVERSE_2_POS", 0) end function TQ_REVERSE_2_POS_15 (flag) ipc.writeLvar("L:ASCRJ_TQ_REVERSE_2_POS", 15) end function TQ_REVERSE_2_POS_30 (flag) ipc.writeLvar("L:ASCRJ_TQ_REVERSE_2_POS", 30) end function TQ_REVERSE_2_POS_45 (flag) ipc.writeLvar("L:ASCRJ_TQ_REVERSE_2_POS", 45) end function TQ_REVERSE_2_POS_60 (flag) ipc.writeLvar("L:ASCRJ_TQ_REVERSE_2_POS", 60) end function TQ_REVERSE_2_POS_75 (flag) ipc.writeLvar("L:ASCRJ_TQ_REVERSE_2_POS", 75) end ------------------------------------------------------------------ event.button("K", 16, "ASCRJ_TQ_TOGA_1") event.button("K", 18, "ASCRJ_TQ_TOGA_2") event.button("K", 17, "TQ_CUTOFF_1_TOGGLE") event.button("K", 19, "TQ_CUTOFF_2_TOGGLE") event.button("K", 21, "TQ_THROTTLE_1_CLOSE") event.button("K", 22, "TQ_THROTTLE_2_CLOSE") event.flag(10, "TQ_REVERSE_1_POS_0") event.flag(11, "TQ_REVERSE_1_POS_15") event.flag(12, "TQ_REVERSE_1_POS_30") event.flag(13, "TQ_REVERSE_1_POS_45") event.flag(14, "TQ_REVERSE_1_POS_60") event.flag(15, "TQ_REVERSE_1_POS_75") event.flag(20, "TQ_REVERSE_2_POS_0") event.flag(21, "TQ_REVERSE_2_POS_15") event.flag(22, "TQ_REVERSE_2_POS_30") event.flag(23, "TQ_REVERSE_2_POS_45") event.flag(24, "TQ_REVERSE_2_POS_60") event.flag(25, "TQ_REVERSE_2_POS_75") (4) Here are the relevant parts of my CRJ700.ini profile, showing Autostart of the LUA and the assignment of axes ranges on the reversers. [Profile] Created=22/08/2017 10:00:51 [Auto] 7=Lua CRJ700box [Axes] 4=EX,256 5=EX,B,10922,16384,L99:S,10 -{ Entering=LuaSet CRJ700box (Flag 10) }- 6=EX,B,5461,10921,L99:S,11 -{ Entering=LuaSet CRJ700box (Flag 11) }- 7=EX,B,0,5460,L99:S,12 -{ Entering=LuaSet CRJ700box (Flag 12) }- 8=EX,B,-5461,-1,L99:S,13 -{ Entering=LuaSet CRJ700box (Flag 13) }- 9=EX,B,-10921,-5462,L99:S,14 -{ Entering=LuaSet CRJ700box (Flag 14) }- 10=EX,B,-16384,-10922,L99:S,15 -{ Entering=LuaSet CRJ700box (Flag 15) }- 11=EY,256 12=EY,B,10922,16384,L99:S,20 -{ Entering=LuaSet CRJ700box (Flag 20) }- 13=EY,B,5461,10921,L99:S,21 -{ Entering=LuaSet CRJ700box (Flag 21) }- 14=EY,B,0,5460,L99:S,22 -{ Entering=LuaSet CRJ700box (Flag 22) }- 15=EY,B,-5461,-1,L99:S,23 -{ Entering=LuaSet CRJ700box (Flag 23) }- 16=EY,B,-10921,-5462,L99:S,24 -{ Entering=LuaSet CRJ700box (Flag 24) }- 17=EY,B,-16384,-10922,L99:S,25 -{ Entering=LuaSet CRJ700box (Flag 25) }- 25=KU,256,D,9,0,0,0 -{ DIRECT: Throttle1 }- 26=KV,256,D,10,0,0,0 -{ DIRECT: Throttle2 }- I would be happy to elaborate on the entire method/scripting if anyone is interested. Regards, Chakko.
  3. ckovoor

    Hotfix 1.0.6

    Well, I am an FSX-SP2 user, and the CRJ 1.0.5.0 + 1.0.6.0 (FIX) works perfectly on my system (Win 7 x64) without the issue you mention.
  4. Sadly, , I have to concur.
  5. ckovoor

    Performance drop w/1.0.1

    I must add my voice to this thread. Performance of 1.0.1.1 is for me FPS-wise between 1.0.0.5c and 1.0.1.0. However, I am confident that Hans will in course of time optimise the code and so improve performance. As the composite photo shows, I operate a networked system of PC's with the CRJ cockpit panels distributed in pseudo-2D format over 6 touchscreens run by my WidevieW-X server: And, as you can guess, I would like to find a way of modifying the NavData files to make Kai Tak accessible via the FMC.
  6. ckovoor

    Performance drop w/1.0.1

    I am sorry, but I have to add my voice to this list....in fact, my symptoms are uncannily like those reported by @PeterZ KCLE EDDN. I experience severe stutters with the periodically dropping frame-rates.
  7. ckovoor

    Displays zoomed in

    Dear Hans, I have found the cause of this 'zoomed display' problem (at least in my own setup). As I have a multi-monitor setup (6 x 1920x1080) in which the Server is generally and exclusively used for 2-D panels (and the scenery views relegated to 8 networked WidevieW Clients) I had unchecked the High-Resolution 3-D virtual cockpit option in FSX/Settings/Display: Selecting the option once again (as above) solved the problems with the displays: However, this comes with a frame-rate hit (especially since I have opened such 3-D views over 6 widescreen monitors. So in order to mitigate this impact I want to request that 2-D popups be also provided for Dave and for the Radio displays, because the popups do not suffer from this problem, even when one uses the 2-D option. This request has been made by other users as well (though for different reasons). Thank you for your help.
  8. ckovoor

    Displays zoomed in

    I am having the same problem. I am running the CRJ in FSX SP2 and Windows 7 x64, and I do not have Ezdok or any other tool which modifies the panel.cfg. I also noticed that I do not have the CRJ under the Add-Ons menu. Please help.