icecold951

I've seen this before. I thought they mostly had it fixed. But if you aren't on a basket, it acts like you aren't there. I've seen them cut way to close even when they miss me. A few updates ago I wouldn't refuel when the AI was refueling.

Blade won't engage 3 out of 3 tries. He comes back with all his missiles. I thing Shihab also didn't engage. they went down like flies. I had to go infinite missiles to do the mission, because I am the only one shooting at the Iranians. Also Blade didn't kiss off when told to. He stayed right with me.

Note, I have had this happen in my own campaign missions after the update that affected flights attack target. I had the have the command point on top of the target to get them to attack it. I wish ED would return to the methods before. they worked. I was just here checking on this same bug. And I have no mods. Using the MT because it works best for VR now. Ironically I got mission complete when I landed, and moved on to the next.

Second correction. I thought I was using the OpenVR_API mod used before this update. I placed it in the Bin folder, not the MT Bin. DCS appears to now have it's own OpenVR that doesn't use steam, but it is within the MT Bin folder My error issue was within the regular Bin folder.

I know it still exists in non MT play. And I still see an odd double image looking ahead in none MT play. Reminder, I am talking using OpenVR_API, which is a mod to avoid using Steam VR with my Reverb G2 WMR headset. It does not seem to occur in Steam VR, though that has a serious quality level and performance hit.

Okay, I just figured out how to try the multi threading, and the problem appears gone in MT, and unless I'm dreaming, my graphics went up.

Public update, not Beta. OpenVR, Reverb G2. I was just noting today that the update is creating issues of things not showing properly. First it was labels are messed up. Then I noticed that straight ahead, I get overlap on the images. This does not happen in Steam VR, but steam VR is just a bad joke in comparison.

I just cleaned and repaired, and put the Open Composite back in. Same results. I have also noticed that the VR image seems to overlap.

In case anyone hasn't checked, my experience this is an issue of Open Composite. I just tested with Steam VR, yuck, and it doesn't seem to affect that.

Commands don't seem to work in takeoffs. And given the climb they are trying to do, it would lead to a perpetual stall.

Night or bad weather. I've seen nothing to suggest this is deliberate. It creates a fuel wastage issue, and makes it harder to arrange a slower start to allow ai wingman to join up.

In many firing instances, upon firing an AIM-7, the AI immediately breaks the lock by taking an immediate evasive action without any incoming fire. I can see dropping he lock to evade an incoming shot, but not before any incoming fire. Track and mission is quick AI only flight. No human control. F5 set up as target drone. F18 engages from ahead. 1.miz 1.trk

So far one mission consistently. I've had similar mixed hornet tomcat starts. Someone else has reported they've seen it happen on a different mission.

A bit back I posted both tracks, youtube clip, about AI planes doing afterburner climbs to 10k after a carrier takeoff. I've now broken it down to bad weather, night, early morning seems to trigger this. I haven't heard much comments on it, so I have been left with am I the only one getting this on two different computers, if this is intended for some reason, or a bug being worked on that didn't get a 2.8 fix. My biggest complaint about this is fuel waste, when the AI is horrible about fuel management, and that it makes it harder for group craft to rejoin, triggering max after burner until bingo to catch up. Is there any updates regarding this?

I too just noticed lower quality BVR skill. In a mission where I am the striker, my Vet escort wingman fired his 120s way to soon for a guy with only a limited number. Nine Line, that logic only works if you have the missiles to spare. I too have habitually used one or two at longer ranges to put them defensive. But that was when I was in missile truck loadout. Maybe they should take into account if they can spare the missiles that are deliberately 'wasted'.

Can confirm it seems tied to the target. Pre 2.8 it would go to the WP first.

Okay. I think I know what is going on. Traditionally I was able to tell them at any distance from the waypoint, to do this. They would fly to WP 2, Ingress then execute. Now I either have to be closer to the WP, and I suspect that isn't true, or much closer to the target that I had to be before. In the past it wasn't so picky. So missions that work don't now. That would explain why some missions work fine and others don't. Their Ingress WP where the mission order is may now be to far from the recognized distance. I'll experiment with it some, using that mission. Move the target farther away and see what happens.

I'm not sure I follow. Having them do it on the leg you are currently on would be great. I orginally had issues of this over a year ago that they returned to a refueling waypoint first. We already refueled. But unless I missed something in the last couple years....The player leg never advances to the next one. Even if I fly right through the waypoint as closely as possible, I have never seen it advance from WP 1 to WP2 for the player. Is there a way to trigger the player waypoint to advance in the map mode? I don't mean switching the waypoint on the HSI or SA. I do that, but that doesn't change what the map shows.

I hadn't seen this response until now. One fact was that the helicopter showed damage from taking fire. That is why the second helicopter turned around.

Okay, it still seems to do it even with using Missions instead of Mission Editor. Here is the track and miz of the event that happens. In it, 3 waypoints with a ship at WP3 to the east. When I tell my wingman engage the objective, he turns back to the original waypoint. 1.trk 1.miz

Update, it seems to do it both in ME and Mission. Seems a bit hit or miss. Sigh....I'm getting a bit disheartened about making missions that get BROKEN every update. What's the point?

Been a while since I've seen anything regarding this. Why doesn't the Harpoon properly sea skim? I think the radar attack method is fixed. But currently, aside from useless warhead discussed elsewhere, the biggest issue is it is wide open to SAMs. The Harpoon should be able to fly under radar over the horizon. At 67ft, it may as well be at 6700 ft. And the fix is so simple. Before 2.8 I lowered the sea skim. It was still able to be attacked on the way in while at cruise altitude, and engaged by CWIS. So I don't know what they are trying to do with harpoons. As an aside, they seem to have fixed the Russian missiles being sent in as a long stream of target practice. They now come in much tighter and more realistically. So that got some love, but none for harpoon. I gather at one point they did have it fly below radar, but raised it up because it couldn't be engaged. But harpoon missiles were designed to be impossible targets over the horizon. It is impossible for radar to track one over the horizon. You can't see through terrain or water.

For me it works oppositely. The wingman behaved correctly in Missions, but not in ME. Still waits forever to take off.

Semi fix so far. It still won't behave correctly in ME, but flown as a mission I am able to order my wingman as normal. It is inconvenient to mission editing, but going to the missions option seems to work. My test is a single mission so far though.

Actually I haven't tried it outside the ME. That is where my bugs show up. I have two bugs. In one mission, the wingman won't taxi to the Cat for several minutes, and the one I mentioned about WP 1. I'll test outside ME now.