Eclipse

The general flight model for AI has been in development for years now. It is known that the existing flight model for AI is not the same physics-based model that players fly by, but a simpler model that results in the UFO behavior. That behavior is magnified within visual range and with slower aircraft. This is the single biggest issue that keeps me away from DCS warbiards and early jets. I'm very much looking forward to the new flight model eventually being implemented. I'm on the forum today looking for any updates beyond what was released about a year ago.

Anyone have any more recent news to share on this? This is (I think) the only issue that is keeping me from really diving into the warbiards and the Sabre and such, since the AI doesn't obey the same laws of physics with the current flight model. Thanks in advance!

Yeah, I also approach training missions that way. I know how the triggers work, looking for a specific input or event. I waited until the narrator was completely finished and still had that result. Pace was not the problem and I tried the mission multiple times. But whatever glitchy thing was going on was somehow passed when my TADS was aimed a little low and didn't actually get the track

That's the response i get, also. I tried multiple ways and never got the wingman to engage anything. A work in progress, I suppose.

This is really odd. I ran the mission again, and at first had the same result - targeting the second BMP with IAT did not move the mission forward. But... after I had tracked and dropped and re-tracked the second BMP a few times, I decided to drop the first BMP and retry tracking both BMPs. I re-tracked the first BMP with IAT, then MISSED the second BMP, hitting the IAT button with the TADS crosshair a bit below the BMP. The second BMP didn't get tracked since I was off-target, but the mission proceeded as if I had targeted it properly and gotten a track. From there I targeted the second BMP with IAT (not missing the mark that time!) and continued on. The rest of mission went normally from there. Very strange! I attached the track (not sure why it is named "tempMission"). Thanks, @Lord Vader tempMission.miz.trk

AH-64_TRNG_11_CAUC_IAT.miz_19102024_11-13.trk Good morning, @Lord Vader, a track is attached. I retried the mission again this morning and the result is the same. No matter what I do, the mission does not progress past the targeting of the second BMP with IAT, whether or not both BMPs are in the field of view. It's interesting that you had no issue when you tried it. Thanks and have a great day

As the title says, the mission stops advancing at the part where the player targets the second BMP using Image Auto Track. There is no prompt to press spacebar to continue, and I pressed spacebar anyway just in case. I also reloaded the mission and tried again, making sure to wait until the narration was finished before I targeted the second BMP with IAT. In both cases, nothing happens after using IAT to target the second BMP as instructed. The training does not progress past that point. Keep up the fantastic work!

Hi, BIGNEWY - just want to mention that the VR controller laser pointer still does not render. The issue has been around since MT was introduced. Just want to make sure it's on the radar. Thanks

Still no VR controller pointer. Bumping, hoping it gets fixed

The problem persists - still no VR controller laser pointer. Hoping this is fixed soon...

The VR controller laser pointer never worked in the MT version, but still worked in the ST version. It still does not work in the MT version. Hope this is on their fix list!

No issues here, but I use a Reverb G2. I start the Mixed Reality Portal, then launch DCS, and it works normally every time. Good luck

Still an issue - HP Reverb controller assignments are not saved. Sometimes default assignments return, which interfere with axis controls on other controllers. Each time this occurs I clear the category for the Reverb controllers.

I'll retest with attention to the AZ/EL azimuth and range settings to verify whether Auto INT is working. I did verify tonight that a STT did immediately identify the target as hostile, so the IFF is working there at least, now that it's turned on!

Thank you so much, that one bit there is gold. That is probably the issue - I never knew IFF had to be manually turned on! In the simplified experimentation and training type of mission we were running I had no donors on datalink with me. So all this time I've been relying on datalink correlated tracks rather than my own IFF. This would explain some of the weird finicky behavior I've always experienced with the hornet radar... I'll retest tonight and respond back. Have a great day