Jean-Claude

I did spot those in my files (Devices and FS9.cfg) and did put a 0 to all with no result so far, I'll keep trying, I am probably not looking at the right place... Many thanks for the tip. Enjoy a great evening! Jean-Claude

Thank you Pete, this time again you pointed me the right direction, I don't believe I opened that Device file before, but by changing all default settings to 0, I could finally get rid of all default joysticks assignments (as it was before!!!) with one exception that I can't find a way to eliminate whatever I try: View (pan) that remains with the hat switch that I have mapped in FSUIPC with four different assignments. So I need to delete it manually upon starting FS until I figure a smart way to get it off once and for all. Reiterated thanks for your kind help Pete. Warmest regards, Jean-Claude

The mystery is still there. After disconnecting my joxstick, uninstalling the CH driver and re-installing. erasing FS9 cfg file once more, I am still there with the same problem. I attach my FS9 cfg file with the joystick parts only, you may be able to point the problem at first glance to me. All I want to have in my FS9 joystick assignments is my yoke axis and the pedals with the brakes, all other twelve joystick buttons are assigned in FSUIPC, my throttle GF TQ6 have their own separate set. Do you see anything suspicious there Pete? Why do we have what appears to be two identical sets of data by the way? [JOYSTICK_MAIN {2FBCD620-07EA-11DE-8002-444553540000}] AXIS_EVENT_00=AXIS_AILERONS_SET AXIS_SCALE_00=64 AXIS_NULL_00=36 AXIS_EVENT_01=AXIS_ELEVATOR_SET AXIS_SCALE_01=64 AXIS_NULL_01=36 AXIS_EVENT_05=AXIS_RUDDER_SET AXIS_SCALE_05=64 AXIS_NULL_05=36 BUTTON_DOWN_EVENT_00=BRAKES BUTTON_DOWN_REPEAT_00=1 BUTTON_DOWN_REPEAT_02=1 BUTTON_DOWN_REPEAT_03=1 POV_MOVE_REPEAT_00=1 [JOYSTICK_SLEW {2FBCD620-07EA-11DE-8002-444553540000}] AXIS_EVENT_00=AXIS_SLEW_SIDEWAYS_SET AXIS_SCALE_00=64 AXIS_NULL_00=36 AXIS_EVENT_01=AXIS_SLEW_AHEAD_SET AXIS_SCALE_01=64 AXIS_NULL_01=36 AXIS_EVENT_05=AXIS_SLEW_HEADING_SET AXIS_SCALE_05=64 AXIS_NULL_05=36 BUTTON_DOWN_EVENT_00=SLEW_RESET BUTTON_DOWN_EVENT_01=VIEW_MODE BUTTON_DOWN_EVENT_02=SLEW_ALTIT_PLUS BUTTON_DOWN_EVENT_03=SLEW_ALTIT_MINUS BUTTON_DOWN_EVENT_04=SLEW_PITCH_PLUS BUTTON_DOWN_EVENT_05=SLEW_PITCH_MINUS BUTTON_DOWN_EVENT_06=SLEW_BANK_MINUS BUTTON_DOWN_EVENT_07=SLEW_BANK_PLUS BUTTON_DOWN_EVENT_08=SLEW_FREEZE BUTTON_DOWN_EVENT_09=SLEW_RESET POV_MOVE_EVENT_00=PAN_VIEW POV_MOVE_REPEAT_00=1 [JOYSTICK_SLEW {EEC7B8B0-03D4-11DE-800D-444553540000}] BUTTON_DOWN_EVENT_01=VIEW_MODE BUTTON_DOWN_EVENT_09=SLEW_RESET [DISPLAY.Device.ATI Radeon HD 4870 .0] Mode=1600x1200x32 MipBias=7 [JOYSTICK_MAIN {2FBCD620-07EA-11DE-80F2E16-00F30142071A9CB2072C4EC2072C4AC2FBCD620}] AXIS_EVENT_00=AXIS_AILERONS_SET AXIS_SCALE_00=64 AXIS_NULL_00=36 AXIS_EVENT_01=AXIS_ELEVATOR_SET AXIS_SCALE_01=64 AXIS_NULL_01=36 AXIS_EVENT_02=AXIS_THROTTLE_SET AXIS_SCALE_02=127 AXIS_NULL_02=1 AXIS_EVENT_05=AXIS_RUDDER_SET AXIS_SCALE_05=64 AXIS_NULL_05=36 BUTTON_DOWN_EVENT_00=BRAKES BUTTON_DOWN_REPEAT_00=1 BUTTON_DOWN_REPEAT_02=1 BUTTON_DOWN_REPEAT_03=1 BUTTON_DOWN_EVENT_08=VIEW_MODE POV_MOVE_REPEAT_00=1 [JOYSTICK_MAIN {2FBCD620-07EA-11DE-80F326E-00F346C2071A9CB2072C4EC2072C4AC2FBCD620}] AXIS_EVENT_00=AXIS_AILERONS_SET AXIS_SCALE_00=64 AXIS_NULL_00=36 AXIS_EVENT_01=AXIS_ELEVATOR_SET AXIS_SCALE_01=64 AXIS_NULL_01=36 AXIS_EVENT_02=AXIS_THROTTLE_SET AXIS_SCALE_02=127 AXIS_NULL_02=1 AXIS_EVENT_05=AXIS_RUDDER_SET AXIS_SCALE_05=64 AXIS_NULL_05=36 BUTTON_DOWN_EVENT_00=BRAKES BUTTON_DOWN_REPEAT_00=1 BUTTON_DOWN_REPEAT_02=1 BUTTON_DOWN_REPEAT_03=1 POV_MOVE_REPEAT_00=1 Many thanks for your kind help! Jean-Claude

