Jump to content
The simFlight Network Forums

Kevin Brigden

Members
  • Posts

    10
  • Joined

  • Last visited

Posts posted by Kevin Brigden

  1. Kevin,

     

     I have a version 1.1 for you. I scrapped the idea in post #10 about easier calibration. I feel that may a bit too much and some logic anomalies may occur. Otherwise I added a "latch" which takes care of problem #1 in the same post above. The controller will not connect to FS until the controller gets in a settable range based on what the what the value for FS is at the time of mode change. In "both engines" & "left engine" it will not latch until the controller matches what the FS "left engine" is at. Range for right control for FS "right engine" only. This will make the axis "unavoidable consequence" at least more livable.

     

     In ALL 3 lua files there is a new setting, "range =". This is a value +/- of the current FS value at the time the mode was changed. It will not "latch" until the controller gets in this range. If you are having problems latching, raise this number. I tested all the way to 500 but at that high of a number the controller will "jerk" the FS control slightly at the time of latching. The faster you move the controller, the higher the number should be in order to latch.

     

     In just the throttle lua there is even one more setting. My FS install did not like the "lua" type display window and would occasionally crash FS on an aircraft change. It works fine in the "greenline" display, results may vary. The setting "greenline =" will change between "lua" and a "greenline" type display. In order to see the "greenline" display make sure that the setting in FSUIPC/About "Hide all single line messages" is unchecked.  (greenline now default)

     

     To install, just copy these files over to FSX\Modules and overwrite while FS is closed. You should not have to do anything else.

     

     With these new files you should add to your preflight SOP or at any aircraft change - When in "all engines" mode make sure all 3 controllers (throttle,prop,mix) are latched by being able to move freely with your throttle quadrant. (Standard issue anyway for real aircraft)   

     

    Helpful hint - If you need to adjust any of the user settings use FSUIPC/Key Presses and assign 2 keyboard keys to the following.  Lua MAxis Throttle & LuaKIllAll. This way you can make changes without exiting/restarting FS every time.  Once all setup nicely you can delete these commands.

     

    You can get the files here.

     

    Hope this works, and...... Much better. I needed to get this type coding done for my controller's lua anyway.  :D

     

    EDIT - These should work as long as your throttle quadrant has raw outputs of -16383 to 16384. (Fingers Crossed) If it doesn't and the outputs are different we would have to figure out what the raw outputs are.

     

    Roman  

     

    That's awesome, thanks Roman! I'm going to be out of town for a few days doing a rally down to the south of France but I will report back next week when I've tried this latest version.

     

    Many thanks

  2. My mistake, I needed to remove the existing calibrations before recalibrating. It now works! I suppose the only thing I need to figure out now is how to prevent the activation of an axis suddenly changing the position of an axis after a mode switch. I.e. after setting the right throttle to 80% from idle, I don't the left throttle to flick up to 80% as soon as I move it. However, I think this is an unavoidable consequence of having the physical lever left in the 80% position and in any case I am prepared to live with that. 

  3. Kevin,

     

     I already have a better codes set in mind. 1. After switching modes, the axis of the controller will not engage until within a small range of the current axis already set in FS for each throttle, mix & prop. 2. Easier calibration - instead of having in the both "mode" the controls set to "all" engines set the control input to engine 1 and 2 separately. Drawback at this point - only good for 2 engines.

     

     Just a quick test and this should work for 3 buttons. Through the "Buttons + Switches" interface you could use Offset Byte Set with the offset being x66C0 in all 3 modes. Button 8 value = x00, Button 9 value = x01 & Button 10 value = x02.

     

    Or hand editing the .ini under [buttons]

     

    XX=P0,8,Cx010066C0,x00

    XX=P0,9,Cx010066C0,x01

    XX=P0,10,Cx010066C0,x02

     

    Will not have much time today to try new coding but hopefully tomorrow.

     

    Glad it is working for you.

     

    Strangely, that particular code works with the throttle but now the mixture and prop no longer respond in any setting. 

  4. Roman,

     

    That worked perfectly! Excellent work much appreciated! Can I ask a couple of questions of you please?

     

    1. At the moment, this switching works by using a single switch to cycle through the modes. Is it possible for me to modify the scripting to enable use of an individual switch for each mode? i.e. switch 8 for mode 1, switch 9 for mode 2 and switch 10 for mode 3? My understanding is that I will need to use a different offset command to the one used in this profile data. I understand that at the moment the command is instructing the offset to increase by a single byte until it reaches a count of 0, 1, 2 and then it loops back to 0. So am I correct in thinking that I need to use a byte "select" or "set" command?

     

    2. You have saved me from spending a needless £40 on a second throttle quadrant from Saitek. Please see your private messages. 

     

    I also believe that on Pete's return this thread should be a made a sticky or placed in the FAQ because I seriously doubt I am the only person who wished to do this. 

  5. Kevin,

     

     It is much more complicated than just a button assignment and axis assignment. You will need a LUA file tailored to your needs. I have a LUA file that will have to highly modified and will give it a shot. There is one drawback to using this method. The axis of the controller does not know where the actual FS control is therefore when you switch modes and move the controller axis the FS control matches the controller axis. In any case will help out in creating a LUA for you, it may take a few hours/days since it's been awhile

     

    Roman my apologies, I should have said that I had fully followed Pete's instructions (including the LUA file) however thus far I have not been able to make it work. As such, I think I was missing something obvious. I'll try your tips now and see how I get on. Please bear in mind, I am a mechanical engineer, not a software engineer so my programming skills are... not the best!

  6. Just by way of an update I attempted this again this afternoon but to no avail. I'm sure it's something simple I've missed. 

    [Buttons.Beech Baron (Default)]
    3=P0,8,Cx030066C0,x000100E5
    

    I appreciate Pete's away but if there's anyone who can spot the error please advise. 

  7. Hi Pete and the gang, hoping you all might be able to help me out here. I've read through the tutorial material and done a forum search but I've not quite found the answer I'm looking for. 

     

    What I'd like to do

     

    I have a single throttle quadrant for the Saitek Pro Flight. I understand the concept of compound button mapping and I would like to apply this to twin engine controls. Specifically: I wish to be able to control both engines throttles, props and mixtures when in mode 1, the left engine controls in mode 2 and the right engine controls in mode 3. I thought this might be a case of simply applying the relevant logic statements as per compound buttons but that doesn't appear to be the case. 

     

    i.e. 

     

    [Axes.Baron 58 - Twin Piston]
    ...
    
    
    2=C(+0,8)0Z,256,F,65765,0,0,0
    3=C(+0,8)0U,256,F,66291,0,0,0
    4=C(+0.8)0V,256,F,66292,0,0,0

    In this instance, button 8 represents the mode 1 detent of the control wheel on the back of the right hand grip. My plan was to then generate similar lines of code for "engine 1 prop, engine 1 mixture" etc. Unfortunately, this first stage in my testing rendered the axes inoperable suggesting I cocked up the syntax or that it simply isn't supported. 

     

    Any suggestions?

     
     
     
     
×
×
  • 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.