monacoBMW

Apologies for making a comment that was deemed disrespectful. Hopefully whenever OnReTech sees this thread they'll respond in a way that respects everyone who paid for their content as well.

I'm having the same issues but on an Nvidia card. The squadron I fly with has all three of those mods, but I was the only one having the issue tonight and I know most of them are on Nvidia as well. So it sounds like it's just completely random... I'm AFK right now otherwise I'd try it and report back. Thanks for giving us something to try.

I'm also having constant crashes trying to get into multiplayer servers now since the last OB update. As soon as it gets into the Post Start stage of loading I get a popup that the game crashed. I can load a single player session just fine. The guys I fly with all run the same mods and none of them are experiencing this. I've already run a repair and that didn't change anything as far as I can tell. I attached the logs the game generated for the latest crash. Sure hope whatever was added in today's patch was worth it. dcs.log-20231220-011504.zip

Very big fan of 2.8 so far. Some great improvements to the F10 map and the night lighting on PG is stunning.

k

I just played around with this tonight and am already very impressed. Really excited to see the progress on this!

I've been having every problem you just described. I play on a friend's dedicated server the most and the only other Hornet regular in our group is having similar experiences as well. Zero lag issues that we can see and all of us have low pings. Something is very wrong with its online performance for sure. What made me abandon any sort of A2A mission in this plane was that inexplicable L&S issue you mentioned, but it was even worse the one time I experienced it. 2 Mig23s directly on my nose at ~30 miles and instead of locking any one of them up, it jumped to a friendly that was 120 miles away at about my 2 o'clock. Happened in both TWS and RWS modes. Even with a narrow azimuth, it would just jump way off in the distance for absolutely no reason. No track file because that made me rage quit ngl.

Same thing just happened to me, except another issue prevented me from even dropping the TALDs on those stations (which I'll be reporting elsewhere). I was trying to jettison to get ready for A2A and it crashed. This is what I was able to find in logs afterwards - hopefully it helps dcs.log-20210206-013453.zip

Other users are reporting midcourse guidance issues with the AIM-120 which sounds familiar to what I saw last night, and I remember hearing the AIM-54 uses the same guidance in the game. Can probably chalk this up to a core game issue especially if you guys didn't touch anything. Next time I see it happen I'll be sure to save the track just in case

I've had some odd Phoenix behavior too after today's update. I've had multiple shots run out of energy from a target within 20 miles or so, which I've never had happen before unless I'm chasing a target - in these instances I was either head on or they were flanking. When I F6 them I can see them maneuver way more than the target is and thus bleed off a ton of speed in the process. And then in two scenarios I've had the first Phoenix shot track while the second goes straight off into the nether even though it appears that Jester has both targets queued up correctly. They're either never tracking to begin with or lose lock by the time they go pitbull. I'm not exactly an expert on this but I've engaged two ships with Phoenixes numerous times and never had this happen before. I'll see if I can get a track of this. And yes, it's definitely possible that I'm just doing something wrong lol edit: of course now I can't reproduce

I've been flying this on and off for about as long as this issue has been reported and never had this happen, but I guess I popped that cherry tonight. F

It also happened to me when landing on shore. I only realized when I speared off to the side because I couldn't turn my NWS on lol. Flicking it to extend real quick on takeoff after hooking up works like a charm for me too.

Bumping this too. I've noticed this in about a quarter of all shots I take now, MP and SP. This was with both the Hornet and Eagle in various radar modes. The 120 will track perfectly with a solid radar lock and at some point in its flight will just dart off in a totally different direction just long enough so that the shot is wasted. Tonight I had this happen to me when the target was maybe 500 feet away. It's like the missile had a collision avoidance system and just skirted around the target.

I've experienced most of these issues as well. But there also seems to be this target designation way off in the distance as soon as I power the thing on and I can't undesignate it and find my own targets. Yet when I hit A/A mode and the FLIR comes up on the left DDI, then I'm able to slave the pod and designate targets mostly as normal (even then the VVSLV mode points to the exact opposite place it should be pointing). It's so broken right now it's actually kind of funny.

The 3 wire landing I just had tonight still returned an EGIW even though I 100% did not touch the throttles when I was in close. ED plz.