Hi,The description of the problem at General Discussion:http://forums.avsim.com/dcboard.php?az=sho...id=116524&page=Has anyone here with the problem come up with a solution yet ?As a side note: I run FS2002 in WINDOWED mode, because I have three monitors that contain different parts of the panel. In FULL SCREEN I'm not able to move the mouse from one monitor to the other. I tried last night, and discovered that the FSUIPC keypress lag is significantly smaller when in FULL SCREEN. So the key might be it... it's weird though that I didn't have this problem before in the windowed mode.Tero

I see in the Simflight FSUIPC forum that you posted this issue. I added a confirming comment. It is hard to believe that only a few of us with the CH Yoke are having this happen. It becomes even more complicated with WideClient running and also having much of the panel undocked and sitting on multiple monitors. This makes me seriously consider going back to the CH Manager to try and handle it all.MikeB

I can add my "me too" here as well.

Murf,Check out the simflight forum and add your "me too!" there as well!Tero

Tero and others,I have the same problem. It looks to me that it mainly/only? occurs when still on the ground waiting at the gate. When airborne the PTT switch on my CH Yoke is working fine again...Another problem that might be related, are my my light switches (landing, wing, strobes..). When I toggle or push them on the ground at the gate, they do not change position in my panel, while the result (lights on or off) is visible though (e.g. I can see the effect of the landing light through my cockpit window). When airborne I suddenly hear a few 'clicking sounds' and they are working again....Have you also noticed his?Regards,Nicohttp://www.nicokaan.nl/

My reply got lost in the forum system failure so I will try and remember what I had said.A couple of suggestions were offered by Pete Dowson on his support forum, here is a link to the thread http://www.forums.simflight.com/viewtopic.php?t=7569I am trying those suggestions out over the next few days. As you can see in the thread, he is quick to blame in on the code in 767PIC. As I had commented previously on another thread, it looks like system load may be at the heart of the problem.Mike

Mike, thanks for the heads up!I'm currently at work so I'm unable to try out Pete's suggestions.Did you try them already ?Tero

My reply also got lost.I can confirm Kiek's findings: the first time I encountered this problem was on the ground at EHAM. A very high system load. Later during the flight the problem disappeared.Kind regards,Stephan Haashttp://vatsim.pilotmedia.fi/statusindicato...or=SVA1&a=a.jpg

Hi guys,Well, Pete's suggestion to change the poll interval of joystick buttons to a lower value helped!add:PollInterval=xxto your FSUIPC.ini in the Buttons section. Replace XX with values between 10-50. The default value is 55 (there's no entry in the ini by default), and I changed it to 30, which basically eliminated all the lagging and such from the button -> keypress. Great!regardsTero

Hi,With me, polling at 30ms works fine too, thanx!But I still have the problem of my light switches that are frozen until I have lift of....Any ideas how to solve this? With a 2.4 GHz machine and 512 Mb RDRAM the load should not be a problem. If I am flying off-line everything works fine, so there must be a relationship with one of the programs for VATSIM, FSUIPC, WIDEFS, SB, ...?Regards,Nicohttp://www.nicokaan.nl/

I will go with the polling change this evening and try that out.Nico,When you fly off line, do you stil have WideFS running, connected to another computer running wideclient? I know wideserver will always be active unless you pull the dll out of the modules folder. Step through this and see where the problem developes. If everything works fine off-line, then do each of the on-line steps seperatly and check the light button function between each. Maybe we can define the breaking point that way.Another thing I will point out here that is also valid in my case. It seems like the bigger/faster computer I get, the more I ask of it by cranking sliders up to max and all the video card options possible turned on. Then on top of that, mesh terrain, airport scenery, etc.My point is that the power of the computer is not the question but rather the relitive load and demand on the processor. If I am working to maintain 15-25 frames per second, the available resources are being strained regardless of the processor speed.Good topic guys!

Mike,Did some research, here are my findings:Off line: OKOff line with Wideserver at main and Wideclient at second pc: OKOff line with SB running in the Wideclient window but not connected to VATSIM: OKBUT: As soon as I connect to VATSIM, by hitting the OK button in the connect pop up window, my light switches freeze (Note that in my configuration, RW is starting up as well, at that time).However, when I tried to reconstruct this erroneous behavior, it did not freeze....Needs some more research, to be continued...Nico

Still could be a system load issue. Particularly if VATSIM brings traffic into range, and worse if said traffic is not found in your CSL or VIP aircraft directories and you see that aircraft in your own active texture.Something else to think about!Mike

Mike,Did the PollInterval help you ??Tero

Changing the PollInterval to a 30 has a positive effect for me. There is still about a 1 in 5 failure rate when in dense scenery airport areas, a touch better when on the ground at default airports. That is much better than I had before.