Announcement

Collapse
No announcement yet.

TF30 Asymmetric AB light: How much is bad?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    TF30 Asymmetric AB light: How much is bad?

    I'm playing with curves on my Warthog throttle to get the detent to match with MIL and over the detent to start AB. Right throttle is set up perfect, left throttle is having issues: MIL is MIL, but when I advance both throttles to AB simultaneously, the left throttle punches the AB Zones almost a full second in advance of the right throttle, causing some major (or so it seems) asymmetric lighting of the blower. It's almost as if getting 10 booms from the 5 Zones lighting so out-of-sync.

    I assume in real life there was always some asymmetric lighting of the burners, but how much of a delay between the left/right engines is acceptable vs potentially hazardous?
    YouTube Channel: "Clutch"

    Z390 Aorus Elite | i5-9600k @4.7Ghz | RTX2070 | 32GB DDR4 | Windows 10 | Odyssey Plus | Warthog HOTAS | 20cm Extension

    #2
    The throttles in the whole module have been asymmetric (Left more than right) ever since, which can be seen clearly by the FF and other gauges. It's about time to be fixed finally!

    As a side note, I also see this in the Hornet, but not by as far as much.

    Comment


      #3
      I understand some asymmetry is normal, but to what degree is normal? Is a one-second delay between left/right Zone lights normal or not?
      YouTube Channel: "Clutch"

      Z390 Aorus Elite | i5-9600k @4.7Ghz | RTX2070 | 32GB DDR4 | Windows 10 | Odyssey Plus | Warthog HOTAS | 20cm Extension

      Comment


        #4
        Do you mind posting your throttle curves? I would like to try them

        Comment


          #5
          All the asymmetric AB light is intentional, it take 3-5 seconds to fully light the TF30 AB to zone 5. AB operation starts at 80% of total travel if that helps for your throttle curves.
          Systems Engineer & FM Modeler
          Heatblur Simulations

          Comment


            #6
            Originally posted by Eldur View Post
            The throttles in the whole module have been asymmetric (Left more than right) ever since, which can be seen clearly by the FF and other gauges. It's about time to be fixed finally!

            As a side note, I also see this in the Hornet, but not by as far as much.
            It’s normal and is exacerbated by pilot technique.
            Originally Posted by Larkis

            “Imo im glad he is gone. He was a really mean, narcissistic and disrespectfull person. Everyone has to cheer him that hecwas a real tomcat driver and only his way is the best way. And when you question him or want to discuss stuff like "shutdown hud for landing" he get angry and offensive very fast. Im glad he is gone...”

            Comment


              #7
              My main question still isn't answered:

              How much asymmetry is normal? If the left engine leads by 1~2 seconds, is that normal? Or is the normal range more like a half second?
              YouTube Channel: "Clutch"

              Z390 Aorus Elite | i5-9600k @4.7Ghz | RTX2070 | 32GB DDR4 | Windows 10 | Odyssey Plus | Warthog HOTAS | 20cm Extension

              Comment


                #8
                What you see in the sim is normal.
                Originally Posted by Larkis

                “Imo im glad he is gone. He was a really mean, narcissistic and disrespectfull person. Everyone has to cheer him that hecwas a real tomcat driver and only his way is the best way. And when you question him or want to discuss stuff like "shutdown hud for landing" he get angry and offensive very fast. Im glad he is gone...”

                Comment


                  #9
                  So it's normal for the left engine to go into Stage 1 AB at the MIL stop? Because that's what's happening to me with my throttle's AB detent. The context of my question is being overlooked and I'm getting a lot of non-answers

                  I'm trying to fix my left throttle so that it will give me "what [I] see in the sim is normal." Currently it's established in Zone 5 while the right throttle is just beginning to light Zone 3 (or still in Zone 2!) despite moving the throttles simultaneously. I would expect maybe a 1-Zone delay, not a 2-Zone or 3-Zone delay.

                  For the record, I'm using this curve:

                  F-14B:
                  0-4-10-19-32-44-56-67-79-90-100

                  And it works perfect for the right throttle. MIL is MIL. For the left, MIL is Zone 1 AB, so I tried lowering the 10 and 18 values, but now I'm having the aforementioned issue with the left throttle lighting Zone 5 while the right throttle in the same position lights Zone 3 or so.
                  YouTube Channel: "Clutch"

                  Z390 Aorus Elite | i5-9600k @4.7Ghz | RTX2070 | 32GB DDR4 | Windows 10 | Odyssey Plus | Warthog HOTAS | 20cm Extension

                  Comment


                    #10
                    Is the left engine always ahead of the right? I'd expect light off to be more random.

                    Comment


                      #11
                      Originally posted by r4y30n View Post
                      Is the left engine always ahead of the right? I'd expect light off to be more random.
                      For me, yes. I can't get them timed well unless I lead with the right throttle by a solid 5mm. If I reset the curves to where they were, I get Zone 1 in the left at MIL and MIL in the right at MIL.
                      YouTube Channel: "Clutch"

                      Z390 Aorus Elite | i5-9600k @4.7Ghz | RTX2070 | 32GB DDR4 | Windows 10 | Odyssey Plus | Warthog HOTAS | 20cm Extension

                      Comment


                        #12
                        It should be somewhat random for each individual zone light, if it's always consistent it could be a bug or your throttle may be out of alignment?
                        Systems Engineer & FM Modeler
                        Heatblur Simulations

                        Comment


                          #13
                          Have you tried tieing both throttles to a single axis, just for test purposes?

                          Sent from my Mi 9T Pro using Tapatalk

                          Win10 x64, 16 GB RAM, Ryzen 5 1600X @3.60 GHz, 500 GB SSD, GeForce 1080 Ti

                          Comment


                            #14
                            I think the point is being missed here. I am using this curve for both my right and left throttles:

                            F-14B:
                            0-4-10-19-32-44-56-67-79-90-100

                            I use this curve in the F-14B, and there it works perfect for both the right and left throttles.

                            However the same curve in the F-14A only seems to work for the right throttle, and is "out of alignment" for the left throttle. I tried adjusting the curves, but since the mechanism of how those curves actually work is not explained anywhere, it just made the "out of alignment" a bit worse.

                            I'm asking for help fixing the above curve so that it works on the left throttle just as it does on the right throttle.
                            YouTube Channel: "Clutch"

                            Z390 Aorus Elite | i5-9600k @4.7Ghz | RTX2070 | 32GB DDR4 | Windows 10 | Odyssey Plus | Warthog HOTAS | 20cm Extension

                            Comment


                              #15
                              Just to clarify, if set to the same position both throttles should eventually catch up, even in afterburner. If you're throttles are physically at the same position and you see a larger difference between engine rpm than like 1-2% or the throttles visably in different positions in the pit there's likely something wrong with your input hardware as if both throttle tell dcs that they're at, as an example, 80%, that's where they'll be in the aircraft as well.

                              The afterburner delay we're talking about is just the time it takes for the zones to light, they should still end up the same after that delay.

                              Comment


                                #16
                                I will check that, but without a reference for how big of a delay is "normal" I cannot tell what's "normal" and what is still a hardware issue. Is one engine being 2~3 zones ahead of the other within acceptable limits?
                                YouTube Channel: "Clutch"

                                Z390 Aorus Elite | i5-9600k @4.7Ghz | RTX2070 | 32GB DDR4 | Windows 10 | Odyssey Plus | Warthog HOTAS | 20cm Extension

                                Comment


                                  #17
                                  If you set both throttles at the same location and they after delay end up in the same zone (setting) it is correct.

                                  Comment


                                    #18
                                    So the amount of delay between the two is just not even worth worrying about so long as they end at the same noz pos?
                                    YouTube Channel: "Clutch"

                                    Z390 Aorus Elite | i5-9600k @4.7Ghz | RTX2070 | 32GB DDR4 | Windows 10 | Odyssey Plus | Warthog HOTAS | 20cm Extension

                                    Comment


                                      #19
                                      Yes, pretty much. According to our sources the delay could be long enough that it affected handling.

                                      Comment


                                        #20
                                        Well that answers that....wish it were mentioned 18 replies ago
                                        YouTube Channel: "Clutch"

                                        Z390 Aorus Elite | i5-9600k @4.7Ghz | RTX2070 | 32GB DDR4 | Windows 10 | Odyssey Plus | Warthog HOTAS | 20cm Extension

                                        Comment

                                        Working...
                                        X