Draken35

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.

Concur! F1M > English cockpit all day long... tbh, I was only using the mod because it has a lot less shimmering with MSAA in VR, not because the actual language

Well.. It did work for that first login in DCS after the F-4 reinstall... The moment I logged out and came back it, the crash reappeared! So, I went back to a clean install and started troubleshooting again, focusing in the options.lua. After many DCS restarts going back and forth checking the options, I noticed that the when the DCS Launcher is enabled in Misc. Options, the Phantom works as expected but if I disable the launcher, it produces the crash! I disabled the DCS launcher within two hours of it been released and have played the "old fashion way" since... IIRC, last time I flew the F-4 was in February of this year, so either something happened in the last couple of updates or this is a byproduct of me going from Win10 to Win11 around the same timeframe. For now, I have the launcher work around, but I cannot believe I'm the only one not using the launcher!

Yes Sir! That's the one

Well, don't know why it did not occurred to me before, but in my full install, including MODS, I uninstalled the F-4 from the module's manager and reinstalled it and it now WORKS.

When trying to spawn into a Phantom hot or cold, any map, SP or MP I get either a crash to desktop of DCS just hangs. Does not always generates the zip crash file in \logs. This is what I have done to troubleshoot: 1) Remove all mods 2) renamed Saved Games DCS folder to DCS.old. 3) Slow repair 4) Launch instant action cold start mission in the Caucasus map and test. WORKS! 5) Copy the Config\Input folder from SG\DCS.old to the clean one (to get my keybindings back) and test as #4 and it WORKS. 6) Copy the DCS.old Config\options.lua into the clean cone and test, same as #4 and it FAILS. So, seems that the crash is related to my old options.lua file, which I attached. Also attached are the latest log and crash files. Any ideas of what this can be? options.lua dcs.log dcs.20250427-170052.crash

Hit load.. I haven't added any other functionality to it and probably won't until the module is more developed (and I get the desire to fly it )

I think you assumed that I did not check my code before posting and that I meant the codes were changed recently (as in the last DCS update). Unfortunately, you were wrong in both accounts. Also, you made the mistake of comparing two different pieces of software (even if they try to accomplish the same thing) made by different developers, but thanks for trying to help. @greyeagle787 I updated the key codes and uploaded it to the user files . I'm not currently flying the hook so, please, give it a good test and let me know.