John Dowson

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

What aircraft are you using - the FSLabs A320? I don't have that aircraft so cannot reproduce here. What function is your rectangle id (0x40000039) activating? I've tried here using an A2A Cherokee and cannot reproduce, even with no delay, and have tried various multi-mouse operations. Can you try see if you can reproduce with a default aircraft so I can reproduce here? John

Good to know its now working. Profiles are for aircraft, so that you can have different assignments/settings for different aircraft. It pretty much works right out of the box if you load an appropriate profile for your aircraft. Still, always best to check the user manual! Are you referring to the set-up wizard in SPAD.next? You can use SPAD.next with or without FSUIPC. You can run without if you don't need it. The original SPAD requires FSUIPC. Cheers, John

I downloaded SPAD, ran the installer, then ran the SPAD.exe. It recognised my switch and multi-panels without a problem. I then started FSX-SE, and loaded the Mooney Bravo. Tried the flaps switch on the multi-panel, and it operates the flaps without a problem. I therefore do not know what your issue is. It may be the Saitek drivers and/or software. As I said, best to remove these completely from your system. Btw, what aircraft are you using? Have you tried with different aircraft? John

Hi, can you please try the attached dll: FSUIPC5.dll I've added a new function called ipc.mousemacro, taking two arguments, the first being the rectangle id as an unsigned int, and the second the mouse operation. e.g. ipc.mousemacro(0x25C01807, 13) I've not added much (any!) error checking yet, so please use/test with caution. Cheers, John

I've not used SPAD before. When I get a chance over the next few days, I'll download it and take a look to see if I can get it to drive my multi-panel in FSX-SE and let you know. I recommend that you first uninstall any Saitek drivers or software. Also try SPAD.next - it is a different product to SPAD. SPAD is freeware and SPAD.next is payware, but you get a 14 day free trial license so I suggest you use that. Set-up in SPAD.next is also pretty straightforward and then are free profiles available for many aircraft. Also make sure that you have the latest version of FSUIPC4 installed (available from www.fsuipc.com). John

I guess FS RAAS 2.0 may be using the sound interface provided by FSUIPC at offset 4200. However, there is nothing related to volume in those offsets. Presumably you have sound but just want the volume increased, no? And you have tried the standard windows volume control, or the volume control used by whatever is driving the sound card? If you've checked those, then I suggest that you contact FS RAAS support. Cheers, John

No idea. What does this have to do with FSUIPC? ...later: can you not just increase the volume on whatever device the sound is being played through? FSUIPC has no control over the volume on a sound device.

Its the software that you are using to drive the Saitek multi-panel that I am interested in - did you try SPAD or SPAD.next? Did you install the saitek drivers as well or not? Best not to, and uninstall if installed. I am not interested in a pic of his stuff - this won't help in his problem with the multi-panel. John

I use SPAD.next, not SPAD. You don't provide much detail on what you are using or what your problem is. If you can provide more info, I can possibly check here as I have the Saitek multi panel, although I don't have FSX, only FSX-SE. John

Hi Rob, I've added further logging in the attached if you could try please: FSUIPC5.dll Thanks, John

I don't see a problem adding this, but it may take some time as I'm quite busy at the moment....I'll flag this and add it to the list. I'll post again here when I have something for you to test. John