Thamk you Pete, I appreciate your fast response on a Sunday morning to help me with something not even linked with FSUIPC! As always your assistance and knowledge in FS are unvaluable. I did not think about the hardware issue and will investigate that tomorrow. I keep my joystick activated in FS because I am testing one add-on in Beta stage that has yet to "talk" to FSUIPC. But I will see how I could circumvent this. Again thank you so much for the tip. With best regards, Jean-Claude

A new phenomenon appeared recently, I have been using FSUIPC successfully and with no problem for years now to control my AETI yoke buttons and my 14 GoFlight modules, of course all of them are NOT in the assignments of the FS9 cfg only with FSUIPC. All of a sudden, my yoke buttons are now systematically loaded by FS9 with assignments I never allocated in the assignment menu... Each time I start FS9 I check the assignment menu, delete all joystick button assigned by FS9, go back to the cockpit, to realise that new assignments appeared (different from the ones I deleted). After the second set of deletion, I am ready to go... How can I get rid of these strange assignments that I never created? Of course I realise this is not provoked by FSUIPC but I seek your expertise and kind help. I tried deleting FS9 cfg to create a new one to no avail, I investigated with the only new software addon I acquire lately, but they gave me the assurance that their programme cannot do this. Thank you and best regards, Jean-Claude

Sorry Pete, this is beyond me, I am only a pilot (I mean RW that explains my mediocre IT skills and limited understanding...), I can't read this log below (only a excerpt of a lengthy similar set of repetitions), it only tells me that something is obviously wrong given the repeated similar commands with the "axis elevator" and the panel lights??? but after spending three hours today checking all my commands (GF, FS9 and FSUIPC) there is no other button to set flaps other than TQ6 and LDG neither with GF nor my joystick. Next week-end I will uninstall FSUIPC and reinstall and shall input my commands one by one. I have not selected a flap command. All I know is when FSUIPC is removed from the module folder, everything is back to normal therefore the key to this problem is there. FYI Excerpt of log: 4279407 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 1167 (0x0000048f) AXIS_ELEVATOR_SET 4279516 *** EVENT: Cntrl= 66057 (0x00010209), Param= 1 (0x00000001) PANEL_LIGHTS_OFF 4279532 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -8 (0xfffffff8) AXIS_AILERONS_SET 4279641 *** EVENT: Cntrl= 66057 (0x00010209), Param= 1 (0x00000001) PANEL_LIGHTS_OFF 4279657 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -3 (0xfffffffd) AXIS_AILERONS_SET 4279657 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 965 (0x000003c5) AXIS_ELEVATOR_SET 4279782 *** EVENT: Cntrl= 66057 (0x00010209), Param= 1 (0x00000001) PANEL_LIGHTS_OFF 4279813 *** AXIS: Cntrl= 65763 (0x000100e3), Param= -1 (0xffffffff) AXIS_AILERONS_SET 4279813 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 891 (0x0000037b) AXIS_ELEVATOR_SET 4279922 *** EVENT: Cntrl= 66057 (0x00010209), Param= 1 (0x00000001) PANEL_LIGHTS_OFF 4279938 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 4279938 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 855 (0x00000357) AXIS_ELEVATOR_SET 4280032 *** EVENT: Cntrl= 66057 (0x00010209), Param= 1 (0x00000001) PANEL_LIGHTS_OFF 4280047 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 846 (0x0000034e) AXIS_ELEVATOR_SET 4280141 *** EVENT: Cntrl= 66057 (0x00010209), Param= 1 (0x00000001) PANEL_LIGHTS_OFF 4280157 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 843 (0x0000034b) AXIS_ELEVATOR_SET 4280250 *** EVENT: Cntrl= 66057 (0x00010209), Param= 1 (0x00000001) PANEL_LIGHTS_OFF 4280250 *** EVENT: Cntrl= 65956 (0x000101a4), Param= 1 (0x00000001) FUEL_SELECTOR_ALL 4280266 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 842 (0x0000034a) AXIS_ELEVATOR_SET 4280360 *** EVENT: Cntrl= 66057 (0x00010209), Param= 1 (0x00000001) PANEL_LIGHTS_OFF 4280407 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 841 (0x00000349) AXIS_ELEVATOR_SET And my Joystick calibration [JoystickCalibration] ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=Yes ApplyHeloTrim=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Thank you. Jean-Claude

