Menachem Posted January 11, 2013 Report Posted January 11, 2013 Hi pete not all the toggles i can assign as macro for example , t try to assign the guard of the emergency toggle and when i close the guard with the mouse the left upper windows doesn't appear thanks Menachem
Andydigital Posted January 12, 2013 Report Posted January 12, 2013 The NGX doesn't support Mouse Macros, you have to use the NGX SDK provided by PMDG and L:Vars, Lua scripts etc. You should also look at the free program LINDA, they already have an extensive collection of scripts that do all the hard work for you, converting the lua scripts to work directly with FSUIPC is simple but tedious, so using them via LINDA itself is far easier. http://forum.avsim.net/forum/424-linda/
Pete Dowson Posted January 14, 2013 Report Posted January 14, 2013 Apologies for the delay in replying. As announced, I have been away on holidays. The NGX doesn't support Mouse Macros, you have to use the NGX SDK provided by PMDG and L:Vars, Lua scripts etc. However, for almost all switches, knobs, etc, the update for the NGX which included the SDK documented all of the control numbers needed, and these can be assigned directly, by number, in recent versions of FSUIPC4. The list is in the .h file provided by PMDG in the SDK subfolder. You don't really need any Lua or L:Var implementatin. Regards Pete
Menachem Posted January 14, 2013 Author Report Posted January 14, 2013 Thanks Pete I use ngx_h file and i assigned most of the switches by using the offset but some of them don't have assignment in this file. some of the switches i used the mouse macro, so i still had some switches without assignment. what did you mean in "can be assigned directly, by number" Menachem
Pete Dowson Posted January 14, 2013 Report Posted January 14, 2013 I use ngx_h file and i assigned most of the switches by using the offset but some of them don't have assignment in this file. Sorry, but the offsets for the NGX are not writable. I assume you must mean control number, not offset? what did you mean in "can be assigned directly, by number" When you assign a button, key or switch, in the assignment drop down you can select <custom control> (at the top of the list) and enter the control number (range 65536-131070), as derived from that .h file. Pete
Menachem Posted January 14, 2013 Author Report Posted January 14, 2013 yes you right i mean control number. the problem is that there are no lines for all the switches, for example 'start switch' so for that i used mouse macro and it works. there are two lines with numbers for the emergency guard ( 69632+101= 69733 ) and "battery guard" ( 69632+2 = 69634) but even i enter those numbers and parameter 1 they don't work and for those guards the mouse macro doesn't work too so i thought there is another way. Menachem
Pete Dowson Posted January 14, 2013 Report Posted January 14, 2013 the problem is that there are no lines for all the switches, for example 'start switch' so for that i used mouse macro and it works. Okay. But try also FSUIPC's Event logging and operate the switch and see what numbers it uses. It is probably related to the parameter value. What about EVT_OH_LIGHTS_L_ENGINE_START EVT_OH_LIGHTS_R_ENGINE_START I think those are the starter controls. Maybe parameters 0-3, or some others based on the MOUSE_FLAGs? Pete
Andydigital Posted January 14, 2013 Report Posted January 14, 2013 From another section of the .h this is mentioned; unsigned char ENG_StartSelector[2]; // 0: GRD 1: OFF 2: CONT 3: FLT[/CODE]Don't know if its of any help but VRinsight do have the start switches working perfectly on their V737 Overhead panel hardware.
Pete Dowson Posted January 14, 2013 Report Posted January 14, 2013 From another section of the .h this is mentioned; unsigned char ENG_StartSelector[2]; // 0: GRD 1: OFF 2: CONT 3: FLT[/CODE].Yes, but of course that is read-only. However, it does give a hint as to what the EVT parameters may be.RegardsPete
Menachem Posted January 14, 2013 Author Report Posted January 14, 2013 Okay. But try also FSUIPC's Event logging and operate the switch and see what numbers it uses. It is probably related to the parameter value. What about EVT_OH_LIGHTS_L_ENGINE_START EVT_OH_LIGHTS_R_ENGINE_START I think those are the starter controls. Maybe parameters 0-3, or some others based on the MOUSE_FLAGs? Pete what are the control number for those two lines ?
Andydigital Posted January 14, 2013 Report Posted January 14, 2013 119 left and 121 right + 69632 so; Left 69751 Right 69753 Then parameter 0 to 3 depending on what state you want to set the switch to.
Menachem Posted January 14, 2013 Author Report Posted January 14, 2013 119 left and 121 right + 69632 so; Left 69751 Right 69753 Then parameter 0 to 3 depending on what state you want to set the switch to. thanks it works ! par: 0-grd , 1-off, 2-cont where did you find the numbers ?
Andydigital Posted January 14, 2013 Report Posted January 14, 2013 If you look in the folder; ....Microsoft Games\Microsoft Flight Simulator X\PMDG\PMDG 737 NGX\SDK and open the file "PMDG_NGX_SDK.h" with something like Notepad. Search for; EVT_OH_LIGHTS_L_ENGINE_START You will see at the end of the line it says; (THIRD_PARTY_EVENT_ID_MIN + 119) 119 is the number you have to add to the number 69632 to get the correct control number to input into FSUIPC. For the parameter I searched nearer the beginning of the file and found; unsigned char ENG_StartSelector[2]; // 0: GRD 1: OFF 2: CONT 3: FLT
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now