Dougal

First off, this is not a request for support, it's simply a HELLO and a thank you! It feels great to be BACK in here after years of being 'on the dark side' in XP11 and without FSUIPC. I gave up on Microsoft sims some years ago when I defected to XPlane, but now I have FS2020 installed and can once again return to my trusty companion that is FSUIPC, and have it do all things properly:-) I nearly fell off my chair when told I could buy this again for FS2020:-) Pete Sir, you have been around for as long as I can remember. You and I probably don't like to remember just how many years that is:-) Returning to FSUIPC is like 'coming home' for me, and even better to see John's name there also! GREAT to be back! And thanks to ALL concerned in keeping this truly GREAT product alive and kicking.

Found the fault Pete! HARDWARE!!! Most unusual. There's something wrong with the main USB ports on the motherboard. Thankfully, whatever the issue, its only affecting the main ports, and not the extra onboard ports. I had to update the BIOS to accept a new i7 7700k chip, and now realise, that's when my problems all started. Trouble is of course, I can't roll it back as then the chip isn't supported. I've contacted Asus, but you know what they're like at implementing stuff on older boards (Z170). Some things will work correctly on those USB ports, but not all. Thats why it was hard to track down the issue.

Yea Ha! I can now use FSUIPC to control all my aircraft once again! Frustratingly, it ended up requiring a COMPLETE re installation of Windows and P3D to cure the problem. I ‘THINK’ the problem was within the Windows USB control environment. It really isn’t until one has to do without it, that you realise just how important FSUIPC is. Ho Hum…. Now I just have reinstall all my addons……

I guess i probably knew that as i've never had an issue actually caused by FSUIPC itself. I must have something conflicting with it, but god only knows what:-( I'll stick with X-Plane for now until I find the issue....

Hi Pete Sorry about that. I had the answers done and thought I'd done a 'copy & paste' but obviously forgot the 'ctrl-V' ;-) The problem is spread evenly between the two quadrants. Not 3 axis as I first thought, but four; axis 1 & 2 on both units. They are both USB (not PS2) and independent of each other; each being plugged directly into a separate motherboard USB port. No hubs in use. The issue is both in the calibration and axis assignment tabs. Within FSUIPC, the same levers always act exactly the same way, behaving just like the pots themselves are damaged. They definitely are not. They’re almost new, and function perfectly outside of FSUIPC which doesn’t make sense does it. Never thought to keep the old ini file:-( and only keep backups of C (Windows) and D (Data), so no FS backup. Need another HDD for this.

I'm hoping this new log will tell you something;-) I hadn't realised just how much I take FSUIPC for granted. I'm really missing the profiles. FSUIPC5.log

This is really strange. I’m still having this issue and not able to use FSUIPC at all for assigning or calibrating the Saitek USB throttle axis. No problems with joystick axis. This all started after a Windows and P3D reinstallation. I have two USB (3 axis) throttle quadrants. All controllers are disabled within P3Dv4. There are no conflicting commands within FSUIPC. Three of the six axis will not operate smoothly. As you said before Pete, they ‘act’ just as if there are conflicting assignments, but there are not. When assigning, calibrating and using the quadrants outside of FSUIPC, they’re fine, with no jumping around. I’ll attach the log and ini files again just in case you can see something I can’t. I’m pulling my hair out with this as I’ve never experienced anything like it before. FSUIPC5.ini FSUIPC5.log

Hi Pete Yeah it does doesn't it. If disable them completely, I have to set up a way of using the HAT switch I don't like. All my previous installations I've done this way but I guess the latest P3D doesn't like it. Still, I'll go that route and see what happens...... joy.cpl is the app in the windows10 system for calibrating controllers. I hear Stoke got it pretty bad with the winds last week. Is all well? PS Thanks for replying on sundays;-)