Thanks for your straightforward reply Peter. I wish it was that simple. It's not. I am currently fighting with my plane at the end of the runway with flaps going up and down at random after I checked FSUIPC several times and made sure that NO axis was processed for that and every other planes I have. Neither the joystick calibration has any value entered whatsoever and yet, my flaps are playing yo-yo permanently. One hint, when I go to the axis calibration, it has values entered that I cancel for all axis and save with all boxes in blank, on the joystick page, all axes are left unprocessed, there is not one value entered in any box either for that plane or for FS9. I reinstalled FSUIPC and copied all my ini file EXCEPT of course the first part of it with the wrong flap settings. I am back to where I was and my flaps still don't allow me to fly. Thank you.

To follow-up on my previous post, here are the parameters of FSUIPC regarding the calibration. According to GF support, FSUIPC would be corrupted and would need to be reinstalled. If I do so, would I be able to copy all my settings for my various planes and hardware into the new folder? What part should I avoid copying? [JoystickCalibration] FlapsSetControl=0 ReverserControl=66292 MaxThrottleForReverser=0 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 SepRevsJetsOnly=Yes Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 ApplyHeloTrim=No FlapDetents=No MaxSteerSpeed=60 Flaps=0,16380/16 ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes Thank you. Jean-Claude

Hi Peter, I have used fourteen GF modules for the past three years with a registered FSUIPC successfully. Suddenly, out of the blue, the flaps command of my GF modules (LDG and TQ6) do not work normally anymore, i.e. I get full flaps down and flaps full up only, no increment. All other GF modules do work correctly with FSUIPC. Yesterday GF support asked me to remove FSUIPC from my Modules in FS9 and sure enough, my GF flaps command works like before by increment up or down for both the LDG and TQ6... So what can cause this sudden and new interference? For your information, I did not change any GF settings or config for the last two years so I am at a loss to understand what I should do to get the whole GF/FSUIPC package to work together again for the flaps. Flaps and throttles were not calibrated with FSUIPC but I left them on the GF cfg. All other GF modules (other than radio) are programmed on FSUIPC. Any assistance would be welcome. Kind regards. Jean-Claude

Many thanks Pete. Your explanations as always are to the point. I hope you had wonderful vacations. All the best. Jean-Claude

