IxIFelIxI

Look at that slow speed performance. In case if they delete the video from Youtube here is what 9.12 can do. Height ~ 300 m Speed 200 kph AOA 18-20 80% thrust Fuel 1.5 and all of that produces sink rate of only 2 m/s Can your miggy do that?

Same problem with GS server. However, on GS it crashes occasionally but still crashes. ECW replays crash 100% of the time. Here is the log filedcs.log-20240125-072728.zip And here is the replayServer_1_Operation_Urban_Thunder_V7.7.29.2-20240125-015510.trk

When loading multiplayer replays game crashes or drops to to desktop. Tried 2 servers, clean install, file integrity checks nothing helps and the problem is reproducible. Attaching replays and a crash log. Cold-War-Syria-v182_DME1-20231228-015508.trk dcs.log-20231228-072742.zip

Here is a track of how SU 25T performs the same task. As you can see I can easily pick and choose next laser guided weapon and launch it without waiting for 29Ls to finish their flight. I believe a year ago or so SU 25A was able to perform similarly but then something must have changed. su25T L AG Test .trk

In SU 25T your can launch many laser guided weapons concurrently on a target area. Lets say I need to suppress an installation of short range SAMS and AAA guns. You can initiate your run with a couple of 29L's followed by 4 25 ML's and finish off with a couple of 25L's. This is needed because some of those rockets will get shot down. In SU 25, however, you can only concurrently launch laser guided weapons of the same type. If we take the above scenario and launch 29Ls first the plane will not auto select the next type of laser guided weapons, you have to wait for 29 Ls to impact the target or ground. If you attempt to select a follow up laser guided weapon, let's say 25MLs, then the laser goes into cooldown mode and starts flashing which renders the entire run useless. Is this behavior for laser guided weapons on SU25 modeled correctly as compared to real life? See attached replays. su25a L AG Test.trk su25a L AG Test impact.trk

This is the issue that I had: Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll" Physical USB HID devices managed by script! Currently plugged USB HID devices[1]: 1: "T.16000M" - "USB\VID_044F&PID_B10A&REV_0500" Installing filter driver to VID_044F&PID_B10A. Please Wait...Script stopped! Done! Error: (internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_B10A" Runtime Error: STOP request received while running main on line 21 in "C:\Users\Username\AppData\Roaming\Thrustmaster\TARGET\Scripts\123.tmc" Error: Script run timed out! What I did to remedy this. 1. Unplug joystick and uninstall Drivers, then TARGET 2 Deleted all Thrustmaster folders in >Program Files, Program files x86, and Users\UserName\AppData\Roaming 3 Went to Device Manager>View> show hidden devices 4 (make sure at this point al your regular USB devices such as phones, printers and headphones are connected to USB) DO NOT CONNECT your Thrustmaster device 5 Right clicked and uninstalled all greyed out Universal Serial Bus controllers, Human Interface Devices. ( for a good measure look through other categories to make sure there isn't a greyed out Thrustmaster device somewhere there) 6 Restarted the PC 7 Plugged in my joystick and let Windows install drivers. I did not install drivers from thrustmeter support downloads. What that changed is that now my joystick is displayed as a Thrustmaster Virtual Game Controller (root) : Status OK. instead of T.16000m FCS : Status OK. 8 Installed TARGET and bound some bottoms to act as F keys. Issue solved, works fine in game as intended. As a side note as I was assigning the F keys to the Thrustmaster buttons I left all the layers ( I, O, U, M, D) in default state unlike advised in YouTube tutorials. Hope this helps.

Somewhere in F15 manual I found that amraam will hone in on a target (goes pitbull) that provides the fastest signal return of the amraam's radar and not the launching aircraft radar, IF the amraam is launched in enemy's general direction without a lock. So I began experimenting with R77 basically launching it in enemy's direction without a lock and even without the plane's radar on. My findings are that R77 indeed goes pitbull on an enemy aircraft without any sort of guidance from the MiG if launched within 16 km of the enemy. However, If launched lets say at 25 km of the enemy but prior to Rmax it never goes pitbull when it reaches that 16 km threshold. Observing this behavior I started wondering how does R77 know it is within 16 km pitbull range (Mig's radar off)? Is the pitbull mode time dependent? Meaning it only scans in front of itself for a limited amount of time and then goes dumb if it does not see anything?

Had to try this mission like 20 times before figuring it out. Wingman is a lot more active if you use Execute>Primary and Rejoin. He downed 3, I was able to Fox 1 another on the merge, lure 1 more into SAMs, and Fox 2 last one. Hope it helps others.