ranm

Ah - I assumed wrongly that a toggle is a press and release action - my bad. I understand now that this is just a change from a previous state. my challenge is that the mobiflight app that I am using only assigns action on an encoder set, and not on release. I was hoping that the toggle action will be translated as a press+release. And the repeats you see in the log are probably due to a noisy hardware button - thanks for tip re-performance, I will check it out. (I need the repeat to simulate a press and hold, and I have to use a key press via an LUA script as the stupid GTN750 gauge I am using doesn't respond to virtual joystick button presses directly - a long story). thanks for your time helping me with this - I can take it from here. Regards - Ran

here is the log with the dialog window closed Regards - Ran FSUIPC6 - Copy.log

I have Pete, and I get the same experience. To test I mapped button 3 i.e. virtual joystick 64 button 2 to the ADF freq swap function and it only works sometimes. I guess I'll stick to using VJoy if this works more reliable for me. Regards - Ran

thanks for looking into this matter further Pete. I realise that this is not right. I am using Mobiflight to write the values in the offset based on buttons connected to an Arduino, and I cannot find the log file, though the Mobiflight console window shows the buttons being pressed. attached are the FSUIPC logs and INI files. I have three buttons programmed in Mobiflight as follows: Button 1: on press : write 0x00014000 to 0x29F0; on release : write 0x00024000 to 0x29F0 Button 2: on press : write 0x00014001 to 0x29F0; on release : write 0x00024001 to 0x29F0 Button 3: on press : write 0x00004002 to 0x29F0; on release : do nothing with the FSUIPC dialog open on the Buttons and Switches page, flicking between button 1 and 2 is instant - the button change shows up in the tab. Getting a response to pressing button 3 is intermittent. I may not be reading the log quite right, but it looks like while offset 0x29F0 is updated with the right value (0x00004002), the button press action isn't (I hops this make sense). the reason I am keen to get the Toggle working is so I could use this with encoders, and unlike for buttons, the Mobiflight app has no option for 'release' - just one action for 'press'). so at present I am using VJoy - but I would like to use the FSUIPC virtual joystick if I can. again, apologies for not being able to find the Mobiflight log. If you want to rule out Mobiflight I'll be happy to try another option for writing the offsets if you can point me in the right direction. thanks again for your help Pete, much appreciated. Regards - Ran PS. I have written down the sequence of buttons I pressed and results - I can send this to you to compare with the log file if this is any help FSUIPC6.ini FSUIPC6.2 - Copy.log

Hi Pete, Just one last note. I noticed that initiating a toggle action straight after another action (for example press and release) doesn't register unless I wait for 4 or 5 seconds. (e.g. setting 0x29F0 offset with the value or 0x00004000 on a press of a button for toggling button 0 on Joystick 64). The logs show no change at 0x29F0 or 0x33F0, unless I wait few seconds before initiating the toggle action. regards - Ran

Thank you Pete for a quick reply don't know what I just did differently to last night but now the button press is picked up in FSUIPC (and of course showing up in the logs). I could swear I used the same values for press and release, but anything could have happened. it was a long day. Thanks again Ran

Hi folks I'm following the documentation trying to use offset 0x29F0 to simulate joystick buttons. E.g. I am writing the value of 0x00014000 to 'press' button 0 on virtual joystick 64. I have enabled monitoring of offset 0x29F0 (well, I think I have) and I can see that the offset is updated with the right value (it is showing the value as 0x14000 - I assume that's the same as 0x00014000). problem is, FSUIPC does not show the button being pressed in the FSUIPC dialog Buttons and switches tab and there is nothing in the buttons and switches log. what am I missing? do I need to enable the FSUIPC virtual joystick feature specifically? I am using the registered version of FSUIPC6 in P3D 4.5. I am setting the value in the offset using Mobiflight based on a button press any assistance will be highly appreciated. Kind regards - Ran

Cheers Pete I would have thought that the 2 'other' axis not supported by FSUIPC are the ones Windows calls Slider1 and Slider2, just because they are coupled together. - never mind. Next time I have my throttle open, I will connect the last two axis to see if one of them shows up as U. - I'm curious now :) I appreciate your help, and thanks again for a great product in FSUIPC. Ran

Hi Pete using JoyView, the axis for the throttle have been discovered as follows (I didn't check FSUIPC but I assume these will be the same): Joystick 3 -------------- throttle 1 - X throttle 2 - Y prop pitch 1 - Z prop pitch 2 - V mixture 1 - missing (persuming should be U - value constant on 32767) mixture 2 - R The plasma controller I use has dedicated connection for a POV switch which I don't use, so it shouldn't be a factor. Thanks again - Ran

Thanks for a quick reply pete Windows XP supports 8 axis joysticks 'out of the box', as I can see all 8 in the Windows XP games controller applet. I'm only using 6 axis anyway: x-axis: throttle 1 y-axis: throttle 2 z-axis: prop pitch 1 x-rotation: prop pitch 2 y-rotation: mixture 1 z-rotation: mixture 2 FSUIPC detects all above but not the y-rotation axis. In any case, I will keep on using the fS assignments as you suggested as that works for now Kind regards - Ran

Hello I've tried using FSUIPC 3536 to achieve a more presice calibration of my home built throttle quadrant. FSUIPC 3536 doesn't seems to pick up the Y-Rotation axis of the joystick. I'm using a Plasma controller, which presents 2 X 8 axis joysticks to Windows XP. It works fine with FS assignments, calibrated with FSUIPC, but I would like to use direct assignment if I could. FSUIPC detects all other axis fine; CH Yoke and Pedals, as well as the plasma's other axis, but not y-rotation, which is Engine 1 mixture :( I turned off the FS joystick off while trying direct assignments, the Y-Rotation shows up in Windows XP and is calibrated OK using Control panel, and as I said, works when assigned from FS (after re-enabling the joystick) Any help would be appreciated Regards - Ran

Yes, sorry - must be too late at night for me :oops: Thanks for a quick reply Ran

Hello I'm using a registered FSUIPC 3.44, and looking at the callibration options, there is no way to calibrate a single throttle for trust reversers. I have just upgraded from FS2002 and FSUIPC 2.95, which allows that by mapping the single throttle to 4!. Is there a workaround? - INI file hack or something else I could do? - I use CH Yoke, and have configured stops on the throttle and prop levers to allow for reversers and prop feather. It worked like a charm in FSUIPC 2.95, and it will be great to get it working again. having only 3 levers on the yoke, I'm a limited to a single throttle lever as I would like to retain a dedictaed throttle, prop and mixture lever control, and be able to map them to all engines (2 or 4, what ever the case may be). looking at previous posts I couldn't find anything that may help. looking forward to your reply Ran