Jump to content

autogyro

Members
  • Posts

    44
  • Joined

  • Last visited

Everything posted by autogyro

  1. None. I have that turned off, although I was playing on Open Conflict, which may have overridden my off setting. I never even got off the runway.
  2. Could this be related to the as yet unimplemented flame out and compressor stall modeling? I've definitely experienced this as it caused me to crash on take off.
  3. Was the F-5E on blue or red in round eight? I'd happily sign up and join red to fly it as a MiG-28 pilot.
  4. The A/A1 gunsight lead computing doesn't mean you place the pipper on the target. You still have to provide lead in front of the pipper for maneuvering targets. Someone correct me if I'm wrong but it is a real time sight to show the position of the bullet now in real time if it was fired one bullet time of flight (ToF) ago, taking into consideration target range, target range rate and your movement. Dogfight Guns mode and I believe the 2 normal guns modes boresights the reticle 4.7 degrees below the ARL in line with the radar boresight... that could be what you're experiencing.
  5. In the same boat. Unfortunately there's no easy way to make spotting easier without using imposters for VR users - even on 2.0 pixel override it's extremely difficult to see targets as they blend so well.
  6. Both issues have been resolved as of the 1.5.4 patch from last week. Arguably the 9P5s are still slightly underperforming... but both they and the A/A1 gunsight mode is working.
  7. Updated version 3, including trim takeoff tables, turn performance charts and ZSL sight depression settings. I did not include the nose/tail arming though as it didn't seem necessary. Refer to links in first post - the Google Drive link is updated, with the DCS link shortly to follow. Edit: Both are now up to date.
  8. Yes gravity will feed the engines but I believe you are recommended not to fly above 25,000 ft with inoperative fuel pumps. Also can't be pulling negative Gs for obvious reasons.
  9. Pylons are not supposed to have a significant effect on handling of the aircraft.
  10. Good post and I too have found difficulty, especially in VR with target acquisition and maintaining visual.
  11. This is "corrected" for altimeter lag as it had taken true altitude via the stats at the bottom of the screenshot, he hasn't used the altimeter inside the aircraft. All the values check out to me and thus I agree that the manual sight tables are not producing consistent impacts with the module.
  12. Luckily enough those are already default key commands. Look for the CW or CCW key binds for the various knob commands.
  13. Did you remember to turn on pitch and yaw dampers?
  14. Unfortunately you can't simply use the bombing tables as the number you input into the Sight Depression setting. You have to adjust from 0 mil setting down to angle of attack and add that to the Bombing Table value.
  15. How'd you work out 177 mils? I'm seeing for 400 KTAS release, assuming full load, roughly ZSL AoA = 56 + 16 + 0 - 35 = 37 Sight depression = 37 + 183 (from Bombing table, 0 degrees 400 KTAS 400 ft release) = 220. Edit: I guess flying at 480 KTAS with a lighter load will be about closer. ZSL AoA = 5 (centerline store and sidewinders, assuming 18000 lbs) Sight depression = 156 And for 440 KTAS with a full load ZSL = 15 Sight depression = 186
  16. Really fantastic series so far! Keep up the great work
  17. Looking forward to it!
  18. So it appears for new players there's some confusion as to how the radar operates in its different modes and what all the RWR settings do. Hopefully we can distill some tips on how to best make use of it, in this thread. First things first, bind the STBY and OPER modes to easily accessible keys. You can't fight toe to toe with most fighters so subtlety will be your specialty. Have a look at Chuck's excellent guide and the manual for radar basics. I won't recap what's in there but I'll explain what it actually does. When you switch the radar on, the radar acts as a B Scope radar. This means range in the y axis and azimuth on the x axis. When you lock onto anything it changes to a C Scope display - elevation in the y axis and azimuth on the x axis. In this mode it acts sort of like a mini HUD with your target drawn as an aiming cursor. Now when you press the radar acquisition button, certain things happen. Firstly, the radar goes into a boresight kind of sweep. Instead of the normal 2 bar 3 degree sweep across 90 degrees azimuth, it maintains a 4 degree conical scan about the TDC and antenna elevation. That's it. That's what happens when you press acquisition. Actually locking up a target is different matter. This is generally done automatically and often coincides with the press of the acquisition button, but you will soon realise that this is not always the case. It'll look like a lock, since the TDC stows to the left but you get no locking information. What gives? Well the radar cone isn't detecting a signal strong enough to get an automatic lock. What you can do is cancel the narrow sweep and try and acquire again. That's what most of us do. However, if you're close but not quite there you'll still see the target bar on the radar scope. It just isn't a strong enough signal. You can alternatively fine tune the radar conical scan by gently manipulating the TDC or the antenna elevation until it does lock. This also helps you fine tune exactly where in the sky the contact is. As an aside, you want to be locking when the target on the radar is not flashing. The signal should be bright green just after sweeping through and remain lit until the vertical scan bar passes over the target again. Often it's your antenna elevation which isn't quite pointed at the target. Secondly, you can determine the targets relative elevation to you as the antenna elevation is noted in degrees, even without a lock cursor. You can therefore zero in on a target well outside the 10 nm lock range by flying at the same pitch as the antenna elevation and keeping the azimuth at 0 degrees. For the RWR, I suggest running Priority RWR mode - this gives 6 maximum contacts on your RWR ordered by threat priority so you don't get contacts too far to distract you. You can also run TGT SEP, which offsets the target bearing on the RWR so you can clearly read the radar type without it overlaying others. The highest threat priority will be at the correct bearing.
  19. Ok consider it done! I'll also add in the nose/tail arming table as well. Finally I'll also add a page or two on how to calculate sight depression without reverting to charts as it appears to be a source of confusion at the moment.
  20. No ILS or VHF radio I'm afraid for our module.
  21. Rev2 uploaded. Includes dive bombing tables for Mk82, Mk82 SE, Mk83, Mk84, M117, M39 20mm HEI, 2.75 FFAR.
  22. Are you guys adjusting the attitude pitch zeroing on the ground for these bombing run tests? I.e. zero at nose hiked position such that the attitude indicator shows 0 degrees pitch at cruise?
  23. Make sure you press the missile uncage switch when you hear the lock tone so the seeker head tracks the IR source. The missile seeker field of view will be fixed in an upcoming patch. Have you got both launch rail pylons selected when firing your sidewinders?
  24. I'd love to see a Thunderbirds livery based on the T-38 Talon.
×
×
  • Create New...