Jump to content

slug88

Members
  • Posts

    879
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by slug88

  1. Only thing I can think of would be the radar altimeter warning, which goes off each time you descend below the warning radio altitude (set to 100m by default, adjust it via a knob next to te r alt dial).
  2. You said you only bought the game yesterday. Have you installed installed the latest patch (1.01c) available on this site? I had occasional crashes like that, but it's never happened since I applied the patch.
  3. The sound you get when you switch back into the cockpit is actually the normal sound. The high pitched engine sound should only be audible when the cockpit door is open or when you're outside of the chopper. Inside things should be fairly muted. This is a known bug, and probably won't be fixed for this iteration of DCS. We just have to live with toggling outside views/toggling the cockpit door in order to get the proper in-cockpit sound for now.
  4. My own testing confirms this. I saw absolutely no benefit from changing affinity on XP.
  5. Good luck, and if things don't go as planned once again, save the track and post it here, I would love to analyze it :D
  6. There was never a submenu that allowed you to select a target type over the radio. That's not what that command means. When you transmit a datalink target, you transmit a location, as well as a tag (armor, air defense, vehicle, ingress point). So say you make an ARMOR point, and transmit it to a wingman. You can then tell the wingman to attack TARGET, and he will engage everything at that point, prioritizing higher threats. Or, you can tell him to attack TARGET TYPE, and he will only attack enemies at that location that correspond to your tag (in this example, he will only attack the armor at that point). Also, there is a very large difference between telling him to attack TARGET/TARGET TYPE, and ordering him to attack TARGETS/TARGETS BY TYPE. A TARGET order means he will engage enemies very near to the datalink point only. A TARGETS order means he will engage enemies within a few kilometers of that point. So, say you want Wing 1 to clear a valley of enemy air defenses, while Wing 2 concentrates on armor at a bridge crossing. You create an datalink point with the air defense tag at the center of the valley, transmit it to Wing 1, and tell him to ENGAGE TARGETS BY TYPE. He will then fly around and clear the valley of air defenses. In the meantime, create a datalink point with the armor tag at the bridge, and tell Wing 2 to ENGAGE TARGET BY TYPE. He will then engage the armor that is in the vicinity of the bridge, ignoring other enemies in the area.
  7. Then, either there is a rare bug with wingmen that came up this one time, or the fault was yours. It's very easy to make a mistake with datalink transmission. Perhaps you transmitted to the wrong wingman, perhaps you didn't lase before transmission. It's even possible that your laser was damaged and got the range wrong, which would send the wrong coordinate to the wingman. In my experience, every single time that a wingman has done something that I didn't want, it was due to my own error. The datalink system is very nuanced, and one has to be very familiar with all of its idiosyncrasies to operate it well.
  8. I know I said in an earlier thread that I'd post a track of how I control my wingmen, and I have not yet done so. Hopefully in the next few days I'll have some time to dive back into the sim and do this. But, in my experience, the wingman AI works quite well. I get through the majority of single player missions by letting my wingmen engage all the ground targets; I have them recon for enemy air defense, and then I send one or two to destroy the AD while the rest concentrate on the mission objectives. Most of the time I just hang back and play air guard, saving my Vikhr's for enemy helicopters. Occasionally I'll engage an enemy air defense unit that my wingmen missed. Most missions, my AI wingmen have 10-15 vehicle kills each, while I often land with less than 5, and I very rarely lose any members of my flight. This is in the Georgian Oil War campaign.
  9. When you send a DL coordinate with an associated target type, all it does is tell the wingman to look for that type of target at or near the coordinate. The wingman has no idea that you were locked on to a T-55 when you transmitted. So when you locked the T-55 and sent those coordinates with a vehicle tag, it tells the wingy to engage any vehicles that he finds in that area. A T-55, in this case, isn't considered a vehicle, it's considered armor. If you want him to attack the T-55, use the armor tag. It works.
  10. What operating system are you using? Most users with multicore processors experience 50% or more FPS improvement when going to Vista or W7 from XP.
  11. I do not have this problem at all. By using combinations of DL ingress and attack points, I got through most of the campaign missions with fewer kills than my wingmen, and its very rare that any get shot down. I always play the role of commander and flank security, hovering 2-3 kms back and assigning targets, as well as responding to enemy air defenses and enemy helicopters when they appear. I let my wingmen handle the destruction of the bulk of the enemy ground forces. I am always baffled at how different my experience with the AI is compared to what I've seen written on here. Perhaps I'll post a track soon showing how I command my wingmen. Also, wingmen can be a very strong asset even if you don't command from behind the front line. Just give your wingy a 'Cover Me' command as you run in on your attack; should you get ambushed by SAMs or AAA, the wingman will engage the new threats on his own.
  12. I'd say the new patch is needed. It fixes a lot of bugs and adds a lot of functionality to the game. What reason is there not to patch it?
  13. That's probably because such a key would only exist in arcade mode. Real mode is for flying with both real avionics and real FM, afaik.
  14. Er, but the helicopter really does only have 1 flare of each colour...also I'm not sure how that has anything to do with his modification?
  15. You should assign your axes in BS, the SST software is only for assigning key commands. Axis movement is most certainly not a key command, and I can't imagine how miserable it must be flying the KA-50 if you've got the stick mapped to the arrow keys. To assign the axes in game, use the pull down menu at the top when you're in the key configuration screen, there should be a red "Axis Commands" option. Then you'll be able to assign and tune your axes. Also, FWIW, I use an X52 Pro, and I found that the easiest and most reliable solution was to map all of the buttons in game. The only exception is the mode selector wheel, which I converted to a 3-way switch in the SST software and which I now use as the cannon selector.
  16. You need to select "Axis Commands" from the drop down menu in the DCS control configuration screen.
  17. What OS are you using? Setting multicore affinity only has a benefit in Vista or W7.
  18. I prefer the stock sounds.
  19. Also, upon rereading your post, I'm getting the impression that your opinion of the flight model probably has a lot more to do with a misunderstanding of how to fly with the autopilot than the flight model itself. If you're not fully aware of just how the AP functions, the Ka-50 will seem like a nightmare to fly. So, my question to you is, do you know how to fly with the AP? :)
  20. I'm sure you know quite a lot about the flight dynamics of 2ft long helicopters with thrust-to-weight ratios many many times greater than 1. Concerning helicopters that weigh thousands of kg, however, apparently not as much. I'm more inclined to trust the pilots that actually fly combat helicopters and who, as stated above, have endorsed the accuracy of the DCS flight model. Cheers for having the guts to make such a post in this forum, though :D.
  21. Hooooooooo boy.
  22. slug88

    WIP AH64

    There's already a highly detailed AH64A and AH64D in DCS:BS, they jusn't aren't flyable (yet). This is just a skin for an AI helicopter.
  23. No active radar on either the A-10C or the AH-64A.
  24. The HUD gives you the ground speed, while the steam gauge indicates air speed. So, on a windless day the two will ideally read the same. Given headwind or tailwind, however, the steam gauge is what you should use for managing flight parameters, while the ground speed indicator on the HUD is useful for hovering, landing, etc.
  25. AFAIK proximity to the ground should not in any way make you more susceptible to VRS. If you experienced flight issues from flying too low, then the cause is not VRS. I'd wager that your problems resulted from one of the following: dust intake (doubtful) engine icing (not related to being close to the ground, but could be an issue) autopilot failure/shutoff due to loss of electrical power or exit from normal flight parameters (very common for less experienced pilots)
×
×
  • Create New...