nemokin

I flew NGX tonight and used FSUIPC to assign engine cutoff/idle buttons and actions (keyboard shortcut specifically for NGX) without P3D shutting down when pressing "OK". Button assignment looks to be successful, visually checking for the engine levers moving in sim, in sync with TQ's physical movement. For now, things appear to be resolved. As a conclusion, it may have been a simple conflict of axis assignment being made in both FSUIPC and in P3D, since I had not deleted the axis assignment within P3D. A very elementary error (or skip of process) on my part. Thank you, Pete and Thomas, for sticking with me to solve this.

I did try this first but my P3D did not allow device specific controller enable/disable. When I chose TQ in the controller type scroll and unticked "enable controllers" to disable it, all others (Yoke and rudder) too become disabled together. To report on my NGX. What I had assigned/calibrated last night using default B58 worked with NGX (Throttles, Reversers, TOGA and A/T Disconnect). (I flew PMDG NGX tonight and throttles worked fine without any lags. Maybe it was simply my misperception with default B58 yesterday.) I used "Throttle 1" and "Throttle" from the drop-down list, checked Direct to FSUIPC Calibration. No Filer option, no null zones nor response slopes (since I am not familiar/comfortable with these yet). Engine Start Levers did not work, however. They both worked last night in B58's red mixture handles but not with NGX today. Unlike B58, when I move the TQ's engine start levers nothing happens in NGX (I had to move them using my mouse in sim). My TQ's engine start levers are recognized as buttons. Using "Buttons+Switches" tab in FSUIPC, I ticked "select FS control" then chose "Mixture Lean" and "Mixture Rich" using B58. Parameter box remains blank, also Control repeat while held remain unchecked. Maybe I need to select a different control selection from the drop-down list, I do not know. Of note, I have not touched FSUIPC assign/calibration with NGX as active aircraft so don't know if PC shutdown will occur if I were to open and change setting with NGX. I may try this tomorrow night to see if shutdown will reoccur.

