Hi Pete,
Sorry, I didn't use the correct term for "variables monitoring features". What I was referring to was the "Specific value checks" on the "Logging" tab of FSUIPC.
The newer 3999z9b version of FSUIPC works properly for CFS2 for the value checking. I was using various offsets (in conjunction with the "AdvDisplay" and "FS Title Bar" options) to ensure that my 'downward elevator to analog brakes' mapping was working properly.
In the newer 3999z9b version of FSUIPC, the values are reported correctly. But, in the older 3.999 version of FSUIPC, the values are always reported as "0" (this for any value that I tried to log or monitor).
BTW, I'm running Windows XP, and my joystick's ID is always the same. In my "FSUIPC.INI" file here are the entries:
[JoyNames]
0=Logitech Extreme 3D
0.GUID={B6477AC0-AFEB-11E3-8001-444553540000}
...which matches what is in my "CFS2.CFG" file:
[JOYSTICK_MAIN {B6477AC0-AFEB-11E3-8001-444553540000}]
I tried what you suggested of using joystick lettering (as well as the JoyID program), but that didn't help.
After editing my "FSUIPC.INI" file with "AutoAssignLetters=Yes", here was what was added to it after re-running CFS2:
[JoyNames]
AutoAssignLetters=Yes
0=Logitech Extreme 3D
0.GUID={B6477AC0-AFEB-11E3-8001-444553540000}
A=Logitech Extreme 3D
A.GUID={B6477AC0-AFEB-11E3-8001-444553540000}
Then when I set my axis assignments, this is what was added under the "[Axes]" section:
0=AY,256,D,7,8,0,0
...instead of "0=0Y,256,D,7,8,0,0"
Like I posted previously though, after exiting CFS2 and then restarting it, the axis assignment doesn't seem to load in, although the above lines are still in my "FSUIPC.INI" file.
FWIW, If I click on the "Reload all assignments" button (after pressing the "Rescan" button to select the axis), the "0=AY,256,D,7,8,0,0" line (or the "0=0Y,256,D,7,8,0,0" line, if have "AutoAssignLetters=No") is deleted from my "FSUIPC.INI" file.
Anyhow, the older version 3.999 of FSUIPC seems to read and load the axis assignments with no problem, so I suppose that I'll just simply stick with that version :)
The value check logging isn't really that much of a problem (it doesn't seem to function in the older version), but that's not something that I would be using normally.
Anyways, thanks for the help... with the older version of FSUIPC, I love my newly mapped analog brakes :)
BTW, I have another question, concerning LUA scripting.
Is there any way that I can toggle on and off my axis remapping 'on the fly' using a keyboard hotkey? I read quite a few messages about LUA scripting here in the forum (which is how that I think that I may be able to do this, via a LUA script), but that got my head spinning <grin>.