Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About NomadRider

  • Rank
    Advanced Member
  • Birthday 01/01/1970
  1. Anything I can do to troubleshoot WideClient issues? John
  2. 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?
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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.
  13. 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
  14. I am going to delete the FS9.cfg and the fsuipc.ini file and try starting there. It seems odd the axis are still assigned after deleting the Axes part of the ini file. I will post back with the status tomorrow after my testing is done. Thanks, John
  15. I tried the new versions and I am experiencing similar things. I don't have the time out issue with the Saitek levers, now if I set the first 2 levers to throttle 1 and prop 1 it seems that they somehow reverse and are then backwards. This is very frustrating. When I go back to my old FS9.cfg file before I started messing with this those no longer work correctly either. John
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.