ysav

Now using v4.425 Wanted to use FSUIPC’s calibration as a one stop shop for calibration. Otherwise, I’ll need to first calibrate these axes in window’s game controller calibration. I found your tool more convenient. I’ve now set these as per your recommendation, without using the raw value (elev, aileron and throttle). As for other discrete axes values, I have had them defined in epicinfo.cfg from day 1. All ok on this side. My FCU issue arises only – and still arises - when mapping to 4 throttles. Thank you so much for fixing the Raw issue so fast. I do plan to use it soon - for software assigned values. Thank you ! Yves Savard

I have defined axis assignments using raw axis values. All axes are also sent direct to FSUIPC. The ultimate source is actually fed by EPIC so the IN value is always comprised between 0 and 255. Calibration works just fine. However, when I later return to the FSUIPC configuration window and select the joystick calibration tab, the IN and OUT values are much greater than what I initially calibrated. E.g. the throttle1 calibration will show an IN value of 17800 and OUT value of 16384 whereas after the initial calibration, at the same throttle lever position, it showed an IN value of 97 and an OUT value of 2081. However, if I navigate to the axis assignment tab and immediately back to the joystick calibration tab, then the proper in and out values are shown again. How can I avoid this ? After exiting setup, all is generally fine. From time to time however, I have seen the elevator flicker; when pushing the sidestick forward, it would flicker to the neutral position and back. I am currently having problems with magenta's FCU when the single throttle is mapped to 4 throttles and I am questioning if it is related to the above problem. When engaging auto thrust, the left engine's N1 value sticks to whatever it was at before auto thrust was engaged. FCU obviously struggles to achieve the intended performance. Currently using V4.40. Thanks for your help. Yves Savard

I meant MCP_VS_VAR for vertical speed. Both assignment forms you have suggested work. Wow ! I was stunned to see neg = 0 - pos work ! It is the simplest form but I kept away from it all that time also thinking Epic couldn't handle negatives. Your help was appreciated. Yves Savard

My epicinfo.cfg contains an entry MCP_IAS_VAR=4,1 to communicate the Vspeed to Magenta. The value is set in EPIC tru a nqw command. Works ok for positive values however how do I send a negative value ? Thanks. Yves

Right on ! Since the physical build of my project is an overall slow effort, I find myself adding new EPIC devices from time to time and I have seen a displacement of joysticks in FSUIPS's eyes. I obviously had to remap these buttons in FSUIPC. I will rather attempt to define all anticipated joysticks in EPIC and programatically (EPL) avoid scanning unwired joysticks. I will also configure all in FSUIPC Options and settings rather than epicinfo.cfg (only registered recently). Q: Is the likelyhood of missing a button pulse reduced whilst using nqw(BtnP, n) rather than rely on the Windows joystick API to @relay@ it ? Thanks for the great support. Yves

Hello Peter, Pressing a button on my (Epic) joystick no. 5 shows under joystick no. 11 in FSUIPC's Options and settings window. However, if I choose to assign the same physical button tru FS2004's own Control Assignments window, I can do the assignment under the 5th joystick in the list - as I would expect. Is there a pattern to observe/anticipate ? Regards, Yves