pijnackerpilot

Thanks for the reply and yes, Windows did update itself just prior to the 'incident'. I will check out that Joyletters facility to see how that works and how it is set up. For now I manually switched around the control assignments again so that it matches my setup properly.

Hello all, Today I encountered a rather strange issue that I cannot understand. Recently I have bought a second Saitek USB throttle because I want to replace my Saitek yoke. The original Saitek TQ comes with a PS2 connector and connects to the yoke. Since it has no HID interface, it must be connected to the yoke therefore, with a new yoke, that first TQ is useless to me. The new TQ (which I call TQ3 from now) replaced TQ1. So in my setup I have TQ2 to the left and TQ3 (which was TQ1) to the right. I use FSUIPC to assign and calibrate axes and buttons to both yokes. TQ2 orinigally was designated device 0 by FSUIPC and the new TQ3 was designated device 7. Today I wanted to make a flight in the PMDG NGXu (second with the new TQ setup) and I noticed that my Spoiler axis (labeled 0X) now controlled my throttle 2 axis (which used to be 7X). Both the -X axes control the left lever axis on both TQ's and for some reason FSUIPC has swapped around the device designations TQ2 now is device 7 and TQ3 is device 2. This happened completely by itself without changing anything manually. So all two left axes have swapped, the two middle and the right axes. The same for the buttons. Is there a particular reason why these two devices get swapped around? I am really interested to learn what might cause it so I can prevent it from happening again. Thanks in advance for all the information you can give me. For additional clarity and information I have added my log file.FSUIPC6.1.log

I did another flight where this anomaly did not occur. I think it has something to do with me having mapped reversers to the action throttle decrease for separate throttles 1 and 2. I noticed that at the start the axis was deployed. Anyways, I don't know. I did some tinkering and logged using the unsigned 16 b. setting. Tomorrow I will fly again and hopefully I'll have more then. FSUIPC6.log

Will do in the next flight then!

A log of the flight I am currently doing. Let me know if you find something out of the ordinary. Thanks Logs flight 211220.txt

I'll post up the log file later then.

A sim window with the readings from offsets 0898 and 0930 https://pasteboard.co/scpTueFASVL0.png

From SLC support: thing is - i'm not entirely sure how you're managing to show "-xxxxxxxx" .. it's a uint, which means "unsigned" integer. It can't be negative.

So I enter the provided offsets in the tab and then do what? I get no readout window or whatever, Secondly, in that document, I look up what??? According to the folks at SLC, the readouts I get are not what they expecting from the NGXu. I am sorry but this is rather unclear to me.

Many complex add-ons implement their own subsytems and dont use the default P3D simvars. PMDG, for instance, provide their own SDK and have a dedicated offset area. Have you checked this to see if the information you need is available in the PMDG offset area? I have no idea what this means and how I check this.

Yes until two weeks ago, readings were ok. Heck, even a couple of days ago, they reverted from going like these: https://pasteboard.co/O6F3Je2tAt0g.png to normal. As of yesterday. They are all weird again. I have not changed anything major to my settings, other than a bit of fooling around in FSUIPC to get reversers mapped with buttons. All else seems to be ok. I don't get any other issues. I just want this to sort out so we know what is happening here. How do I log these readouts in FSUIPC?

I got a hold of Steve over at SLC and he is telling me the following (Text is very light of colour. select and drag please) Engine1N1 > 0x0898 Engine2N1 > 0x0930 Engine3N1 > 0x09C8 Engine4N1 > 0x0A60 all declared as short (UInt16) variables.

To clarify a little, I post a link to an image that has both the main application and debug window with the odd readouts. https://imgshare.io/image/rrTx9X

Hello all, I am using FSUIPC for loads of good stuff within the sim, like mapping controls and what not. I am also using it as a bridge between the sim an the application self loading cargo. I mainly fly in the PMDG NGXu and as of late I am getting anomalous readings with regards to engine N1 outputs that lets SLC go haywire. For some reason, when engines are off N1 values should be reading 0000000000 but in my case they are reading like -33300000 or whatever. This prevents the application from working correctly. The folks over at SLC say that SLC only reads the data so they cannot help on their end. Any idea what can be done to get these readings back to normal? Regards. Daniel W