John Dowson

Thanks! Ok, thats good. For overly sensitive controls, some folks have also found that extending the range of the axis, so that you get less movement in the sim, works for them. You can do this by editing the ini. So, for example, this is my Rudder calibration entry (in the [JoystickCalibration] section, and also any [JoystickCalibration.<profile>] sections: Rudder=-16384,-650,768,16255 If I extend the max/min entries thus: Rudder=-20384,-650,768,20255 you then get less travel in the sim for that axis. The downside, of course, is that you loose the full range of the axis. Some people find this useful, but it depends on the controls and aircraft. Just FYI, something else to try if curves on their own don't give you what you need.

I'll take a look at the A320 FBW to see what works for these and let you know...may take me a day or so to get around to this though as I've a few issues to sort out first.

Are you sure that lvar exists? Just took a look at the lvars in the FBW A320, and it doesn't exist in the stable mod at least. Can you see it if you list the lvars (Add-ons->WASM->List Lvars)? These are the only A32NX_AUTOPILOT_* lvars I can see: A32NX_AUTOPILOT_APPR_MODE = 0.000000 A32NX_AUTOPILOT_FPA_SELECTED = 0.000000 A32NX_AUTOPILOT_LOC_MODE = 0.000000 A32NX_AUTOPILOT_TRACK_SELECTED:1 = 90.653481

You can zip it. That log file you posted doesn't contain anything useful. But, as I said, if assigning in MobiFlight, you need MobiFlight support, not FSUIPC support. And if assigning in FSUIPC, I need to see your FSUIPC7.ini file as well as the log. So no point in posting the log file really at the moment. As Pete has said, it just looks like you are using the heading as a signed value when it should be unsigned. That shouldn't be too difficult to trace.... And I still don't know why you said Alt+F isn't working, and there is no FSUIPC icon in your system tray.... that log file you did post shows the Alt+F hot key is registered:

Please try the attached version, v7.2.0b: FSUIPC7.exe I have only added the Light Potentiometer Set control. I will add the specific number ones (1-30) if/when requested. John

But what have you actually tried? What do you mean by 'Offset procedure'? Do you mean the new facility to add lvars to offsets? If so, that is only available in the latest 7.2.0a beta release - have you tried that? It is difficult for me to help you when you are not explaining what you have tried. Just saying 'nothing...' and 'I can't customize' doesn't help me. I need to know what you have tried, and what you see, and also see your logs and ini files (attached preferably, not selected contents pasted). And as I said, if using lvars/hvars, test them first using the facilities provided. Did you do that?

You posted your log file, but it was a continuation log file, i.e. you started a new log. I need to see the full log file, not a continuation log file. But, if you are assigning using MobiFlight, not FSUIPC, then you need MobiFlight support. If you are assigning in FSUIPC, I need also to see your FSUIPC7.ini file.

What is this? ....ok, you are using MobiFlight to access the offsets? Then you need to probably need MobiFlight support. If you are assigning in FSUIPC, we need to see your FSUIPC7.ini. The log you posted is also useless as it is a continuation log. Pease supply the full log file, and do not start a new/continuation log file. Then maybe you should ask the person who posted that video. I have no idea what 'codes' you are talking about, sorry.

The LIGHT_POTENTIOMETER_SET control/event are currently not flagged as axes controls. I can add/flag this as an axis control so that it is available in the axes assignments drop-down. Presumably this also applies to the LIGHT_POTENTIOMETER_*_SET (where * is 1,2,3..30), which I can also add. I'll post a version for you to try with this added later today.... John

Integers are either signed or unsigned. How are you reading and setting this value? You need to show us your FSUIPC ini and log files... As Pete says, we don't know where that log you posted came from or why you posted it - it is NOT from FSUIPC. Are you sure FSUIPC is running? If there is no FSUIPC icon in your system tray then it is not running. Why do you assume - why not just look for it and show it to us. If you don't know where this is, you can use the File -> Open Installation Folder... menu entry. Of course, FSUIPC needs to be running to do this....

I don't see an issue with using a function look-up-table, where you get the function to be used based on the integer parameter. You could monitor the offset that the axis changes (using event.offset), and call your function based on the value received. However, I think using the integer parameter and a look-up-table would be preferable.

What do you mean by "nothing"? Do the lvars/hvar work when using them directly, but not via assignments? Or do they just not work? What have you tried?

The logitech yoke and pedals are probably the most common yoke/pedals out there. Thats also what I used until recently, and it shouldn't be a problem setting them up on FSUIPC5. The assignments in FSUIPC6 are the same as in FSUIPC5. You should consult the User Guide, section The Easy Step-by-Step Way to Calibrate Your Controls. You should be able to calibrate to use the full range of your yoke. Calibration "slopes" are lso provided, so that you can make it more or less sensitive at different stages of travel. This is also available in FSUIPC5. Yes, brake calibration facilities are also provided. However, we don't allow you to sync left/right brakes - they are differential brakes after all. But you should be able to calibrate so that they useable. Really, its is best to just try. You could try setting your yoke/brakes up with P3Dv5/FSUIPC5 first. Otherwise, I could supply you with a trial/time-limit license to try FSUIPC6 if you prefer.

Yes, that is correct. Many aircraft continually emit certain events, with the events being different depending on the aircraft. You can such events using the DontLogThese ini parameter. Best to use in a profile. See the Advanced User Guide for details. No. But you have only assigned to the ALTITUDE_SLOT_INDEX_SET control. That should just switch to 'Managed' mode (as parameter=2). Doesn't it do that? Have you tried changing the altitude using the AUTOPILOT ALTITUDE LOCK VAR (offset 0x07D4)? And what does AUTOPILOT ALTITUDE LOCK VAR:3 hold (offset 0x0818)? Maybe try logging those offsets (using Log->Offsets... facility) and also try setting the lock VAR (LOCK VAR:3 is read-only). You can maybe also try using hvars to pull/push the VS knob - best to initially try using the WASM->Execute Calculator Code functionality. You can try with the following: to pull: (>H:A320_Neo_FCU_VS_PULL) to push: (>A320_Neo_FCU_VS_PUSH) They are the hvars in the current A320.hvar file. However, not sure if thats up to date - if they don't work, you can try the following: (>H:A320_Neo_FCU_VS_HOLD) (>H:A320_Neo_FCU_VS_PUSH)

And what happens if you try to increment with a different value using the Set Lvar... menu option? If you can set there, it should be the same via assignments and you are doing something wrong. Again, logging would help. And are you using the FBW mod or the stock A320? If the stick one, you should try the FBW mod instead. What does this mean? If you want to change the value based on the existing value, you would need to read the value first, apply whatever multiplier (ot function) you require, and then write the value back. If you want to do this, you would have to use a lua script.

Ok, but strange, Maybe you just needed to restart FSUIPC, or reload yout assignments if manually changing your files while FSUIPC is running.

You could try reading the WASM section in the Advanced User Guide... You need to set the LogLevel ini parameter to Debug in both your FSUIPC7.ini file (in [WAPI] section) and in your FSUIPC_WASM.ini file ([General] section).

If it works through the lvar menu, it should work using macros. Please activate debug logging for the WAPI and WASM, change the value using the lvar menu, then try changing using your assigned button or key. Then show me your FSUIPC7.log and FSUIPC_WASM.log files, together with your FSUIPC7.ini and macro file. Alternatively, if not using the latest FSUIPC7 beta (see Announcements section), you could try that and add the lvar to a free user offset, and assign your button to an Offset * Set control .

If changing the lvar doesn't change the switch, then no, you can't do it this way. You should try setting lvars manually (using the Add-ons->WASM->Set Lvar... menu entry) to see if they work before attempting to use them. You should try using the standard controls. Please see my previous comments and the link provided.

Please read the provided manual/instructions. The format of yout macro is wrong. It should be: [Macros] 1=L:XMLVAR_Autopilot_Altitude_Increment=Set,1000 Or, better, just: [Macros] 1=L:XMLVAR_Autopilot_Altitude_Increment=Set And then provide the parameter (1000) as the parameter to your assignment. In this way, you can assign it to one button with a parameter of 1000, and another with a parameter of 100.

As I said, you need to determine what is showing that pop-up. You should be able to do that from the task bar - did you try? It would help if you also showed me your FSUIPC6.ini file.... However, your log shows that there was an error starting ProSim: So, if FSUIPC didn't start prosim, something else did. If FSUIPC didn't start prosim, it won't be able to stop/kill it when terminating. Could that message therefore be from ProSim that has lost its FSUIPC connection as FSUIPC has terminated? The error reported (Error=2) indicates 'file not found', which is the error FSUIPC is receiving from windows when trying to execute your ProSim run command.

Was FSUIPC already running when you did this? If so, try either restarting it or 'Reload' your assignments. If its still not there, check the extension is. .mcro - if its not, it won't be recognised. You can take a look at your FSUIPC7.ini file, in the [MacroFiles] section, to see if your file is listed - if not, it is not named correctly or is in the wrong location.

First, your log file is in the same location of your FSUIPC7.ini file. in the FSUIPC7 installation folder. This is the location you selected or accepted during the installation process. If you don't know where this is, you can use the File -> Open Installation Folder... menu option. If you can't see the FSUIPC7.log file there, you probably have windows explorer et to hide known file types. If this is the case, see the Addendum in the Installation and Registration guide (Identifying Files in Windows Explorer). And you should not need to edit the FSUIPC7.ini file except for some more advanced uses. You can assign most things via the UI. Which aircraft are you using? Try activating logging for Events (Log -> Events), then open the console (Log -> Open Console). Then operate the functions you want to assign in the UI, and you will see what event the loaded aircraft is using (it can be different for different aircraft). Then, knowing what events are logged, you can then assign to those to controls via your devices. For further help, please let me know what aircraft you are using and what you want to control/assign. Also, please see the provided documentation, and for further help please attach your FSUIPC7.log and .ini files and let me know what you have tried and what your issues are.

The same location as in all versions of FSUIPC - in the FSUIPC installation folder. If you don't know where that is, use the File -> Open Installation Folder... menu option. If using lvars, you may want to look into using the latest FSUIPC7 beta (if not already) that allows you to add lvars to free user offsets for reading and writing. See the Announcements section for details and to download. John

Please show me your FSUIPC7.ini file. Also, please activate logging for Buttons & Keys as well as Events and generate a short log file showing your issue, i.e. turn each of your encoders to show your issue, and attach the FSUIPC7.log file generated.