jclay13

Thanks, I'll try that and let you know. Can you help me understand the logic around IGN L not being a separate button? I'm sure there is a logical reason and was wanting to know how it works. I also see that GRD and OFF are the same button.

Makes sense. Thanks for clarifying that.

The GoFlight MESM 3-position toggle switch in the center of the board reports the following in FSUIPC: IGN L = button 3 released BOTH = button 3 pressed IGN R = button 4 pressed I want to use the 3-position switch to engage the starters and hold them in for a 2 engine jet (not auto start) like this: Flip switch to IGN L - "Starter 1 Set" and hold it in Flip switch to IGN R - "Starter 2 Set" and hold it in BOTH - Do Nothing It works good for IGN R where I configure the press as "Starter 1 Set" and "control to repeat while held". The starter stays engaged until I flip the switch back to BOTH. The challenge is IGN L. I configure the release as "Starter 2 Set" and it engages if I flip from BOTH to IGN L. But if I flip from BOTH to IGN R the button 3 release is triggered along with the button 4 press and both starters engage at the same time which is not what I want. Plus I can't do a "control to repeat while held" on a release so it only engages it for a second. I've also tried some creative things with key presses in FSUIPC in conjunction with GF Config key mappings and I can get IGN L to engage starter 1 and IGN R to engage starter 2 but the issue I run into there is it only engages the starter for a second and the key presses need to be held in until the engine starts. It obviously works fine using a keyboard because I can hold in the mapped key. Any ideas on this? Thanks! Jon.

When programming keyboard commands using the "Key Presses" tab, is there a way to get the keys to "repeat while being held" similar to what is available on the "Buttons and Switches" tab that has a check box for "Key press to repeat while held"? Thanks! Jon.

You said...."Though it shouldn't simply be related to the installation of a new version of FSUIPC -- I still cannot make sense of that." Just to clarify, I think I confused the issue by saying it only occurs during an upgrade of FSUIPC. I said that because it was only after an upgrade of FSUIPC that would I be impatient and click on the "PFC Connection Check" menu option and then receive the error. Bad assumption on my part. Hopefully this clears it up. Thanks!

I did a little experimenting and I figured out what is happening. After FS2004 is done displaying the message box about "Loading Scenery", "Loading Terrain", etc., the menu bar of FS2004 becomes enabled and I can see the "PFC Connection Check" menu option on the FS2004 menu bar. If I click on the "PFC Connection Check" menu option before the "PFC Control Connection Check" window appears, I get the error "Version of FSUIPC is insufficient: 0.000" when the "PFC Control Connection Check" window does appear. It happens everytime I select the menu option to display the connection checks window. If I let the window appear on its own, all checks pass and I do not get the error. It seems that I would only try to select that menu option after doing an upgrade of FSUIPC. I attached a zip file wth the PFC.log and FSUIPC.log files. I turned some logging on for fsuipc. Not a big deal. If I'm patient the checks all pass. Try it yourself and see if you get the same thing. I wonder if I uncovered something. Thanks! Jonathan Clay Des Moines, Iowa logs.zip

Unfortunately I deleted the log that might of had any errors in it when I reinstalled and re-registered FSUIPC. When it happens I delete all ini/log/key files. That seems to be the only way I can get the check to pass. I attached the current log if it is of any use. It has happened with 1.92 and 2.10 Happens anytime I replace the FSUIPC.dll with a newer one. This time I went from 3.70 to 3.72 and the last time I went from 3.65 to 3.70. I started noticing it when you added the verification checks in the PFC.dll. I usually try to upgrade whenever you have a new version out there. I've never mentioned it before because I've aways been able to get it working by blowing away the ini/log/registration files and starting fresh. I've kept an eye on the forum but never ran across others having this issue so I figured it was isolated to my system. Hopefully this helps. Not really a big deal. I get it working. I realize having the log files from when the error ocurred would be of more use. We can revisit next time I come across the issue and I will save the log files this time.

