Draken35

How to control the mouse cursor in DCS is a very subjective experience and your overall setup matters. I have a dedicated simpit and I've tried using a traditional mouse, trackballs, trackpads, hand tracking, VR controllers (Quest 2 & 3) and a set of PointCtrl... For me, VR Hand controllers works best, but I echo @Hempstead advise, try then and form your own opinion.

Looking good! Looking forward to it and the updated version of the T-45!

Cool! I was typing this script using moose (untested) : Posting it as a starting point if you or anybody else wants to used it... I'll probably add it to my library just in case Checking speeds is a lot easier ... Sometime the first idea is not the best

My pleasure... That was a quick idea and not knowing the context (but I assume it is about the training mission of the T-45C ) and toolbox used (native, mist or moose), although it should be doable with all. Good luck! @Rudel_chw Another one.. If any of the speeds (GSmost likely) you can get for the plane, matches the carrier's , then they are not moving...

Would checking distance variation from carrier to plane work? That would have to be in a loop and require an initial/prior position, sorta asking has it moved since I last checked?

The prior version was posted on 4/27/25... I touched the Hook script after for the Viggen

Hook script is needed too…

Update 250607A pushed to the user files https://www.digitalcombatsimulator.com/en/files/3344152/ - AJS-37 Support added (Yes, I'm aware and know how to use the DTC functionality) - Coordinate load speed improved for the Hornet -- AJS-37 Viggen Only B & M waypoints can be added. Bearing and range for offset points can be manually added. Waypoint Sequence Start can be used to specify a startup waypoint and route. Default is 1 Examples: Set WSS to point 3 : @<3> @|#| ... will load/replace the next B point in the load sequence @|B| ... will load/replace the next B point in the load sequence @|M| ... will load/replace the next M point in the load sequence @|B3| ... will load/replace B3 point @|#|N 41°36'41"|E 44°33'51"||| -> will load the coordinates in the next waypoint in the sequence @|#|N 41°36'41"|E 44°33'51"|180|10| -> will load the coordinates in the next waypoint in the sequence with an offset of 180° at 10km

Poor guy... Still sitting there...

I watched your track and, according to DCS the bombs were doing about 530sh Knots before impact and then I looked at it in Tacview. That gave me 49822 ft/ min which are 830ft/sec , and not accounting for g or other accelerations, that bomb could had moved, vertically, 150ft in 0.18s...The 25ms of the FMU-152 should give around 20ft according to these numbers.

I would try this: The arming delay is how lot it takes to arm itself after leaving the rack and the function delay is how long after "impact" (fuse activation) it will detonate... Not sure if the type of plug makes a difference, but the long conical look pointy enough I did not suggest the GBU-24 because they are LGB and, probably, don't "fly right" in CCIP or AUTO and since the weather is reported as "terrible", laser shouldn't work either (but it is DCS after all)...

Did you change any fuse settings in the rearming screen or just selected tail in the Stores page?

Yes. I actually discover the issue while developing a script that creates the laser spot ( which I've done before and was tested with a Hornet/tpod as well) BUT for the bug report, I used a native JTAC which was tested, and confirmed working, with the Hornet/tpod prior to create the report track with the Harrier... It is been a while since I used the DMT LSS so I don't put it beyond me that I'm doing something wrong but it is such a simple procedure that I doubt it...

Unless I'm doing something wrong, it seems to me that the laser spot search function of the DMT is broken. Tested from active pause / air start, using a JTAC, which was confirmed working with a Hornet with a TPOD. Test Harrier DMT LSS.miz Harrier DMT LSS broken.trk

You can use aerobatic tasks in the AI waypoints to control a little bit more their speeds and bank angles and to add interesting maneuvers, but forget about formation landings or take off with the current AI.

Easy work around but please, fix nullnull

These options are new but autoexec.cfg is not... It will stay in place until you modify or delete it.

Sorry... couldn't resist Cheers!

I think the real issue is how the head set sits on the individual faces and not really in the modules code. The Quest 3 "center of vision" sits a bit high on my face with the OEM face interrace and in comfortable position. This is only evident when a Helmet Mounted Display is used (Apache, Hornet, Viper and Blackshark). With the Blackshark it can be fixed via special options easily but with the others, my only solution is to push the headset down and crush my nose, which is very uncomfortable of course. The Quest 2, on the other hand, sits perfectly on my face. Since this is "hardware" (our faces) related, I suspect that you will have a hard time reproducing it if your current team members cannot already experience it. The best and only solution, IMHO, will be to add special options to the modules to allow to adjust the HMD device like the Ka-50 does.

I'm sure this has been asked before in one way or another, but here it is again. Please have the the infantry that belongs to a ground group mount into transports belonging to the same group when the group moves at above a threshold mount speed and dismount when stopped or moving below that threshold speed. Additionally a couple of group options could be added: Enable/Disable the auto mount/dismount Allow partial mounting or not. Basically, if there is not enough transport capacity in the group, allow mounting some infantry and let the other walk.

@LordOrion thank you

Is there any resource available (pdf, video, etc) that shows how to fully use the CDU, beyond the half a page in the manual?

Yes.

Sit in a cockpit and try again

Yes it takes out the shimmering in the cockpit.