I could put together a home network after a lot of trial and errors with three PC (all Windows XP)... I downloaded WideFS with a view to try it, but unlike FSUIPC "light" (I mean the non registered version), there is no way to see if one is able to make WideFS work and what are the gains in FPS on the main computer. Of course I read the instructions but quite frankly feel intimidated by the networking procedure which sounds less than obvious for a non IT person like me! In short, once one has a running network (my case) FSUIPC registered installed (also my case), does one still need to get through the network configuration or is it not necessary? (that question alone will tell you how much I know about this whole matter!). If not, then my credit card is ready. On a different note, did anyone try to figure what gain in FPS a WideFS setup would offer? Many thanks for any feedback. Jean-Claude

Hello Pete, I reinstalled FS9 as you suggested with PMDG 737 NG only to test it. First good news, my virtual cockpit is back! Thank you. Second good news, my PMDG/FSUIPC/GoFlight orchestra plays in tune... Even if further rehearsals may be in order. No more crashes, just a few keyboard freeze from time to time immediately after programming FSUIPC (I can't have access to the menu bar for example when pressing Alt. After a while, back to normal. My GF MCP and RP48 work fine and were totally programmed using the key commands of PMDG with fast and slow modes for the rotary buttons. GF MCP: CRS, HDG, SPD, V/S rotary buttons work very well and are reliable. Some difficulties though with ALT, for small variations in descent, it would not take it (I checked FSUIPC, commands were OK on slow variation). The push buttons were a bit more impredictable, the CMD button would not work regardless, the APP was not reliable, but SPD, CRS, NAV, ALT were OK at all times. RP48: I programmed FD, A/T, TOGA, Kneeboard, FS Nav, all were 100% reliable. However LVLCHG, VNAV, LNAV were not reliable at all and needed to be "refreshed" in FSUIPC, although the commands were there and correct, immediately after closing FSUIPC, they reworked. Rotary buttons were programmed as Baro pressure, ND mode, ND range, Autobrake and performed well in general with a few miss from time to time. They tend to need two increments for one unit of variation. I used PollInterval=66 in FSUIPC.INI and tested with and without but did not notice any drastic changes if any. I left this setting. Let me know if there is anything else you would like me to do. With kind regards, Jean-Claude

Thanks Pete for all your assistance, I understand your point regarding testing further. Eventually I will do that tomorrow and see if I can bring you better news for your latest version, I really had enough today and need to cool down as my experiences today and yesterday and the day before yesterday were quite frustrating, leaving my weekend with no flight and only FS tweaking. I thought about reinstalling FS9, but this is a heck of a job with all the add-ons, updates, patches, sceneries, hardware I have, probably a two-day job if I get it right the first time. Being a real world pilot does nothing to help as these problems have nothing to do with flying... and that's probably what I find most aggravating! Tomorrow will be another day. Tell me if there is anything you would like me to do for your tests. By the way I am running Windows XP Home edition. Best regards, Jean-Claude

Thanks Pete, I spent the past three hours trying to resolve this problem, again without meeting with any degree of success. My system is a Dell 8300 Pentium 4 3.2 Ghz with 2Gb of RAM and ATI Radeon 9800 Pro 128 DDR. I have 12 GF modules including the MCP, which are plugged on three USB cards. Incidentally, I do know where the FS9 cfg file is and how to amend it. Given the number of incidents I met this past week when attempting to "improve" my FS experience, I made a permanent FS9.cfg backup file with a shortcut on my desktop, this allows me for speedy recoveries... My view problem did not change a bit, I am still stuck with no pan views in my virtual cockpit (which did work perfectly until I stupidly wanted to refine it with views of my own on FSUIPC!) To make another attempt to solve my problem, I downloaded Active Camera on trial basis and used it, to realise that it too would not want to pan left or right (up and down is fine as a reminder). Getting back to GF programming with FSUIPC, I simply gave up as I was everytime freezing my system after programming the GF MCP, and since I could not use anything anymore, I had to exit FS9, messing my cfg again and again in the process (FSUIPC does not do that, but the key commands seems to be causing that phenomenon). I am prepared to forget about this facility and, for once, be part of the unlucky guys who can't make it work. I am much more ennoyed with that virtual cockpit business and don't have a clue as to where to look now, and it does not appear to be a FSUIPC either. There are times where this hobby becomes too obsessive, this is one of them! Thanks for your help anyway. Best regards, Jean-Claude

Hello Pete, It looks like I now have a mess in my hands... I tried about everything you suggested and I could think of to no avail: - I used FS9 assignments instead of FSUIPC, no change - I cleaned up FSUIPC and reprogrammed, no change - No luck with rebooting with no FS9.cfg, the new one would not change the problem - No joy either with copying my old FS9.cfg file which I kept in archive just in case - Version 3.229 test did not help, I still have the same "hat switch" setup as follows: 1/ Upper button left for pan up (works fine in 2D cockpit, virtual cockpit and exterior view) 2/ Upper button right for pan down (works fine in 2D cockpit, virtual cockpit and exterior view) 3/ Lower button left for pan left (works fine in 2D cockpit and exterior view, DOES NOT WORK IN VIRTUAL COCKPIT) 4/ Lower button right for pan right (works fine in 2D cocpit and exterior view, DOES NOT WORK IN VIRTUAL COCKPIT) The effect I get when pressing pan right or left (in virtual cockpit ONLY) is a slight move on the correct side but immediately rejected and sent back to forward view and repeated as long as I keep pressing. It cannot be a hardware problem since the same two buttons work normally for 2D and exterior views. In FSUIPC, I use the following selections: FS9, Pan left, Pan right and tick on repeat when held. I also tried to allocate keyboard commands for the same in FS9 assignments, no change! FSUIPC version 3.229 (test) also did not perform well (for me that is) with the GoFlight hardware, I could not use any of my GF modules (rotary buttons or press buttons) with this version whereas I could with version 3.224 at least use the press buttons and some of my rotary. It looks like there is a fast repeat command freezing my keyboard. And I keep losing my FS9.cfg file as I did with version 3.22... Sorry to get back with more challenges, I am really lost here! Best regards, Jean-Claude

Thanks for your prompt reply (on a Sunday!) Pete... I have programmed my hat switches only in FSUIPC, I did delete them in FS9. I used the FS control of FSUIPC and ticked the "repeat command when pressed". I tried to reset all default in FS9 to no avail, it would not give those settings back to me, hence my predicament having to find a way to programme them in either FSUIPC or FS9! What puzzle me is that the vertical axis was no problem to programme, but I can't fix the horizontal one, so simple and yet so tricky it seems. Many thanks for your kind help. Regards,

After tweaking a number of new activities, thanks to FSUIPC 3.22, I must have made a mistake somewhere since I lost my horizontal pan views in my virtual cockpit and I am unable to restore them. I have programmed (with FSUIPC) my "hat switch" with two switches for up and down pan views and they work fine as they did before. I have done the same selections for left and right pan views but they do not work: all I get is a "shaking" move to the correct side but no other effect, as if something was preventing the view to pan further than a couple of millimeters to that side. Since the values selected are the same for "up", "down", "left" or "right", where did I miss something? Could anyone assit? With anticipated thanks. Best regards,

Pete, I could use 30 minutes to quickly check your test version. Here is a status report with PMDG 737-700: A) With the GF MCP.dll: 1/ No more keyboard problem as soon as I move one knob on my GF MCP, that's good news, this was not the case before 2/ All knobs work fine but do "jump" from time to time 3/ For info, if my memory serves me well, CRS and HDG selectors work without FSUIPC, I would need to double check that, but I believe it is correct 4/ The altitude knob does not seem to accept the fast rotation even though it is correctly programmed and checked thoroughly 5/ The speed knob IS the problem, it can be used for a while normally and suddenly goes full speed and cannot be stopped. When this happens, then all other knobs (HDG, CRS, ALT) become inoperative and the keyboard is stuck for a long while, but this time I could exit FS9 with the task bar without jumping to the desktop and did not lose my cfg file. B) Without the GF.MCP.dll 1/ Of course there is no more dials visible, but there is no significant change for any knob, same general behaviour as mentioned above, a tendancy to jump or miss numbers even when turning the knobs very slowly 2/ There is also a strange interference between the HDG bug influenced by the speed selector or the CRS knob (not seen above) 3/ The altitude knob remains unchanged, no fast rotation (incidentally, I had to "reactivate" it by going to FSUIPC, the programming had been kept in memory but the selector was not moving the numbers at all). After a while, I could decrease altitude but not increase my selection 4/ The speed knob behaves strangely, this time if you select 250 knots for example, it will slowly decrease, and come back, and decrease again, sometimes interfering with CRS or HDG 5/ The keyboard was also stuck at one time, but more briefly than before and I could again exit normally not losing my FS9.cfg. It looks like you have your nail on the problem Pete, I hope this helps. Let me know if you need more testing, I had no time to try the buttons yet. Kind regards

My apologies for the mistatement, last night was extremely short (3 hours) hence my confused mind, there is no GoFlight FMC, but an MCP, my mistake. . I use FSUIPC version 3.22 downloaded last Friday. . I do not click on "repeat whilst held" option . My keyboard is not USB connected . There is no such problem when using my GF hardware on the GF cfg I checked this morning with a hardware specialist about my USB setup and he found it adequate. I posted the same message on GoFlight forum hoping to get a reply this afternoon. Thanks for the help anyway. Regards.

I wonder if I could get some help with the following problem: When I programme my GoFlight FMC with PMDG keys on FSUIPC (latest version), immediately after this process, my keyboard does not work anymore except for the "esc" key which immediately sends me to the desktop and loses my FS9.cfg file in the process. I could replicate that problem over and over again making my hardware programming impossible. I suspect that this could be caused by a hardware problem with my USB setup. I am using three USB multi-port cards, each of them individually powered, one with seven ports and two with four ports each. These three USB cards are plugged at the back of my PC on three of the USB ports. Would it be better or worse to have one USB card with 10 or 12 ports, or to the contrary more of smaller cards? If this is not the likely problem then what could be the next probable culprit? I use a Dell 8300 3.02, 2Gb RAM, ATI Radeon 9800 128DDR Pro. Could anyone offer some advice on this item please? Many thanks for any help.

