NomadRider

Yeah I copied the key from the old install and it worked. Just seems weird the installer didn't recognize the key text that I copied and pasted from the file. Thanks, John

I installed a new CPU and MB along with Windows 11. Installed MSFS2020, FSUIPC and my WideFS key doesn't work. FSUIPC key worked fine. It worked just fine on the other system before the reinstall. John

Thanks for your help John. I uninstalled the program and moved it from H:\Program Files\FSUIPC7 to H:\FSUIPC. Not sure why the Program Files directory was so restrictive, I create it my self. Oh well it's working now. Thanks Again!!! John

I have the program installed in a directory I created on my H drive. I will check permissions on that folder. Thanks, John

Using the newest version of FSUIPC. I am trying to bind my aileron, elevator, rudder and left/right brakes using FSUIPC. I am not selecting the aircraft specific because I want this to work for all aircraft that I fly. Is there some reason that the settings aren't being saved? When I get back into the same aircraft I have to rebind them again. I am pretty sure the settings are saved in the FSUIPC.ini file but I notice that the files hasn't changed since 4/5/2022. Thanks, John

After getting my FSUIPC and EXE.xml file squared away, I am still having trouble getting the AFC_Bridge to work correctly with my HoneyComb Bravo. I have to start it manually from a shortcut on the desktop. Here is my EXE.xml: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>EXE.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Name>FSUIPC7</Name><Path>H:\FSUIPC7\FSUIPC7.exe</Path> <CommandLine>-auto</CommandLine> <NewConsole>False</NewConsole> </Launch.Addon> <Launch.Addon> <Name>SPAD.neXt</Name> <Disabled>False</Disabled> <Path>C:\Program Files\SPAD.neXt\SPAD.neXt.exe</Path> </Launch.Addon> <Launch.Addon> <Name>AFCBridge</Name> <Disabled>False</Disabled> <Path>H:\MFS2020\Community\AFC_Bridge\bin\AFC_Bridge.exe</Path> </Launch.Addon> </SimBase.Document> And the location of the AFC executable: H:\MFS2020\Community\AFC_Bridge\bin SPAD.neXt program starts fine. Thanks, John

Yes I did John. I am not posting this question in multiple threads. I am asking jannier if his ACF_Bridge is working now. I didn't ask him that in the other post as he wasn't involved in the other conversation between you and me. John

I followed the post from jannier to add that. Thanks, John

Did you get the AFC_Bridge to work now? It seems I still need to start it manually in order to get the lights on my Bravo quadrant to work. John

So once the EXE.xml file is fixed I can use the shortcut? And will the AFC_bridge work now or maybe that’s something you don’t know. John

Thanks for the info If the desktop shortcut isn't supposed to be used in starting MSFS2020 and FSUIPC, maybe you should refrain from asking if you want to add the shortcut to the desktop when installing the program. John

After installing the most recent versions of FSUIPC I noticed that FSUIPC wasn't running when MSFS2020 started. I noticed the following in the .bat file. :: start FSUIPC7 :: start "" "H:\FSUIPC7\FSUIPC7.exe" This isn't correct I don't think. I want to have the second line: start "" "H:\FSUIPC7\FSUIPC7.exe" without the :: John

Anything I can do to troubleshoot WideClient issues? John

It is set correctly. Screenshot of my network settings. On this flight it seems to be keeping the profile, but shouldn't the "Profile Specific" checkbox still be selected when looking at the settings?

A couple of questions. I recently rebuilt my sim computer with new OS install and P3D. I configured it to connect to my stream PC with WideClient so that I could run ACARS and LiveTraffic apps on the secondary machine. Everything was working fine until yesterday. Out of the blue the WideClient was no longer connecting to my flight sim computer. Nothing was changed with either computer. I have attached my log files. The second thing. I have created a new profile in the FSUIPC drop down on P3D for the Aerosoft A330. Shouldn't that profile remain active until I either change it or end the flight. Several times my buttons quit working and I go back and see that I have to select the Profile in order for it to work. Thanks, John FSUIPC5.log WideServer.log WideClient.log

Pete, I tried your above fixes without any results. I went ahead and deleted the fsuipc.ini file and started from scratch. I assigned all axis and buttons like I had before with the exception of the throttle controls. I then went in and reassigned the F1-F4 keyboard keys for throttle like the default simulator is setup. Everything worked fine in regards to the auto throttle. Looking at my old fsuipc.ini file, one of the guys noticed the discrepancy: Throttle1=-16384,-512,512,16256/32 Throttle2=-16384,-512,512,16383/32 His thoughts were the values for 1 & 2 should be the same. I haven't had any problems with my other payware aircraft so I didn't know if that would affect the iFly 737 or not. The same comment has been placed on their forums as well. Thanks for all of the help, John

My bad calling it a "BUG". That is not the case and I shouldn't have used that term. I changed to FSUIPC settings so that I could "fine tune" sensitivities and such. I was having issues with FS9 changing the null zone and sensitivities. It has been working out real well until the iFly 737 came along. I don't use the Reverse Range as I have my Saitek throttles calibrated so that when I pull the throttle back, it activates the decrease throttle command which puts the engine in reverse thrust. John

Ok, so here is what I did. I removed the 2 throttle axis from FSUIPC and am using FS9 for throttle control. Now the question is why am I having to do this in order to get the AT's to work correctly. All of the other payware planes (PMDG 737 & 747, PSS 757, LevelD 767 and Wilco 737 & Airbus) that I have aren't affected by the FSUIPC bug. What can possibly be happening with the throttles that would keep them from working correctly when using calibration through the FSUIPC program? Very frustrating that it is affecting only this airplane. John

The free version of FSUIPC is installed when the iFly 737 is installed. Could something have corrupted my fsuipc.ini file in the installation process. John

There answer is to delete the fsuipc.ini file and have it rebuild when FS9 restarts. Not really what I am wanting to do with all the work programming my axis and switches. :angry: I should get a chance to work with it tonight. Before completely removing the throttle assignments, I will try changing to "send to FS as normal axis". We'll see what happens. Thanks for you help Pete, John

Pete, I won't have a chance to mess with it the next few days. I am getting to fly a real 737 simulator tonight for a test conducted by the UofI's OPL lab. Link located here: OPL's 737 Sim When I get a chance I will remove the assignments for the throttles and use FS9 assignments for throttles only. Thanks, John

Ian, Yes that was my plan. I was hoping that if it did work, I would try cutting and pasting the yoke, rudder pedals and throttle quadrant settings into the new ini file. John

I am having issues with the AutoThrottle on the iFly 737NG and have been told that I need to delete the fsuipc.ini file and have fsuipc automatically recreate a new one when FS9 is started the next time. Is anyone else having these issues? I am leery of doing so as I just got all of my sensitivities, etc setup correctly. ARGH!!! John

It seems to be working now. I found another set of documentation that helped me with the setup. The rescan button wasn't being used correctly I don't think. I just need to get my problem worked out with the rudder pedals and brakes. Thanks Pete, John Edit: Update - the rudder pedals and brakes are fixed now as well. I had to adjust the endpoints for the low side axis.

Ok so after deleting the FS9.cfg file and starting from scratch, I was able to get the correct controls to work, but only half the travel. When I would go from 0-100% on all 6 levers, the control didn't start working until I was at 50% on the control. This doesn't work real well with thrust reverse. :mrgreen: I tried looking at the joystick calibration settings but I am unable to get them to change to the full travel. John