John Dowson

First, you posted in the FAQ section - I have moved your post to the main Support forum. Please post all support requests here. When you unpack the FSUIPC installer (you do not say which version you are using) you should find the installer exe (Install FSUIPC5.exe or Install FSUPC4.exe) together with a manual telling you what is installed and where, and how to register. When you run the installer, it should also create an installer log file (FSUIPC5 Install.log or FSUIPC4 Install.log) in both the directory where you ran the installer and in the install location. If you ran the installer, FSUIPC will be installed in a folder called 'Modules' under your FS directory. Under this will be another folder called FSUIPC Documents where the manuals for FSUIPC are installed as explained in the Installation and Registration manual. If you ran the installer and FSUIPC is installed correctly, you should see an FSUIPC... entry in the Add-on menu. If you open FSUIPC and go to the Logging tab, there is also a button called something like Open Log Folder which will open an Explorer window showing the contents of the Modules folder, where FSUIPC is installed. John

This can't happen, unless you remove the calibration entries from the ini file. Check that the axis haven't been re-assigned in P3D - its better to disable controllers completely in P3D if you are doing all your assignments in FSUIPC. Anyway, glad your problem is solved. John

In your Modules folder, under your P3D installation directory, where FSUIPC5 is installed. You can also use the button 'Open Folder' in the FSUIPC Logging tab which will open an Explorer window showing you the location & contents of this folder.If you cannot see the file, you may have to change your Explorer view options to see the file extension (you need to un-check the option 'Hide extensions for known file types'). John

FSUIPC5 runs as a dll within P3Dv4. It cannot possibly be running without the sim running - you will not see it in the task manager, only P3D itself. And if P3D is still running, you should not be able to restart it until you have closed the one already running. Did you try closing down P3D fully and restarting? If you still have your issue, please attach your FSUIPC5.log file (after you have closed down P3Dv4) and also a pic of the actual message you are getting. John P.S. You posted in the Announcements section. I have moved your post for you. Please post all support requests here, in the main support forum, thanks.

Are you running both the FS and FSRADIOPANEL as administrator? Both programs need to be ran at the same privilege level. The firewall shouldn't affect communication between processes on the same machine, but that depends on the configuration so you may wish to check this. You could post your .log and .ini files and I'll take a quick look to see if there is anything unusual. Other than that, I think you would be better off contacting the support for FSRADIOPANEL Are you getting any errors at all? John

You also seem to have not calibrated your spoilers correctly: 1=0Z,B,0,0,66067,16383 -{ DIRECT: SpoilersEntering=SPOILERS_ARM_OFF }- 2=0Z,B,0,0,66066,15000 -{ Entering=SPOILERS_ARM_ON }- 3=0Z,B,-16384,10237,66068,0 -{ Entering=SPOILERS_ARM_SET }- You have conflicting ranges: 0-0 for both SPOILERS_ARM_OFF and SPOILERS_ARM_ON, and -16384 - 10237 for SPOILERS_ARM_SET. You are probably better off calibrating a null zone for your spoiler. From the FSUIPC User Guide (section: The Easy Step-by-Step way to calibrate your controls, P42): The Spoiler (speed brake) control is a little special. It has no “centre” as such, but the facilities for setting a centre in FSUIPC are used to calibrate a zone on your lever in which the spoiler should be “armed”. You don’t need to do this, it is options: if the two centre calibration values are the same (i.e. there is no centre “zone”), then there is no arming action taken by FSUIPC. If, however, you do calibrate with a centre zone, then the values from “minimum” (the left most value), or lower, up to the lowest of the Centre values will all select spoilers down (i.e. parked). The centre zone will arm the spoilers, and the range from the higher of the two centre values up to the maximum (the right-most value) will actually operate the full range from 0% to 100% deployed. Note that if you arm the spoilers when on the ground, P3D will deploy them to 100%, as if you have just touched down. However, they should return to the “armed” position when the throttles are advanced. John

Looks like you didn't activate the logging for Axis controls, or you activated and clicked the 'New Log' button so you started a new log file which you did not attach. Could you do this again please, make sure the Axis control is being logged, and not start a new log so I can see the complete log file. Thanks, John

