![]() ![]() sim/current-view/goal-heading-offset-deg 0.0 Should now be the most finely tuned rudder script possible !!! So converted it back to rudder and deleted the high low bindings. Note also how low I have been able to set deadband and tolerance factors, rudder (view) centres nicely and not a jitter in sight. Note to test this I added GUI to show "LO" and "HI" when you hit each end stop. The problem of not quite getting the full -180 at full twist either way can be mostly overcome by adding "low" & "high" scripts to set-prop + or -180. The deadband and tolerance definitely are more effective outside the bindings You sure could see even a tiny jitter using Helicoptor-View! I know thanks to our exchange on this topic just how to do that as I reckon your -180 view will be better at showing jitter than any rudder will. Great this xml stuff Mike, What I'll do is put 'em both in my stick xml and test both out with different deadband & tolerance factors. Same thing if you have more than one variant of say 777-200 keep 'em in zips in Aircraft folder and extract your choice for the day! The old one will still be available safe in it's own zip next time you need it. Then simply delete the current xml and extract the new one you choose for that flight. Keep each different joystick xml in a zip in your manufacturer (say Saitek) folder. Here is my tip to quickly swap to another joystick xml because it may suit a particular flight better. In fact I have currently 3 stick xml files which I can swap easily. My stick xml too Mike, always making mods. Will remember that it overcomes the potentiometer jitter effect. So now you fixed yours you have 2 different code-boxes, both will work with your twist axis. But that is the code I tested your -180 View on not your original. ![]() It does the same job but using a different construction. Glad you fixed it Mike, The 0.1 deadband you queried is in the code box you appear not to have seen in my earlier post. My full custom joystick xml file (which also remaps zoom to the hat) is located here:īeware that I may make modifications to this file at any time without warning, so ask me if you think something's hokie! itismike Posts: 47 Joined: Fri 11:05 pm Callsign: EZSPIN sim/current-view/goal-heading-offset-deg It also is optimized for airplane piloting, so the view increments in smaller steps first, then when looking behind you it jumps several steps at a time (the 'power' command does that): This "may not be suitable for all viewers" because it introduces some unexpected behavior, such as: if you look far left, then quickly look far right, it looks left instead until you allow it time to re-center. I ended up using both dead-band and tolerance for the smoothest result. Thanks for making me analyze my code so carefully! Sim, you may want to move that line up if your rudder ignores dead-band. Also, I confirmed dead-band is ignored if it is located inside of the tags, so there is no error in the documentation. I removed the equal sign and dead-band works as expected. I had an equal sign in in the dead-band line. It was a typo in my originally posted code. Here is the rudder script I use which looks different whether it can control panview instead of rudder I have no idea but I will see if your -180 degree view idea works. What view function do you expect this rudder script to perform (Pan-View?)and is it doing what you wanted? Is your HAT busy doing something else as that will pan the view better? The deadband 0.4 is supposed to eliminate the mid axis jitter so reading between the lines I have to guess you have a jittery view when the twist is centralised and increasing the dead band doesn't cure it? Does it work ok if you revert it to controlling rudder? sim Mike, Not that clued up on this particular one but you have not explained the problem properly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |