Pete
I've been using FSUIPC for a long time & have taken time to read your docs supplied with it, all functions are fine for long periods then this problem occurs occasionally, usually when FS is started though it has happened when loading flight videos and when switching views during flight.
My normal method of setting up (after one of these 'events') is:
1 Make sure FS can 'see' my three joysticks in Options- Controls- Assignments.
2. Disable the joysticks in FS via Options (as recommended)
3. Open FSUIPC and assign axes, selecting direct FSUIPC calibration
4. Calibrate axes & assign buttons etc to create an ini for each 'type' of addon, ie. twin jet, 4-jet, twin prop, single prop, etc (this technique stems from the time that FSUIPC calibrations were tied to individual liveries, I know you've moved that on but I found this an acceptable method of creating generic FSUIPC configs & it worked very well)
Before subsequent sessions with FS are started, I select the pre-saved ini I intend to use, dependent on addon flown, and place this in the modules folder acknowledging the overwrite. I'm fairly pc literate & confident handling files, particularly within the FS architecture, so I don't think I'm corrupting the inis.
After FS has loaded and flight selecting I take a glance at options to ensure FS still has joysticks disabled,l do a 'control check' to ensure all is as it should be, then fly, normally with no problem till this random event.
My comment regarding re-enabling the joystick was referring to the fact that AFTER this occurs, I'm attempting to trouble-shoot the problem to see if FS has re-assigned the axes to different controls as well. The point being that it does not, & removing the ini file from modules stops FSUIPC from doing it too, the 'new' ini that's created can be modified as normal through FSUIPC options and settings.
I stress, it all works perfectly well untill this happens, but it's a catastrophe in FS terms because all my ini files are useless again.
One thought I have is that WinXP is changing the joystick numbers for some reason, you've said before that FSUIPC just takes what it's presented with by the OS, though this has been a long term issue for me across three separate computers, plus, if it was simply that why doesn't FS 'see' the sticks in the wrong order too after it happens? (Reiterating: FS controls are normal if sticks are re-enabled during troubleshooting efforts within the same session of this event occurring - after resetting axes in FSUIPC back to 'Send to FS as normal axis')
I downloaded the current version from your page yesterday 01/10/08, specifically to check I was in the support bracket, so I'm not sure why I'm outdated today. I'll get the newer version installed though.
Thanks for taking time with this.
GordyC