stopnicki

Hello again Bob. I am not sure if this is an "AHA!" moment but it surely should help to isolate the CH Quadrant as the culprit form FSX. When I disable the joystick lever assignment and replace it with the standard keyboard commands for "arm" (shift + /) and "raise/lower" (/)the spoilers, these, operate rock solid. Still have to try your suggestion to reverse the lever commands (although it would be soooo not real :rolleyes: ) Regards, Roberto

Hi Bob: Thanks for sticking with this on a Sunday! It has stopped raining here in Toronto and I have run out of excuses to stay home. I will attempt your suggestions tonight upon our return home. What I fail to understand (other than understanding that add-ons like PMDG and Level D are extremely complicated) is why the spoilers work absolutely fine with the default aircraft. I should have mentioned that in FS9, on the same computer, the spoilers worked OK with sophisticated add-ons like PMDG and Level D. I also want to try to remove completely the joystick from the spoilers and operate them via the keyboard and see if that shows an anomaly or not. Thanks again. Regards, Roberto

Hi Bob: I don't have the CH Manager installed, as I have been unable to understand its use :roll: :oops: showing my age, my lack of computer savvy and being a great source of entertainment for my kids. I did not download a specific driver for the CH Quadrant, as (with formerly FS9 and now FSX), Windows appeared to do a good job in determining what it needed to run the hardware. "Fully closed" spoilers (or fully down) is "fully forward" on the lever. I added the "arm" setting in FSUIPC, about 1/3 down from the "fully closed/forward" lever position. Just to try and describe it again, after the first movement of the spoiler lever (say fully back for "spoilers up"), and when the anomaly starts, I have to slowly move the lever back to find a random point, where the spoilers remain down. When that happens, the lever is close to the "fully forward" position, but at a random point. If I were to push the lever to the "full forward" position, the spoilers would close and after a very shor hesitation, raise fully again, without me moving the CH Quadrant lever. The lever on the FSX panel however, is moving as randomly as the spoilers on the wing (I guess it is commanding the random movements) Thanks for your help!! Many regards, Roberto

Hi Bob: Thanks for the advice. I checked all joysticks (Saitek Pedals, Saitek Yoke and the CH Throttle Quadrant) and I ensured that only the CH yoke has the spoilers axis assigned. I also deleted the keybooard "spoiles arm" and "spoilers" key assignments, so that, as far as I can ascertain, only the CH Throttle Quadrant was assigned to the spoiler axis. I assign the axes, through the FSX assignments page. I also went back to FSUIPC and I realized that I hadn't assigned an "arm" middle point in the spoiler page settings. I did that. After this assignment (max, middle and min), an entire (albeit short) flight looked very very promising as the spoilers truly behaved. Until I landed, put them up to slow down (which they did) and as I tried to stow them, the problem started again. The jittering has stopped, but when I get to the fully closed position on the CH Quadrant lever, the spoilers hesitate and then reopen (go up) fully, without me doing anything. I will continue to search for the offending "other" assignment, but if you have another thought, please let me know. Ragards and thanks again. Roberto

Hello everybody: I post this here, hoping to be directed in the right heading. I have a very unstable (jittery) spoiler axis when using an add on such as LevelD B767 and/or the new PMDG B737-NGx. At the start of a simulation session, the spoiler lever on my USB CH Throttle Quadrant is "forward". On the aircraft's throttle quadrant, the lever will also be "forward" and the spoilers (on the wings) stowed. As soon as I move the spoiler lever on the CH Quadrant, the lever on the aircraft's panel will start to behave strangely, wherein it will jump from position to position or jiggle/jitter. The spoilers on the wings, unfortunately, follow suit and do exactly the same thing. If I lower the CH Quadrant lever completely, to raise the spoilers, they will raise and then, uncommanded, they will return to the closed position, then back to open, hesitating and jittering along the way. If I try to close them, the reverse occurs, etc. etc. I have changed the axis to another lever on the CH Quadrant, just to see if I can try to eliminate an obvious hardware issue with the CH Quadrant, but the same behaviour happens on the aircraft's panel. I have calibrated via the FSX controls and I have also calibrated via FSUIPC. The axis during the calibrations is nice and stable. All other controls, throttles, flaps and some asssigned buttons on the CH Quadrant, work OK. It is only the spoiler control that gives me problems. This does not happen at all with the default B737 or B747 of FSX. The system is as follows: Windows 7 i7 - 64bit FSUIPC 4.719 FSX - Acceleration Level D - B767 X (I have had it for a while, with the issue, but I "lived" with it) New PMDG B737-NGX (the issue is more pronounced with larger variations and jitters) Several Go Flight modules, but none related to the throttle quadrant. As usual, any help and advice is greatly appreciated. Regards, Roberto

