PythonFlightSim

It was installed into the location it chose, which seems to be directly at C:/FSUIPC7. What sort of personal information about my computer do these logs share? Is it possible that it's not working because I am using a different livery for the 738?

Here is what I see when I am loaded in with the PMDG 738. Shouldn't those fields all be populated with what I assigned them with when I set them? For example, where do I quickly check the slope I set before, so I can tweak it? I check the profile button and selected the profile I had set up before, but still nothing populated. This feedback might be more of a UX one again. I should be able to easily see whether the plane that is loaded has calibrations set in FSUIPC. What do you mean? Does FSUIPC check to see if I customized MSFS settings? Wouldn't this prevent me from going back to FSUIPC calibrations once I modified MSFS ones? Also, is there a way to toggle FSUIPC callibrations off, whilst still leaving it on and connected? Let's say I want to quickly switch from FSUIPC calibrations to MSFS ones (mainly for testing purposes). Reason being that I have an addon called PACX that needs it to work, so I don't just want to shut it down. Thanks!

On a side note, I just wanted to say that once you get used to it, it makes it so easy that I feel it's like cheating. You can count on the preciseness of each button press turning X degrees, whereas with yoke, its by feel, and therefore never identical. You can also count on it staying at that X degrees turn, whereas your body can have small movements for various reasons, that will slowly affect the degrees. For sharp turns, it doesn't work so well, lol. For landing though, it's always butter. Most importantly, I won't always have a dedicated room for a yoke on a desk, so being able to fly with less desk space is real handy. Cheers!

Hard to explain over text I guess, which is why I was hoping to just share my screen with you. I will send you the logs sometime as well as perhaps a quick video capture of what is going on. I definitely did not have num lock on as the rest of the controls seemed to work fine without it, so that explains it! Will change the code so it works without it on. Thanks again 😃

Hello, I set up direct calibrations yesterday in MSFS through FSUIPC. I went in again today and found that all the calibrations were missing. I did save everything to a profile called Test-1, but I am unable to load a profile as the profile checkbox is grayed out. On a separate note, I am wondering if with MSFS having its own sensitivity window, whether FSUPIC calibrations are still fully necessary, or even cause conflicts with each other. Thanks!

Thank you, sir, but no worries, I have abandoned this pursuit as I don't want to waste anymore of either of our times. Either way, I greatly appreciate every minute of your help on this matter, and I do think that there are others out there flying on keyboard. If we do end up fixing the script I would use it in the future. I am having an issue with my FSUPIC calibrations disappearing, that I will open a new thread about.

It seems that the enabling of log slows down the game when logging, unless I am mistaken. In order to reproduce the issue, I need to click a couple times in a row, and thus might not be able to reproduce it with logging turned on. Will keep trying to debug it as I get more time.

It's probably because I've used a keyboard to fly with MSFS since it's original version, lol. Didn't have the money for a proper one, and I still think the Logitech one feels cheap, especially with a lack of force feedback like the driving wheels have. One day I hope to be able to afford a Brunner yoke or something similar. Reproduced a bug I keep experiencing. It seems that after you take off, if you increment past the center of an axis, you can end up not being able to increment back past that axis. I end up being stuck in one axis direction, unless I resort to holding the button down, to get back past that axis again. Doesn't always happen, and I am wondering if it's detecting that I am trying to hold down the button, when I am not?

Thanks! That was very useful. Using that tool I was able to set increments to about half their default value. local initialRudderDelta = 2000 local initialAileronDelta = 1500 local initialElevatorDelta = 1000 Centering still doesn't seem to work for me, even with the default Cessna, but I realized the built-in centering should be fine for now, with it just missing elevator centering. Cheers!

Where should I be looking for valid entries for that Offset field in the Offset Logging window? I tried going through the documentation but it is very lengthy. Tried some Rudder related codes from the Offset Status PDF but nothing was printed to console. One suggestion would be to make that Offset field a drop down perhaps, or have a link from that window to a quick cheat sheet showing valid entries. Tooltips above the headers Offset and Type would also be useful, as I am not sure what they are referring to. Thanks!

That is absolutely fair and understandable. Just thought it might be faster. Understood, thanks.

How would I go about debugging this value? I enabled IPC Read and Write, opened FSUIPC console, enabled log activity in the script, but it does not seem to show what is printed out using ipc.log(). Do I need to check a text file somewhere for this log? Any chance I can add you on Discord please? Thanks!

Thank you for the new script! I understand the code so I should be able to tweak it myself as well. I was working with flightsim dev tools last year, and found something that would give me a readout of in-game stats. Am wondering if there is something, that will tell me exactly how much the rudder moves, so I can compare output from default controls, with script. Will let you know how it goes! Hope you had a wonderful weekend 😃

Just to double check, if I have it in the [Auto] section, I don't need to "bind" it through the menu as well on click or release? Or do I still need to keep the on click? I am also seeing some weird behavior with the PMDG 738, whereby single clicks do not work anymore when I want to cross the center, so to speak. So if I am turning left, and click right until the point I should be able to start turning right, it only gets to center and stops. Wonder if this is related to the reversed axis comment from earlier. The only thing that works then, is to hold down the left or right rudder key, which then moves it too much. In general it seems the PMDG is a bit harder to control that the Twin Otter is, so I have some tuning work I need to do. I also don't understand why Num5 doesn't work when the rest do. Am guessing that maybe there is back end logic on their end to not allow centering in this fashion? Can I change the values in the lua script without have to restart MSFS, and just FSUIPC7 instead? Thanks again!

Worked on the first try, thank you! I think this was what I was meant to do, after clearing MSFS control assignments, and placing that lua script in FSUIPC7 folder. The one thing that sadly did not work is centering with Num5, even if I kept it pressed. Test model was Aerosoft's Twin Otter. Precision seems to be a lot finer than default MSFS controls, which is exactly what I was looking for. Will test it some more to fine tune over time. Thanks again for taking the time to help with this, and I hope it helps someone else out there as well in the future.