Can you check your assignments in FSX - if you are assigning everything in FSUIPC it is better to disable controllers completely in FSX. If that is not the issue, then I will need further information. Please activate logging of axis controls (from the FSUIPC logging tab, start the sim, load your aircraft and then move your spoiler axis through its full range, then close the sim. Post again and attach your FSUIPC4.ini and .log files and I'll take a look. John

As SIOC is installed in your 'Program Files (x86)', you probably need to run this as an Administrator. If you do this, you must also run your sim with the same privileges, i.e. also as Administrator. Have you tried this? Anything connecting to FSUIPC needs to be ran at the same privilege level, and as FSUIPC is embedded in the sim, this means that you have to run your sim at the same privilege level as SIOC. If thats not the issue, then you really need to continue your support with SIOC. Also, I take it (hope!) that you are running both SIOC and your sim/FSUIPC on the same pc? If not, it (obviously?) wouldn't connect - if you are running SIOC on a separate PC then you would need WideFS for it to be able to talk to FSUIPC on a separate PC. If SIOC and your sim (FSX or FSX-SE) are running on the same machine, the firewall shouldn't be an issue. John Later: do you have an error code from SIOC from the connection failure? This may also help....

Yes, your registry entries look a right mess with conflicting/duplicated GUIDs for different devices. It would have been a lot easier to resolve these issues if you had used the 'JoyLetters' facility (please read about this in the User manual), but its to late for this now, although you should activate this once your problems have been solved. You say: Do you mean that you have added the Flight Illusion GSA-055, as this is now recognised? I think the best way forward with this is if you could do the following: 1. First, disconnect your new devices (Flight Illusion GSA-055 and Brunner Yoke) and uninstall any software/device drivers for these. Then reboot. 2. Start P3D. load an aircraft and then stop the sim. 3. Attach the newly generated log, ini and JoyScan.csv files - better to attach the complete files rather than copy/paste. Once that is done, we can use the files to work out what needs to be removed from your registry and ini files. After that, you can reconnect your devices and install any software needed and then we can take a look at the files again. John

If you have fps issues for a complex add-on only, it wouldn't be your sound interface. If you think you have an issue with FSUIPC, please raise a separate topic/thread explaining your problem, but I can't remember any fps issues that are due to FSUIPC so I think your problem lies elsewhere. Sometimes stuttering/low fps can be caused by the autosave option being used with complex aircraft add-ons, so if it is only happening on autosave you could check that. John

Presumably he's talking about the P3D Sound options 'Windows Sound Devices', where you an select the sound devices used for primary, voice and voice capture (mic). These default to the windows default sound devices. I've no idea why this would affect the FPS so much though.... John

Glad its now working for you! John

But your ini still shows duplicate throttle assignments for throttle2: 8=DX,256,D,10,0,0,0 -{ DIRECT: Throttle2 }- 9=DY,256,D,10,0,0,0 -{ DIRECT: Throttle2 }- And you also now have an additional custom control defined: 10=DZ,256,F,23,0,0,0 -{ TO SIM: Custom control: <23> }- Not sure what that one does... Yes, after we get a log file produced with only one axis assigned to throttle1 and throttle2! Just delete one of those entries shown above (8 or 9) directly in your ini file (with P3D not loaded). This will remove that axis assignment. Really your log file is confusing as it is only/mainly showing parameter values of 0 and 16 to your THROTTLEn_SET controls. You could also try changing the throttle assignments for the A320 profile to 'Send to FS as normal axis' (rather than 'Send direct to FSUIPC calibration') and use the Axis Throttle<n> Set controls to see if you are getting throttle axis values through using that. John

In FSUIPC? Why do you think this? FSUIPC cannot 'drop assignments'. You now again have multiple assignments to your throttle2: 8=DX,256,D,10,0,0,0 -{ DIRECT: Throttle2 }- 9=DY,256,D,10,0,0,0 -{ DIRECT: Throttle2 }- Also, did you disable controllers completely in P3D, as advised (in Controls -> Other -> 'enable Controllers' checkbox not checked)? As advised, please advance each throttle independently through its FULL range. The log file attached is also a 'continuation log', i.e. you started a new log file. Please do not do this - I need to see the full log. ...later...and just saw Pete's response...try the change in UseAxisControlsForNRZ after you have finally generated the initial request log file please, i.e. - full log file (no continuation) - controllers disabled in P3D - each throttle axis assigned only once in FSUIPC - each throttle moved independently through its full range Thanks, John

That last ini looks fine - it has assigned a letter to each of your device (which is now used in your assignments) and contains the joy id numbers as well, which is needed for the mapping to the letters. Not really much point re-installing FSUIPC - its only the dll that gets installed (as well as you documents). For the test, you moved each throttle independently as asked, no? If so, your logs show throttle1 and throttle2 controls being sent at the same time. You say that you removed all axis assignments in P3D, but these have a tendency to be re-assigned. Can you check again please - and its better to disable controllers completely if not assigning in P3D, or at least for these tests. Still, not seeing any reasonable values for your throttle movements in FSUIPC though, which is strange. I'll check to see what additional logging we can add to track this down and get back to you. John

You now have throttle1 assigned to two axis on your yoke (throttle): [Axes.A320] RangeRepeatRate=10 0=0Z,256,D,22,0,0,0 -{ DIRECT: Spoilers }- 1=0U,256,D,9,0,0,0 -{ DIRECT: Throttle1 }- 2=0V,256,D,9,0,0,0 -{ DIRECT: Throttle1 }- Please remove one of these assignments. You also have your flaps assigned to 2 axis, but that is not relevant to your problem. For your log, did you do as requested, i.e move throttle1 fully forward then back, then the same for throttle2? Your log shows movements on many other axis. Could you repeat please and just use the throttles for the test. The initial throttle1 movement shows it only going as high as 7606 (less than half the full range) before it reduces, and then throttle2 the same, although later I can see higher values for both throttles, which is confusing... What maximum/minimum values are you seeing for each throttle in the calibration screen? ...later: just rechecked your log, and it tells me that the aircraft you used was the Aircraft="Beech Baron 58 BAV Flying Club G-BAVB"? I thought your problem was with the Aerosoft A320/A321? I am confused....could you remove that duplicate throttle1 assignment and provide the log of the suggested test with the correct aircraft please? John P.S. May also be a good idea to set AutoAssignLetters=Yes in your [JoyNames] section. This will prevent problems if/when you change your USB connections (which can give your devices different numbers).

I think you should be ok with 'Send direct to FSUIPC Calibration', so please use that and make sure that you have calibrated both throttle axis in FSUIPC. Once you've done that, can you re-upload your updated ini and log files, with the Axis controls logging activated (and using 2 axis in the configurator.). Please activate each throttle axis independently (throttle1 then throttle2) for the test. You can attach them to your post, no need to copy/paste them. Don't start a new log, and you can zip the log up if it is large. Thanks, John

Can you try the following please: FSUIPC5.dll Cheers, John

Also could you also check your A320 configuration - what 'Throttle Axis count' are you using? This post shows how to set-up the A320 using a single throttle axis: https://www.avsim.com/forums/topic/561341-aerosoft-airbus-professional-throttle-settings-using-fsuipc/ - but presumably you want to use a separate axis for throttle1 and throttle2, no? John

You seem to have your throttle1 assigned to your yoke: 2=0Z,256,D,9,0,0,0 -{ DIRECT: Throttle1 }- and have your throttle2 assigned to two different axis on your throttle quadrant: 8=3X,256,D,10,0,0,0 -{ DIRECT: Throttle2 }- 9=3Y,256,D,10,0,0,0 -{ DIRECT: Throttle2 }- Presumably you want both throttle1 and throttle2 on your throttle quadrant, no? Please try this first. If you are still having issues after you have resolved this, it may be that the A320/1 throttle axis don't play well with FSUIPC calibration due to priority levels. If this is the case, you could try switching the assignments from 'Send direct to FSUIPC Calibration' to 'Send to FS as normal axis', and use the Axis Throttle<n> Set controls instead. Note that you can ignore the errors reported in the log file - see this post for a (partial) explanation: Let me know how it goes. John

No problem - I'm glad his problem is finally resolved! Regards, John

Ah sorry, missed that! I'll check here....

According to the docs, 0x2B00 is read-only, so better to use 0x0580 if writing.

Could you activate Axis controls logging (from the FSUIPC logging tab) and generate another FSUIPC5.log file showing your problem, and then upload this together with your FSUIPC5.ini file please. It seems strange that it was working one day and not the next - something must have changed. Do you know what? Can you also check to see if you have controllers disabled in P3D, and if not then check your P3D assignments as well. Cheers, John