Duplicate switch assignment in Win 7?

[wkrp2005]

Pete or anyone else,

I recently changed from a "desktop sim" to a full up MIP interfaced with two Bodnar cards for switches and a Phidgets LED64 for the LEDs. I use FSX, PS737 and a licensed current FSUIPC.

All switches registered fine using joy.cpl in Win7; however during a flight (both FSX default planes and Prosim Flight Model 2.0) I have a couple odd issues occurring.

1) When I put up my landing gear using my OC lever the view changes from VC to and outside spot.

2) When I move the switch in the Displays Source Panel from NORM to CPT PFD, the view changes from VC to outside spot.

3) Changing the A/P A/T FMC alerts panel from Test 1 to Test 2 changes the view from VC to outside spot as well.

4) Changing the Displays Source Panel from NORM to PRI makes the landing go down.

There could be others not yet discovered.

I don't believe its Prosim since it happens without PS running.

I don't think its FSUIPC since I have renamed my fsuipc.ini and had FSUIPC rebuild the ini file and the same occurs.

It must be a USB device / switch assignment duplication? If so, how does one find where this occurs and how to fix it?

Thanks for any ideas in advance.

Keith

EDIT: I should also add that the MIP switches are all configured via Prosim and only the hat switch and "view mode" are configured via FSX on my Saitek Yoke and throttle. Most else yokewise configured via FSUIPC.

[Pete Dowson]

It must be a USB device / switch assignment duplication? If so, how does one find where this occurs and how to fix it?

 

You could simply enable Button logging in FSUIPC, and check the log.  If you put FS into Windowed mode and enable the console log you could view the logging action in real time.

 

EDIT: I should also add that the MIP switches are all configured via Prosim and only the hat switch and "view mode" are configured via FSX on my Saitek Yoke and throttle. Most else yokewise configured via FSUIPC.

 

In that case it certainly likely to be assignments in FS which are doing it. Unless you disable controllers completely in FS it has a nasty habit of assigning things automatically. This happens particularly when it thinks it detects a new or changed connection, which it does on the slightest provocation.

 

Pete

[wkrp2005]

Thanks Pete. I will give it a look and report back.

Keith

[wkrp2005]

Pete,

 

Upon logging it appears various MIP switches are calling FSX assignments.

 

Question is why.  None of these are assigned in FSX and Prosim is not running during the logging.

 

Thanks again for your insight.

 

[Continuation log requested by user]
Running inside FSX on Windows 7
Module base=5DBF0000
   200367 LogOptions changed, now 60000000 00000001
   206576 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE
   224703 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE
   232020 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE
   238291 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE
   248431 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE
   255077 *** EVENT: Cntrl= 65758 (0x000100de), Param= 0 (0x00000000) FLAPS_INCR
   258150 *** EVENT: Cntrl= 65759 (0x000100df), Param= 0 (0x00000000) FLAPS_DECR
   261036 *** EVENT: Cntrl= 66658 (0x00010462), Param= 0 (0x00000000) RELEASE_DROPPABLE_OBJECTS
   265935 *** EVENT: Cntrl= 65759 (0x000100df), Param= 0 (0x00000000) FLAPS_DECR
   279803 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE
   288555 *** EVENT: Cntrl= 65567 (0x0001001f), Param= 0 (0x00000000) VIEW_MODE
   326978 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES
   327009 *** EVENT: Cntrl= 65588 (0x00010034), Param= 0 (0x00000000) BRAKES

[Pete Dowson]

Upon logging it appears various MIP switches are calling FSX assignments.

 

Question is why.  None of these are assigned in FSX and Prosim is not running during the logging.

 

But obviously there MUST be assignments in FSX! Haven't you disabled controllers in FSX? That's really essential if you want things assigned elsewhere.

 

BTW, you appear to have enabled Event logging instead of Button logging as I suggested.. Did you fancy that more or something?

 

Pete

[wkrp2005]

I had earlier tried to disable all controllers in FSX and go only with FSUIPC and Prosim, but my hat switch did not work fully correctly so I enabled it and the Pan Mode button.  If I recall correctly the possible duplicate assignment was still present.  I will have to retry this weekend.

 

And yes, the log above is the event log since the button log did not show anything when I tried my MIP switches. At the time I could not recall if you said to enable button logging, event logging, or both.

 

Thanks again

 

Keith

[Pete Dowson]

I had earlier tried to disable all controllers in FSX and go only with FSUIPC and Prosim, but my hat switch did not work fully correctly so I enabled it and the Pan Mode button.

 

You can assign a hat to "Pan view" in the FSUIPC axis assignments tab. You do not need to use any FSX assignments.

 

Pete

[wkrp2005]

Pete,

 

Probably little surprise to you but after disabling controllers and assigning all yoke-stuff via FSUIPC it cleared up the initial problem.  The one issue that threw me originally was the hat switch, which I had originally assigned via Buttons not Axis.  So, all is hunky dory at the moment.  Thank you for your time and continued daily support of all our (learn as we go) issues.

 

Cheers

Keith