Pete and Thomas Here is the latest. Firstly, I was able to assign/calibrate with FSUIPC without the sim crashing. Below is what I did and did not do. 1. Windows file/program search did not find any Revolution Simproducts drivers, Opencockpit drivers, or SIOC, so I passed on disabling these drivers. 2. Launched P3D at default airport and default B58. 3. Deleted throttle axis assignment for the TQ using Option/Control menu within the sim. These were the only axis assigned by the sim. 4. Checked and verified that my throttles were not moving despite moving my TQ. 5. Opened FSUIPC and assigned and calibrated throttle 1 and 2, reversers 1 and 2 axis. Also assigned TOGA, A/T disconnect and mixture 1 and 2 buttons. Not ticking the "Profile specific" tick box. 6. Once done, clicked "OK" in FSUIPC. No crash, back to B58 cockpit. 7. Flew for 30 minutes with B58. Mixture handles (red ones) moved OK, Throttles moved OK. (Although throttles seems to move less smooth/gradual in sim - lags physical TQ movement than before.) I did not have the time to check with NGX last night, so I have not tested the reversers, TOGA, A/T functions yet. Hopefully I will have time later tonight. Of note, I have not assigned the flaps and spoiler axis to my TQ yet. (I don't intend to assign spoiler axis, may assign flaps specifically for NGX) Will update further on how NGX works.

Thomas, I live in Asia so I am smack in the middle of the work day, away from my PC. I will be home in about 4 hours after which I shall begin the assignment/calibration tasks as you two commented. In the past, I have used FSUIPC to assign/calibrate my RevSim TQ for both throttles, reverses, spoilers and flaps and they were working fine in FSX and in P3D v2.5. I also had TOGA, mixture engage, parking brake and A/T arm/disconnect buttons as well. I remember Revolution TQ recognized in the device manager of Windows but never attempted to see if the drivers are the ones you commented. I hope I can figure out a way to search for these drivers somehow.

Hmm... I thought I only had 1 USB connection but I have not looked in the back of my PC for years now so I am not sure. I shall take a look and try both Peter and your advice tonight. Thank you and I shall provide an update of the result.

Thomas, I shall try to disable the drivers, thank you. A dumb question maybe but if I disable the drivers wouldn't that make my PC not recognize the TQ as active device? Will this still allow FSUIPC to recognize and assign/calibrate? ( I suppose P3D and its option/device selection within P3D will not recognize the TQ.) I just never done something like this before so it's a whole new experience for me.

Pete, Thank you for clarification. I will attempt a general setting first. Thomas, Appreciate your advice. I own a non-motorized TQ. How would I go about disabling the drivers you mention? Apologies for an elementary level question..

Pete, Thank you for your reply. I have checked the Windows Event Viewer after the forced reboot but there really isn't any error entry other than a forced reboot. I also have a "Bluescreen checker" type of application and that too registeres no error. Correct me if I am interpreting your comment wrong, but is it your recommendation that I try to update my nVidia drivers and see if that will solve the issue? (I am not questioning your advice, I am simply not PC literate enough to know that a graphic driver may affect how the FSUIPC data registers/saves) Alternatively, what do you think about if I try to assign/calibrate using default B58 instead of NGX and apply that to not any aircraft specific, thus allowing to be used for all aircrafts? If successful, then it probably is NGX issue but if not successful then it's not aircraft specific. If/when this fails, I will try to update the graphic drivers. I just thought that trying this first is much easier than updating the graphics drivers (or even possibly reverting back to the older version if the new driver performs poorly). Thanks again

Pete, First of all, thank you for this wonderful tool you have provided. I have never flight simed without FSUIPC since FS2004. Before I go to my problem, a little background info as to my currect setup. I recently installed P3Dv3.2, and only three Aersoft add-on airports (along with ORBX Global, LC and Vector). Only add-on aircraft I have installed is PMDG NGX. I have three hardware devices, GoFlight YOKE by GoFlight Technology Inc. 737-type Throttle quadrant Rev-Simproducts 8 axes by Revolution Simproducts and MFG Crosswind V2 rudder pedals. All three are USB devices and conntected and recognized by P3D. Flying the default B58 has seen no problems, assigning some functions such as "autopilot disconnect" or "elevator trim up/down" to my GoFlight YOKE via button assignment within P3D options/controls menu. My throttle too work without any problem, properly throttling from idle to max on both throttles 1 and 2. Here is my challenge. In an attempt to assign and calibrate, for an example, Reversers 1 and 2 (phycially available on TQ similar to real 737), I go into FSUIPC. Once finished assigning and calibrating various TQ functions in FSUIPC using PMDG NGX and press "OK", my PC automatically shuts down and forces a restart of PC itself. This occurs everytime I press "OK". Restarting P3D and NGX, I notice that my assignment/calibration that I made prior to the shut down has not been reflected. Since every "OK" leads to a forced shutdown, I am unable to assign/calibrate. Any hints as to what I need to do/correct will be appreciated. Of note, I am using Version 4.953. (Win7-64) I am only trying to assign/calibrate the TQ via FSUIPC and not the Yoke and Rudder; they are assigned within the P3D Option/Control and work perfectly in both default planes and NGX. I don't know if this has anything to do with this forced shutdown, but I still have my TQ device "enabled" within P3D. Do you think simply "disable" the TQ within P3D will solve this forced shutdown issue? (I could might as well try it but trying to think ahead and wanted to get your POV). Please know, Pete, I am not complaining about FSUIPC itself; I am simply trying to figure out how this can be solved.

Got it clearly, thank you Pete.

I am having a hard time finding my "Profile sub folder" for P3Dv2.5. Can you point me in the direction please?

Thank you Pete. I shall try this today. To make sure I understand your pinned topic correctly, I can still calibrate my hardware with FSUIPC (throttle quadrant for example) as long as I use the FSUIPC to assign various functions (flaps, spoilers, throttles, reversers, etc), correct? I have also disabled the throttle quadrant hardware in the P3D setting/device menu. (This is what I have done in the past.)

Hi. I currently have P3D v2.5 and I would like to use the same key commands and calibration I had set for my hardware(throttles and yoke) for v3.0. I suppose I can start from scratch and reassign/calibrate in v3.0 but is there any easier way to copy over relevant FSUIPC files from v2.5 to v3.0 to avoid any rework? If so, which files are to be copied over to which folders? I am not a FSUIPC veteran, apologies if my question is too elementary. Kay

Pete, Thank you for your feedback. Apologies for being inaccurate regarding "IN" and "OUT". After taking a look at the calibration page, numbers in the "IN" box has negative value when my throttles are pulled back but the "OUT" box has 0 in it, as you said if I have "no reverse zone" ticked. I am not using any addon formula, so the number in the "IN" box is what the TQ feeds. What I attempted today was to tick "filter" for both throttles 1 and 2. (I didn't have them ticked). I only made two flights since so not statistically saying anything, but at least in these two flights I did not see the unexpected reverse activation in throttle 2. I shall make a few more flights to see if this "filter" can be my permanent solution. Kay

Pete, Thank you for your response. To answer your question. Yes, the IN values I see are in the range you indicated, both negative and positive, and they do change gradually as I move the thottles. When calibrating for the default Baron, the IN numbers act the same way that they do gradually change from he negative and positive. Throttles in my P3D with Baron behaves properly without any problem. No Reverse Option I have chosen for NGX, my IN numbers still show -16323 and not 0 as you mentioned. I therefore move the throttles a tad forward to find a positive number and SET that as min. IN numbers do gradually move but not linearly - -16323 to 0 to positive number rather with a small throttle movement but 0 to 16323 with nearly 90% of the remaining movement to full throttle. As long as I don't set the min IN value at the min of -16323 by finding value closer to 0, then the throttles will move gradually in NGX as it is supposed to. Then the only problem is a sudden reverser activation when retarding the throttles, only with the right engine, never the left. Left engine is working fine. If I set the min IN value at the real min of -16323, then the throttle will jump in NGX. My throttle quadrant is not Saitek, rather a B737-like quadrant. The manufacturer no longer makes them but it is similar to Flight Deck Solutions TQ. It is not motorized TQ so it acts simply as an input control device. I have not ticked the "filter" , would that make any difference? Also, does it make any difference to manually modify FSUIPC.ini file to change the min value? ( I've read in some forum about someone modifying the ini file.) By the way, I have been using this TQ under FSX and NGX, having calibrated with FSUIPC and have not had this unexpected reverser activation when retarding my throttle. Kay

Hi, First time posting here. I am experiencing a slight problem properly calibrating my throttle quadrant using FSUIPC. I have been using FSUIPC for several years now and I generally understand (or so I think) on how to calibrate various functions but I am having problem with my PMDG NGX throttles. Since my throttle quadrant has reversers just like the 737's, I have checked "no reverse zone" and moved my throttles 1 and 2 in the Max and Min positions. One has a large negative number, like -16323 and the other an exact same number but a positive one. If I set them accordingly in the calibration window, what I get in NGX is a sudden throttle movement from retarded position to nearly a max throttle position without any gradual increase despite my hardware throttle being gradually moved. To alleviate this issue, I have set the minimum position in FSUIPC to be not the min point but a slightly forwarded point, only a centimeter or so away from the retard position. With this, the calibration window no longer shows -16323 but a small positive number like 56 or similar. Max point remains unchanged, something like 16323. If I do this, then now the throttle in NGX does respond to gradual throttle movement but I have a different problem. Things are mostly fine except after I taxi in to runway getting ready to takeoff and I slowly begin to increase power, one of the two engines will go into reverse while the other doesn't. This is always with my right engine. For default BE58 which doesn't have reverse, my engines spool up on takeoff properly without any problems. (Hardware actions is the same for both engines, I have not pulled up on my physical reversers.). So, I basically have two unknowns from my above situation. 1. My current calibration puts one of the engines to go into reverse despite my having chosen "no reverse zone". Is my way of selecting min point inappropriate? (My other engine is behaving without problems) 2. My first method of selecting my min point at my hardware's retared position, while I move my hardware throttles gradually, the response in NGX is not gradual but abrupt min to max. I'd appreciate your feedback on how I can properly calibrate my NGX. Kay