Jump to content

DarkFire

Members
  • Posts

    1838
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by DarkFire

  1. I'd also heavily recommend getting Tacview: http://tacview.strasoftware.com/product/about/en/ It's probably THE most useful tool for evaluating your own performance, see what went well and what didn't in any given situation and how to improve next time.
  2. Sounds like the centre position of your stick might be worn. Try using a small dead zone for pitch & roll and see if that makes a difference. Also make sure your stick is properly calibrated using the CH control manager.
  3. If I remember correctly no. 1 is coming to the mission editor at some point. While we wait, this looks like a very useful tool, thanks for posting the link :)
  4. Wow, that's one damned fine paint job!
  5. Ah yes, could be I misunderstood. In this situation, to answer one of the original questions, neither the radar nor the EOS will auto-lock, you'll need to do it manually. It can take a second or two for either system to achieve a lock which can be difficult against a highly manoeuvrable target. Edited to add: the fact that it's possible to turn on the radar or EOS and lock a target to change to LCOS mode needs to be added to the Su-27 flight manual. One of the few features that's missing from the manual at the moment.
  6. Read pages 63 - 65 of the Su-27 flight manual. Funnel mode doesn't use either a radar or EOS lock. If you have a bandit locked using either the radar or the EOS system, when you activate (not fire) the cannon the HUD will automatically enter LCOS mode. If you lose lock it's necessary to regain it using one of the radar or EOS modes (probably vertical scan or helmet modes) and when you do the HUD will again show the LCOS gun site. The funnel mode is only for use when you can't achieve a lock with radar or EOS and even then can only be used accurately from rear of the target. Hope this helps...
  7. Some times DCS doesn't recognise keys as what you might think it should. For example, my Roccat Ryos reports the "\" key as being something like "user 2" under DCS, so to make it work I had to re-program it under the game options. Might be worth a try...
  8. By default when in direct control mode (after the first time you press S) the nose will tend to pitch down strongly, so keep some back pressure applied to the stick to prevent this from happening. As soon as you're level re-engage the FCS (press S again). The strength of the nose-down pitch tendency increases with airspeed.
  9. Glad it helped, and welcome to the forum :)
  10. The no.1 problem people experience with controls is due to the game by default having multiple physical devices connected to the same axes in the game. Make sure that only 1 physical device axis is assigned to your pitch, roll, yaw, throttle etc.
  11. As a bit of an aside, this problem seems to be confined to the F-15C. No problems noted with TWS on the Su-27...
  12. YMMV of course, but the procedure I always try to use is this: 1. Build a mission where you start in the air. Fly around for a bit to get a feel for how the aircraft flies. Use this sort of mission as a sort of 'incentive flight.' 2. Read the manual. Read it again. Then read it again. And again, absorbing each section as I go and if necessary have the sim running so I can test things on the aircraft as I read. 3. Take things slowly and one step at a time. Learn and practice every particular procedure and facet of the aircraft systems before moving on to the next thing. 4. After you're satisfied with a basic proficiency level, go back to brush up on the manual covering whatever you feel might be your weak points. 5. Practice, practice, practice. DCS is very much a sim that rewards patient, long-term time and effort invested in learning and practising everything. Given that a conversion course for a particular aircraft for a real air force pilot can be anything from 20 - 100 hours, assume that the same sort of time investment will be necessary to achieve a basic operational capability in whatever aircraft you chose, and then assume the usual 1,000 hours for professional level employment. As an example, I currently have just over 50 hours in the Su-27 between DCS 1.5 and 2.0. I'd rate myself a very good pilot but a beginner at combat employment. Perseverance is the key. Time and effort invested will pay off. Take things steadily and when things come together the feeling of reward will be immense.
  13. I sometimes experience the same thing with wingman Su-27's, with the exception that after about 3-5 minutes the AI will eventually taxi off the runway.
  14. Good point. I recently did a great mission called something like "long range strike escort" or similar which called for a bit of A-A action then bombing 3 x IL-76's on the ramp at Batumi. 2 x FAB-500s blew the wings off an IL-76 but didn't do much more than that :(
  15. I'd say very much a simulation. The flight model for example has been verified by actual Eagle drivers, so in that respect I don't think there's anything available for PC outside of an actual USAF trainer that models the flight characteristics as accurately as DCS does. Same for the other aircraft that have professional or advanced flight models.
  16. Wow, that was one tough chopper! It shouldn't take anything like that level of ordnance to destroy, on the ground or in the air. I wonder if the chopper being on a FARP has something to do with the amount of 'health' it has. Given any options the way I'd do it would be a Kh-29T from an Su-25T. A ~600Kg warhead should obliterate any aircraft within its blast radius...
  17. Radar in BVR mode? On an Su-25? Have I vastly underestimated the Su-25 or is this thread in the wrong sub-forum :)
  18. I agree. My Pk with the R-27ER has improved to somewhere between 25 - 33%, particularly against low aspect targets within Rtr. I wonder if anything changed in the last patch...
  19. Interesting, I didn't know that. Though carrying all 3 tanks I was obviously speed limited, in reality I take it neither the belly nor the wing tanks are supersonic rated? I would imagine that the tanks also have some pretty low max-G ratings in reality. I might give this another go with just the wing tanks, and then with none to see if it makes a difference.
  20. Unfortunately DCS doesn't model fragmentation, only blast damage as 1/r^3. So, frag that would in reality severely damage a chopper well outside of the blast radius isn't there. Some weapons have much higher than reality blast damage outputs to compensate, but yes, we have to be very accurate with bombs. Given the target in the mission you just flew I'd be tempted to take RBK cluster bombs or maybe heavy calibre rockets instead of FAB bombs.
  21. Having thought some more about this, I think what it's doing is confusing different physical axes on different devices and is applying those different axes to different in-game axes under but the same label, e.g. it might think that a trim wheel on a joystick is the same sort of device as the thumb-stick on a throttle, and then call them both an "X" axis but apply them to different commands. But, it only seems to understand an input from one of what it thinks are all "X" axes, with the effect that it confuses the trim wheel on the joystick (which is supposed to act on the in-game zoom axis) with the X-axis on the stick, which is supposed to apply to the in-game pitch axis. I think this is what it's doing. Maybe.
  22. When manually assigning interface devices (e.g. joystick) to axes that's true, but the automatic assignment when you first install a module or run the game doesn't seem to abide by the same rules. For example, if you have a thumb-stick on your throttle DCS will think it's an extra mouse & assign the "mouse" X & Y axes to all sorts of weird things. The default mapping is actually pretty good, it's just necessary to remove all the duplication to make it actually work.
  23. No problem :) With regards to the yaw on throttle change problem, does it yaw in the opposite direction when you throttle up? If so, it indicates that your left & right throttles aren't perfectly matched in terms of calibration or axis curve so when you change both throttles you get a differential thrust condition. I don't have the Warthog but if it's possible try mapping both throttles as a single item to both engines & see if the problem goes away.
  24. Something changed in a recent patch. The Su-27 now releases pairs of bombs (FAB or RBK) by default.
×
×
  • Create New...