Chris_CYWG

I haven't played Fsim too much lately, but reinstalled FS9 and FSX yesterday on my machine. I am using unregistered versions of fsuic.dll on both setups if it matters. My problem is with the throttle quadrant gear selector in the down position, I do get 3 greens on the RIC, but it is intermittent.. it sometimes stays on for a minute, other times all will go out, or one will stay illuminted, then they all come back on.. has anyone ever run across this problem? Using most recent pfc dll files. Thanks! Update... I installed an older PFC.dll 2.0.0.0 and I am getting no flicker??

I don't think this is related to the .flt situation. This is something to do with fsuipc and the scarebus. I tried every possible thing pss recommended, and then I deleted the airbus, reinstalled it, and got fsuipc 3.2.0. I tried the bus and it flew like a charm, put in v 3.3, slammed to the ground, went back to 3.2 flys like a charm.. somebody doesn't want to play nice :shock:

I am experiencing the same problem. The FSUIPC that comes with the 320 download (3.2) works fine, the newer versions cause the bus to slam to the ground when engaging the autopilot. I am also using PFC compoenets.

Hi Pete, I was reading through the SDK last night, I am an ex programmer turned commercial pilot now, so alot of my programming skills have well errr been left behind :) My question is this regarding visual approaches. I fly mainly in the Hawaiian Islands, and am getting sick of ATC clearing aircraft straight in through the mountains to land on runway 26R when there is a westerly wind... (In real life they do the LDA approach 26L and sidestep 26R) So in my quest for reality, is it then possible to "trick" the sim into thinking its ALWAYS IFR conditions but have the actual weather always there to FORCE the aircraft into doing an instrument approach? I see in the MS help files it will clear for a visual approach if vis is greater than 3 miles and ceiling greater than 1000 feet... if one could trick the sim into "thinking" its lower it might make things a little more realistic?? Chris

Hi Pete, Thansk for the quick reply.. I am using FS2004. After getting my PFC equipment configgeg, and getting the sim configged I have tried at least 10X to reduplicate the problem and haven't been able to do so... hopefully they won't happen in flight!! Thanks again for the clarification. Chris

Hi, I was having several CTDs when simply exiting the sim. I could fire up the sim, goto the default KSEA with the 172, allow the plane to sit on the runway for 10 seconds, hit the close button, and I would get a gauranteed CTD involving nt.dll atc.dll weather.dll etc.. I thought at first it might be my sound card as I am running a Hercules Fortissimo III 7.1 with non WHQL XP drivers.. not being able to cleaning strip the drivers out, and up for some experimenting today, I reformatted my HDs and did a fresh XP install with no soundcard installed. I proceeded to add all the ASUS P4S533 drivers, the XP service packs, DX9b, and the Radeon 4.1 drivers, then installed COF. I set my display settings up, loaded up the normal default setting at KSEA described earlier, let it sit 10 seconds, closed out, and got a clean exit. I tried this several times proving to myself it worked. I then added in the fsuipc and pfc dll files, got a message from pfc.dll that I needed to select my com port. I went to the defualt setting, closed out, and bang CTD. I loaded up the sim again went to the default setting, selected my com port, exited the sim, and bang another CTD. Reloaded went to the defualt, closed out , exits clean. Reload, back to defualt, call up the menu to alter my aircraft settings, close out , CTD. Come back into the sim, go back and realter my ac setting as the CTD has not allowed them to save, exit out, its OK... go back in, call up PFC.dll to alter some of my buttons, exit out CTD. Now the trend I am seeing is this: If I access a menu, or the dll dialog box to alter anything, it seems to be wanting to write something (some kind of new config setting) but for some reason when I exit out after accessing, I get a CTD.. This now seemed to be a break in trend, which has stopped all together after the original install of the dll files... I have added in my yoke commands with no CTD on exit at all. Thanks, Chris