Been off flight sim for some time and now finished reinstalling all my flightsims; P3Dv4, X-Plane 11 and DCSWorld etc. Having major issue trying calibrate or use my two Saitek throttle controls, using FSUIPC5 in P3Dv4. If they weren't almost new, I'd say the pots are dirty. That's just how they're behaving within FSUIPC. They calibrate and operate smoothly and perfectly in Windows10, using 'joy.cpl'. There's also no issue using them directly in P3D, or the other flightsim programs, but once I disable the axis within P3D and attempt to calibrate with FSUIPC, they jump around and become unstable:-( I normally setup numerous profiles in FSUIPC, which is why I use it. It's also a new Windows 10 (x64) installation. No Saitek drivers are installed. This is a new one to me, so if anyone have any idea what might be going on, I'd be most grateful. log attached FSUIPC5.log

Ooops! Thanks Pete. I'd downloaded the latest, then promptly threw it away and was trying to use the old one (sheepish look). Just think of all that spare time you'd have if it wasn't for people like me;-)

Should MakeRwys work in P3Dv3? I get an error when trying: 'Failed to make runways CSV files' and 'Failed to make FStarRC RWS files' Thanks

Now using: [Programs] RunIF1=READY,CLOSE,"C:\FS ADDONS\OpusFSI\FSISERVER.exe" and so far seems to be working 100% cheers Pete

Cheers Pete I'll try the RunIf. Interestingly, the 'close' command WILL work. If I've launched Opus manually, the: Run1=CLOSE,"C:\FS ADDONS\OpusFSI\FSISERVER.exe" does close it

I take back the above comments;-) Once again, the entry: [Programs] Run="C:\FS ADDONS\OpusFSI\FSISERVER.exe" no longer works 99% of the time. Just occasionally, Opus will launch. Wouldn't have thought it possible. It either should or shouldn't work! Any ideas?

All now working! No idea why or how. Didn't change the entries, but after adding a few more addons and a reboot, all is now well. Happy bunny;-)

I have the following entry in the ini file, just as in the FSX version, but the applications are not starting when P3D launches. [Programs] Run="C:\FS ADDONS\OpusFSI\FSISERVER.exe" Any ideas please? I also tried: [Programs] Run1=READY,"C:\Program Files (x86)\SPAD\Spad.exe" Run2="C:\FS ADDONS\OpusFSI\FSISERVER.exe"

Hi and thanks for responding I see from my log, that FSUIPC version, is 4.6a, although I was sure I updated recently. Have restored a backup though, so that could be why. Will download latestb and retry, though I don't think it's actually an FSUIPC issue. Separate tabs do indeed show for each panel when its running. The issue, is that sometimes, like about 2 minuits ago;-) SPAD simply doesn't launch

What I think is probably very bizarre, is that according to log below, surely SPAD opened without issue. And yet, the drivers failed to launch or inisialise the Saitek devices: ********* FSUIPC4, Version 4.60a by Pete Dowson ********* Reading options from "F:\FSX\Modules\FSUIPC4.ini" Trying to connect to SimConnect Acc/SP2 Oct07 ... User Name=removed User Addr=removed FSUIPC4 Key is provided WideFS7 Key is provided Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=255 375 System time = 14/02/2015 04:30:22 390 FLT UNC path = "\\MAINPC\Flight Simulator X Files\" 390 FS UNC path = "\\MAINPC\FSX\" 640 F:\FSX ADDONS\OpusFSI\FSISERVER.exe 765 LogOptions=00000000 00000001 765 SimConnect_Open succeeded: waiting to check version okay 23806 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 23806 Initialising SimConnect data requests now 23806 FSUIPC Menu entry added 23853 \\MAINPC\Flight Simulator X Files\737 Default at VHHX.FLT 23853 \\MAINPC\FSX\SimObjects\Airplanes\B737_800\Boeing737-800.AIR 107204 System time = 14/02/2015 04:32:09, Simulator time = 11:49:21 (04:49Z) 107204 Aircraft="Boeing 737-800 Paint1" 126158 C:\SPAD\Spad.exe 127297 Advanced Weather Interface Enabled 189604 \\MAINPC\FSX\SimObjects\Airplanes\PMDG 737-700NGX\B737-700.AIR 190587 Aircraft="Boeing 737-700NGX PMDG House" 282175 Sim stopped: average frame rate for last 91 secs = 14.7 fps 501559 Sim stopped: average frame rate for last 27 secs = 16.2 fps 682957 Sim stopped: average frame rate for last 25 secs = 16.5 fps 740162 Sim stopped: average frame rate for last 35 secs = 16.3 fps 977752 Sim stopped: average frame rate for last 33 secs = 14.4 fps 981449 \\MAINPC\FSX\SimObjects\Airplanes\B737_800\Boeing737-800.AIR 981449 Weather Mode now = Custom 981449 \\MAINPC\Users\Dougal\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 995879 System time = 14/02/2015 04:46:57, Simulator time = 11:53:25 (04:53Z) 995879 *** FSUIPC log file being closed Average frame rate for running time of 247 secs = 15.7 fps Memory managed: 112 Allocs, 111 Freed ********* FSUIPC Log file closed ***********