Well, this is precisely the problem many of us are facing: correct information before buying!!! Where is it? Although I did quite a bit of Forum browsing lately to understand whether or not FSUIPC would allow me to use my GF MCP with PMDG 737, I received all sorts of comments and affirmative statements and assurances from various quarters, to discover after registering my FSUIPC copy last week that in spite of following the instructions to the letter, I can't make it work either. If the GF MCP does work thanks to FSUIPC with PMDG 737, then there ought to be on one of the three forum or the three of them (PMDG, GoFlight and/or FSUIPC) a clear set of instructions, this would be terribly useful and would remove the doubt from the mind of many potential buyers. I am now a potential ...user, until I find the way to make it work!

Many thanks Pete, most helpful, I believe I have a better understanding of the issue causing the crash now. It is most likely a mesh/scenery since those crashes happened to be in the same geographical area. I have taken note of your advice regarding weather files as well, that may be another lead. I have also found a post about a known bug in FS9 scenery causing this sort of shut down without notice, and there appears to be a fix for it. http://forums.simflight.com/viewtopic.php?t=20488 Best wishes.

Last week, I have been using the 747 200 RFP with Flight Deck Companion and, four times in a row, my flights aborted at different times during the flight when I was selecting a different view, FS9 shut down and I was back to the desktop in a split second (my FDC and GoFlight hardware were still active). I first suspected FDC to be the culprit but Dave March replied as follows: "On some systems, when using different views, FSUIPC will timeout when attempting to read some data. My guess would be you were also using a third party aircraft. Really not an FDC issue" So here I am, seeking some light from you on a possible FSUIPC untoward action, and how I could avoid those shut down with my preferred add-ons. Thank you for your help. My system is a Dall 8300 3.02Ghz, 1Gb RAM and Radeon 9800 Pro 128

Thank you for this clarification Ben, I was really confused about what was possible with GoFlight and FSUIPC. Much appreciated. Best regards, Jean-Claude

Do I understand from the above that FSUIPC makes the GoFlight MCP fully compatible with the 737 PMDG NG and the Airbus PSS A320 auto-pilots? I did read about the GoFlight being supported but did not find detailed explanations. Please kindly clarify because I sought some clear answers to these questions before but did not get any, since this would be for me the reason to buy the FSUIPC license, I have no real use for the other proposed modules. Many thanks for your help!