I have the registered version of FSUIPC and I have Precision Flight hardware. I upgraded FSUIPC from 3.70 to 3.72 by replacing the FSUIPC.dll file only and I get the following error during the PFC Connection Check: "PFC Connection Check - Version FSUIPC is insufficient 0.000" I get this error everytime I upgrade. I'm then forced to delete my registration key for FSUIPC and the .ini files for FSUIPC and PFC and it then works after I re-register. I can then put back my original .ini files and I'm back in business without having to redo my setup for FSUIPC or PFC. Is this normal? Am I doing it wrong? I would think I could just replace the FSUIPC.dll file with the newer one and it should work. Any help would be greatly appreciated. I always get it working, but it is a hassle. Thanks!

Hey Peter, Thanks for the quick fix on the PFC dll. You're the man!!! :D I have a question...What exactly do the restart facilities do? :?: I see you disabled them in Windows 98. Just wondering. Thanks in advance for your reply. :) Jonathan Clay

Thanks for looking into that Peter. Sorry I couldn't get back to you sooner and help debug the problem. It was around 3 AM my time when I wrote the post and I had to get some sleep before I had to be at work 5 hours later. I'm at work now and it looks like you figured it out. I will stick with 1.63 for now and look for your update. I need to get off Windows 98. Thanks again.

Hi Peter, I seem to have a problem with any version of PFC .dll higher than 1.63. I was running FSUIPC v3.11 with PFC v1.63 and had no problems. If I change the PFC .dll to v1.70 or 1.71, FS9 crashes the instant I touch my Mooney Yoke, rudder pedals, or throttle quadrant. Change back to v1.63 and all is well. Any idea? Brief system specs: Windows 98 SE AMD Athlon 1.33 Ghz 512 MB RAM GeForce 4 Ti 4200 Mooney Yoke Rudder Pedals Digital Throttle Quadrant

I found these by searching for the exact phrase "black screen" on the MS knowledgebase. I also did another search "flight black screen" where I asked for a match on all words. Some good ones: Games: The Screen Turns Black http://support.microsoft.com/default.as-us;813712 Black Screen When You Run a DirectX-Based Program http://support.microsoft.com/default.as-us;184541 Games: How to Troubleshoot Display Issues http://support.microsoft.com/default.as-us;263039 Games: Hangs or Slow Performance on AMD System with VIA Chipset http://support.microsoft.com/default.as-us;274629 I've tried everything that these asked for but still have the GPS problems. I finally got an error screen at one time where it said ddhelp performed an illegal operation. I assume that is a DirectX program. I'm with you. I think Microsoft has some DX9 issues to contend with. Thanks for the reply. You are an invaluable asset to the flight sim community. Regards, Jonathan Clay Des Moines, Iowa

Peter, I apologize in advance because my question does not relate to any of your modules, but I wanted to get your opinion on the black screen issue that seems to have shown up in FS9. FS9 runs like a dream on my machine with all default aircraft. The problem is when I'm in the EagleSoft Beechjet 400A aircraft and I try to bring up the GPS, I get the black screen and FS9 quits. I even tried a different video card and older, newer, and the latest drivers of everything on the machine from motherboard, sound, video, and including the latest DirectX. Rebuilt from scratch many times trying different drivers and approaches. Tried the Microsoft knowledge base and they suggested changing different DirectX settings and video settings but nothing worked. But, if I go to a lower resoultion such as 800x600, it works but it is very touchy when I try to open the menus. Seems like the "black screen" issue is experienced by some and not others. The Microsoft knowledge base even has a long list of games that have the black screen problem. I'm not asking for a solution, I just wanted to get your opinion on the issue and what you think might be happening. Thanks, Jonathan Clay (registered user of FSUIPC and WideFS) My machine: ASUS A7V133 motherboard w/ VIA KT133A chipset AMD 1.33 Ghz Thunderbird processor Crucial 256 MB RAM x2 for 512 MB total ASUS GeForce 4 Ti 4200 video w/ 64 MB RAM Creative Sound Blaster Audigy Gamer Western Digital 7200 RPM 40 GB HD x2 RAID 0 configuration Latest VIA Hyperion 4in1 v4.49 drivers Latest Nvidia 45.23 drivers Latest Sound Blaster drivers Win 98 SE