Hello Pete Definately not running when it happens. Checked the task manager straight away, as I have that issue often with Mozilla Firefox. Would love to know what stops some programmes exiting properly, as its a right royal pain. I digress.... Will try your other suggestions....

Nothing in log it fails to launch. Don't know if that tell you anything. Doesn't mean much to me i'm afraid;-(

Just had a thought.... Although UAC is OFF, I'll try installing Spad to a different location......

I have the following at the end of the ini file.... [Programs] Run1="C:\Program Files (x86)\SPAD\Spad.exe" Run2="F:\FSX ADDONS\OpusFSI\FSISERVER.exe" However, very often the SPAD driver simply fails to launch. No idea if this relates to SPAD or FSUIPC, but thought i'd start by asking here. Being as Opus ALWAYS starts, i'm guessing the issue is elsewhere, but i can't think where to look. No doubt i'm missing the obvious, but would appriciate a pointer? Win7 UAC is OFF;-) Ta!

Thought I'd pop in here quickly just for once, when I'm NOT looking for help, needing no advice, and whiile my system is running just fine thanks;-) Just to say a BIG thank you to you Pete!!!! Ok so its payware, and I've paid for the privilage, but like perhaps only one or two other FSX addons I have, from the hundreds in my setup, FSUIPC is, without doubt, a truly indispensible piece of kit. There it sits, quietly getting on with 'doing its thing' in the background, never causing an issue, neither for me, nor for FSX. Never parading itself or shouting 'here I am' like some software. It simply gets on with it and does EXACTLY what it says on the can. Nothing more and nothing less. Without Pete and FSUIPC, my FSX world would be an even more frustrating place to reside than it often is. I know its not in your nature Pete, but take a bow and accept that your surpurbly supported piece of coding, had had a bigger impact on FSX, than probably any other single addon. For making my FS experience so much the richer, I thank you Pete! I bet when you first coded that little app all those years ago, you never foresaw where it would lead. Be proud of 'your baby' Pete. It's a corker!!!!

Hi Guys Like I said Pete, I knew it wasn't an FSUIPC problem. It had to be a Windows issue. No, it keeps the correct devices, just mixes up the assignments, so I get things like left yoke application applying the right brake etc. Makes for a VERY interesting flight;-))) I've never used a hub for my controllers. Always directly into PC USB sockets. The ini file doesn't change, so its obviously NOT FSUIPC. I was just asking as I know its come up before.

Hi Guys I know this has come up before but i cant find it anyware. Nor is it specifically an FSUIPC problem. I think its a Windows issue. Every single time I restart my PC (not FSX), I have to reallocate and calibrate all my controllers in FSUIPC:( Really frustrating:( It's like windows and or FSUIPC forgets everything when shutting down. Can anyone remember the fix please?