Cathnan

Sure thing. The 20240713 is my first run on veteran difficulty. I don't have a Trackfile for that. I attach that one mainly because I noticed Matrix not firing 120. Not sure if this may be intended tho, or he was intimidated because I launched 3. The 20240714 is the one with rookie difficulty. Tacview-20240714-100621-DCS-SYRIA M8 TO CATCH A SPIDER.zip.acmi Tacview-20240713-175645-DCS-SYRIA M8 TO CATCH A SPIDER.zip.acmi

Thank you. I watched the Tacview meanwhile and Joker misses one of the vehicles on the first run. They appear to be going in for a second run but don't fire and instead RTB.

Hi, I played this mission on standard difficulty yesterday. Everything fine. Joker engages spider, Mig's turn hot, I take them out. After Matrix call's "that's all of the bastards" I looked at my SA Page and saw Joker on course back to base. I circled a while longer but after a few minutes I heard nothing. Checked the briefing and decide, it says after mission complete RTB via WP6. So I decide to do that. I pass waypoint 6, turn on waypoint 7 and slow decent is announced and fence out is called. And while fence out is called by everyone else I get the mission failed screen and the mission is aborted. I just played it again, this time on rookie to make sure none of the Mig's does anything rude. I saw the four smoke trails right next to each other, so they definitley didn't engage Joker this time. Maybe I just missed doing something? I checked at the waypoint given for spider after splashing the migs and saw 3 burning vehicles there that Joker must have destroyed. The track attached is from my latest go at the mission. Mission 8 Spider not stopped.trk

I had exactly the same problem. My drops went well, but Matrix drop went to mission failed before the bomb impacted. I got the message to hold the trigger until it impacts right after the impact. The destroyer also called the hit and then the mission terminated. I have the trackfile attached as it apparently exceeds the size limit I can send through e-mail. A bit of buddy time Mission 1 Laser Trigger not recognized.trk

Hi I bought the app earlier today, and it seems great so far. But I think there may be a bug. I enabled the additional info and when I mark a target in the app the distance units seem to be reversed. Meaning, when I lock the same target in my hornet, I get the distance, and in the app with imperial units the number is almost twice as high (which would be correct for metric). In metric it pretty much matches what my hornet says. Also is there a way to have the heading to the target go from 0 to 359, instead of -180 to +180?

Did you get the crackles solved? I have a Logitech G-733 and it works perfectly everywhere. Except for DCS. I just won't stop crackling.

For what it's worth, I read that line as good news. An external client should be way lighter to run than even the server itself. I have no clue how mods like OverlordBot are integrated serverside. But a small external program that can be feed basically any audio through a virtual audio device, and can provide an audio stream to other programs through another virtual audio device? I'm sure that must be good for something.

Can you bind SRS and DCS VoIP to the same buttons, so both get activated simultaneously? Sent from my Pixel 7 using Tapatalk

I was wondering why he swivels the TADS all the time. Thought he may have learned a trick from Petrovich and is now activley searching for targets, and it just wasn't mentioned in the changelog for some reason. But this makes more sense

I just had the same problem. From cold start flying to a target, he won't designate. Modified the mission to mid flight start, close to the target to get a track file. And what am I looking at? George designating and hellfires in the air heading to the target. Did something change in the cold-start procedure? Didn't see anything in the changelog tho.

Awesome to hear that [emoji1]. I'm excited to see how you fill this with live Sent from my Pixel 7 using Tapatalk

+1 for the idea to make the sensitivity adjustable. I think with 100% setting having it as fast as it now is will still be in spirit with the realism. But the possibilty of slowing it down with a slider accounts for the fact that we do not have the military grade force sensing hardware this behaviour is meant for. Actually I like this change because selecting things with the tdc cursor now doesn't take forever as it did before. But I still would appreciate the slider option. to account for the hardware reality. Even with my Winwing Orion with the Hornet grips, that has excellent accuracy with the slew thumbstick it's really hard to be precise.

I don't know about one being more accurate than the other. I always thought it should be about equal, with toss bombing maybe being less accurate. But that mainly because it's a more dynamic situation and depends more on pilot skill (managing speed, keeping the plane steady). Also I thought the main attraction of auto mode is that you don't have to dive (into potential ground fire). That however I can confirm. Using auto throttle I also hit bullseye from 6k feet. 14k however fell long, outside of splash damage radius. I don't have an old version to compare. I also tested dive bombing. From 14k it fell long. From 6k it also fell short. Track for 6k attached. FA-18 MT MK-82 Auto Bombing Caucasus 6k feet dive-bombing.trk

That being said, I assume Auto mode also doesn't work by magic and therefore isn't 100% accurate even without wind. What is a reasonable hight at wich a vehicle can be expected to be hit? I feel like 14k may be a bit much to expect that.

I tested as well, on South Atlantic and Caucasus at 6k and 14k each. For some reason mine fell long more often, but never exactly on target. Although sometimes within splash damage radius. All tests on MT version FA-18 MT MK-82 Auto Bombing test South Atlantik 14k feet.trk FA-18 MT MK-82 Auto Bombing test South Atlantik 6k feet.trk FA-18 MT MK-82 Auto Bombing test Caucasus 14k feet.trk FA-18 MT MK-82 Auto Bombing test Caucasus 6k feet.trk