Jump to content
The simFlight Network Forums

PythonFlightSim

Members
  • Posts

    28
  • Joined

  • Last visited

Posts posted by PythonFlightSim

  1. 8 hours ago, John Dowson said:

    Where have you installed FSUIPC?

    It was installed into the location it chose, which seems to be directly at C:/FSUIPC7.

    8 hours ago, John Dowson said:

    Otherwise, please show me your FSUIPC7.ini and FSUIPC7.log files.

    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?

  2. 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.

    ihKMw2e.png

    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.

    On 10/7/2022 at 12:30 AM, John Dowson said:

    They are independent. If you assign in MSFS, you use the sensitivity windows in MSFS and such axes will not be calibrated 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!

  3. Just now, PythonFlightSim said:

    I find it very difficult to control using keys

    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!

  4. On 10/7/2022 at 3:55 AM, John Dowson said:

    Fixing the script how? Is this your issue?

    I don't see this at all and would need to see your logs to see why this is happening. The script works as expected here, although I find it very difficult to control using keys rather than a yoke or joystick...

    I think I also now understand why the Num5 key isn't working for you - you do not have NumLock on! I just tried with NumLock off, and the other keys still work but not the 5 key. So, either switch numlock on, or change the centreAllKeycode from 101 (Numpad5 with NumLock On) to 12 (Numpad5 with NumLock Off). Looks like the other numpad keys send the same keycode regardless of the NumLock state. Or, you can just add the following line to the bottom of the script to support when numlock is on or off:

         event.key(12, 0, 1, "flightControl") -- request on initial press only, NumPad5 with NumLock Off

    John

    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 😃

     

  5. 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!

  6. On 10/5/2022 at 12:37 AM, John Dowson said:

    I will take a ;ppl at the script again later today and try it for more than a few seconds and let you know if I find anything...

    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.

  7. 7 hours ago, John Dowson said:

    Enable logging in the lua script by setting the logActivity variable to true (and re-start)- that should tell you what is happening.

    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.

  8. Just now, John Dowson said:

    Those increments/deltas are over 10-times greater than the delta I started with and provided to you, which was 128. They are pretty huge increments and I can't see how you can control the primary flight surfaces with those...but each to their own!

    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?

  9. 1 hour ago, John Dowson said:

    Btw, maybe take a look at FSInterrogate (FSInterrogate2std.exe) or Examiner - both available in the Utils folder of your FSUIPC7 installation folder.

    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!

  10. 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!

  11. 55 minutes ago, John Dowson said:

    No, I do not provide support via Discord. I spend a lot of time on support as it is - I don't want to open another support channel - I would never get anything else done....!

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

    55 minutes ago, John Dowson said:

    To log offsets, use FSUIPC's offset logging capabilities (Log->Offsets..) - see the User guide for details.

    Understood, thanks.

  12. 11 hours ago, John Dowson said:

    That would be the Rudder Position offset, that the script already uses.

    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!

  13. 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 😃

  14. 1 hour ago, John Dowson said:

    If always using the script, it should be started automatically using the FSUIPC7.ini [Auto] section.

    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!

  15. 11 hours ago, John Dowson said:

    Let me know how it works and if you have any issues.

    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.

    mEv5PJW.png

    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.

  16. 13 hours ago, John Dowson said:

    You should really have tried with the trial license first to see if FSUIPC7 is suitable for your needs....

    There are various things you can try  to achieve this. The first, an easiest, would be to assign your key presses to the *_UP, *_DOWN, *_LEFT, *_RIGHT controls, but this would probably just duplicate the movement that you see when assigning in MSFS.
    For more refined control, you would need to write a lua script which would wait for your key press (using event.key) and in the handling function read the offset with the current value, most probably offset 0x0BBA for rudder, then adjust thus value with the required change and then write the value back to the same offset.

    I am a bit busy at the moment but when I get time I can look inot providing you with a lua script that does this for the rudder to get you started. What keys are you planning to use?
    Noe that if you have keys assigned in FSUIPC, you should remove any assignments to those keys in MSFS.

    John

    Thank you for the quick, detailed, reply and solution suggestions. I do have the Logitech yoke I will need FSUIPC7 for eventually anyway, but it's just that I hate how cheap it feels and prefer using the keyboard. Also allows for more space on my desk.

    Do you think there would be lag with the lua script? I usually use Numpad 1 and 3 for left and right rudder. I also very much miss how Numpad 5 on P3D would center everything. MSFS has a center option in menu, but it doesn't seem to work the same way as P3D's version did, as I think it affects fewer surfaces. Would love to get that up and working again as it makes flying with the keyboard a breeze.

    I just went in the game and tried trim, but it's too slow unfortunately.

    P.S. Thank you for being an awesome dev that goes above and beyond the call of duty to respond and even offer script suggestions. You fully deserve every penny! No worries if you don't have time to write the script, I will still need this app for other purposes. Cheers.

     

     

  17. Hello,

    I just bought FSUIPC 7 for MSFS, and would like to use it with the PMDG 738. Problem I am trying to solve with this addon is as follows:

    Context: I use keyboard and mouse to fly.

    Problem: Left and right rudder are too sharp in terms of degrees turned, as compared to how they were in P3D. So a single press of left rudder key now seems to turn twice as many degrees.

    Goal: I would like to use FSUIPC to make smaller incremental movements, when controlling flight surfaces through the keyboard. So each keyboard button press would move the surface X%, for example.

    W3K3sNs.png

    Is this possible? If so, how would I go about doing it?

    Thanks!

  18. 10 hours ago, John Dowson said:

    Sorry, but where is your name displayed exactly?

    It is unfortunately visible as soon as I select FSUIPC from the drop down menu, in the Registration section of the About tab. Not a big deal, as I will just make sure to never use it on stream, but I thought I would mention it as a suggestion for a future update. Perhaps we can toggle it off permanently, as I don't really need to see that information. Not just my name, but also my email, and another personal information. Thanks for your time!

  19. @John Dowson Thank you for the very detailed reply! Went ahead and bought the upgrade to version 6. I know its not much, and I thank you for your hard work and time over the years.

    I set up the axes by using the Direct to FSUIPC calibration option, and everything seems to be working great so far! The calibration slopes you mentioned might be the ticket I am looking for in terms of a pressure curve.

    Have a great day 🙂

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.