Jump to content

Thump

Members
  • Posts

    298
  • Joined

  • Last visited

Everything posted by Thump

  1. Glad to hear you're having forward progress! Some quick images that might help both your horizontal & bank concerns. Horizontal: Slight correction to my last. Place the pod in the upper right corner of the HUD glass, that will make a straight line down the middle of the drogue pod Bank Angle: The simple answer is to just match the wing bank of the tanker. The biggest issue is that the tanker never informs the pilot that they are getting ready to enter the turn (which happens IRL) and this causes a YOLO event. Because the tanker is functioning in 0's & 1's, any bank movement should be considered as an intent to turn. They will go to approximately 27 degrees of bank (probably 'autopilot' software rules). This means that once you start seeing the turn happen, start your effort to match them and know they will stop around 30 degrees of bank. Because of reaction time, you will probably need to initially not match their wings, but go slightly beyond it until the LOS of the tanker in your canopy stops. If you are in position and the LOS of the tanker has stopped where you want it, then match their wings. I've attached 2 pics to show what I'm talkin' about. Cheers, Thump
  2. Hopefully this might help with the PIO stuff. My TM Warthog Curves/Settings (factory base, no mods): Pitch: 3, 100, 100, 15, no boxes checked Roll: 3, 100, 100, 15, no boxes checked Yaw: 0, 100, 100, 0, no boxes checked Throttle(s): 0, 100, 100, 0, no boxes checked My (unsolicited?) A/R Techniques to prevent PIO: Closure/Distance: 1) Know your tanker's speed in IAS (i.e. the speed you see in the HUD). Do this by locking the target and do some quick public math. I believe they give a TAS speed and not IAS, so if you go off of what they say, you will have closure issues. This will get you "in the ballpark" to be refined in pre-contact. (I.E., they say "at 300 (knots)", I lock them up anticipating it being +/- 10-20 knots depending in refueling altitude). I use that as a baseline to get into pre-contact. 2) Once you know your tanker's airspeed, get behind them and match them in pre-contact, quick glance at your current IAS with them at ZERO visible closure. For argument's sake, they are going exactly 300 knots indicated with you having zero visible closure in pre-contact. That is now your baseline number and deviate from that number no greater than 2-3 knots. With that ZERO visible closure & known tanker IAS speed, make a mental note where your TM throttle physically is. Any movement in throttle from that "starting" position will require corrections to get back to that zero visible closure state (example: if I add a hair of power to get 2-3 knots closure, I need to take out a hair and a half to decelerate back to tanker speed, once at tanker speed, I will need to add a half hair back in to get back to my "starting" throttle position to maintain tanker speed). If you're moving it greater than a few hairs to generate the 2-3 knots closure, you're moving too much. This technique will give you stable fore/aft movement. In Steps: 1) Call Tanker, get stated speed 2) Lock tanker, get general speed to get into pre-contact 3) Once in pre-contact, establish zero closure actual IAS with reference to HUD. 4) Establish "starting" throttle position mentally with Zero Visible Closure IAS Note : If tanker starts moving (i.e. the start of a PIO), Look at HUD, put FPM on horizon. Gentle & decisive but timely corrections will help. Vertical (when ready to go from pre-contact to contact): Rule 1: DO NOT STARE at the basket, do not make corrections solely off the basket. Fly off the tanker for general position and make small corrections to align the probe with basket. Rule 2: Fly a bit below the tanker as wake turbulence will kick you around a bit these days. 1) Use the manual gun cross in the upper right hand corner of the HUD & place the basket in it. Use the controls smoothly to keep the basket there until you are a few feet behind the basket. 2) Swap to a 60/40 focus between basket & tanker respectively when trying to close those last few feet. 3) If you feel a PIO coming on, use the FPM in the HUD to reference level flight. The AI tanker is usually shacked on altitude & so make timely/positive corrections to place the FPM on the horizon. In Steps: Moving pre-contact to contact: 1) Add power to get 2-3 knots closure, place basket on manual gun cross reticle (upper right part of HUD, circle with cross in it) 2) Drive up to a few feet from basket, transition to 60/40 focus between basket & tanker 3) Make fine corrections to align basket 4 ) Contact, push in a few feet to "create some slack", & establish zero visible closure (i.e. that throttle "starting position"). Horizontal: 1) Adjust as necessary to keep the drogue on the right upper corner of the HUD Once Connected: 1) Keep corrections very small. 2) Remember that zero closure speed you established in pre-contact & your corrections are now based on tanker LOS movement in canopy & not airspeed directly. 3) Reference FPM if you feel like a PIO is coming on and get it back stable on the horizon. 4) If you start entering a vertical PIO, smaller continuous corrections to stop the tanker LOS (line of sight, ie movement in the canopy) in any position is better than trying to solve that problem & return to perfect contact all in one go. I.E. Cut the corrective process into manageable sections. Hopefully this helps & wasn't too overbearing. Cheers, Thump
  3. At about the same rate as dynamic weather & enhanced ATC.
  4. Looks like I hit a sensitive spot... enjoy the next decade of waiting for a complete map
  5. Just poorly worded. In any case, my overall point about the topic is made so I'll be refraining from posting further on it unless I'm directly addressed.
  6. Still not my point. Ground, whether at 1 foot elevation or 25,000, is dangerous in any significant weather (of which you made a very specific point).
  7. Not the point I was making in that post...
  8. Why was I quoted in this? I get the "master genius plan" baked up by ED.....
  9. So is a 300m hill in the bad weather. What's your point?
  10. You read the announcement and missed that the SOUTHWEST of the map is the most complete and will be sold first at at the highest detail? Ya might want to get the cliffnotes version next time.
  11. Doubt. You'd might get people knowing Helmand/Bastion/Lash (which are right next to each other) and KAF but I'd put money on damn near everyone being able to remember Kabul over any one of those locations.....but you can justify their decision all ya want. You're gunna need to wait a few years....all those mountains are in the Northeast. You know, the place they teased but didn't include in this release.
  12. You sweet summer child.
  13. Can we break it down a little further and pay per killbox keypad?
  14. 1) That point that you quoted doesn't apply to you. 2) When ya tease Afghanistan by giving Bagram coordinates and then don't include Bagram....They could have done themselves a solid and did...I don't know, a part of the map on release? Kandahar is a moderately known location/base. 3) You can look forward to it all day long. Me voicing my astonishment as to their prioritization after 20 years of U.S. conflict in the area where the lion's share was in the East on the Pak border shouldn't change that. You're free to buy it, enjoy it, and play with the toys that they give you. I would put money on far more people being familiar with Bagram, Kabul, Jalalabad, Mazar E Sharif, FOB Shank, & the Khost bowl to include the borders along Pakistan than what is in the West, hence my comment. Not gunna buy it in this state....pretty simple. Edit: You are now how the excellent opportunity to pay for Afghanistan 3 times since apparently the country is fractured into West, East, & North.....
  15. Once again, you missed the point. Thanks.
  16. There's literally one chance to stick the landing and it was East by about 200 miles....
  17. We are quickly approaching end of Q1 2024....any form of communication/update would be appreciated.
  18. Lmao. This is both sides pointing the finger at one another saying, "it's THEIR fault.!!" Bignewy pointed the finger at OnRetech and now it's ED's fault. It honestly sounds like a project abandoned and still being sold.
  19. Can we get a progress update? This map has been languishing for quite a while.
  20. I appreciate the out reach but it has to do with MP being heavily affected by the 2.9 update and was looking to see where the devs were on finding a solution to it.
  21. Can we get an update as to where we're at? This has been a R O U G H release....
×
×
  • Create New...