Jump to content

Machalot

Members
  • Posts

    1385
  • Joined

  • Last visited

Everything posted by Machalot

  1. They said this one is proving hard to solve but they're still working on it.
  2. Can you explain what this means?
  3. This is in HB's bug tracker.
  4. What do you expect to happen to show that it works? And what actually happens?
  5. They put in several features that were requested in these forums. In my case the trigger safety toggle keybind. It's great!
  6. It's not on the list for this patch. It is still on the bug tracker though.
  7. I gave you reasons above why hitting a ground target is different from hitting a ship. Those are not mysterious reasons. I don't understand what your are asking for.
  8. I don't have anything better than that. However, I can provide more speculation for you . It is grounded on engineering principles so you can decide how much you believe it. The ability to fly waypoints is not sufficient to hit ground targets at long range. It has to fly waypoints very accurately. Even a few tens of meters of inertial drift can be enough to reduce the lethality depending on the target, or even to hit the wrong target. Or impact terrain along the route Maybe the RB15F didn't have the inertial accuracy required to be useful or safe for land use.
  9. Speculation: It's programmed to look for the radar return contrast between a ship and the water, which is a lot greater than between a building and the ground. Its radar image may become cluttered by the typical kind of ground objects and textures like trees, rocks, roads, which do not appear in water, and it doesn't have the processing algorithms to handle it. It has a radar altimeter for sea skimming, but it doesn't have terrain following radar that would be necessary to navigate anything other than flat plains.
  10. Yeah, you need to hit T0 to complete the fix. That is the equivalent of releasing the trigger.
  11. Yeah, dead units should still have an RCS. Something ED will hopefully implement someday.
  12. Can you explain what buttons you are pushing when the grid is blinking on and off the CI, and what you are expecting to happen? It seems like maybe you are never returning the trigger to T0. The sequence for a fix should be, starting with the trigger out (T0 position): 1. Begin fix [trigger first detent, T1] 2. Slew cursor to target [radar stick] 3. Designate fix point [trigger second detent, TV] 4. Complete fix [release trigger, T0] You are also able to continue slewing while the trigger is fully depressed in TV, but I don't know if that's realistic.
  13. This aligns the first 40 Group channels with the 40 default channels for other aircraft such as the Hornet and Viper, rather than automatically generating them based on other flights in the mission when you spawn (I think that's what you meant by "automatically"). It somewhat elevates the Group selector in importance, since it was not much use before. Now in missions where the designer didn't put useful frequencies in the Special and EFGH channels, you would just use the Group channels primarily. They are all configurable in the Mission Editor, but not "manually" within the aircraft.
  14. The stresses that destroy a wing during heavy g are primarily caused by lift, which creates both a bending stress and a shear stress at the wing root. If you are pulling a certain number of g's that puts you near but under the limit, the wings should survive. But if you then apply roll input, the aileron deflection causes one of the wings to generate even more lift, increasing the bending and shear stresses and possibly exceeding the limits. That may explain why roll input under high g is breaking things.
  15. Are the slow bullets acknowledged?
  16. The animations for air brake and thrust reverser are linked in the current model for non-self aircraft (including other human player aircraft).
  17. It seems like the blind spot that is supposedly caused by the wing is on the opposite side. I assumed it would be caused by the raised wing blocking the antenna line of sight, but it's in the direction of the lower wing. What's the deal?
  18. Well, now I can't reproduce it either. I noticed this issue probably almost a year ago, and just finally got around to reporting it. I definitely observed it the night that I reported it. My HUD reference lines would slew up and down very fast when I used the trim switch while in altitude hold. But now when I tested it tonight, they move at a very slow rate and the aircraft follows them to the correct altitude. I wonder if the most recent patch affected something, or who knows.
  19. It's also true for the RB04. Does it apply to all missiles in DCS? Or just anti ship missiles? Or just Viggen missiles?
  20. Ha! I guess I'll blame ... autocorrect?
  21. They're doing a cockpit overhaul so I guess we should just wait for that.
  22. I noticed upon close inspection that the 1 lamp on the afterburner stage indicator sits at a different angle when illuminated than when unlit. I didn't get a screenshot, but I can add one later. It's trivial to reproduce. Obviously not a high priority.
  23. I think it would just assume all latitude is south, similar to using all west latitude in Nevada.
  24. Last year I had an issue similar to this which was the result of a corrupted MagVar table in my Save Games folder. I eventually fixed it by deleting the contents of ...\Saved Games\DCS.openbeta\Data\MagVar\TabularData What clued me in was that all the files in there are the same size, but one of mine was an odd size. Next time I started DCS it rebuilt those tables and everything was fine. Maybe worth a try.
×
×
  • Create New...