solentflyer

Pete has already indicated in a couple of posts that a new release compatible with P3D 2.2 is due for release shortly. Best regards Dennis

Pete, your level (and speed) of support is without equal! I can confirm that the fix works a treat. Thanks again, Dennis

Yes setting both programs to be started via the Run command worked - it's only when setting one or both to start via RunIf that one of them doesn't start. I will leave them both set to Run until a new version of FSUIPC containing the fix is released. Many thanks for your help Pete - much appreciated. Regards Dennis

Thanks for replying so quickly Pete. I have updated to the latest version 4.841 and still have the same issue, even if I put it first. Strangely however, if the entry is on it's own, it works fine. Regards Dennis

I'm having a problem running a particular program with RunIf and I was wondering if there is a limit to the number of characters in the program name? In FSUIPC,ini, I have the following lines inserted: RunIf1=READY,CLOSE,"L:\Microsoft Flight Simulator X\FSMap\FSMap.exe" RunIf2=READY,CLOSE,"L:\Microsoft Flight Simulator X\rcv4x\rcv4.exe" RunIf3=READY,"L:\Microsoft Flight Simulator X\HiFi\AS2012\AS2012_Exec.exe" RunIf4=READY,CLOSE,"L:\Microsoft Flight Simulator X\GoFlight\GoFlight PMDG Interface.exe" RunIf5=READY,"L:\Microsoft Flight Simulator X\AivlaSoft\EFB\AivlaSoft.Efb.DataProvider.exe" RunIf6=READY,CLOSE,"L:\Microsoft Flight Simulator X\AivlaSoft\EFB\AivlaSoft.Efb.DisplayUnit.exe" Programs in lines 1-5 run fine. The AivlaSoft.Efb.DisplayUnit.exe program however refuses to run regardless of which RunIf number I assign to it or if I use the Run command as opposed to RunIf. If I paste the part in quotes to the Windows Run dialog box, the program runs fine. The relevant lines from the FSUIPC log file are below: ...... 58438 GoFlight GFMCPPRO detected: 1 device 58454 Run: "L:\Microsoft Flight Simulator X\FSMap\FSMap.exe" 58454 Run: "L:\Microsoft Flight Simulator X\rcv4x\rcv4.exe" 58470 Run: "L:\Microsoft Flight Simulator X\HiFi\AS2012\AS2012_Exec.exe" 58470 Run: "L:\Microsoft Flight Simulator X\GoFlight\GoFlight PMDG Interface.exe" 58470 Run: "L:\Microsoft Flight Simulator X\AivlaSoft\EFB\AivlaSoft.Efb.DataProvider.exe" 59983 Advanced Weather Interface Enabled ...... I have checked the Windows Task Manager (I'm running Windows 7 Ultimate x64) and the AivlaSoft.Efb.DisplayUnit.exe program is definitely not running at the time I load a flight. Kind regards, Dennis

Thanks Pete. I followed your advice and have now tracked it down to a program that iFly supply called GoFlight.exe, which is started manually outside of FSX and controls the display of digits on the GF-MCPPro unit. When this isn't started, the unit works perfectly (although the displays are blank) and the autothrottle does not disconnect whenever a button/knob on the unit is pressed/turned. When it is started, the autothrottle starts to disconnect again. I'll raise it as a problem via iFly's support site. Thanks again for your help - much appreciated. Regards, Dennis

Thanks Pete. Due to the over-sensitivity of the iFly 737NG to yoke movements, I had already calibrated a large central dead zone and also reduced the sensitivity slider in the iFly configuration program to 'Minimum'. This had prevented the autopilot suddenly disconnecting with even the slightest movement of the yoke. In this case, it's the autothrottle (not autopilot) that is disconnecting. I'll raise it in the iFly forums and see if I get any joy there. Thanks again, Dennis p.s. apologies for posting in the wrong subforum - I must have been looking at a post there when pressing the New Post button.

Hi Pete, I use FSUIPC as the interface for my GoFlight MCPPro as I (usually) find it far more reliable than GoFlight's software interface (no sudden freezing etc). However, when flying the iFly 737NG, whenever I press any button on the MCPPro, the autothrottle disconnects. This is the only aircraft on which this occurs. The screeshot attached shows an example of a command set up in FSUIPC (Altitude Increase) that causes the autothrottle to disconnect when used. Is this likely to be a problem with FSUIPC or the iFly 737NG? Regards, Dennis