John Dowson Posted Tuesday at 09:41 AM Report Posted Tuesday at 09:41 AM I have done some further testing on writing to offsets 0x3110 (for control number) an4 0x3114 for the parameter, and this works as expected, i.e. the control is always sent when writing to offset 0x3110, even if its the same control number, and if the parameter in 0x3114 has been changed or not - whatever that offset holds when 0x3110 is triggered will be used. This is the case in the current released version, so that patched version I attached is not actually needed. So if you are seeing different behavior when writing to these offsets via SIOC, then it is an issue with SIOC. John
AlMassimo Posted Tuesday at 10:47 PM Author Report Posted Tuesday at 10:47 PM Thanks John, an extraordinarily clear and exhaustive explanation and let say "tutorial". I learnt a lot of things, and now all seems a lot clearer (or I hope so). My cockpit is now working at 99.5%, after a lot of years I decided to buy an FMC and since the one procuced by Winwing is more than affordable I bought one and it was delivered in less than a week. With SimAppPro it works like a charm. It is a big step forward for me. In the next months I will try to use it for different planes. I have no idea if the keypresses can be captured and handled outside SimAppPro, maybe by Fsuipc... but for sure the display is a totally different story! Anyway, thanks for your great support. It is a pleause seeing how deep is your knowledge and understanding of how MSFS and many other programs work and interact with or by Fsuipc, lua, etc. Have a good day. Massimo
Byronb Posted Thursday at 01:36 PM Report Posted Thursday at 01:36 PM After following this topic its still beyond me i think i need an Encoder Setup for Dummies. I have a leo Bodnar Encoder and have used preset PMDG B737 MCP FO CRS turn left decr. right for incr. that goes 1 degree at a time how can i make it go 10 degrees at a time. When i was Using LINDA there was an option to use the push button as a shift key for fast or slow. Is there a lua if so how do i get that to work. Brian
John Dowson Posted Thursday at 03:41 PM Report Posted Thursday at 03:41 PM There are various methods to have fast & slow inc/dec on a rotary button, and this depends on the rotary and what button events it sends out. Some rotaries have two buttons in each direction, one triggered on a slow move and another on a fast move. For such rotaries, you can assign the slow buttons to the small inc/dec and the fast buttons to the larger inc/dec controls. For rotaries that have only one button in each direction, you can either: 1. Use a lua script to convert the single button press/release to two virtual buttons, one for fast and another for slow, and then assign to the virtual buttons. There is an example script provided that does this (will need configuring for your system), called Rotaries.lua. 2. You can overload the buttons to have both fast and slow in/decs, and then use a compound condition on the assignment so that only one of these is fired depending upon the state of another button or offset. You could also do this on the state of a key press, but to do this the keypress would set an FSUIPC offset and then the inc/dec assignment would use a compound condition on this offset, and the key release would then clear the offset. Note also that some rotaries alternate between sending out button presses and button releases. For such rotaries, you need to assign to both the press and release. You also need to determine what to send for the fast increment/decrements. FSUIPC does provide some fast controls (e.g. Heading Bug Inc Fast, Heading Bug Dec Fast), but I doubt these work with PMDG. The simplest thing to do would be to send the same control that you use for the slow inc/dec, but send it multiple times (e.g. duplicate the fast assignment line 10 times, changing the index number for the assignment so that it is unique, to send the control 10x). Alternatively, you could have a lua script that read the current left/right course value, applies whatever delta you need to that, and then send that. The current course headings are held in the PMDG-specific offset 0x6520: Quote 6520 4 WORD x 2 MCP_Course[2 and the following PMDG custom controls allow you to set the course directly: Quote // MCP Direct Control #define EVT_MCP_CRS_L_SET (THIRD_PARTY_EVENT_ID_MIN + 14500) // Sets MCP course specified by the event parameter #define EVT_MCP_CRS_R_SET (THIRD_PARTY_EVENT_ID_MIN + 14501) John
John Dowson Posted Thursday at 04:50 PM Report Posted Thursday at 04:50 PM 3 hours ago, Byronb said: I have a leo Bodnar Encoder and have used preset PMDG B737 MCP FO CRS turn left decr. right for incr. that goes 1 degree at a time how can i make it go 10 degrees at a time. I have just looked into this further. I have rotaries with two buttons in each direction, for fast and slow, and the rotary alternates between sending button press and release events. If I assign both the fast and slow inc/clockwise buttons to the preset PMDG_B737_MCP_FO_CRS_INC on both press and release (with a similar assignment for the dec), then I can get single increments when turning slowly, and large increments (>100) if I turn fast. No need to overload the assignments to send multiple controls. 1 hour ago, John Dowson said: Alternatively, you could have a lua script that read the current left/right course value, applies whatever delta you need to that, and then send that. The current course headings are held in the PMDG-specific offset 0x6520: Quote 6520 4 WORD x 2 MCP_Course[2 Not sure what these offsets hold, but it is not the actual course set, so this cannot be used.
Byronb Posted Thursday at 05:35 PM Report Posted Thursday at 05:35 PM Thanks John for your time and effort in your reply but l,m afraid It still goes way over my head and wouldn’t know where to start. I have used the hdg fast and slow but that was because they were an option in the drop down list. Parameters offsets & script’s I’ve looked at the manual and examples but I just can’t grasp it and at 83 I think l,m past learnings. The one thing in my favour is I,m not pushed for time so moving just 1 degree isn’t the end of the world. Thanks again Brian.
John Dowson Posted Thursday at 06:09 PM Report Posted Thursday at 06:09 PM 30 minutes ago, Byronb said: Thanks John for your time and effort in your reply but l,m afraid It still goes way over my head and wouldn’t know where to start. Its not that difficult.... First, do your rotaries have 1 or two buttons on each direction? You can check this in the FSUIPC button assignments window - do you see different buttons registered if you turn fast and slow, or just the one button regardless of speed (try a few times)? If just one button, do you want to use a different button or key press to switch between slow and fast selection? And do your rotary buttons emit just presses, or alternate press and releases? If you show me your assignments (FSUIPC7.ini file), I can help you set this up. John
Byronb Posted Friday at 12:33 PM Report Posted Friday at 12:33 PM The encoders just have one button in either direction ie rotate ccw button 17 cw button 16, Pressing the knob is button 18 Pressing the knob and rotating still only shows 17 & 16 The flight sim is MSFS 2024 PMDG 737 is the 2020 version , all the FSUIPC presets on my Home made panels work. FSUIPC7.ini
John Dowson Posted Friday at 01:14 PM Report Posted Friday at 01:14 PM 43 minutes ago, Byronb said: Pressing the knob is button 18 Pressing the knob and rotating still only shows 17 & 16 On the same controller? If not, which controller? How many button box interfaces do you have? Your ini shows 4 detected: Quote 3=Button Box Interface 2 3.GUID={A51AF430-7D8A-11EE-8001-444553540000} 4=Button Box Interface 2 4.GUID={A51AF430-7D8A-11EE-8002-444553540000} 6=Button Box Interface 2 6.GUID={A51B1B40-7D8A-11EE-8003-444553540000} 7=Button Box Interface BBI-64 7.GUID={FEBCBA10-2445-11F0-8001-444553540000} but you also have assignments to another one that is no longer detected: Quote D=Button Box Interface 1 << MISSING JOYSTICK >> D.GUID={23804ED0-1E00-11F0-8002-444553540000} You have several assignments to this that will not be working: Quote [Buttons] ... 48=PD,29,C65752,0 -{PARKING_BRAKES}- ... 51=PD,25,C66080,0 -{GEAR_DOWN}- 52=PD,24,C66079,0 -{GEAR_UP}- ... 57=PD,23,C66904,0 -{AUTOPILOT_DISENGAGE_TOGGLE}- .. 80=PD,30,C66379,0 -{TOGGLE_NAV_LIGHTS}- 81=PD,27,CPLSK1_-_Pilot_-_Push,0 -{Preset Control}- ... [Buttons. PMDG 737-600] ... 64=PD,24,CPPMDG_B737-7_GEAR_UP,0 -{Preset Control}- 65=UD,24,CPPMDG_B737-7_GEAR_OFF,0 -{Preset Control}- ... 68=PD,19,CPPMDG_B737-7_FUEL_PUMP_CTR_L_OFF,0 -{Preset Control}- 69=UD,19,CPPMDG_B737-7_FUEL_PUMP_CTR_L_ON,0 -{Preset Control}- 70=PD,17,CPPMDG_B737-7_FUEL_PUMP_CTR_R_OFF,0 -{Preset Control}- 71=UD,17,CPPMDG_B737-7_FUEL_PUMP_CTR_R_ON,0 -{Preset Control}- Looks like that device is now the K device (Button Box Interface BBI-64) as you have re-assigned some of those buttons to that. In the attached ini, I have removed those assignments to the missing device that were re-assigned, and updated the remainder to use the K device. I have also added assignments to send the CRS inc/dec on a button release to see if this improves things. If you let me know which device has button 18 that you want to use for fast inc/dec then I can add that for you. Note also that you have several assignments to PMDG 737 presets in your general profile. These should really be in your PMDG profile - shall I move these across for you as well? John FSUIPC7.ini
Byronb Posted Friday at 01:27 PM Report Posted Friday at 01:27 PM Thanks John Yes i have 4 button boxes i had to change a faulty one and installed the BB 64 Please tidy up the PMDG presets The button press is G 18 Brian
John Dowson Posted Friday at 02:02 PM Report Posted Friday at 02:02 PM 2 minutes ago, Byronb said: The button press is G 18 Ok. But be aware that is assigned in your general profile to start the ipcReady.lua: Quote 91=PG,18,CL1:R,0 -{Lua ipcReady}- Not sure why you would want an assignment to start/restart that, as it is started by default once an aircraft is loaded. I will remove that. Please try the attached and let me know how it goes. When you hold button G18, the inc/dec should be 10x faster. John FSUIPC7.ini
Byronb Posted Friday at 02:42 PM Report Posted Friday at 02:42 PM Thanks John Not working i'm afraid Button G18 on press the Degree jumps x 2 ie 170-172 on rotation in reverts to 1 at a time. The decrease button G17 doesn't work at all nor when G18 is held. Brian
John Dowson Posted Friday at 03:12 PM Report Posted Friday at 03:12 PM 26 minutes ago, Byronb said: Button G18 on press the Degree jumps x 2 ie 170-172 on rotation in reverts to 1 at a time. The decrease button G17 doesn't work at all nor when G18 is held. That is very strange...Nothing should happen when G18 is pressed on its own. Could you please activate logging for Buttons & Keys, and show me/attach an FSUIPC7.log file showing those issues, and also attach your current FSUIPC7.ini file. John
John Dowson Posted Friday at 03:31 PM Report Posted Friday at 03:31 PM Also set WAPI Debug level logging (Log->WAPI->Debug) and use the following ini: FSUIPC7.ini
Byronb Posted Friday at 03:35 PM Report Posted Friday at 03:35 PM Ok will get back to you tomorrow Brian
John Dowson Posted Friday at 03:48 PM Report Posted Friday at 03:48 PM 13 minutes ago, Byronb said: Ok will get back to you tomorrow Ok, no problem.
Byronb Posted Saturday at 09:10 AM Report Posted Saturday at 09:10 AM Good Morning John log files as requested log 1 is the log from first attempt. Looking at log file i didn't know LINDA was working in the back ground. Brian FSUIPC7.ini FSUIPC7.log FSUIPC71.log
John Dowson Posted Saturday at 12:07 PM Report Posted Saturday at 12:07 PM The log file shows that the assignments are working as expected: - pressing button 16 without 18 being pressed sends one inc preset: Quote 53890 Button changed: bRef=0, Joy=3 (G), Btn=16, Pressed 53890 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 86=CP(-G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 53890 .... Condition (-G,18) = TRUE 53890 [DEBUG]: Calculator code sent: 40907 (>K:ROTOR_BRAKE) 53890 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 108=CP(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 53890 .... Condition (+G,18) = FALSE 53890 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 109=CP(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 53890 .... Condition (+G,18) = FALSE 53890 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 110=CP(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 53890 .... Condition (+G,18) = FALSE 53890 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 111=CP(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 53890 .... Condition (+G,18) = FALSE 53890 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 112=CP(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 53890 .... Condition (+G,18) = FALSE 53968 Button changed: bRef=0, Joy=3 (G), Btn=16, Released 53968 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 118=CU(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 53968 .... Condition (+G,18) = FALSE 53968 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 119=CU(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 53968 .... Condition (+G,18) = FALSE 53968 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 120=CU(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 53968 .... Condition (+G,18) = FALSE 53968 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 121=CU(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 53968 .... Condition (+G,18) = FALSE 53968 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 122=CU(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 53968 .... Condition (+G,18) = FALSE - pressing button 17 without 18 being pressed sends one dec preset Quote 60984 Button changed: bRef=0, Joy=3 (G), Btn=17, Pressed 60984 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 84=CP(-G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 60984 .... Condition (-G,18) = TRUE 60984 [DEBUG]: Calculator code sent: 40908 (>K:ROTOR_BRAKE) 60984 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 88=CP(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 60984 .... Condition (+G,18) = FALSE 60984 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 89=CP(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 60984 .... Condition (+G,18) = FALSE 60984 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 90=CP(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 60984 .... Condition (+G,18) = FALSE 60984 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 91=CP(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 60984 .... Condition (+G,18) = FALSE 60984 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 92=CP(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 60984 .... Condition (+G,18) = FALSE 61062 Button changed: bRef=0, Joy=3 (G), Btn=17, Released 61062 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 98=CU(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 61062 .... Condition (+G,18) = FALSE 61062 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 99=CU(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 61062 .... Condition (+G,18) = FALSE 61062 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 100=CU(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 61062 .... Condition (+G,18) = FALSE 61062 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 101=CU(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 61062 .... Condition (+G,18) = FALSE 61062 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 102=CU(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 61062 .... Condition (+G,18) = FALSE - pressing button 16 with button 18 pressed sends 10 inc presets: Quote 67312 Button changed: bRef=0, Joy=3 (G), Btn=16, Pressed 67312 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 86=CP(-G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 67312 .... Condition (-G,18) = FALSE 67312 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 108=CP(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 67312 .... Condition (+G,18) = TRUE 67312 [DEBUG]: Calculator code sent: 40907 (>K:ROTOR_BRAKE) 67312 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 109=CP(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 67312 .... Condition (+G,18) = TRUE 67312 [DEBUG]: Calculator code sent: 40907 (>K:ROTOR_BRAKE) 67312 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 110=CP(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 67312 .... Condition (+G,18) = TRUE 67312 [DEBUG]: Calculator code sent: 40907 (>K:ROTOR_BRAKE) 67312 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 111=CP(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 67312 .... Condition (+G,18) = TRUE 67312 [DEBUG]: Calculator code sent: 40907 (>K:ROTOR_BRAKE) 67312 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 112=CP(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 67312 .... Condition (+G,18) = TRUE 67312 [DEBUG]: Calculator code sent: 40907 (>K:ROTOR_BRAKE) 67406 Button changed: bRef=0, Joy=3 (G), Btn=16, Released 67406 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 118=CU(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 67406 .... Condition (+G,18) = TRUE 67406 [DEBUG]: Calculator code sent: 40907 (>K:ROTOR_BRAKE) 67406 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 119=CU(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 67406 .... Condition (+G,18) = TRUE 67406 [DEBUG]: Calculator code sent: 40907 (>K:ROTOR_BRAKE) 67406 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 120=CU(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 67406 .... Condition (+G,18) = TRUE 67406 [DEBUG]: Calculator code sent: 40907 (>K:ROTOR_BRAKE) 67406 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 121=CU(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 67406 .... Condition (+G,18) = TRUE 67406 [DEBUG]: Calculator code sent: 40907 (>K:ROTOR_BRAKE) 67406 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 122=CU(+G,18)G,16,CPPMDG_B737_MCP_FO_CRS_INC,0 67406 .... Condition (+G,18) = TRUE 67406 [DEBUG]: Calculator code sent: 40907 (>K:ROTOR_BRAKE) - pressing button 17 with button 18 pressed sends 10 dec presets: Quote 74296 Button changed: bRef=0, Joy=3 (G), Btn=17, Pressed 74296 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 84=CP(-G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 74296 .... Condition (-G,18) = FALSE 74296 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 88=CP(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 74296 .... Condition (+G,18) = TRUE 74296 [DEBUG]: Calculator code sent: 40908 (>K:ROTOR_BRAKE) 74296 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 89=CP(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 74296 .... Condition (+G,18) = TRUE 74296 [DEBUG]: Calculator code sent: 40908 (>K:ROTOR_BRAKE) 74296 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 90=CP(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 74296 .... Condition (+G,18) = TRUE 74296 [DEBUG]: Calculator code sent: 40908 (>K:ROTOR_BRAKE) 74296 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 91=CP(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 74296 .... Condition (+G,18) = TRUE 74296 [DEBUG]: Calculator code sent: 40908 (>K:ROTOR_BRAKE) 74296 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 92=CP(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 74296 .... Condition (+G,18) = TRUE 74296 [DEBUG]: Calculator code sent: 40908 (>K:ROTOR_BRAKE) 74375 Button changed: bRef=0, Joy=3 (G), Btn=17, Released 74375 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 98=CU(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 74375 .... Condition (+G,18) = TRUE 74375 [DEBUG]: Calculator code sent: 40908 (>K:ROTOR_BRAKE) 74375 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 99=CU(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 74375 .... Condition (+G,18) = TRUE 74375 [DEBUG]: Calculator code sent: 40908 (>K:ROTOR_BRAKE) 74375 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 100=CU(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 74375 .... Condition (+G,18) = TRUE 74375 [DEBUG]: Calculator code sent: 40908 (>K:ROTOR_BRAKE) 74375 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 101=CU(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 74375 .... Condition (+G,18) = TRUE 74375 [DEBUG]: Calculator code sent: 40908 (>K:ROTOR_BRAKE) 74375 [Buttons.PMDG 737-600 PMDG House (N736PM | 2021)] 102=CU(+G,18)G,17,CPPMDG_B737_MCP_FO_CRS_DEC,0 74375 .... Condition (+G,18) = TRUE 74375 [DEBUG]: Calculator code sent: 40908 (>K:ROTOR_BRAKE) So the assignments are working as expected. What do you actually see on slow/fast clockwise/anticlockwise rotary movements? Are he slow ones now at least working. incrementing and decrementing by 1? Do you see any change when also using button G18 (i.e. the fast/larger in/dec)?
Byronb Posted Saturday at 01:45 PM Report Posted Saturday at 01:45 PM The slow ones now at least working. incrementing and decrementing by 1 yes they are. G18 (i.e. the fast/larger in/dec they increase & decrease by 40 So thats working but could you set the fast x 10 without going to much trouble. Brian
John Dowson Posted Saturday at 02:03 PM Report Posted Saturday at 02:03 PM 10 minutes ago, Byronb said: G18 (i.e. the fast/larger in/dec they increase & decrease by 40 That's rather strange, as only 10 presets are sent each time - well, 10 on press and 10 on release, so maybe 20. So I am not sure why 1 "fast" inc/dec would change by 40. 9 minutes ago, Byronb said: So thats working but could you set the fast x 10 without going to much trouble. You can adjust this yourself - just remove some of the fast inc/dec assignment lines from your ini. Try with the release assignments removed, i.e. the ones that start with 'CU'. Note that you can edit the ini with FSUIPC7 running so you can adjust this and test without restarting. Just make sure that the button assignment panel/window is open when you edit the ini, and once you have saved your changes, click the Reload all buttons button to reload the updated ini and then test. You can repeat and add or remove more assignments until it inc/decs how you would like it to. John
Byronb Posted Saturday at 02:59 PM Report Posted Saturday at 02:59 PM Thanks John Followed your instructions and now works great Thanks for your time and knowhow. I started Flight Sim about 20 years ago and using the mouse didn't appeal so building switch panels became part of the hobby, but it was only with FSUIPC with yourself and Pete (hope he is keeping well) that i could get them to work. Kind Regards Brian 1
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