PM, Wilco 12-13 patch and PFC

[DLC323]

Hi Pete,

Thank you for your wonderful gifts to the flight sim world!

I am the proud owner of windows 2.4gig XP system running PM, Wilco 767.

It all goes well on my new PFC Cirrus with the latest PFC dll and FSUIPC and wide FS all on FS2002.

I have purchased an Aerosoft MCP which requires the Wilco patch 12 to 13 so that external 3rd party products can communicate.

Providing I DONT use the PFC and instead us CH yoke, all is beaut.

When I use the PFC yoke the elevators lock full down or full up All else on PFC works perfectly (thro, switches etc)

So there is conflict when both PFC dll and Wilco patch are installed. I can have both yokes plugged in (CH is USB, PFC COM 1) and the CH yoke can actually unlock the full up or down created by first application of PFC elevator.

Can you hepl please?

Dave Chapman

[Pete Dowson]

I have purchased an Aerosoft MCP which requires the Wilco patch 12 to 13 so that external 3rd party products can communicate... So there is conflict when both PFC dll and Wilco patch are installed. I can have both yokes plugged in (CH is USB, PFC COM 1) and the CH yoke can actually unlock the full up or down created by first application of PFC elevator.

No, it isn't a conflict. It sounds very much like the bug in the 767PIC code which for some insane reason sends "full deflection" messages now and then to FS. This does actually occur regardless of whether you use PFC controls or not, but the scanning of the normal joystick inputs usually overrides it, so what you see are short-lived "flickers" to maximum deflection. These can still play havoc, however.

The main fix for this is in FSUIPC. Go to the Technical page in the FSUIPC options and enable the "control spike elimination" for all three main controls.

Those facilities were, in fact, deliberately added to FSUIPC for 767PIC users. Even the earlier releases of 767PIC exhibited some tendency to lock the rudder full over. In 1.3 the elevator was also a big problem, often locking full up This occurred without PFC.DLL, it is not actually a conflict with it.

Also you need to remove all normal control inputs to FS from the game port or USB connection otherwise you will tend to get interference in any case. Assuming you have no other joystick inputs to FS than PFC, disable joystick in FS itself. Otherwise go into the assignments and delete the ones also present on the PFC device (though this may not be permanent --FS has a habit of reconfiguring itself next time you load).

You should probably really also check the "suppress possible interference from game port throttle assignments" on the main page of the PFC options.

Regards,

Pete