Just completed a flight with FS on the server and FSCommander on a client WWOOWW!!!!! Smiling widely Roberto

Hello Pete: I regret that I caused your obvious (and justified) frustration. While any explanation is now an excuse, I have been in the hobby for over 10 years and carefully (as I am totally system ignorant) following instructions, to avoid the disasters that just befell upon me. I made an error in the numbering of FSUIPC download folders, and re-installed the old 3.947 thinking that I had installed the new 3.96 version. As simple, unfortunate and silly as that. Many more problems were created as a result, but now that I know their source, I am slowly trying to repair them. While I cannot promise to ever annoy you again, I can promise that I will really try not to. Thanks for your continuing help. Regards, Roberto

Hi Peter: I think that unwittingly, I got myself into immense trouble. And your response above is so "on the mark". Impatient as I am, I installed/registered WideFS in the server and the appropriate two files in another PC that will be my client in anticipation of the help of a friend who will help in establishing the network. That is all I did. I did not run any of the programs that have to be run with WideFS. Just installed them. After registering WideFS last night, FSUIPC asked to reinitiate the FS and I did that today. Unfortunately, after starting FS (2004) I am now getting an error that says: "The Squawkbox was unable to start because FSUIPC could not be initialized. Ensure that FSUIPC is properly installed and restart Flight Simulator to try again". I am unable to understand what happened. To try to "undo" whatever I did, I deleted the WideFS dll's from the server PC. I uninstalled and re-installed SB4, I deleted and replaced the FSUIPC.dll (the version is 3.947). To no avail, as the same error message continues to appear. The "Modules" tab in FS only shows FSUIPC, but not the "Start Squawkbox" option that it did before. When I open FSUIPC, it appears to be quite content, telling that it (and WideFS) are registered. All the my settings/selections that it had before are there. The "Modules" folder of FS has the "fsuipc.ini" file. I have also realized that Active Sky is not connecting and that the flaps that were calibrated via FSUIPC are not working properly either .. Sorry about the wordy message, but I just don't know where could this have gone wrong? (As an aside, I tried to open the connection to IVAO and it complained similarly that it was unable to connect with FSUIPC, however it continued with the on-line connection warning me that options such as TCAS, etc. would not be available)) Thanks again. Roberto

Hello Peter: I am not sure if this question belongs here, but I will only know if I ask. After observing a networked FS arrangement at a friend of mine, I have decided to attempt it myself. I have re-enlisted the help of a couple of old PC's that were on "door- stopper" duty for a while. After a good dusting, they appear happy to work again. I currently have FS (2004) and a large number of add-ons, running on one PC. I have always had a registered copy of FSUIPC and since yesterday, I am the proud owner of a registered copy of WideFS. My questions are: 1) Do I have to un-install the add-ons (i.e. Squawkbox, ActiveSky, FSCommander, etc.) from my current PC (that will become the server) and install them on the PC's that will become the clients? 2) Can I just leave things as they are in the current PC and install the add-ons on the soon-to-be client PC's? Would this create confusion and/or conflicts? As always, I appreciate any advice. Regards, Roberto

