Jump to content

Rmnsvn

Members
  • Posts

    151
  • Joined

  • Last visited

Everything posted by Rmnsvn

  1. Для TWS выстави время стирания трека на 16 (кнопка Data - правая верхняя кнопка, у которой написано 4 по умолчанию) и будет тебе счастье. Либо ставь меньше горизонтальную зону сканирования.
  2. I guess it shouldn't be letting you have any control over the elevation when there's L&S which is not the case now
  3. @BIGNEWY I think I got a bug here. Сould you move it please to the relevant section of the forum? Here's a track replay showing the problem. I will also attach it to the first post in the topic. TWS Auto problem AZEL page.trk
  4. I usually have no time pressing man button, contacts disappear before I manage to do that. I wonder if selecting contact refresh rate (default 4) to 16 will remedy the situation and tws will have time to sort itself out.
  5. When I’m in tws auto and I’m scanning for targets, I put antenna elevation to correct value to see the particular bandit. Then I press NWS button and get L&S for him. Right at this moment TWS auto would tilt antenna well below the bandit and consequently loose the lock. This happens consistently when I’m trying to lock someone up who’s below me. For coaltitude targets seems fine. Tried only in SP and in MP. The altitude range shown by the tdc would go negative the moment L&S is acquired. If you slew antenna back up while tracks are not yet deleted, TWS keeps them in the center of a scan without issues. Track attached. TWS Auto problem AZEL page.trk
  6. Hi all, I used to have the same problem and solved it the following way: I did not have full screen enabled in settings but I did have “full screen optimisations disable” in the compatibility options for DCS. Removing it solved the crash issue completely.
  7. Deleting the Saved Games folder worked for me. All the stutters are gone. Note, that it was not sufficient for me to delet FXO and Metashaders folders, apparently some old setting was causing conflict.
  8. The problem personally for me, Максим Сергеевич, is the FPS dips and terrible stutters. I have all the same settings for 2.7 as before but rotating my head in the cockpit now causes freezes now and then. Will try to play with settings and see which one is affecting me.
  9. Same here. -25 FPS for me in average. Terrible stutters when rotating head. Also terrible loading times. Clouds seem fine and they don’t influence performance at all on my side. I deleted fxo and metashaders folders with no joy.
  10. Jester works just fine there, no issues. I also noticed that when my RIO has some 'lags' on his side, my radar seeker won't move on the hud when in PAL/Vertical Scan. Probably related to his FPS or ping.
  11. Alright, I must've mentioned it in the opening post that I'm familliar with the basics of phoenix employment. I guide the missile to the target the whole time until pitbul and usually keep the lock until impact. Again, there's absolutely no problem with Jester, the problem happens only when I fly with a human RIO.
  12. Thanks for reply. In fact, the engagements were against AI and they behaved pretty similarily. As I mentioned with the second shot the missile flew right past the target (seen it with F6 view) so the distance was much less than 1 mile at the closest point.
  13. THE SHOTS WERE MADE IN TWS AUTO
  14. Hi everyone, Tried to google on the issue but no joy so far. Me flying with my RIO, engaging an airplane with target size set to medium, TTI starts to flash at 16 sec to impact, all good, good kill. Next shot, exactly the same settings, missile never activates, flies right past the target. Next shot, exactly the same settings, missile activates at 5 sec TTI. In Single player with Jester missile consistantly goes pitbul at 16 sec tti. All shots made in TWS Auto. Is it us doing something wrong or is it multiplayer issue? No track at the moment, they're too heavy and lengthy. Thanks all for your input Regards, Roman
  15. That’d be hornet, 100%. Can easily beat mirage and 29 if flown well, f14 could put up a challenge but they broke its subsonic aerodynamics lately. The cat is also much trickier.
  16. Today is literally the only time I regret not being on Steam
  17. No news on Phoenix going dumb just before impact?
  18. Yep, Viper was also clean and approx 80% of fuel. I'm actually able to at least match the hornet at 430-440 IAS but then the GLOC kicks in and here we go: either i soften the backpressure and gain speed or I go out of burner and loose that energy. I understand the G is there but i remember reading Viper pilots are trained to sustain 9g to like 12 seconds without even color loss. Here you completely black out after about 7 sec (feels like this, didn't measure it) Yep but Viper was also clean
  19. Any word on performance with shadows on? thanks
  20. I like BFM and usually fly hornet for this purpose but recently I started adding some viper. here what I observed: Hornet, about 7000 lbs of fuel, no pylons, sea level. I’m able to sustain 7.5g at around 380-390 kts. Viper can take about 6 g at best at this speed without loosing energy. is this expected behavior? I’d expect vipers tr to be better due to better tw ratio. Apologies if the question is stupid. Just curious.
  21. Didn’t think of it this way actually, would be good chance. Too bad I bought myself a new monitor
  22. 2 more weeks with broken F14, broken HMCS, broken phoenix, sparrow problems probably many more... Way to go.
  23. Thanks Bankler for this awesome mission. Should really be included with FA-18 and Tomcat by default!
  24. Just tried, wouldn't say so. The B still feels like a fat cow in the turns at low speeds.
×
×
  • Create New...