Eclipse

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

Could you please describe how IFF is turned on or off via the UFC? Nevermind, I see the IFF button on the UFC. Clearly I didn't accidentally turn it off since I forgot the button existed! The manual could use some updating for some things (like datalink having 2 pages but still having only 1 covered in the manual). I'll have a look at the L+S INT setting on the AZ/EL page tonight, as well. I have never intentionally unboxed it, and I specifically go in to the AZ/EL page to enable Auto INT, so either way it should have been working, whether automatically or bc of the STT. Unless IFF now needs to be turned on somewhere else that I'm not aware of I really appreciate the help!

Thanks for the response. I have had the target locked in STT while it's flying directly at my nose, well within 25nm, and the HAFU remains unknown. So either NCTR or my internal IFF isn't doing its job. I'm fairly certain I even saw the target under cursor data in the lower right of the SA page had the aircraft identied as a Su27 at one point, and yet the HAFU remained an unknown. Nice to see a fellow RTFM guy!

The past couple nights of flying, I have not gotten a single radar track to be identified, even while in single target track on that target at close range. The HAFU remains a yellow bracket "unknown" symbol. This has been in a air-to-air experimentation mission with no AWACS, and my datalink (the second D/L page) is turned on, with auto-IFF turned on from the AZ/EL page. Am I missing a setup step that is keeping IFF from functioning? Has something changed? I'm at a loss. *edit* The only thing I can think to check is to make sure Non-Cooperative Target Recognition (NCTR) is still boxed on the RWS radar format by default. The opposing fighters have been high aspect flying directly at me while in STT, so NCTR should have identified them as hostile. Anyone else feeling like something has changed?

Could you share what those other means were? I attempted to set up a flight of Ju-88s to carpet bomb a city and they only dropped the external bombs, even though I had them set to drop all bombs and they had internal bombs in the bay. Is the workaround to just not use the carpet bombing action, and use a regular ground attack action? I just thought of trying that while writing this. It's a shame the 88 that is modeled had it's level bombing capability removed to accomodate the torpedoes, which I assume is true. I promise I'll behave like an adult if you respond

The General Flight Model will be a huge improvement. The demo I saw maybe a year or so ago was very impressive. Anyone who has a "the team is bad at doing X" attitude has no concept of how complex and difficult the "X" actually is. I'm looking forward to seeing how DCS continues to evolve over the next year, next few years, next decade... Thanks for all you do!

The general flight model for AI will be one of the best improvements to DCS in a long time, when it eventually is released. Authentic maneuvering and dogfights in the incredible DCS warbirds with AI planes that follow the same physics as player aircraft with no UFO behavior will revive interest in the WWII through Korean War periods like nothing else could. It will revive my own interest, at least. I assume I'm not alone in this! There are so many incredible things being developed right now. The multithreading and rendering reworks and so many other "under the hood" modernizations have been huge. Prior to these I could barely handle multiplayer in VR on my PC, and now it's a low 30s framerate with suitable settings but it's relatively smooth so it's still enjoyable. It's a very noticeable improvement. Not every update helped my situation but in total it's been a good step up. Vulkan and further VR rendering efficiency improvements down the line will only make it better. We are still only seeing part of what it will eventually be, which is exciting. I can't imagine how complex these projects are. The ED team should be proud of all they've accomplished. It's a great time to be into DCS!

Just bumping this post - this issue still exists. Changes to VR controller assignments are not saved properly, as described above. Thanks

I see. Either that was a different issue or it has returned, then. My guess is it's related to mission/server load. Liberation missions have a good bit going on. Hopefully it gets sorted out soon. Until then we'll have to make sure we have hornets available from airfields as a backup plan.

When was that fix releaaed? We use the open beta, MT client and it was up to date as of Wednesday December 13 when I had the experience I described.

If only that worked. Even in full afterburner he just continues that motion and will not launch the aircraft. I haven't been able to find this signal when searching flight deck hand signals online. The wand is at waist level, held pointing up, and it is moved slowly back and forth across the body. This failure to launch issue and the instability of the aircraft sitting idle on the carrier deck interrupting ordnance loading and causing the jet to tip over and explode are pretty big problems. Hopefully they can be resolved in the near future.

I spawned in an F/A-18 on the Supercarrier in a Liberation mission. While starting up, I attempted to rearm, and repeatedly got the "Hey, what are you doing?" message as if I was moving. I was at idle with the parking brake on, but my aircraft was bumping and jumping around every several seconds or so, which was interrupting the rearming process. After many minutes and several rearming attempts, I decided to launch and go to the nearest friendly airfield to rearm and go fly my tasking. However, the cat crew hooked me up and then would not launch me - the director was waving the wand back and forth across his body repeatedly, whatever that means. I decided to return to spectator and re-slot into the F/A-18 to try again. On attempt number two, I spawned in, and still got the "Hey, what are you doing?" a few times, but the rearming was successful. My aircraft was still bumping around like before, and I was still at idle with my parking brake on. Then came an especially big bump, and my aircraft was on its side resting on the left wing and left gear. Then my Hornet exploded. This was a Liberation mission, hosted on a dedicated server with a fiber internet connection, and pings were low and stable. At this point, Supercarrier appears to be unusable. I hope this report helps, and I hope Supercarrier gets some much needed bug fixing soon! I attempted to attach the track file, but it is 102MB, and the limit is apparently 50MB. I uploaded the track to my OneDrive, here is the link: liberation_nextturn-20231213-212338.trk