Hi Pete: It just goes to show my utterly inadequate knowledge of computer systems and their programming. I manage to enjoy this hobby and all it offers, by strictly following manuals and procedures developed by others. At times, I am a bit embarrassed at having to post my questions (after duly searching the FAQ's and forums!) but then, I have always received a solution. I believe that the GF displays are handled through their own ".dll" files (GFMcp..., GFDev..., etc.). However, now that you have mentioned "your little" GFDisplay file, I have downloaded it and I will see how it might help me if the re-programming of the "buttons" as you suggested above, does not go well. Thanks again for all the help Roberto

Hi Pete!! You are!! :D :D :D I mean, your FSUIPC is :D As usual, you are right. I will correct the programming to include the "release" as that for sure is the issue. Thanks for the very prompt reply. Roberto

Hello! With the help of some good folks in the LVLD767 forum and Pete*s manuals, I learned how to program two important GoFlight modules (the EFIS and the MCP-Advanced) with FSUIPC, for use with add-ons to the FS9. They both, work *like a charm* with the LVLD767 in my FS9. Granted, the MCP*s program files (.dll*s and such) are readily available from LVLD and the EFIS programming was carefully explained in their forums. I followed the process to program other add-ons and the *macro* and *buttons* programming of the EFIS for the PMDG 737-700 went OK. However, when I programmed the FMC-Advanced for the PMDG 737, I am faced with a particular problem, related to the rotary knobs/functions. What happens is that the speed/rate at which the numbers in the monitor (panel) window change, is half the speed/rate at which the numbers change in the respective window of the MCP module. In other words, for each two *clicks* of the rotary knob, the number changes once on the monitor/panel while it changes twice in the GoFlight MCP window. So, for example, if both heading windows started at *000* and I turned 30 *clicks* to the right, the GoFlight module window would show a heading of *030*, but the heading on the panel (in the MCP window as well as the magenta dashed line on the HSI) would only show *015*. This happens with the four rotary knobs which are assigned to CRS, HDG, SPEED and ALT. I have currently updated and registered versions of everything and my PC runs on Windows XP. Could anybody suggest what I might be doing wrong? Thanks for the assistance! Regards, Roberto

Thank you Peter for the quick response. I have to confess that, notwithstanding the many checks, I had indeed left the offending slider on the wrong side. All is well! Roberto

Hello everybody: I have a CH Throttle quadrant that I had been using successfully in my old PC with many add-ons for FS9. I just changed to a new more advanced PC (Intel Quad, etc.). I have re-installed all programs, including FS9 and have a registered version 3.75 of FSUIPC. I have tried to calibrate this joystick in FSUIPC and I can do this for all axes, except the one assigned to Throttle #2. I have assigned "Axis Z" to Throttle #2 and the axis responds properly, when I calibrate the joystick in the FS9/PC calibration program. However, when I try to process this throttle/axis in FSUIPC, as I want to include the reverse option (Page 3 of Joystick Calibration), this axis does not respond. Its "IN" and "OUT" values, remain at zero. The throttle, does not respond in the simulator itself either. I am at a loss and any advice will be greatly appreciated. Thank you Roberto

Paul!! BINGO!! If you are ever in Toronto, lunch is on me! Thanks a lot. Roberto (Ben, thanks to you too)

Hello Ben: Thanks for the very prompt response. Now I understand what Peter meant by "before" :-). My difficulty still resides in my inability to make FSUIPC recognize any of the two GoFlight modules I have (RP-48 and GF-45). When I enter the "Buttons" page, it does not recognize any of the Go Flight buttons, push or rotary. It does, however, recognize the buttons in the CH FlightSim Yoke that I have. The Go Flight modules are recognized by FS, as I have mapped them to various controls and work fine. They are connected via a USB hub. The yoke is connected via a "run of the mill" game port (it is an old one!) As I use FS2004, I have checked the main folder of GoFlight and it does have a "GFdev2k4.dll" file. I have also downloaded a "GFdev.ddl" file and placed it in that folder as well. I am sure that you are absolutely right, and that I am doing something absolutely wrong, but I really do not know what. I suspect that I might have created a conflict with my previous programming and mapping of the Go Flight modules, but I am at a loss as to how I can "undo" something like that. Thank you for your interest and help. Roberto

Hi: I have a registered version (3.201) of FSUIPC. I have two Go Flight modules, an RP48 and a GF-45. My difficulty is having FSUIPC recognize any of the buttons in these modules, as joystick buttons. I have managed to map the Go Flight buttons to PMDG 737 MCP buttons (via the PMDG mapping), and I would like to try to map the rotary buttons as well. I have read Peter's instructions: ----> "1. First, please make sure that your device, the one with the buttons, is plugged in and working BEFORE running Flight Simulator. The Windows joystick interface used by FSUIPC to scan the buttons will not recognise any devices that are plugged in after Flight Sim has started. I know USB is supposed to be “hot pluggable”, but this doesn’t seem to be the case with respect to running programs." ----> I have the GoFlight modules connected via USB ports and they are automatically activated as FS starts. I suspect that this is part of my difficulty. How can I start them in advance of FS as Perter's instructions indicate? Thanks for any advice. Roberto